ERROR: device 'dev/sdd1' not found. Skipping fsck.
mount: /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#
I am now greeted with this message after upgrading, and in fact I have that error since the 12th April every time I attempt to upgrade. Fortunately I have a snapshot that I can revert to in order to get the desktop running again.
I am using LXQT-openrc and it is running on a file server with a pair of disks mirrored for the files. The OS is on a separate hard drive.
I was also having the 'nss' error mentioned in another topic, but have successfully overcome that error by following the instructions.
Can anyone give any clues as to why this is happening please?
I don't believe anything particularly important was updated around April 12th. Certainly not openrc at any rate. This seems pretty bad though. Do you feel like figuring out which package leads to your root not mounting (which is something certainly shouldn't happen)?
Make sure in fstab you list which filesystem root is, that would be one thing I'd look at here.
My guess would be, your mkinitcpio.conf isn't properly set for raid or whatever you use.
Thanks for the replies, I will check the /etc/fstab file and see what it says. Report back later.
Also, the linux kernel doesn't guarantee the disk letter order, if 2 or more disks are present; if you're using the /dev/sdX naming scheme, you should consider switching to UUIDs or LABELs.
I have checked the /etc/fstab and it uses UUID for the root file system so I don't think the problem lies with fstab.
Is there any way I can partially upgrade some of the packages to try and narrow down the problem? Or is there anything else I can try please?
Thanks.
My mkinitcpio.conf hasn't been altered at all by me, and was created when the system was installed in February. I have upgraded every couple of days since then without any problems until this arose earlier this month. Nothing has been changed in the raid setup either, it has been running for several years in that configuration.
You could do it manually. See what list of packages comes up in the upgrade in a pacman -Syu, cancel it, and then install them one by one.
Thanks for that, I had already considered doing it that way but wondered if there was an easier way! No worries, I will have a go over the weekend, many thanks.
Edit: Oops, posted in the wrong topic.
Update:
It would appear that it is the Linux kernel upgrade that is causing the problem, so any advice on how to proceed would be very welcome!
Thanks.
Of course not, your error shows before fstab is used; check your grub.cfg (or
cat /proc/cmdline. If you've got a
root=/dev/sdXY line there, edit
/etc/default/grub and change the
GRUB_DISABLE_LINUX_UUID setting to "false".
Thanks for the advice, and even though I didn't appear to have that 'root=/dev/sdXY' line in grub.cfg, I changed the GRUB_DISABLE_LINUX_UUID setting to "false", that did enable me to boot. However, that opened a can of worms with all sorts of problems with applications refusing to open and most importantly no internet connection even though it is a wired device.
So, after spending some time on this I decided to do a reinstall using an updated image from the 'weekly builds' section. After installing and then updating with 'pacman -Syu' I rebooted and all was well. I have been busy both with work and configuring the server to my satisfaction, so have not replied until now, but thanks to all who have offered advice.
I don't really know exactly what the problem was other than an update appeared to change the drive designation of the OS drive from /dev/sdd to /dev/sdc, which resulted in the original error message. Whatever, I am now happy to be up and running properly again!