Description of problem: I have just installed F20 on an EFI based machine with an existing F19 installation. OS prober created entries in /boot/efi/EFI/fedora/grub.cfg for F19 containing linux and initrd instead of linuxefi and initrdefi. In passing, it also used device names for root rather than UUID Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Please attach grub.cfg and the installer logs from /var/log/anaconda/ as individual text/plain attachments.
Created attachment 849516 [details] Bodged grub.cfg Sorry, but you are going to have to trust me on this one. :-) I knew I should have saved that file but I have edited it twice since installation. The grub.cfg.orig I am attaching has had the first edits removed by hand from the the backup of the second edit, as best as I remember them.
Created attachment 849518 [details] anaconda log
Created attachment 849519 [details] anaconda log
Created attachment 849520 [details] anaconda.log
Created attachment 849521 [details] anaconda.packaging.log
Created attachment 849522 [details] anaconda.program.log
Created attachment 849524 [details] anaconda.storage.log
Created attachment 849525 [details] anaconda.xlog
Created attachment 849526 [details] syslog And there is an empty ks-script-P2mHH3.log
Neither os-prober, nor grub2-mkconfig scripts have anticipated this case. I'll fix the os-prober part and create a bug for grub2 (or update this bug accordingly).
While the os-prober part will be fixed soon, this bug is more likely to be a grub2-only bug since when grub is generating these entries using os-prober output, it knows that it should generate entries for EFI booting so it can generate entries with linuxefi/initrdefi instead. And finally, this bug is a duplicate! *** This bug has been marked as a duplicate of bug 964828 ***