The ESP fills up after the linux-omarchy migration: two kernels plus snapshot copies, and the update checks only /
Confirmed that bin/omarchy-update-requires-free-space is byte-identical on quattro and in /usr/share/omarchy/bin and checks only / against 10 GiB. Confirmed in /usr/share/libalpm/scripts/limine-mkinitcpio-install line 115 that each kernel package gets ${UKI_PREFIX}_${KERNEL_NAME}.efi, with CUSTOM_UKI_NAME="omarchy" and ENABLE_UKI=yes from /etc/limine-entry-tool.d/. It runs from the PostTransaction hook /etc/pacman.d/hooks/90-mkinitcpio-install.hook. LIMIT_USAGE_PERCENT=85 is in /etc/limine-snapper-sync.conf. The limine-snapper-sync README recommends at least 4 GiB, and the Arch wiki ESP page suggests 8 GiB for Limine with Snapper. Issue 13355 supplies the quoted listing, the 280 MB UKI and the unbootable outcome, and issue 11821 supplies the REPLACE_EXISTING trace. Three defects. First, the skipping. string in the verify and danger is printed only when mkinitcpio fails to build the image in a temp directory (lines 202, 231, 244), not when the copy to the ESP runs out of space, so its absence proves nothing. Second, step 4 says a 98-*.conf drop-in is overridden by omarchy-defaults.conf's MAX_SNAPSHOT_ENTRIES=6. The only config paths in the limine-snapper-sync 1.31.0 binary are /etc/limine-snapper-sync.conf and /etc/default/limine, and its README names only those two. So it likely does not read /etc/limine-entry-tool.d at all, and Omarchy's pin of 6 may be inert, which leaves the default auto pruning. That is likely, not confirmed by running it. The advice to use /etc/default/limine stands either way. Third, the listing in 13355 shows UKIs named recovery20260920_* from a second root, which the cause did not explain. Not exercised: no command under /boot was run because it needs root, and no entries were removed.
Never delete files in /boot/EFI/Linux/ or limine_history by hand. Use limine-snapper-remove and package removal, which also update limine.conf. If a kernel update printed an ERROR: from the UKI hook or ran out of space, do not reboot until sudo limine-mkinitcpio finishes without an ERROR: line and sudo ls -lh /boot/EFI/Linux/ shows a full-size UKI for the kernel you boot. The hook's skipping. message covers only a failed image build, not a failed copy to the ESP. Repartitioning the ESP can destroy data.
Symptom
Since the 4.0.4 update df -h /boot keeps climbing. Then one of these: snapshot entries stop appearing in the Limine menu, a kernel update ends with a write error from the UKI hook, or the machine no longer boots its normal entry. omarchy update never warned. A reporter's 2 GB ESP held:
834M /boot/EFI/Linux
280M omarchy_linux.efi
277M recovery20260920_linux-omarchy.efi
277M recovery20260920_linux.efi
277M /boot/<machine-id>/limine_history/omarchy_linux.efi_sha256_...
Cause
With ENABLE_UKI=yes (Omarchy's omarchy-uki.conf) each installed kernel package gets its own UKI in /boot/EFI/Linux/, named omarchy_<package>.efi because Omarchy sets CUSTOM_UKI_NAME="omarchy". The migration keeps stock linux and adds linux-omarchy, so the ESP space needed for current kernels doubles. UKIs written under another name, for example by a recovery root as in issue 13355, stay on the ESP until removed. limine-snapper-sync also stores the kernel files of each snapshot under /boot/<machine-id>/limine_history/, deduplicated by hash, so each distinct kernel version costs another copy. A UKI carrying NVIDIA modules and GPU firmware can exceed 250 MB. limine-snapper-sync stops adding entries at LIMIT_USAGE_PERCENT=85, which still allows the ESP to fill to 85 percent. Omarchy pins MAX_SNAPSHOT_ENTRIES=6 in /etc/limine-entry-tool.d/omarchy-defaults.conf, but limine-snapper-sync 1.31.0 names only /etc/limine-snapper-sync.conf and /etc/default/limine as its config files, so that pin likely does not reach it. omarchy-update-requires-free-space checks only / for 10 GiB (identical in 4.0.4 and quattro). The UKI is written by the 90-mkinitcpio-install hook after the pacman transaction has committed. Issue 11821 traced that limine-entry-tool copies with replace-existing, which unlinks the old UKI first, so running out of space part way through leaves that kernel with no UKI at all.
Fix
**1. See what is using the ESP.** /boot is mounted dmask=0077, so listing it needs root:
df -h /boot
sudo du -h --max-depth=3 /boot | sort -h | tail -15
sudo ls -lhS /boot/EFI/Linux/
limine-snapper-list
sudo limine-snapper-info
A UKI in /boot/EFI/Linux/ that does not start with omarchy_ was written by another root or under an old name. Find out which root wrote it before removing it.
**2. Remove the kernel you do not boot.** If linux-omarchy works on this machine, removing stock linux halves the space taken by current kernels. Follow the record on removing the unused stock kernel, which lists the checks to do first.
**3. Remove old snapshot entries** (the IDs come from limine-snapper-list):
sudo limine-snapper-remove 1..2
**4. Keep fewer entries from now on.** Put the setting in /etc/default/limine. limine-snapper-sync reads that file and /etc/limine-snapper-sync.conf, and it likely ignores /etc/limine-entry-tool.d/, so a drop-in there does not reliably reach it.
sudoedit /etc/default/limine
MAX_SNAPSHOT_ENTRIES=4
If you keep both kernels, the EXCLUDE_SNAPSHOT_ENTRIES setting documented in /etc/limine-snapper-sync.conf can keep the stock kernel out of new snapshot entries. Its patterns match entry names, so EXCLUDE_SNAPSHOT_ENTRIES="linux" should match only the entry named linux. That is untested here, so check sudo limine-entry-tool --tree after the next snapshot.
sudo limine-update
sudo limine-snapper-sync
**5. Before each update until this is fixed upstream**, check the ESP yourself:
df -h /boot # keep free space above the size of your largest UKI plus a margin
The lasting fix is a larger ESP. limine-snapper-sync recommends at least 4 GiB, and Arch suggests 8 GiB when booting Snapper snapshots from Limine. Resizing means repartitioning from a live USB with a full backup.
Verify
df -h /boot shows free space well above one UKI's size. sudo ls -lh /boot/EFI/Linux/ lists a non-empty omarchy_<package>.efi for every installed kernel. sudo limine-entry-tool --tree lists each kernel, and sudo limine-snapper-info reports no missing or corrupt kernels.
Sources
- https://github.com/omacom/omarchy/issues/11821
- https://github.com/omacom/omarchy/issues/13355
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-update-requires-free-space
- https://gitlab.com/Zesko/limine-snapper-sync
- https://gitlab.com/Zesko/limine-entry-tool
- https://wiki.archlinux.org/title/EFI_system_partition