You are not logged in.
I have a dual-boot system with WIndows 10 and Arch. Both are using UEFI boot with an ESP partition. I used efibootmgr according to the EFISTUB wiki article to add Arch as a boot option. This works perfectly fine, with the output from efibootmgr being:
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0002
Boot0000* Arch Linux
Boot0002* Windows Boot ManagerI am trying to add a third EFI boot option to load memtest86. I installed the memtest86-efi package from AUR. I copy it onto the EFI partition. The EFI partition is mounted at /boot, with the full path to the memtest .efi file "/boot/EFI/memtest86/memtestx64.efi".
I run the efibootmgr command to add the boot option. It tells me there is "No space left on device":
[root@arch boot]# efibootmgr -c -L "MEMTEST86" -l "EFI\memtest86\memtestx64.efi" --verbose --disk /dev/nvme0n1 --part 1
Could not prepare Boot variable: No space left on deviceBut this is completely wrong. There is more than enough space left on the device:
df -h
Filesystem Size Used Avail Use% Mounted on
dev 7.8G 0 7.8G 0% /dev
run 7.9G 1.5M 7.9G 1% /run
/dev/nvme0n1p5 435G 332G 81G 81% /
tmpfs 7.9G 916K 7.9G 1% /dev/shm
tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup
tmpfs 7.9G 4.0K 7.9G 1% /tmp
/dev/nvme0n1p1 96M 47M 50M 49% /boot
tmpfs 1.6G 80K 1.6G 1% /run/user/10001So how do i fix this?
Offline
Weird and confusing, those entries are in the mobo methinks, so the issue would be in the mobo, weird UEFI thingy in mobo only likes 2 entries?
Anyways, why not a bootloader, only one and does the job, throw it on fallback place and it’s failsafe to UEFI derp...
Offline
Could not prepare Boot variable: No space left on device
I don't think efibootmgr is referring to the amount of space of your EFI partition but the space in your NVRAM.
Refer to the Troubleshooting of the EFISTUB wiki.
Offline