Bug#733232: [Pkg-systemd-maintainers] Bug#733232: systemd: Systemd fails to boot after fscking filesystem if plymouth not installed

2014-06-25 Thread intrigeri
Hi Phil, Michael Stapelberg wrote (04 Jan 2014 21:57:52 GMT) : > My _guess_ is that this is an LVM-related problem. Please see > https://wiki.debian.org/systemd#Issue_.233:_Booting_with_lvm_.28especially_with_separate_.2Fusr.29_fails > and try whether the packages there fix your problem. Any news

Bug#733232: [Pkg-systemd-maintainers] Bug#733232: systemd: Systemd fails to boot after fscking filesystem if plymouth not installed

2014-01-04 Thread Michael Stapelberg
Hi Phil, Phil Armstrong writes: >> Furthermore, both occur in rescue.service and emergency.service, >> respectively, so I think something else is failing before that. Can you >> reproduce this with the kernel parameter systemd.log_level=debug and >> then attach the entire journalctl -xb output pl

Bug#733232: [Pkg-systemd-maintainers] Bug#733232: systemd: Systemd fails to boot after fscking filesystem if plymouth not installed

2014-01-04 Thread Phil Armstrong
On 01/01/14 14:53, Michael Stapelberg wrote: Furthermore, both occur in rescue.service and emergency.service, respectively, so I think something else is failing before that. Can you reproduce this with the kernel parameter systemd.log_level=debug and then attach the entire journalctl -xb output

Bug#733232: [Pkg-systemd-maintainers] Bug#733232: systemd: Systemd fails to boot after fscking filesystem if plymouth not installed

2014-01-01 Thread Michael Stapelberg
Hi Philip, Philip Armstrong writes: > If systemd decides to fsck one or more of my filesystems, then the > boot consistently fails, dropping me to a root password prompt. If I > login & run journalctl -xb than I find the following error in the > journal: > > Dec 27 12:39:53 xanthus systemd[1]: St