In 4.2 I’m able to unlock a disk in dom0 and have the fs’s automatically discovered to mount etc. So they are in /dev/mapper/… and /dev//…
But in 4.3 when unlocking in the same way with cryptsetup, it doesn’t work the same. Is there some required lvm command or additional step
that needs to be done, or what has changed? Thanks<!— Before asking, did you search first? Press 
at the upper right to search. ---->
Does your encrypted drive have LVM?
You can force LVM to rescan drives using pvscan and vgscan
If the lvm is visible, you can activate the vg with vgchange -ay.
As far as I remember, secondary lvm pools are not auto activated by default.
You could change auto_activation_volume_list=... in /etc/lvm/lvm.conf
Or try a vgchange --setautoactivation y that_other_vg
Yes I use LVM, I did custom installs and so the VGs are not named “qubes_dom0” but have more sensible names according to what drive it was installed on.
pvscan/vgscan/vgchange didn’t seem to make much of a difference.
Added in /etc/lvm/lvm.conf:
auto_activation_volume_list = [ “driveAp3”, “driveBp4” ]
had no effect…
Added partition that contains the other Qubes install on another drive
lvmdevices --adddev /dev/sddX
then
cryptsetup luksOpen /dev/sddX drivepX
vgscan --devices /dev/mapper/drivepX
vgchange --devices /dev/mapper/drivepX -ay
This worked better, as I’m able to manually mount, copy stuff etc.