Arch Linux

duhan_solo

Member

Registered: 2025-06-04

Posts: 1

[SOLVED] Failure to boot after updating

I've been using arch for a while now. After the most recent update, I turned on my computer and selected arch from the grub menu. Instead of booting I get the following:

ERROR: device 'UUID=...' not found. Skipping fs
ck.
mount: /new_root:can't find UUID=[same uuid as above].
ERROR: Failed to mount 'UUID=[same uuid]' on real root
You are now being dropped into an emergency shell.
sh: can't accesstt; job control turned off
[rootfs ~]# _

I had a USB lying around with Kali on it, so I followed some advice from the internet, booting into Kali, then chroot-ing my usual root directory (which was mounted and accessible) and running 'pacman -S linux'. This time I paid attention and I didn't see any errors thrown by pacman with regard to mkinitcpio. But when I rebooted into arch, I got the same error.

So, I put arch on a USB and booted into that, because it seems like "arch-chroot" is better than "chroot" for these purposes. But the arch USB can't even see my computer's disk. lsblk and fdisk -l only turn up the usb arch is running off of, and loop0. I can't find anything in /dev/ that might be what I want either.

TLDR after updating, arch (even from a fresh live USB) can't find my computer's SSD, even though Kali can. What could the problem be?

Edit: I downgraded my kernel and it works again

Last edited by duhan_solo (2025-06-04 18:46:02)