Red Hat Bugzilla – Bug 448132
F9 kernel 2.6.25.3-18 update broke grub.conf
Last modified: 2008-06-02 10:44:20 EDT
Description of problem: When updating the newly-upgraded (F8->F9) Fedora 9 system (kernel 2.6.25-14) with 'yum update' in my dual-boot (Win XP & Fedora) x86_64 desktop box to kernel 2.6.25.3-18 and rebooting, the boot process stopped at a stage where only the word "GRUB" was displayed on screen and the system loudspeaker kept on playing 'error' sounds. Ctrl-Alt-Del was able to stop that and reboot, but I never got past the "GRUB" stage. Neither of the OS'es could be booted. Version-Release number of selected component (if applicable): I don't know. What is the anaconda version on the F9 DVD? How reproducible: Hard to say. This may be a hardware-specific problem or the result of upgrade instead of clean install. It has happened to one other reporter on fedora-list at least. Steps to Reproduce: 1. Upgrade F8->F9 on an x86_64 platform 2. Update kernel from 2.6.25-14 to 2.6.25.3-18 3. Actual results: Booting stops at "GRUB" and rings system loudspeaker Expected results: Boot continues to a fully operational F9 system Additional info: I used the F9 DVD and its "Rescue" option. Checking grub.conf revealed that (probably) anaconda had rewritten grub.conf to contain lines such as: kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet instead of the expected: kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet I replaced the "UUID=..." with "/dev/VolGroup00/LogVol00" using vi and rebooted. Now both OS's *can* be booted but I wonder why my UUID ended up in grub.conf. I can't figure out how it could be useful to GRUB.
I forgot to mention that *before* editing grub.conf I ran grub-install. I'm not absolutely sure whether I tried rebooting after running grub-install but I probably did - to no avail. However, after editing grub.conf and rebooting, everything seemed to be OK.
*** This bug has been marked as a duplicate of 446362 ***