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

[Antonio-M. Corbi Bellot]

El Sat, 03 Aug 2013 12:37:20 +0200
Michael Stapelberg <stapelberg at debian.org> escribio:

> Hi Antonio-M.,
> 
> "Antonio-M. Corbi Bellot" <antonio.corbi at ua.es> writes:
> > I've to say that I've just had another bad boot with systemd after
> > moving 'usr' and 'var' to '/'.
> 
> > I got a time out trying to moun 'home' that is on another lvm
> > 'partition'... so I'm lost now, it must be a problem with lvm.
> >
> > As always when boot stops, after a time out, I get dropped into a
> > shell and the 'vgchange -a y' trick works for me...
> Yeah, the symptom looks very similar. The device gets put into the
> “plugged” state far too late.
> 
> Can you add udev.log_priority=8 to the kernel command line and attach
> the new logfile of a failed boot please?
> 

Hi Michael:

Attached are the outputs from dmesg and 'journalctl -xb' after a failed
boot. Hope this helps.

Antonio.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boot.log.nonworking.udev8
Type: application/octet-stream
Size: 69576 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20130804/78e1f4f0/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: journalctl.log.udev8
Type: application/octet-stream
Size: 119326 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20130804/78e1f4f0/attachment-0005.obj>