F16 Update Kernels fail to boot
awilliam at redhat.com
Wed Aug 24 22:31:03 UTC 2011
On Wed, 2011-08-24 at 18:22 -0400, Andy Lawrence wrote:
> Maybe include --force with grub2-install? WFM.
> YES! That ignored the error, however didn't boot. But, I just
> happened to boot to my bios for another reason and to my surprise I
> saw two possible boot devices (even though I only have one drive)!
> First was the original named "Fedora" from the default DVD install.
> Second (which wasn't there before) was one named just the hard drive
> device name, picking it booted to grub2 and allowed all kernels to
> I'm gonna guess this is still a bug of some sort, but I don't really
> know what or how to report it. Perhaps an EFI BIOS bug?
The fact that GRUB 2 by default won't install to a partition, and will
only do it if you use --force, is known. It's why anaconda can't install
the bootloader to a partition in Alpha. That will be fixed (by using
--force) in Beta. The bug for anaconda is
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
More information about the test