Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

Rick Thomas rbthomas at pobox.com
Thu Apr 23 11:49:57 BST 2015


On Apr 23, 2015, at 1:29 AM, Michael Biebl <biebl at debian.org> wrote:

> Can you boot with systemd.log_level=debug on the kernel command line and
> attach the journal output of this boot, so we have more information out
> the timing, i.e. when certain services are started
> 
> There might be a race somewhere, i.e. lvm2-activation(-early).service
> being run *before* mdadm has assembled the RAID.
> 
> You could test this theory, be artifically delaying those two services.
> Copy them to /etc/systemd/system, and add a ExecStartPre=/bin/sleep 30
> to the [Service] section of those two units.
> 
> Michael

OK, here’s the log…  Hope it helps!

Interestingly, one time (just once! out of several tries) it booted fine — so it pretty clearly *is* a race condition!

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: boot-journal.txt
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150423/182f5ff7/attachment-0002.txt>


More information about the Pkg-systemd-maintainers mailing list