-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-10.0, rhel-10.1, rhel-10.2
-
None
-
None
-
None
-
ZStream
-
1
-
rhel-bootloader
-
3
-
False
-
False
-
-
None
-
Bootloader Sprint 2026.4
-
Regression Exception
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
x86_64
-
None
Cannot change the state of not last boot entry in order to active or deactivate this boot entry.
# efibootmgr
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,0002,0000,0001
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Boot0002* UEFI Misc Device PciRoot(0x0)/Pci(0x2,0x3)/Pci(0x0,0x0){auto_created_boot_option}
Boot0003 EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Boot0004* AlmaLinux HD(1,GPT,0f25fa15-39ea-4a66-b45d-4011512ef886,0x800,0x12c000)/\EFI\almalinux\shimx64.efi
efibootmgr -a -b 0003
efibootmgr: Boot entry 3 not found
Could not set active state for Boot0003: No such file or directory
Expected results
The specified entry has been activated / deactivated.
Actual results
efibootmgr: Boot entry 3 not found
Could not set active state for Boot0003: No such file or directory
NB
The issue was reported on GitHub in 2023 - Could not set active state.
It was fixed in upstream in commit 3eac27c5; however, the latest version of efibootmgr was in 2022 and the issue is still present on RHEL 10.
Can a newer version of efibootmgr be released, and addresses this long-standing issue?
