• CameronDev@programming.dev
    link
    fedilink
    arrow-up
    4
    ·
    11 months ago

    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 :)

    • Synthead@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      11 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!