Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1093316

Summary: RHEL7 installation into exisitng Fedora 20 UEFI system bungles up boot
Product: Red Hat Enterprise Linux 7 Reporter: Harish Pillay <h.pillay>
Component: os-proberAssignee: Peter Jones <pjones>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: pholica, redhat-bugzilla, riehecky, toracat
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-13 16:55: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:
Attachments:
Description Flags
the grub.cfg file in /boot/efi/EFI/fedora
none
the grub.cfg file in /boot/efi/EFI/redhat none

Description Harish Pillay 2014-05-01 11:01:41 UTC
Created attachment 891447 [details]
the grub.cfg file in /boot/efi/EFI/fedora

Description of problem:
Existing UEFI enabled laptop has Fedora 20 installed. An empty partition was then targetted for installation of RHEL 7 RC. Installation of RHEL 7 went well. Upon reboot, the boot options show RHEL 7 RC and Fedora 20. But choosing Fedora 20 fails to boot it up with error.


Version-Release number of selected component (if applicable):
RHEL 7 RC

How reproducible:
Install into new partition of a system that has already got Fedora 20 installed.
Upon completion, rebooting and choosing Fedora 20, the boot fails saying: 

"error: can't find command: `linux'.
 error: can't find command: `initrd'.

press any key to continue."

Steps to Reproduce:
1. Previously installed Fedora 20
2. Into empty partition, install RHEL 7 RC
3. Reboot and only RHEL 7 boots, not the Fedora 20.

Actual results:

RHEL 7 boots up successfully but Fedora 20 can't.


Expected results:

Should be able to choose either OSes to boot up. They are kept entirely in different partitions.


Additional info:

see attached grub.cfg files from both /boot/efi/EFI/redhat/grub.cfg and /boot/efi/EFI/fedora/grub.cfg

Comment 1 Harish Pillay 2014-05-01 11:02:40 UTC
Created attachment 891448 [details]
the grub.cfg file in /boot/efi/EFI/redhat

Comment 2 Harish Pillay 2014-05-01 11:03:50 UTC
I am hoping that this is an anaconda issue.

Comment 3 Harish Pillay 2014-05-01 11:05:32 UTC
In the redhat-grub.cfg I commented out the section for Fedora and added the section that I think is supposed to work that I extracted from the fedora-grub.cfg file.

Comment 5 Brian Lane 2014-05-06 00:06:50 UTC
Those entries come from os-prober which didn't use linuxefi and initrdefi like it should have.

Comment 6 Harish Pillay 2014-05-06 00:36:54 UTC
Thanks for that. 

What should I edit in the /boot/efi/EFI/redhat/grub.cfg then to allow for the Fedora 20 instance to boot successfully?

Comment 7 Akemi Yagi 2014-06-22 16:38:35 UTC
(In reply to bcl from comment #5)
> Those entries come from os-prober which didn't use linuxefi and initrdefi
> like it should have.

I hit the same issue. In my test case, I first installed RHEL 7GA (let's call it el7-1) and then installed the same RHEL 7GA (el7-2) as if it is a dual-boot system. Upon installation of el7-2, el7-1 was sent to the os-prober section and now has linux/initrd instead of linuxefi/initrdefi. 

If I manually append the 'efi' by editing the respective lines during booting, el7-1 boots fine.

Is this bug being taken care of?

Comment 9 Dave Cantrell 2015-03-13 16:51:38 UTC
Not an elegant way to solve this as we have to patch the RHEL-7 tools to understand and keep track of foreign OS installs.  Where foreign is defined as really anything past Fedora 19 as that what version of Fedora we branched RHEL-7 work from.

This is an issue best resolved with specific documentation for the multiboot setups in question.

Comment 10 RHEL Program Management 2015-03-13 16:55:51 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.