On 23/12/2018 15:43, Michael Biebl wrote:
Ok, first of all thanks for the information you provided so far.

You are welcome. Thank you for the quick turnaround and detailed instructions.

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?

Yes, the failure is observed for systemd 239-15 with udev 240-1.

And vice versa, systemd 240-1 together with udev 239-15 should also not
be problematic.

Yes, no failure for systemd 240-1 with udev 239-15. The only oddity is the two minute hang at shutdown after systemd upgrade, as shown in the earlier photo. We can deal with that later if it persists. Boot proceeds normally.

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.

In rescue shell after boot (systemd 239-15 with udev 240-1):

# udevadm info /sys/class/block/dm-2
P: /devices/virtual/block/dm-2
N: dm-2
L: 0
E: DEVPATH=/devices/virtual/block/dm-2
E: DEVNAME=/dev/dm-2
E: DEVTYPE=disk
E: MAJOR=253
E: MINOR=2
E: SUBSYSTEM=block
E: USEC_INITIALIZED=9715169
E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1
E: DM_UDEV_DISABLE_DISK_RULES_FLAG=1
E: DM_UDEV_DISABLE_OTHER_RULES_FLAG=1
E: DM_UDEV_RULES=1
E: DM_UDEV_RULES_VSN=2
E: net.ifnames=0
E: SYSTEMD_READY=0
E: TAGS=:systemd:

Compare with normal boot (systemd 240-1 with udev 239-15):

# udevadm info /sys/class/block/dm-2
P: /devices/virtual/block/dm-2
N: dm-2
S: disk/by-id/dm-name-vg-home
S: disk/by-id/dm-uuid-LVM-SiqeiwSeAj9MM50Phu717igDgDlF5NIq0N9nmHNGMYuvfy7LFfYfUQpyivO394C5
S: disk/by-label/Home
S: disk/by-uuid/39303d70-dd06-4356-b413-efcb35f8cd4c
S: mapper/vg-home
S: vg/home
E: DEVLINKS=/dev/mapper/vg-home /dev/disk/by-id/dm-name-vg-home /dev/disk/by-id/dm-uuid-LVM-SiqeiwSeAj9MM50Phu717igDgDlF5NIq0N9nmHNGMYuvfy7LFfYfUQpyivO394C5 /dev/vg/home /dev/disk/by-label/Home /dev/disk/by-uuid/39303d70-dd06-4356-b413-efcb35f8cd4c
E: DEVNAME=/dev/dm-2
E: DEVPATH=/devices/virtual/block/dm-2
E: DEVTYPE=disk
E: DM_LV_NAME=home
E: DM_NAME=vg-home
E: DM_STATE=ACTIVE
E: DM_SUSPENDED=0
E: DM_TABLE_STATE=LIVE
E: DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG=1
E: DM_UDEV_PRIMARY_SOURCE_FLAG=1
E: DM_UDEV_RULES=1
E: DM_UDEV_RULES_VSN=2
E: DM_UUID=LVM-SiqeiwSeAj9MM50Phu717igDgDlF5NIq0N9nmHNGMYuvfy7LFfYfUQpyivO394C5
E: DM_VG_NAME=vg
E: ID_FS_LABEL=Home
E: ID_FS_LABEL_ENC=Home
E: ID_FS_TYPE=ext4
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=39303d70-dd06-4356-b413-efcb35f8cd4c
E: ID_FS_UUID_ENC=39303d70-dd06-4356-b413-efcb35f8cd4c
E: ID_FS_VERSION=1.0
E: MAJOR=253
E: MINOR=2
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: USEC_INITIALIZED=12329587
E: net.ifnames=0

Kind regards,

--
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand

Reply via email to