Bug#917124: systemd: local-fs.target fails with result 'dependency'

[Michael Biebl]

Control: retitle -1 lvm2 logical volumes are not properly initialized

Am 23.12.18 um 01:38 schrieb Ben Caradoc-Davies:
>> Can you provide a verbose debug log as requested in my previous reply?
> 
> "journalctl -alb" output attached to my previous email. Please let me
> know if you require

Ok, first of all thanks for the information you provided so far.
I doubt it's a but in systemd itself, it's just the recipient of a
device not showing up properly.

The issue is really between the interaction of udev and lvm2.

I suppose if you keep systemd at 239-15 and upgrade udev to 240-1, you
still get the failure. Can you confirm that?
And vice versa, systemd 240-1 together with udev 239-15 should also not
be problematic.

For some reason, lvm devices (logical volumes) are not properly initialized.

When you are dropped into the rescue shell, can you check the following:

Determine the device name for your lvm logical volume. Check the output
of lvdisplay. It should say Block device 253:?

Then check the state of the device in the udev db

udevadm info /sys/class/block/dm-? (? being the number you determined
earlier).

Paste that output please.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20181223/6e1841c8/attachment.sig>