this post was submitted on 13 Dec 2023
996 points (99.1% liked)

linuxmemes

20463 readers
580 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 4 points 8 months ago (1 children)

Those are all hardware management services (as far as I can tell), and are configured before the root is mounted.

I have hit this exact error before, that is what failing to mount the root disk looks like. A bunch of services will start, and then you get dropped into a shell (with a login).

If you want to see it for yourself, change /etc/fstab such that /root is now pointing to the wrong device, and then rebuild your initrd. When you reboot you'll see exactly that output. To fix it, login to the shell and mount your root on /new_root, and ctrl-d to continue the boot (from memory it has a message telling you to do that anyway). When your system boots you can fix fstab and rebuild initrd. Its reversable, but maybe test on a machine you dont care about to be safe :)

[โ€“] [email protected] 2 points 8 months ago

Oh interesting! I suppose I have just been very careful with /etc/fstab and I haven't seen systemd fail this way. TIL! Thanks for letting me know!