On Mon, Jun 17, 2019 at 3:58 AM Lennart Poettering <mzerqung(a)0pointer.de> wrote:
On Sa, 08.06.19 15:34, Chris Murphy (lists(a)colorremedies.com) wrote:
> However, in the failing case, that doesn't happen, and systemd hangs
> indefinitely waiting for it to appear. And in the early debug shell,
> 'blkid' sees it. That means the kernel and libblkid see it. I've got
> no idea why systemd doesn't see it.
Wat does udevadm info on the block device node say? i.e. does the
device carry the right tag, does it have SYSTEMD_READY=0 set?
Yes.
# udevadm info /dev/mapper/cryptswap
P: /devices/virtual/block/dm-0
N: dm-0
L: 0
S: disk/by-id/dm-name-cryptswap
S: mapper/cryptswap
S: disk/by-id/dm-uuid-CRYPT-PLAIN-cryptswap
E: DEVPATH=/devices/virtual/block/dm-0
E: DEVNAME=/dev/dm-0
E: DEVTYPE=disk
E: MAJOR=253
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=23080972
E: DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG=1
E: DM_UDEV_PRIMARY_SOURCE_FLAG=1
E: DM_ACTIVATION=1
E: DM_NAME=cryptswap
E: DM_UUID=CRYPT-PLAIN-cryptswap
E: DM_SUSPENDED=0
E: DM_UDEV_RULES_VSN=2
E: SYSTEMD_READY=0
E: DEVLINKS=/dev/disk/by-id/dm-name-cryptswap /dev/mapper/cryptswap
/dev/disk/by-id/dm-uuid-CRYPT-PLAIN-cryptswap
E: TAGS=:systemd:
systemctl list-jobs says dev-mapper-cryptswap.device is running,
everything else is waiting, but when I get a systemctl status on
dev-mapper-cryptswap.device I get
● dev-mapper-cryptswap.device - /dev/mapper/cryptswap
Loaded: loaded
Drop-In: /run/systemd/generator/dev-mapper-cryptswap.device.d
└─90-device-timeout.conf
Active: inactive (dead)
Jun 18 08:19:41 flap.local systemd[1]: dev-mapper-cryptswap.device:
Merged dev-mapper-cryptswap.device/start into installed job
dev-mapper-cryptswap.device/start as 158
Jun 18 08:19:41 flap.local systemd[1]: dev-mapper-cryptswap.device:
Merged dev-mapper-cryptswap.device/start into installed job
dev-mapper-cryptswap.device/start as 158
--
Chris Murphy