I booted Anaconda with Fedora-10-Snap3-x86_64-netinst.iso and used a local HTTP server to use the Fedora-10-Snap3-x86_64-DVD.iso as an installation source. I upgraded the existing Fedora 9 install on the hard drive, including selecting the upgrade option for the boot loader. When I rebooted from the hard drive after the installation was complete I got the text "GRUB" in white text on an otherwise blank black screen, and a constant stream of system beeps.
I was able to repair the problem by booting off a LiveUSB, mounting /dev/sda1 on /home/liveuser/hd, and running: grub-install --root-directory=/home/liveuser/hd/ /dev/sda I did save the old files if anyone needs them for diagnostic purposes.
Something very similar happened to me, may or may not be the exact same problem. I used preupgrade to upgrade to Rawhide, from Fedora 9, and used the "update boot loader" option. And after reboot was left in the grub prompt. root (hd0,1) [ where my /boot partition was ] configfile /grub/grub.conf Allowed me to boot normally. I assume running grub-install will fix.
Is the upgraded grub.conf actually correct, and it's just the install on disk that's broken?
For me, running grub-install without adjusting the configuration fixed booting.
Created attachment 322507 [details] Comparing original (broken?) and current working /boot I'm not sure where the problem is; I've attached a diff of /boot between the working and non-working versions. I've since updated the kernel and removed older ones.
Can you attach /var/log/anaconda.log and /var/log/anaconda.syslog to this bug report? Hopefully there's something in there that indicates what went wrong.
Created attachment 322666 [details] anaconda.log
Created attachment 322667 [details] anaconda.syslog As requested.
Updated the bug title to be easier found and reflect the problem.
This is one of those bad bugs that we can't reproduce to even come close to fixing, and we've had it since F8->F9 days. Quite simply if we delayed the release for this we could be waiting for ever. I'm punting this to F10Target.
Is there anything to be done to make the problem easier to diagnose next time it happens?
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This has happened on every computer I've upgraded to F10 from F9 or F8. I run the installer to do the upgrade, then I reboot and log in to finish upgrading the rest of the packages. Then I reboot and get "GRUB" at the top of the screen and nothing else. I boot the rescue mode from the installer, chroot to the installed system and run "grub-install /dev/sda" and everything works from there. The last one I did seems to be slightly different. The upgrade went fine, I rebooted a few times trying to sort out a video card issue. Then I modified the menu.lst file and then rebooting gave me the "GRUB" problem and required running rescue mode as above. I did actually run into this one on a plain F9 system after a large update (not to F10). I did the updates remotely, rebooted, and fortunately I went past the computer a little later and saw the "GRUB" message or there would have been some unhappy users.
Has anyone been able to reproduce this with the F11 pre-releases? There's been major work done regarding partitioning and bootloader installation which makes it a bit difficult to tell if this report is still valid or not.