efibootmgr: Could not set BootOrder: No space left on device after update today

English Install/Boot/Login
1

Having had recent issues with efi booting after any update I check to see what options are set to boot efi. I ran efibootmgr -v as root and got


BootCurrent: 0003
Timeout: 1 seconds
No BootOrder is set; firmware will attempt recovery
Boot0000* opensuse      HD(1,GPT,2eca2750-fed6-4e3f-887f-27f183020fda,0x800,0x61800)/File(\EFI\opensuse\grubx64.efi)
Boot0001* Hard Drive    BBS(HD,,0x0)
Boot0002* CD/DVD Drive  BBS(CDROM,,0x0)

if I run efibootmgr -o 0000,0001,0002 I get

efibootmgr: Could not set BootOrder: No space left on device

as yet I have not rebooted my PC. Has anyone else seen this?

Stuart

2

Hi
The efimanager update returned the -v option. Working fine on my DELL system.

Maybe pop in YaST bootloader and reduce the grub menu time down a second and save so it runs through it’s rebuild routine and see if get the same waring.

3

Do you have a bootable CD or DVD or USB or an earlier version (13.1, 13.2 or Leap 42.1)? The install media should be okay if you don’t have a live system.

If you have, then try running “efibootmgr” from the bootable media. Partcularly, check the “-o” option and see if that can work.

There was a recent update to “efibootmgr” to fix another bug. Possibly a new bug was introduced. Or maybe you have a firmware problem.

I don’t think I’m having a problem here. But on the system where I checked, “efibootmgr -o” doesn’t actually do anything. I have to boot into the firmware settings to change the order.

4

I tried running both update-bootloader --reinit which failed, then grub2-install which failed as well, both I think were trying to use efibootmgr which would not work. I was left with no efi boot options at all in the hardware when I rebooted so I had to boot TW rescue and chroot to the correct disks etc and do the grub2-install from that which worked (I guess becuase it uses efibootmgr from the rescue system) and now I can boot the system once again. There does not seem to be any f/w issues and this is the first time it has been this bad although I have had some issues with recent updates messing up the efi boot options both on my desktop (this system) and my laptop both run TW.

Stuart

5

Then I think you have found a new bug in “efibootmgr”. I suggest that you open a bug report.

https://en.opensuse.org/Submitting_Bug_Reports

6

Bug #996088 created for this issue now.

Stuart

7

Thanks for reporting.

8

This same siution happened again today with the latest set of updates.


# 2017-02-10 10:34:38 Output of grub2-i386-pc-2.02~beta3-19.1.x86_64.rpm %posttrans script:
#     update-bootloader: 2017-02-10 10:34:25 <3> update-bootloader-9754 run_command.274: '/usr/lib/bootloader/grub2-efi/install' failed with exit code 15, output:
#     <<<<<<<<<<<<<<<<
#     target = x86_64-efi
#     + /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg
#     Installing for x86_64-efi platform.
#     Installation finished. No error reported.
#     efibootmgr: Could not delete boot variable: No space left on device
#     >>>>>>>>>>>>>>>>

running grub2-install worked OK having mounted the relevant directories using the TW restore CD. I have updated the bug with this as well.

Stuart