Live installer USB: "ERROR: Device '<label>' not found" right after the bootloader
Issue 8454 is real and the replug workaround is exactly what the reporter confirms. But the issue's own quoted cmdline uses archisosearchuuid= and waits on /dev/disk/by-uuid. Current archiso replaced archisolabel= with archisosearchuuid=/archisosearchfilename=, so the suggested archisolabel=<LABEL> line is obsolete and will not be honoured. copytoram is also the wrong tool for this failure: copytoram runs *after* the medium is located, so it cannot rescue a device that is never found. It helps only once boot already works. And dd of=/dev/sdX is offered with no instruction to confirm the target, which is the classic way to overwrite the wrong disk.
dd of=/dev/sdX will destroy everything on whatever device you name. Confirm the target with lsblk immediately before running it, and never point it at a partition (/dev/sdX1) or at your system disk.
Symptom
Booting the Omarchy/Arch installer USB, the bootloader loads the kernel and then the initramfs cannot find the medium it just came from:
:: running hook [archiso]
Waiting 30 seconds for device /dev/disk/by-label/2026-08-25-11-17-12-00 ...
ERROR: Device '2026-08-25-11-17-12-00' not found. Skipping fsck.
You are now being dropped into an emergency shell.
Keyboard input in that shell is sluggish and drops characters. Reported on a ThinkPad T14 (basecamp/omarchy#8454).
Cause
A USB/xHCI enumeration handoff problem between the firmware and the kernel: the stick is present to the bootloader, but after the kernel takes over the xHCI controller the device is either not re-enumerated or is not present under /dev/disk/by-uuid in time, so the archiso hook's search for the boot medium times out. Current archiso locates the medium by archisosearchuuid=/archisosearchfilename= (the older archisolabel= label search is gone), so the wait is on the by-uuid symlink appearing. The image itself is fine.
Fix
**Verified workaround**: physically unplug and re-plug the USB stick as soon as the bootloader has handed off to the kernel (the moment the 'Waiting N seconds for device' line appears). The device re-enumerates and boot proceeds.
If it already dropped to the shell, re-plug and then:
blkid # confirm the medium is now visible
exit # returns control to the archiso hook, which retries
**Other things worth trying, in order:**
- Use a different physical port. Prefer USB-A 2.0 over USB-C/Thunderbolt on affected machines.
- At the boot menu press
eand lengthen the initramfs device wait: appendrootdelay=60to the kernel line. This is the timeout that produces the 'Waiting N seconds' message. - Do **not** bother with
copytoramfor this failure. It copies the ISO to RAM only *after* the medium has been found, so it cannot help when the device is never detected. (Current archiso also no longer usesarchisolabel=. The parameters arearchisosearchuuid=/archisosearchfilename=, set by the ISO's own boot entries, so do not hand-write them.) - Re-write the stick with
dd. **Confirm the target device first**:of=pointed at the wrong disk destroys it with no prompt and no undo:
lsblk -o NAME,SIZE,MODEL,TRAN,MOUNTPOINTS # identify the USB stick by size/model/TRAN=usb
sudo dd if=omarchy.iso of=/dev/sdX bs=4M status=progress oflag=sync # replace sdX, no partition number
sync
Verify
The installer reaches its menu/desktop without the emergency shell, and lsblk -f inside the live session shows the ISO label on the USB device.