Bug 1051632

Summary: F20 x86_64 EFI installation, os prober creates non-efi entries in grub.cfg
Product: [Fedora] Fedora Reporter: Keith Dixon <kldixon>
Component: os-proberAssignee: Hedayat Vatankhah <hedayatv>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bcl, dennis, gczarcinski, hedayatv, kldixon, mads, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-18 08:17:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1108344    
Bug Blocks: 1108296    
Attachments:
Description Flags
Bodged grub.cfg
none
anaconda log
none
anaconda log
none
anaconda.log
none
anaconda.packaging.log
none
anaconda.program.log
none
anaconda.storage.log
none
anaconda.xlog
none
syslog none

Description Keith Dixon 2014-01-10 18:26:38 UTC 
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:
Comment 1 Brian Lane 2014-01-13 17:01:16 UTC 
Please attach grub.cfg and the installer logs from /var/log/anaconda/ as individual text/plain attachments.
Comment 2 Keith Dixon 2014-01-13 18:06:44 UTC 
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.
Comment 3 Keith Dixon 2014-01-13 18:12:20 UTC 
Created attachment 849518 [details]
anaconda log
Comment 4 Keith Dixon 2014-01-13 18:13:11 UTC 
Created attachment 849519 [details]
anaconda log
Comment 5 Keith Dixon 2014-01-13 18:14:21 UTC 
Created attachment 849520 [details]
anaconda.log
Comment 6 Keith Dixon 2014-01-13 18:15:14 UTC 
Created attachment 849521 [details]
anaconda.packaging.log
Comment 7 Keith Dixon 2014-01-13 18:16:21 UTC 
Created attachment 849522 [details]
anaconda.program.log
Comment 8 Keith Dixon 2014-01-13 18:17:15 UTC 
Created attachment 849524 [details]
anaconda.storage.log
Comment 9 Keith Dixon 2014-01-13 18:17:47 UTC 
Created attachment 849525 [details]
anaconda.xlog
Comment 10 Keith Dixon 2014-01-13 18:19:40 UTC 
Created attachment 849526 [details]
syslog

And there is an empty ks-script-P2mHH3.log
Comment 11 Hedayat Vatankhah 2014-06-02 19:59:35 UTC 
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).
Comment 12 Hedayat Vatankhah 2014-06-18 08:17:51 UTC 
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 ***