Am 24.07.2014 22:59, schrieb Benoit Friry: >>>> After a reboot your problem will be gone. > > No more error in log after reboot. Bug report can be closed. > >>> Is there any other way to fix that without rebooting? >> >> Unfortunately not. The new logind requires systemd as PID 1, which >> means you need to reboot. > > Not a good news. :( > > I used the opportunity of rebooting to test systemd > (init=/bin/systemd). I hope next upgrade will not need rebooting. > > (First impression is rather bad: boot is slower, boot messages are > unreadable, and password prompt to luksOpen is hidden.)
If you want a verbose boot, you can remove "quiet" from the kernel command line. Can you boot with "systemd.log_level=debug" on the kernel command line and send me the output of "journalctl -alb". Do you have any mount points in /etc/fstab which are not accessible during boot? Systemd has a 90 secs timeout for those. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
