Hi all.
It's been a while since I've had any issue like this. Luckily I have multiple kernels and both the zen kernel as well as the standard kernel work just fine. I recently was testing out booting into the lts kernel l due to it having a bit better stability with a video game I play and received this message when it attempted to launch udevd:
Starting udevd version 254.5-1-artix
ERROR: device 'UUID=...etc' not found. Skipping fsck.
mount /new_root: can't find UUID=...etc. on real root
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ~]#
And I can't type into the prompt, I'm assumming because udev failed to recognize my keyboard. This only happens on linux-lts, not linux-zen or the standard kernel. Any ideas on how to troubleshoot? I like having multiple kernels in case one fails, but this is one of my backups, so I'd like to take care of this to ensure I have the lts as a failsafe.
As always, thanks in adavance for any advice.
the kernel works fine for me. I don't think it has anything to do with udev, maybe there is a problem with mount UUID.
are you sure the values of the following files:
/etc/fstab
/boot/grub/grub.cfg
are the same with the output of this command
sudo fstabgen -U /
or
sudo lsblk --fs
I checked the cat output of both /etc/fstab as well as /boot/grub/grub.cfg and indeed the UUID both wihtin the fstab file as well as throughout each of the menuentries within the grub.cfg file.
I did not have fstabgen installedd, and I assume you mean genfstab? While both lsblk --fs and genfstab -U gave output about my filesystem (mainly just the standard parition info and in teh case if genfstab, some user id and group id information, there was no info about the UUID if that's what was expected?
Thanks for the insights, but I'm still a bit of a miss. the UUID is correct, but it appears that when I boot the lts kernel and this line of the grub.cfg is run:
search --no-floppy --fs-uuid --set=root $UUID_here...
It doesn't recognize the UUID? But strangely enough both the regular and zen kernels, which have this exact same UUID are recognized and continues to boot and drop me into my usual login tty...
I'm not sure what to make of this, and any other insights you ro anyone else might have would be very appreciated!
I would probably try things like running:
# mkinitcpio -P
# update-grub
(And again later if you make other changes that might affect this.)
Check if there is enough space in your /boot partition if this is separate. Check the uuid that can't be found is actually the correct one, and check /etc/fstab is correct. Also try to boot the full recovery image for lts, presuming you have that enabled. I had something similar when I built a kernel with modprobed-db and missed out the nvme modules, on one laptop with an nvme drive it gave this error, another with an ssd it was fine - if there is some special requirement in terms of file system or drive type, this kind of thing could happen, so try and make sure you have the right modules in the initcpio image. You could also try some older versions of the lts kernel from your package cache or the Artix archive. I guess you are running the latest lts kernel?
If you are using Grub from another partition and install, check the /etc/fstab and /boot/grub/grub.cfg (os-prober can pick up incorrect stuff from an old grub.cfg) are correct in the target partition, and that you have run the above commands there too.
Dang, it was that simple. Thanks. I had forgotten those simple commands. The last time I was using those often was when I first installed multiple kernels and nvidia-dkms. I'm not sure what caused this issue though. Other than running regular updates, I haven't done anything else related to the kernels in over a year now.
Anyways, thanks for your insights. I'm gonna bookmark your comment for later use should I need it. Very much appreciated!