OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel critical very-common DISPUTE

Free space on a full /boot or ESP when kernel installs fail

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

Diagnosis and the du/df triage are fine, and the rm commands are correctly targeted (no rm -rf on a system path). But it tells the user to delete the fallback initramfs and disable the fallback preset with no warning that the fallback image is precisely the recovery path record [1] depends on. After this change, a broken default initramfs leaves no way in except a live USB. It also omits that /etc/mkinitcpio.d/*.preset is a pacman backup file, so the edit reappears as a .pacnew, and on Omarchy/UKI setups the ESP consumer is limine-entry-tool's UKIs, not the plain preset images.

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

Deleting the wrong file in /boot (a vmlinuz or initramfs for a kernel you still use) makes the system unbootable. Removing the fallback image removes your rescue option. Repartitioning the ESP risks total data loss. Take a full backup first, and never reboot with a half-written kernel: always re-run pacman -S linux and confirm both vmlinuz and initramfs exist before rebooting.

Symptom

pacman -Syu fails part-way through a kernel update and the machine may not survive the next reboot:


install: cannot create regular file '/boot/vmlinuz-linux': No space left on device
==> ERROR: failed to install kernel to /boot

or on kernel-install/dracut systems:


install: Errors when writing '/efi/<machine-id>/6.9.1-zen1-1-zen/linux': No more storage space available on the device

df -h /boot shows 100% used. Typical on 300 to 512 MB EFI System Partitions.

Cause

The ESP is mounted at /boot (or /efi) and holds one kernel + one initramfs + one *fallback* initramfs per installed kernel. Fallback images are 100 to 300 MB each. Add NVIDIA/DKMS modules or a UKI layout and a 512 MB ESP fills after two or three kernels. Old images from removed kernels are never cleaned up automatically.

Fix

Triage first:


df -h /boot
sudo du -xh --max-depth=2 /boot | sort -h | tail -20
ls -la /boot
pacman -Q | grep -E '^linux'      # what kernels are actually installed

Delete only images whose kernel package is gone:


sudo rm /boot/vmlinuz-linux-zen /boot/initramfs-linux-zen.img /boot/initramfs-linux-zen-fallback.img
sudo mkinitcpio -P
sudo pacman -S linux              # re-run the kernel install that failed

That is usually enough. **Only if it is not**, disable fallback generation, and understand the trade-off first: the fallback image is your recovery entry when a default initramfs is built wrong. Install linux-lts as a replacement escape hatch *before* removing it.


sudo pacman -S linux-lts          # keep a second bootable kernel
sudoedit /etc/mkinitcpio.d/linux.preset

PRESETS=('default')
default_image="/boot/initramfs-linux.img"
#fallback_image="/boot/initramfs-linux-fallback.img"
#fallback_options="-S autodetect"

This file is a pacman backup file: after a linux upgrade check for /etc/mkinitcpio.d/linux.preset.pacnew and re-apply.


sudo rm -f /boot/initramfs-linux-fallback.img
sudo mkinitcpio -P

On Omarchy/Limine the ESP is filled by UKIs written by limine-entry-tool, not by these presets. Prune old kernels and rebuild with sudo limine-mkinitcpio instead.

Dropping nvidia nvidia_modeset nvidia_uvm nvidia_drm from MODULES=() saves space but disables early KMS (expect a flicker/console-mode change at boot).

The real fix is a 1 to 2 GB ESP, which means repartitioning from a live USB (back up first), then reinstalling the bootloader and rebuilding images.

Verify

df -h /boot shows healthy free space, sudo pacman -S linux completes cleanly, and the machine reboots into the new kernel.

Sources

esp-boot-partition-full-no-space