Boot the fallback initramfs and rebuild after a bad mkinitcpio run
Checked on this machine (omarchy-settings 4.0.2-1, limine-mkinitcpio-hook 1.37.1-1, mkinitcpio 41.1-1) whether a fallback initramfs or fallback boot entry exists at all. It does not. /usr/share/libalpm/scripts/limine-mkinitcpio-install builds the fallback UKI only when MKINITCPIO_FALLBACK is yes or the kernel name, and otherwise calls remove_uki_if_present on the fallback path. MKINITCPIO_FALLBACK is commented out in /etc/limine-entry-tool.conf, absent from all three /etc/limine-entry-tool.d drop-ins (omarchy-defaults.conf, omarchy-uki.conf, resume.conf), absent from /etc/default/limine, and absent from the same two drop-ins in the basecamp/omarchy quattro tree. The record's symptom (the fallback entry boots fine) therefore cannot happen on a stock Omarchy 4, and its verify step names /boot/initramfs-linux.img and /boot/initramfs-linux-fallback.img, neither of which Omarchy 4 produces, since ENABLE_UKI=yes and CUSTOM_UKI_NAME=omarchy give /boot/EFI/Linux/omarchy_linux.efi. /etc/mkinitcpio.d is empty here because limine-mkinitcpio-hook ships /etc/pacman.d/hooks/90-mkinitcpio-install.hook, which shadows mkinitcpio's own hook of that name and never runs generate_presets, so the record's sudo mkinitcpio -P dies with 'No presets found in /etc/mkinitcpio.d' (mkinitcpio line 986) and the -g /boot/initramfs-linux.img form writes a file no Limine entry references. The limine-mkinitcpio line the record already has is the right Omarchy command and was confirmed against /usr/bin/limine-mkinitcpio and /usr/bin/limine-update. On plain Arch the mkinitcpio CHANGELOG (v40, 2025-11-04) says the default kernel preset no longer includes the fallback image, confirmed by PRESETS=('default') in /usr/share/mkinitcpio/hook.preset on 41.1, so the fallback entry now exists only on installs whose preset predates that or was edited. The cited EndeavourOS thread (March 2023, GRUB, encrypt hook) does support the plain-Arch symptom and the fallback-then-rebuild fix. The cited omarchy issue 8319 does not support anything in the record: it is a start-hyprland 'bad json' failure traced by the triage comment to a stale /usr/local/bin/start-hyprland, the reporter's initramfs hypothesis was ruled out there, and nobody in it booted a fallback. Not exercised: booting a Limine snapshot entry, running limine-mkinitcpio with MKINITCPIO_FALLBACK=yes, and the arch-chroot path. The fallback UKI name and the linux-fallback entry name in the corrected fix are read from set_kernel_context and process_uki_kernel in the hook script, not observed on disk.
On plain Arch do not delete the fallback image to save space until the default image is confirmed working. The fallback is often the only thing standing between you and a live-USB rescue. On Omarchy 4 there is no fallback image to keep, and mkinitcpio -P or mkinitcpio -g there can report success while the broken UKI at /boot/EFI/Linux/omarchy_linux.efi is untouched. MKINITCPIO_FALLBACK=yes costs ESP space, and the template's own note says especially so when keeping multiple snapshots.
Symptom
Right after a kernel or system update the normal boot entry drops to an emergency shell or hangs. On plain Arch with a preset that still builds a fallback image, selecting the *fallback* entry in the boot menu boots fine. On Omarchy 4 the Limine menu has no fallback entry, only the normal Omarchy entry and the Snapshots submenu, so the first sign is the normal entry failing with nothing else to pick except a snapshot. Users report this most often on encrypted Btrfs roots after a kernel bump.
Cause
The default initramfs is built with the autodetect hook, which strips out every module the running system was not using at build time. If mkinitcpio ran in a degraded environment (chroot without the real hardware, a full /boot, an interrupted upgrade), the resulting default image is missing the modules needed for your root device. A fallback image is built with -S autodetect, so it still contains everything.
Whether a fallback exists depends on the distro. On plain Arch it is built only if the kernel's preset lists it, and mkinitcpio 40 (2025-11-04) removed fallback from the default preset template, so an /etc/mkinitcpio.d/linux.preset from an older install still has PRESETS=('default' 'fallback') while a newer one has PRESETS=('default') alone.
On Omarchy 4 the initramfs is not built from presets at all. limine-mkinitcpio-hook replaces mkinitcpio's pacman hook, /etc/mkinitcpio.d stays empty, and /usr/share/libalpm/scripts/limine-mkinitcpio-install builds one UKI per kernel at /boot/EFI/Linux/omarchy_linux.efi. It builds a fallback UKI only when MKINITCPIO_FALLBACK is yes or the kernel name, and Omarchy sets that nowhere: not in /etc/limine-entry-tool.conf, not in /etc/limine-entry-tool.d/omarchy-defaults.conf or omarchy-uki.conf, not in /etc/default/limine. With it unset the hook deletes any fallback UKI it finds. A stock Omarchy 4 has no fallback initramfs to boot.
Fix
**Omarchy 4 (Limine + UKI)**
There is no fallback entry to pick. Get to a working root first, either way:
- In the Limine menu open
Snapshotsand boot the newest snapshot taken before the update.omarchy updatetakes a snapper snapshot before upgrading andlimine-snapper-synclists them in the menu. - Or boot the Omarchy ISO, unlock and mount the root subvolume at
/mnt, mount the ESP at/mnt/boot, andarch-chroot /mnt.
Then rebuild the UKI and its Limine entry:
sudo limine-mkinitcpio
Watch the output for ==> ERROR, ==> WARNING: errors were encountered during the build, or mkinitcpio failed for kernel ..., skipping from the hook, which means the old UKI was left in place. sudo limine-update does the same and also redeploys the Limine binary.
Do not reach for mkinitcpio -P or mkinitcpio -g /boot/initramfs-linux.img here. /etc/mkinitcpio.d is empty on Omarchy 4, so -P exits with No presets found in /etc/mkinitcpio.d, and -g writes a file no Limine entry references. The /usr/local/bin/mkinitcpio wrapper that limine-mkinitcpio-hook installs prints This does not update Limine boot entries for exactly this reason.
To have a fallback next time, opt in. /etc/default/limine is the user-owned file that overrides every drop-in:
echo 'MKINITCPIO_FALLBACK=yes' | sudo tee -a /etc/default/limine
sudo limine-mkinitcpio
That builds /boot/EFI/Linux/omarchy_linux-fallback.efi with -S autodetect and adds a linux-fallback entry, which BOOT_ORDER="*, *fallback, Snapshots" in omarchy-defaults.conf already sorts after the normal entry.
Check the result with a privileged listing, since /boot is mounted dmask=0077:
sudo ls -l --time-style=long-iso /boot/EFI/Linux/
sudo limine-list
**Plain Arch (preset-driven, any bootloader)**
Boot the fallback entry, then rebuild every preset:
sudo mkinitcpio -P
Watch the output for ==> ERROR or ==> WARNING: errors were encountered during the build. If only one kernel is broken, target it directly:
sudo mkinitcpio -p linux
sudo mkinitcpio -p linux-lts
# or fully manual:
sudo mkinitcpio -k 6.12.10-arch1-1 -g /boot/initramfs-linux.img
If the menu has no fallback entry because the preset was generated by mkinitcpio 40 or later, uncomment PRESETS=('default' 'fallback') and the fallback_image and fallback_options lines in /etc/mkinitcpio.d/linux.preset, then run sudo mkinitcpio -P again. ls -l /boot/initramfs-linux.img /boot/initramfs-linux-fallback.img should show both with a current timestamp.
If the rebuild itself errors, fix the underlying cause first (usually a full /boot, see that record, or a hook referencing a module that no longer exists).
Verify
ls -l /boot/initramfs-linux.img /boot/initramfs-linux-fallback.img shows both files with a current timestamp and a plausible size (tens to hundreds of MB), and the *default* entry boots.
Sources
- https://forum.endeavouros.com/t/solved-boots-into-emergency-shell-after-update-encrypted-root-is-not-mounted/38101
- https://man.archlinux.org/man/mkinitcpio.8
- https://github.com/basecamp/omarchy/issues/8319
- https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/raw/master/CHANGELOG
- https://github.com/basecamp/omarchy/blob/quattro/etc/limine-entry-tool.d/omarchy-defaults.conf
- https://github.com/basecamp/omarchy/blob/quattro/etc/limine-entry-tool.d/omarchy-uki.conf