996
submitted 10 months ago by CmdrKeen@lemmy.today to c/linuxmemes@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[-] Synthead@lemmy.world 1 points 10 months ago

The root filesystem mounted fine. That's why the init is starting with all the services on the root disk.

[-] neidu@feddit.nl 6 points 10 months ago

Not necessarily. I've seen failures like this if the boot partition works, but fails to mount the root partition. systemd then fails to proceed, and shuts down the running services.

[-] Synthead@lemmy.world 2 points 10 months ago* (last edited 10 months ago)

systemd daemons are configured via /etc/systemd, and systemd itself lives in /usr/lib/systemd/systemd. How can systemd run or start the configured services without the root disk mounted? The initrd (from the boot partition) only contains enough of an environment to call the entrypoint for the init system, not contain the entirety of systemd (or the configured services).

[-] damium@programming.dev 6 points 9 months ago

Initrd contains the systemd binary and enough libraries, services, and kernel modules to get booted this far. The system failed at switch root which is where the real root disk is mounted. Initrd can contain as much or as little as needed to get a working system which can be a lot of you are using a network filesystem as a root for instance.

load more comments (2 replies)
load more comments (2 replies)
load more comments (2 replies)
this post was submitted on 13 Dec 2023
996 points (99.1% liked)

linuxmemes

20935 readers
575 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