From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; SunOS 5.7 sun4u)
Description of problem:
Attempted to install grub to mbr of /dev/hdb because I use Partition Magic
5.0/BootMagic as a primary loader. MBR's of both /dev/hdb and /dev/sdb
were corrupted and those installations could not be booted afterwards.
Steps to Reproduce:
1. On a machine with 2 IDE drives (hda, hdb) and 2 scsi hdd's (sda, sdb),
having different OS installations on each drive, install to /dev/hdb.
Partition Magic/Bootmagic is installed in /dev/hda, Win 98.
2. During boot loader install step, select grub, install to MBR of
3. After reboot unable to boot either /dev/hdb or /dev/sdb.
Actual Results: see above
Expected Results: a bootable system.
It was quite interesting that the first drive in each chain (IDE/SCSI) was
not affected, but the second drive in each chain was corrupted. I
reinstalled, using lilo, and all was well.
This defect considered SHOULD-FIX for Fairfax.
Did you select to install to the MBR or the partition? The MBR exists in one
place, the beginning of the first drive on the system. What does the created
grub.conf look like? (preferably from beta3, but earlier will work as well...
config files for both lilo and grub should be created in beta2+)
Am quite aware of difference between installing to the MBR on /dev/hda versus
installing to the partition. At this point I've not been able to get installed,
so can't view the grub.conf.
Have been on vacation, so didn't get this message till this morning. Will try
reinstalling Beta 2 (all I currently have available) again tonight and make a
boot disk. Will send the conf then and/or report what happens.
Right, but this is why I'm confused as to installing to /dev/hdb... that
shouldn't ever be offered as an option, just the main mbr which would be
/dev/hda or /dev/hdb1
Have you tried again with a more recent beta?
problem continues in Roswell Cut 2 with slightly different behaviour. Current
behaviour on my desktop system is that installing grub to mbr of the root
partition results in getting the line "grub grub" after reboot, and am unable
to boot system into that installation.
If I duplicate the same install, but use lilo installed to the root partition,
all works correctly.
On a system with a different mix of controllers/drives/software this does not
occur. I have detailed system reports if you would like to have them.
What type of motherboard/BIOS? Is the install above the 1024th cylinder (thus
would it be triggering use of the LBA32 behavior)?
Motherboard is ASUS CUBX with flipchip PIII/733MHz CPU. BIOS has not been
upgraded recently, not sure of the current version. Installation is on
/dev/hdb, with boot on /dev/hdb1. Yes, larger drive, but definately boot is in
first 1024. Am sending full system report to katz & glen to insure complete
Is this any better with the grub in Hampton?
Closing due to inactivity; please reopen if you have further infomration to add