Red Hat Bugzilla – Bug 49860
installation of grub boot loader onto partition doesn't mark partition active
Last modified: 2007-04-18 12:35:06 EDT
text or gui install, updates 07192001
using either install method, I told anaconda to install grub onto /dev/hda2
on a machine where hda1 was the bootable partition. anaconda installed
grub onto hda2 but didn't also make hda2 bootable, so the grub install
never came up.
Boot loader installation should at least check that the partition is
active, and warn if it is not, when installing to a partition.
Anaconda folks, does this represent a regression (w.r.t. the past behavior of
lilo)? If so, please let me know so I can mark this bug as should- or must-fix.
Yes, I've seen this behavior on Tammy's test machine. This should be a must-fix.
The bug's actually even worse than I thought. Here's my setup:
/dev/hda1 -- win2k (active partition)
/dev/hda2 -- /
grub is installed in /dev/hda2. After installing Fairfax, I manually make
/dev/hda2 the active partition. At that point, boots get me to the grub menu
like I should.
Now I boot linux. When I power off and boot back up, I still get grub.
Now I boot win2k. When I power off and boot back up, I go straight into win2k.
I never get the grub bootloader.
lilo never had these issues when installed on /dev/hda2 on this same machine.
Seems like a similar issue has already been addressed. Does this ring a bell Jeremy?
this is already fixed in beta3