Hide Forgot
Description of problem: After upgrading from F15 to F16, the system boot stops at the grub> prompt. Looking into this further I have discovered that /boot/grub2/grub.cfg is an empty file. I have worked around this by displaying the old grub config file with "cat (hd0,msdos1)/grub/grub.conf" command, and then typing the "linux /vmlinuz-3.1... <arguments from the grub.conf>", then "initrd /initramfs-3.1...", and finally the "boot" command. I have then managed to re-create the grub2 config file using the "grub2-mkconfig -o /boot/grub2/grub.cfg" command from the booted system, and the system now boots correctly. This has to be pretty common problem, because so far I have upgraded four machines from F15 to F16, and on three of them I have ran into this problem. The machines are pretty different to each other - the bug has appeared on the following ones: 1) F15 laptop with encrypted disk; stock grub1 config file as far as I can remember (the system has been originally upgraded from F14) 2) F15 KVM/qemu virtual machine with LVM, but no encryption; serial console in the original grub1 config (clean F15 install) 3) F15 workstation with no encrypted disk or LVM (upgraded from F14, and before it F13, may be earlier versions as well), stock grub.conf The bug has not appeared on 4) F15 laptop with encrypted disk, stock grub1 config, upgraded from F14, F13, F12 and I think even F11. The only difference I can tell is that the laptop 4) was upgraded from Fedora 16 x86_64 DVD (physical DVD disk), while the earlier three were upgraded using Fedora 16 netinst ISO image (virtual disk in case of the virtual machine 2), USB flash disk with install image created by livecd-iso-to-disk from netinst.iso in case of machines 1) and 3)). I think I have a pre-upgrade snapshot of the machine 2), so I can make it available as a .qcow2 file for further testing.
Please attach logs from those mulfunctioning cases (/var/log/anaconda/* files on the upgraded system) as single plain text files. And since I can't reproduce it running F15->F16 upgrade with netinst.iso on my virtual machines, the .qcow2 file for testing and reproducing would be really appreciated.
Do you really want logs as individual files? It is 7 files for each host. In the meantime, I have attached logs from host 1) and 3) from the original report. As for the virtual machine - I am sorry I no longer have the image, and when I tried to reproduce it with a freshly kickstarted f15 VM, I was not able to reproduce the problem. Hope this helps, altough I did not find anything suspicious in anaconda.log. Grub2-install was running, and finished OK according to log files.
Created attachment 549348 [details] tarball with anaconda log files from hosts 1) and 3)
Yes, really, as individual files please. Otherwise we have to download and untar your logs locally to examine them. This can get very tedious when examining the number of bugs we look at every day.
Created attachment 550259 [details] anaconda.log from one of the malfunctioning cases
Created attachment 550260 [details] program.log from one of the malfunctioning cases
Created attachment 550267 [details] program.log from the successful upgrade
Looking at program.log from your malfunctioning cases I have found out that this part between 'yum clean all' and grub2-install (from the successful case) is missing: 12:56:29,989 INFO program: Running... grub2-set-default Fedora Linux, with Linux 3.1.0-7.fc16.x86_64 12:56:30,134 INFO program: Running... grub2-install --no-floppy (hd0) 12:56:34,589 INFO program: Installation finished. No error reported. 12:56:34,611 INFO program: Running... grub2-mkconfig -o /boot/grub2/grub.cfg 12:56:35,937 ERR program: Generating grub.cfg ... 12:56:36,253 ERR program: Found linux image: /boot/vmlinuz-3.1.0-7.fc16.x86_64 12:56:36,284 ERR program: Found initrd image: /boot/initramfs-3.1.0-7.fc16.x86_64.img 12:56:38,299 ERR program: done But for now I have no idea what could happened.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.