Alright; I think I've finally made some progress on this. Turns out "Block device required" is really a red herring. It's some random value (15) used in efibootmgr code, for any number of causes for failure. We can't read anything into it.
The real error in indeed "Invalid argument", and very much at the point where things are trying to delete the variable. It's either at deleting the variable itself, or updating BootOrder. Could you please run the following command, so as to give us more information to address this issue? sudo strace -ff efibootmgr -b 0000 -B Could you also run: ls -l /sys/firmware/efi/efivars/ This will give us more information to hopefully fix this issue. It seems like you're also seeing this on a Dell XPS 13 (9343), seemingly with BIOS revision A15. Judging from https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518/comments/32; there's a BIOS A18 available from Dell that might address the issue. Now, I'm not absolutely certain that the new *revision* fixes the issue, but updating the firmware might clear things that would fix this. That's partly why we need the extra information (so please run the commands above before updating BIOS). ** Package changed: grub2-signed (Ubuntu Disco) => efibootmgr (Ubuntu Disco) ** Changed in: efibootmgr (Ubuntu Disco) Status: Triaged => Incomplete ** Summary changed: - Grub2 Failed to install "efibootmgr failed to register the boot entry: Block device required." + [master] Grub2 Failed to install "efibootmgr failed to register the boot entry: Block device required." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805490 Title: [master] Grub2 Failed to install "efibootmgr failed to register the boot entry: Block device required." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efibootmgr/+bug/1805490/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
