OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel high occasional DISPUTE

UEFI boot entries vanish after every reboot (NVRAM full, or firmware wiping entries)

omarchyarchendeavouroscachyosmanjarouefiliminegrubsystemd-bootlaptopdesktop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The three firmware behaviours, the fallback-path strategy, and every non-Limine command check out (grub-install --removable, bootctl install which does write EFI/BOOT/BOOTX64.EFI, bootctl --no-variables install, efibootmgr --create/-o/-b NNNN -B, clearing dump-* efivars, Lenovo OS Optimized Defaults, and Omarchy's Direct Boot which is documented as refusing to run on American Megatrends and Apple firmware). But the headline command for the target distro is invented: there is no limine-install binary and no --fallback flag anywhere in the limine, limine-entry-tool, limine-mkinitcpio-hook or limine-snapper-sync packages. The limine package ships /usr/share/limine/BOOTX64.EFI and the fallback install is a config switch (ENABLE_LIMINE_FALLBACK), which Omarchy already sets to yes in etc/limine-entry-tool.d/omarchy-defaults.conf. The manual-copy step also invents a source path (/boot/EFI/limine/limine_x64.efi), and the efibootmgr --loader value repeats it.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Deleting the wrong efibootmgr -b NNNN -B entry (Windows Boot Manager on a dual-boot machine) leaves that OS unbootable until you recreate it. Writing to or deleting files under /sys/firmware/efi/efivars has bricked machines with buggy firmware. Remove only dump-* files, never rm -rf the directory. Do not add efi_no_storage_paranoia as a permanent kernel parameter: it disables the safeguard that keeps NVRAM from filling to the point of bricking the board. On a shared ESP, grub-install --removable and bootctl install both overwrite \EFI\BOOT\BOOTX64.EFI, which may currently be another OS's loader.

Symptom

You create a boot entry, efibootmgr -v shows it, everything works, and after one reboot it is gone again, or the firmware boots Windows instead, or you get No bootable device found / Reboot and Select proper Boot device. Sometimes efibootmgr --create fails outright with:


Could not prepare Boot variable: No space left on device

Common on Lenovo ThinkPads (T16 Gen 2 and similar), on boards with CSM enabled, and after running Omarchy's Setup > Direct Boot, which adds an EFI entry the firmware may then discard.

Cause

Three separate firmware behaviours produce the same symptom. (1) NVRAM is full, and some boards silently drop entries instead of erroring. (2) The UEFI spec allows OEMs to do "NVRAM maintenance" at boot: firmware that finds no EFI binary at a hardcoded path concludes the disk has no OS and wipes the entries associated with it. (3) Options such as Lenovo's "OS Optimized Defaults", or a firmware that removes entries pointing at drives absent at POST, delete non-Windows entries on principle. In all three cases NVRAM is the wrong place to rely on, and the removable-media fallback path is the durable answer.

Fix

Everything in the record stands except the Limine steps.

There is no limine-install --fallback. On Omarchy/limine-entry-tool the fallback path is a configuration switch, and Omarchy already ships it enabled:


grep -rn 'ENABLE_LIMINE_FALLBACK' /etc/default/limine /etc/limine-entry-tool.d/
# Omarchy: ENABLE_LIMINE_FALLBACK=yes in /etc/limine-entry-tool.d/omarchy-defaults.conf
sudo limine-update
ls -l /boot/EFI/BOOT/BOOTX64.EFI

If it is unset (plain Arch), add ENABLE_LIMINE_FALLBACK=yes to /etc/default/limine and run sudo limine-update, or place the binary by hand. The source is the one the limine package ships:


sudo mkdir -p /boot/EFI/BOOT
sudo cp /usr/share/limine/BOOTX64.EFI /boot/EFI/BOOT/BOOTX64.EFI

When recreating the NVRAM entry, look at what is actually on the ESP instead of assuming a filename, and point the entry at a path that exists:


ls -R /boot/EFI
sudo efibootmgr --create --disk /dev/nvme0n1 --part 1 \
  --loader '\EFI\BOOT\BOOTX64.EFI' --label 'Limine' --unicode
sudo efibootmgr -o 0001,0000

GRUB, systemd-boot, the NVRAM-full cleanup (efibootmgr -b 0005 -B, rm /sys/firmware/efi/efivars/dump-*, disabling CSM), the Lenovo advice, and the Direct Boot advice are all correct as written.

Verify

efibootmgr -v lists your entry after a reboot. ls -l /boot/EFI/BOOT/BOOTX64.EFI exists. The machine still boots after clearing NVRAM entries or resetting the firmware to defaults.

Sources

uefi-nvram-boot-entries-dropped-use-fallback-path