Bug 1236934
| Summary: | efibootmgr: Could not add entry to BootOrder: No such file or directory | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> | ||||||||||
| Component: | efibootmgr | Assignee: | Peter Jones <pjones> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 23 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, pjones, surya_prabhakar, vanmeeuwen+fedora | ||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2015-07-22 16:20:13 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
Chris Murphy
2015-06-30 03:39:01 UTC
Created attachment 1044539 [details]
program.log
Created attachment 1044540 [details]
anaconda.log
Created attachment 1044541 [details]
storage.log
-l specifies the loader name which will be used by the EFI firmware, so the path is local to the EFI partition and uses \ as the directory separator. I don't understand how this is not a bug. I get an error message during the installation, there was a failure here. An NVRAM entry was not set. When I do: efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \\EFI\\fedora\\shim.efi I get the same error message as in the program.log, and there is no NVRAM entry. When I do: efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \\boot\efi\\EFI\\fedora\\shim.efi There is no error, and there is a Fedora entry in NVRAM. Rather: \\boot\\efi\\EFI\\fedora\\shim.efi Fedora 22 program.log command: Running... efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \EFI\fedora\shim.efi BootCurrent: 0000 BootOrder: 0005,0000,0001,0002,0003,0004 Boot0000* Mac Boot Boot0001* Mac Boot Boot0002* EFI DVD/CDROM Boot0003* EFI Hard Drive Boot0004* EFI Internal Shell Boot0005* Fedora Fedora 23 program.log command: Running... efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \EFI\fedora\shim.efi efibootmgr: Could not add entry to BootOrder: No such file or directory Fedora 22 UEFI installation always succeeds. Fedora 23 UEFI installation always hits this error (see screenshot of what I see in Anaconda). And yet this morning this command in the same install environment where it failed for Anaconda, there is no error: # efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \\EFI\\fedora\\shim.efi So I don't know what's going on... Created attachment 1045127 [details]
screenshot anaconda installing boot loader error
*** This bug has been marked as a duplicate of bug 1235323 *** |