Created attachment 350477 [details] /var/log/anaconda.log Description of problem: After upgrading from Fedora 10 to Fedora 11 using the F11 DVD, the machine would no longer boot into Linux: instead, I got the "grub> " prompt. To fix it, I had to use the F11 DVD in rescue mode, then do "chroot /mnt/sysimage; grub-install /dev/sdb". That fixed it. But an ordinary user isn't going to know what to do to fix this. And this bug renders the machine unbootable: a serious issue, as it may mean that a novice user who is upgrading their Fedora installation may no longer know how to get to their data. I've experienced this problem before, in earlier versions. I also see many other Fedora users with similar experiences: see, e.g., bug #44636, #473306, #448255, #450143, #505966. It seems like something with anaconda is not working right. My partitioning scheme is as follows: /dev/sdb1 on /boot type ext3 (251MB) /dev/sdb3 on / type ext3 (271GB) /dev/sda is not used or mounted Both /dev/sda and /dev/sdb are managed by my RAID BIOS, but I have RAID disabled. I did not have any removable storage devices attached when I upgraded from DVD. Anaconda correctly found my F11 partition on /dev/sdb and upgraded all of my packages, but failed to do the "grub-install" properly. (Perhaps it did "grub-install /dev/sda" instead of "grub-install /dev/sdb"? Perhaps the "grub-install" failed? I don't know how to tell.) My Smolt profile is: http://www.smolts.org/client/show/pub_06cf7171-6fb1-490f-9e25-0bf86e2dc299 I'll attach /var/log/anaconda.{log,syslog,xlog}. /root/upgrade.log{,.syslog} shows nothing that seems relevant here.
Created attachment 350478 [details] /var/log/anaconda.syslog
Created attachment 350479 [details] /var/log/anaconda.xlog
Same thing here, I burned F11 i586 DVD, booted from it into the installer to upgrade and selected to update boot menu. All went fine and voila, next reboot ended with a system sitting at the 'GRUB' prompt (interestingly, no grub> prompt, but 'GRUB'). I followed the 'grub-install' advice above which made the system boot again (it has networking problems now but this is most probably different problem).
And yes, I upgraded from FC10 (32-bit) to FC11 (32-bit).
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug persists in Fedora 13. See bug #596040.
*** Bug 596040 has been marked as a duplicate of this bug. ***
Created attachment 416920 [details] F13 anaconda.log
Created attachment 416921 [details] F13 anaconda.program.log
Created attachment 416922 [details] F13 anaconda.storage.log
Created attachment 416923 [details] F13 anaconda.syslog
Created attachment 416924 [details] F13 anaconda.xlog
Created attachment 416925 [details] F13 anaconda.yum.log
Created attachment 416926 [details] F13 /root/upgrade.log
Created attachment 416927 [details] F13 /root/upgrade.log.syslog
I've attached /var/log/anaconda*log and /root/upgrade.log*. The relevant ones are marked "F13"; the other attachments are very old and relate to older versions of Fedora. (These log files were requested in bug #596040, where I reported that after upgrading from F12 to F13 using the install DVD, the system would no longer boot and instead gave a grub prompt. On that bug report, I was requested to attach these files to this bug report. I have two hard drives on my system; F13 is installed on /dev/sdb. /dev/sda is an old hard disk that may be failing, contains remnants from an old Linux install, and is no longer used. As mentioned in that bug report, I'm not the only one experiencing this error condition: e.g., http://lists.fedoraproject.org/pipermail/users/2010-May/373041.html ) Comments on the log above: Here is the procedure I used to upgrade F12. I burned a F13 x86_64 install DVD, booted from that DVD, upgraded my system, rebooted, and got the grub prompt. After getting the grub prompt, I rebooted from the DVD using the rescue disk functionality. (I had to try the rescue disk functionality several times. The first time, when the text-mode rescue functionality got to the point of searching for storage devices, it appeared to hang for a very long time, so I used Alt-F2 to go to a separate text console, and run "top" at the shell prompt"; I discovered a "dumpe2fs /dev/sda" process taking a long time. After a while, I gave up, rebooted, went back to the rescue disk functionality, then when it hung, went to a separate text console and used kill -1 to kill the dump2efs processes that were taking a long time. At that point the rescue functionality succeeded and I could do a "chroot /mnt/sysimage" and a "grub-install /dev/sdb" successfully. I'm guessing this is a separate irrelevant bug. I mention this only in case it is relevant, and because it is possible the logs have been polluted with entries from subsequent attempts to use the rescue functionality.)
I just upgraded from Fedora 13 to Fedora 14 using the install DVD, and encountered this problem yet again. It's still present in F14. The machine would not boot after upgrading to F14. After upgrading to F14, I got the grub> prompt, and no way to boot. I had to go to rescue mode, chroot /mnt/sysimage, and do grub-install /dev/sdb. By now, I know the drill, but an average user would be totally screwed at this point, so this is user-unfriendly behavior from the installer. Somehow I can't believe I'm the only one running into this. This bug has been present for the last 4 releases. I'm losing hope that this will ever be fixed. Is there any information I can provide to help debug it?
Could you attach all the install logs from F14 as well? I see the following in the F13 program log: 20:43:51,066 INFO program: grub> root (hd0,0) 20:43:51,067 INFO program: Filesystem type is ext2fs, partition type 0x83 20:43:51,067 INFO program: grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd0,0)/grub/grub.conf 20:43:51,067 INFO program: 20:43:51,067 INFO program: Error 15: File not found 20:43:51,068 INFO program: grub> Which indicates that it is having trouble figuring out that hd1 is where the bootloader and /boot partition are.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping