next box tested. Installed systemd on my main workstation now that I understood how to easily flip back to booting w/ openrc in case of problems.
I heavily use LVM here and this gives me the following issues: I use lvm.service from the gentoo-wiki: http://en.gentoo-wiki.com/wiki/Systemd#LVM For sure I enabled it ... When I boot this machine it boots up to starting the LVM-devices and waits for some time then writes something like: welcome to emergency mode ... Start of /dev/VG...something failed (due to some dependencies) (for all the LVs) and lets me login or press Ctrl-D to continue. (I can't remember the exact words, don't know if they are logged somewhere) When I press Ctrl-D all the LVs are mounted(!) and it boots up fine to graphical login. hmm. It then tells me: # systemctl status lvm.service lvm.service - Linux Volume Manager Loaded: loaded (/etc/systemd/system/lvm.service) Active: active (exited) since Mon, 22 Aug 2011 09:55:36 +0200; 22min ago Process: 5568 ExecStop=/sbin/lvchange --sysinit -a ln $(/sbin/vgs -o vg_name --noheadings --nosuffix 2> /dev/null) (code=exited, status=3) Process: 5861 ExecStart=/sbin/vgchange --sysinit -a ly (code=exited, status=0/SUCCESS) Process: 5738 ExecStart=/sbin/vgscan --mknodes --ignorelockingfailure (code=exited, status=0/SUCCESS) Process: 5654 ExecStart=/sbin/pvscan --ignorelockingfailure (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/lvm.service Why does that ExecStop fail? Why is it called at boot anyway? I also tried another lvm.service from the russian gentoo-wiki, that servicefile just pulls in /etc/init.d/lvm, but that didn't help so I went back to the mentioned file. What I wonder: what changes between running into that timeout and my pressing Ctrl-D? Thanks for helpful comments, Stefan
