Bug#733232: [Pkg-systemd-maintainers] Bug#733232: systemd: Systemd fails to boot after fscking filesystem if plymouth not installed
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]: Started LSB: option to manually > manipulate the IPsec SA/SP database. > Dec 27 12:39:53 xanthus systemd[1]: Startup finished in 4.659s > (kernel) + 1min 30.662s (userspace) = 1min 35.321s. > Dec 27 12:39:53 xanthus systemd[685]: Failed at step EXEC spawning > /bin/plymouth: No such file or directory > > (I don't have plymouth installed & there is no /bin/plymouth) > > The system always boots successfully if no fsck is required. I think you are misinterpreting the situation. In the systemd source, there are only two occurrences of /bin/plymouth: $ grep -r '/bin/plymouth' . ./units/rescue.service.m4.in:ExecStartPre=-/bin/plymouth quit ./units/emergency.service.in:ExecStartPre=-/bin/plymouth quit Both are prefixed with a minus, meaning it’s not a problem if they cannot be started. 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 please? -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733232: [Pkg-systemd-maintainers] Bug#733232: systemd: Systemd fails to boot after fscking filesystem if plymouth not installed
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 please? Attached! cheers, Phil failed-boot-journalctl-xb.txt.gz Description: GNU Zip compressed data
Bug#733232: [Pkg-systemd-maintainers] Bug#733232: systemd: Systemd fails to boot after fscking filesystem if plymouth not installed
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 please? > > Attached! Thanks. From looking at that log, I think you may have been mislead in your original message. It seems to me like your trouble starts here: Jan 04 19:01:09 xanthus systemd[1]: Job dev-mapper-Kantaka\x2dHome.device/start timed out. Jan 04 19:01:09 xanthus systemd[1]: Timed out waiting for device dev-mapper-Kantaka\x2dHome.device. Jan 04 19:01:09 xanthus systemd[1]: Dependency failed for /home. Jan 04 19:01:09 xanthus systemd[1]: Dependency failed for Local File Systems. Jan 04 19:01:09 xanthus systemd[1]: Triggering OnFailure= dependencies of local-fs.target. Jan 04 19:01:09 xanthus systemd[1]: Dependency failed for File System Check on /dev/mapper/Kantaka-Home. However, when actually grepping for fsck, these are the results: $ zgrep fsck failed-boot-journalctl-xb.txt.gz Jan 04 18:59:39 xanthus systemd-fsck[324]: /dev/mapper/Kantaka-Root--Squeeze: clean, 433977/1262320 files, 4241638/5062656 blocks (check in 5 mounts) -- Subject: Unit systemd-fsck-root.service has finished start-up -- Unit systemd-fsck-root.service has finished starting up. -- Subject: Unit systemd-fsck-root.service has finished start-up -- Unit systemd-fsck-root.service has finished starting up. -- Subject: Unit systemd-fsck@dev-disk-by\x2duuid-c0f47c3e\x2d58a9\x2d4f1d\x2d9690\x2d614cf1228f75.service has begun with start-up -- Unit systemd-fsck@dev-disk-by\x2duuid-c0f47c3e\x2d58a9\x2d4f1d\x2d9690\x2d614cf1228f75.service has begun starting up. Jan 04 18:59:39 xanthus systemd-fsck[637]: /dev/sda2: clean, 300/244320 files, 125283/488448 blocks -- Subject: Unit systemd-fsck@dev-disk-by\x2duuid-c0f47c3e\x2d58a9\x2d4f1d\x2d9690\x2d614cf1228f75.service has finished start-up -- Unit systemd-fsck@dev-disk-by\x2duuid-c0f47c3e\x2d58a9\x2d4f1d\x2d9690\x2d614cf1228f75.service has finished starting up. -- Subject: Unit systemd-fsck@dev-mapper-Kantaka\x2dHome.service has failed -- Unit systemd-fsck@dev-mapper-Kantaka\x2dHome.service has failed. I don’t see an actual fsck running for Kantaka/Home. 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. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733232: [Pkg-systemd-maintainers] Bug#733232: systemd: Systemd fails to boot after fscking filesystem if plymouth not installed
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 on this front? Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
