This bug is related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917124
My layout is as follows: sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 40M 0 part /boot/efi ├─sda2 8:2 0 128G 0 part │ ├─helios-crypt 254:0 0 112G 0 lvm │ │ └─crypt 254:1 0 112G 0 crypt │ │ ├─crypthelios-debian 254:2 0 8G 0 lvm / │ │ ├─crypthelios-srv 254:3 0 8M 0 lvm /srv │ │ ├─crypthelios-usrlocal 254:4 0 56M 0 lvm /usr/local │ │ ├─crypthelios-opt 254:5 0 1.3G 0 lvm /opt │ │ ├─crypthelios-home 254:6 0 96G 0 lvm /home │ │ └─crypthelios-var 254:7 0 3.5G 0 lvm /var │ └─helios-boot 254:8 0 192M 0 lvm /boot └─sda3 8:3 0 2G 0 part When system was dropping into rescue shell only /, /boot, and /boot/efi were mounted. lvscan was showing all of the volumes as active, yet none were showing up either in expected /dev/crypthelios/, or under /dev/mapper/ (except for helios-boot or helios-crypt, don't remember with certainty which one). I could get device files to show up by running 'vgscan --mknodes', but I couldn't actually mount them, neither through symlinks nor through actual /dev/dm-# files. Again, the only thing that got me going was downgrading udev from 240-1 to 239-15. -- This message was created with 100% recycled electrons
signature.asc
Description: This is a digitally signed message part.
