Hello there. Last time I've tried systemd - was version 29. But I had some problems with it, so I decided to stick with openrc. Now I want to give systemd one more try.
So I enabled systemd overlay, emerged systemd-195, also emerged systemd-units form the overlay. Then did

Code:

eix -I -U systemd

And reemerged all packages with systemd flag enabled.
Then I tried to reboot with systemd as my init, root partition was mounted fine, but every partition except root failed to mount. If I comment out all these partitions from fstab, system boots and I can get to kdm, but I can't login, as my home partition is not mounted. Any advices?

1) There is no overlay needed to run systemd as init! Probably your overlay is outdated and pulls in bad unit files.

2) Think of Gentoo having two releases:
arch as stable
~arch as a current/unstable release.
Current systemd-195 should be run with current~arch. And as systemd-195 needs udev-195 you have to special configure some linux kernel .config: devtmpfs_________________fun2gen2

Thanks for your answer!
1) I've removed overlay, and unmerged package which was from that overlay. But that didn't help
2) I'm using ~arch, so udev is latest version (195). Also it has openrc use flag enabled, could it be confusing for systemd?
My kernel has those options which you are referring about:

USE flag openrc doesn't matter. Systemd and openrc are quiet good compangions living in different rooms in the same house.

To your problem:
You could show us your /etc/fstab
But before that, try fsck of your partition reseved for /home when not mounted!
And "systemctl disable" your somehow rotten plymouth ..._________________fun2gen2

About plymouth: I am not sure how could it got rotten, I have no service files for plymouth, and no plymouth installed either. However, there are some files which could be plymouth's, but I am not sure how they got here:

Also, I am not a systemd expert yet, keep in mind:
It is my personal opinion plymouth is a rotten approach, I don't have any plymouth configs. Please look into yours! Might be an automatism of systemd there?

You advise in /etc/fstab your fsck to check two partitions at the same time (1 1)
smoothly diagnose your system:
- make /home in /etc/fstab 1 2 to let check /home after root /
- I would simplify /etc/fstab: comment out what you don't need OR use noauto,defaults as options
- I don't have in fstab: /proc /sys /dev/pts - Isn't this an automatism nowadays?
- Look if the "famous" /usr move is done correctly: /lib/udev symlinks to /usr/lib/udev
- boot with cmdline: nosplash
- boot with cmdline: systemd.unit=multi-user.target OR symlink default.target to multi-user.target - to ignore X at first
- You should use systemd diagnostics: journalctl OR with "systemctl status XYZ" you also get logs shown_________________fun2gen2

But it didn't help...
About the infamous /usr/ move: no, /lib/udev was not a symlink to /usr/lib/udev. It was a dir containing only virtualbox files, so I removed that dir, symlinked /lib/udev -> /usr/lib/udev, and reemerged virtualbox. However it didn't help too...
Tried to boot with nosplash option - nothing.
And sorry for asking, but how could booting with systemd.unit=multi-user.target help? As far as I can see, it can't get until that target, because it's deps (local-fs) are failing...
It's odd that I can't find anyone with a problem like that, with a google search. It used to be really helpful with other problems of mine

What is
1 3
1 4
This is not defined! man fstab:
The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. ...zero is returned and fsck will assume that the filesystem does not need to be checked

Also you could temporarily disable (noauto) all /mnt and ntfs-3g drives, just to diagnose the /home issue at first!

And yes, with your dependency insight! (local-fs) Actually as I said I am not the expert yet ...