[Pkg-systemd-maintainers] Bug#718190: Bug#718190: Bug#718190: systemd: sometimes computer doesn't boot. It seems a problem with lvm.

[Michael Stapelberg]

Hi Antonio-M.,

"Antonio-M. Corbi Bellot" <antonio.corbi at ua.es> writes:
> Attached are the outputs from dmesg and 'journalctl -xb' after a failed
> boot. Hope this helps.
Thanks! I spotted this in your log file:

ago 02 12:01:42 hal9000 lvm2[316]: Setting up LVM Volume Groups...
/run/lock/lvm/V_hal9000:aux: open failed: No existe el fichero o el
directorio
ago 02 12:01:42 hal9000 lvm2[316]: Can't get lock for hal9000
ago 02 12:01:42 hal9000 lvm2[316]: failed.

The directory /run/lock is created in /usr/lib/tmpfiles.d/legacy.conf,
so my guess is that /run/lock/lvm/ is missing and lvm does not create
it. It seems odd, but let’s just make sure whether this is the problem
or not. Can you apply the following patch to /etc/init.d/lvm2 please?

--- orig    2013-08-04 19:11:15.120273531 +0200
+++ new     2013-08-04 19:11:35.600702987 +0200
@@ -17,6 +17,8 @@
 
 [ -x /sbin/vgchange ] || exit 0
 
+[ -d /run/lock/lvm ] || mkdir -p /run/lock/lvm
+
 do_start()
 {
        modprobe dm-mod 2>/dev/null || :

In case you still have broken boots, please attach the new logfiles.

-- 
Best regards,
Michael