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.
Description of problem:
When I fresh install RHEL6.9 in UEFI mode, there is no boot entry for RHEL in the NVRAM. So I can't boot into OS successfully.
Version-Release number of selected component (if applicable):
efibootmgr-0.5.4
How reproducible:
Steps to Reproduce:
1. Set BIOS to UEFI mode
2. Fresh install the RHEL6.9
3. Then I cannot boot into OS as there is no boot entry for RHEL6.9
Actual results:
I cannot boot into RHEL6.9 after installation.
Expected results:
Boot into OS normally.
Additional info:
I can boot the OS from BIOS - "Boot from file" or "Add the UEFI boot path manually".
When I boot into OS, I found that there is a boot entry variable Boot0003xxxx which is related to Network devices created by BIOS. It's size is 3.3k large than 1k size limitation.
So I think it's this variable affected the creation of RHEL6.9 boot entry.
But I can't figure out the root cause in the efibootmgr source code.
So I need help from Red Hat.
Hello Lenovo,
Please boot the system in rescue mode. Create and attach a sosreport from this mode.
This this give us the anaconda logs and additional information that will assist in working this issue.
Thank You
Joe Kachuck
(In reply to Joseph Kachuck from comment #5)
> Hello Lenovo,
> Please also confirm is this is the same issue as:
> https://bugzilla.redhat.com/show_bug.cgi?id=1401776
>
> Thank You
> Joe Kachuck
I don't think it is the same issue.
One is boot entry creation problem. The other one is ACPI issue.
I think you may paste a wrong bug number.
Hello Lenovo,
Please boot the system in rescue mode. Create and attach a sosreport from this mode.
This this give us the anaconda logs and additional information that will assist in working this issue.
Thank You
Joe Kachuck
Can you help us understand the detailed OS handling:
1. If Boot#### exist and less than 1K size, BIOS will return EFI_SUCCESS(0)
2. If Boot#### not exist, BIOS will return EFI_NOT_FOUND(0x8000000E)
3. If Boot#### exist and larger than 1K size, BIOS will return EFI_BUFFER_TOO_SMALL(0x80000005)
How do OS handle these 3 cases respectively?
(In reply to Joseph Kachuck from comment #11)
> Hello,
> Due to were are for the RHEL 6.9 release. This will not make RHEL 6.9. This
> is being moved to RHEL 6.10.
>
> Thank You
> Joe Kachuck
Hi Joseph,
Do you mean RHEL 6.10 will introduce the new EFI variable interface - efivarfs?
Hello Lenovo,
Please confirm to correct this issue. It would be required to add a new EFI variable interface? This is something that was not included in RHEL 6.x previously?
At current this is requested for RHEL 6.10.
Thank You
Joe Kachuck
(In reply to Joseph Kachuck from comment #13)
> Hello Lenovo,
> Please confirm to correct this issue. It would be required to add a new EFI
> variable interface? This is something that was not included in RHEL 6.x
> previously?
>
> At current this is requested for RHEL 6.10.
>
> Thank You
> Joe Kachuck
Hi Joseph,
This defect is caused by 1K size limitation of EFI variable.
If there is a boot entry variable large than 1K, the defect will occur.
So the new EFI variable interface - efivarfs should be introduced in kernel.
It would better if it can be fixed in RHEL 6.9.
If there is no possibility to fix this defect in RHEL 6.9, please add the request in 6.10.
Thanks~
The 1KB variable problem had been fixed in previous version.
* Thu Sep 04 2014 Peter Jones <pjones> - 0.5.4-12
- Display UEFI boot variables when the contents are > 1024 bytes
Resolves: rhbz#1121782
Hello,
RHEL 6 has entered Phase 3. In phase 3 only Critical impact Security Advisories and selected Urgent Priority Bug Fix Advisories will be accepted.
https://access.redhat.com/support/policy/updates/errata
At current this BZ does not meet these requirements. I am closing this BZ as WONTFIX.
Please reopen if this fix is required for RHEL 6. If so please also provide a justification for this fix.
Thank You
Joe Kachuck