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

Recover from "ERROR: device 'UUID=...' not found" dropping to an initramfs emergency shell

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

Diagnosis and one-boot bootloader edits are correct, but the persistence step is wrong on two loaders. bootctl update only refreshes the systemd-boot EFI binary on the ESP. It does not regenerate or fix boot entries, so a stale root= survives it. And on Omarchy /boot/limine.conf is destroyed on every omarchy-refresh-limine (verified: the script does mv /boot/limine.conf /boot/limine.conf.bak then copies a template), so a root= fixed there is lost at the next update. HOOKS line itself is current and correct.

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

Editing the kernel command line permanently in the wrong place can leave you with no bootable entry at all. Always test the change as a one-off edit in the boot menu first, and never delete the fallback entry until the default entry boots.

Symptom

After a pacman -Syu (or after cloning/resizing/reformatting a disk) the machine no longer boots. Instead of the desktop you get a tiny busybox prompt:


:: running early hook [udev]
ERROR: device 'UUID=6f3c1b2a-...' not found. Skipping fsck.
:: mounting 'UUID=6f3c1b2a-...' on real root
mount: /new_root: can't find UUID=6f3c1b2a-...
ERROR: Failed to mount 'UUID=6f3c1b2a-...' on real root
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#

Cause

The initramfs cannot find the root device the kernel command line told it to mount. Three realistic causes. (a) The UUID in the bootloader's root= parameter no longer matches the filesystem (disk re-created, restored image, new SSD). (b) The initramfs is missing the hooks needed to expose the device (block, or encrypt/sd-encrypt for LUKS, lvm2 for LVM). (c) mkinitcpio failed or was interrupted mid-run and wrote a truncated/incomplete image.

Fix

From the emergency shell, compare what exists against what was asked for:


blkid
cat /proc/cmdline

One-boot menu edit (GRUB: e, fix root=UUID, Ctrl+X / Limine: e, fix cmdline:, Enter / systemd-boot: e, edit appended cmdline).

Once booted, make it permanent:


sudo blkid
sudoedit /etc/fstab
sudo systemctl daemon-reload
sudo mount -a          # must return clean BEFORE you reboot
sudo mkinitcpio -P

Then persist root= in the place your loader actually reads:


# GRUB
sudo grub-mkconfig -o /boot/grub/grub.cfg

# systemd-boot: bootctl update does NOT touch entries. Edit the entry itself:
sudoedit /boot/loader/entries/arch.conf     # fix the `options root=UUID=...` line
sudo bootctl update                          # only refreshes the EFI binary

# Omarchy / Limine: /boot/limine.conf is overwritten by omarchy-refresh-limine.
# The persistent cmdline lives here instead:
sudoedit /etc/default/limine                 # KERNEL_CMDLINE[default]="..."
# or a drop-in: /etc/limine-entry-tool.d/<name>.conf with KERNEL_CMDLINE[default]+=" ..."
sudo limine-mkinitcpio

If you cannot boot at all, use the fallback entry, or repair via chroot from a live USB.

Minimum HOOKS in /etc/mkinitcpio.conf:


HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck)

For LUKS add encrypt (busybox initramfs) or sd-encrypt (systemd initramfs) before filesystems.

Verify

sudo mkinitcpio -P finishes with no ==> ERROR lines, cat /proc/cmdline after reboot shows the correct root UUID, and the system boots to the display manager/Hyprland without touching the boot menu.

Sources

emergency-shell-device-uuid-not-found