is this issue necessarily a cryptsetup issue, or could lvm2 or even update-initramfs be responsible for the bug? At least for me, I get the message, that the volume-group is now active, before the error message.
is this issue necessarily a cryptsetup issue, or could lvm2 or even update-initramfs be responsible for the bug? At least for me, I get the message, that the volume-group is now active, before the error message.