Red Hat Bugzilla – Bug 1260999
efibootmgr: EFI variables are not supported on this system.
Last modified: 2015-10-12 07:26:13 EDT
Created attachment 1071303 [details]
Description of problem:
I tried to install F23 Beta TC4 on UEFI machine. The installation went fine until boot loader installation, which failed with error message:
The following error occurred while installing the boot loader. The system will not be bootable. Would you like to ignore this and continue with installation?
failed to set new efi boot target. This is most likely a kernel of firmware bug
Checked dd and livecd-iso-to-disk creation method, occurs on both.
Version-Release number of selected component:
Steps to Reproduce:
1. create installation media usable on UEFI machine
2. boot a do default install
3. boot loader fails to install
This is the relevant part of the log:
14:23:49,005 INFO program: Running... efibootmgr
14:23:49,017 INFO program: efibootmgr: EFI variables are not supported on this system.
14:23:49,017 DEBUG program: Return code: 2
14:23:49,018 INFO program: Running... efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \EFI\fedora\shim.efi
14:23:49,031 INFO program: efibootmgr: EFI variables are not supported on this system.
14:23:49,032 DEBUG program: Return code: 2
However, Lukas forgot to mention that if you switch to VT2 and run "efibootmgr", it prints current boot options just fine. So there seems to be some difference between running it in a VT and anaconda running it inside its process (in a chroot?).
Lukas, can you please test on a different UEFI system as well, and if it happens on both, propose this as a blocker? Thanks.
I just tried it on another machine and it is there, the same error.
Proposed as a Blocker for 23-beta by Fedora user lbrabec using the blocker tracking app because:
I propose this as an Beta blocker using this criterion:
As previously proposed by kparal in https://bugzilla.redhat.com/show_bug.cgi?id=1235323#c10, and because it presumably violates Beta criterion:
Any installation method or process designed to run unattended must do so. There should be no prompts requiring user intervention.
Despite the error alert, the system booted as expected, however, I'm not sure whether it wasn't caused by previous fedora installation and efi fallback.
J.A. Watson reported UEFI boot manager failure to me via email, so I suspect he's hitting this and it's indeed a general issue in anaconda/efibootmgr, not a system-specific firmware problem.
Can you attach the dmesg output? This looks like it may be the same things as bug 1260799.
I also reproduced this in a UEFI VM. +1 blocker for me - fallback will sometimes save us, but not always.
For F24 (F23 is string frozen) we might want to change "will not be bootable" to "may not be bootable" here?
Created attachment 1071442 [details]
dmesg from a UEFI VM reproducer
Here's the 'dmesg' after booting the TC4 installer on a UEFI VM.
Looks like the same thing: the kernel is creating /sys/firmware/efi, but for whatever reason it's not finding the EFI memory map, so /sys/firmware/efi/efivars never gets mounted.
*** This bug has been marked as a duplicate of bug 1260799 ***