Bug 39952

Summary: Crashes partiton table
Product: Base System Reporter: John Hawk <johnhawk>
Component: i386Assignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description John Hawk 2002-06-28 16:10:02 UTC
 Copies partion table form harddisk 0 to hardisk1 (ads's)

System and boot:
hd0 3.1 G vfat32 (Windows XP)          /dev/hda1
    6.9 G ext3   (Redhat 7.3)  grub on /dev/hda2
hd1 5   G        (FreeBSD 4.6)         /dev/hdb1
    5   G vfat   (MSDOS)               /dev/hdb2
    10  G ext3   (Mandrake 8.2)grub on /dev/hdb6

All items booted from Windows XP BootMgr
boot.ini
c:\bootsect.os ="Operating System"
created via dd if=/dev/drive of=bootsect.os bs=512 count=1

When FreeBSD 4.6 is booted this way it writes the hd1 partition table to hd0 thus crashing all Operating Systems on hd0

How-To-Repeat:     Set up as above stated the boot into FreeBSD
Comment 1 dschultz 2002-07-06 08:58:19 UTC
You probably have boot0 installed on your second drive.  When
boot0 is configured to save your last choice, it writes a modified
copy of itself to whatever disk the BIOS considers to be the first
one.  Since the boot sector is only 512 bytes, it really isn't
reasonable for boot0 to attempt to detect these sorts of
configuration errors.  Your only boot manager should be on the
master, and you should use it to boot all of your operating
systems.
Comment 2 Jonathan Chen freebsd_committer freebsd_triage 2002-07-19 08:26:32 UTC
State Changed
From-To: open->closed

if you wish to use some other boot manager, you shouldn't be using FreeBSD's as well.  When installing FreeBSD, choose 'Install a standard MBR (no boot manager)'.  You should configure your other boot loader to boot directly to the slice (or partition) instead of the master boot record.