Control: tag -1 - unreproducible Control: reassign -1 lvm2 2.03.15-1 Control: forcemerge 1018730 -1 Control: affects -1 cryptsetup-initramfs
Thanks for the the reproducer! Much appreciated. So the problem is that your VG spans over multiple PVs, but the LVs that are required at early boot stage (the ones holding the root FS and the resume device) reside only on the first PV so cryptsetup-initramfs rightfully never tries to unlock the second one (which only holds /home hence is not needed that early). This used to work, but it looks like lvm2's udev rules never try to activate complete LVs residing on incomplete VGs, hence the deadlock. This mostly affects cryptsetup-initramfs and perhaps the issue could be mitigated there, but this is an lvm2 regression and non-luks systems can be affected too [0] so I'm reassign the bug accordingly. (Turns out it was already reported, hence also merging.) A quick fix for your particular setup is to edit crypttab(5), add the ‘initramfs’ option for the ‘4Tsolid’, and rebuild the initramfs image. That should force the device to be considered at initramfs stage. -- Guilhem. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1337220#c10
signature.asc
Description: PGP signature
