Hello, I've faced the same error for a while on an x86_64 computer running Debian sid amd64, which has a VG spanning two PVs inside LUKS volumes located on a SSD (rootfs) and a HDD (home). Both LUKS volumes is declared into crypttab, as they should be. This two-LUKS volume, two-PV setup was created by the then-current Debian testing installer (weekly ISO build) when I installed that computer at the end of 2018, so arguably, it ought to be a supported configuration - plus it's nothing out of the ordinary anyway :)
Granted, ISTR about moving the rootfs from the HDD to the SSD after the initial install; also, I temporarily used cache volumes on the SSD, but I removed them, so they don't contribute to the current issue. With lvm2 2.03.11 and older, upon every boot, I duly noticed the warning messages related to partial activation, after entering a single passphrase; however, both LUKS volumes get opened successfully, all VGs and LV are activated, and the system boots properly. With lvm2 2.03.15 and newer, the rootfs is no longer being found, after the VG is not activated at all, because partial activation is no longer enabled. I set the activation mode to partial in the LVM config, and regenerated the initramfs, to no avail. Swapping the order of the two lines in the crypttab and regenerating the initramfs does not help either. For now, I've held the lvm2, liblvm2cmd2.03:amd64 and dmeventd packages, and removed the cryptsetup-initramfs package. That computer is therefore stuck on an older kernel & initramfs, because I need it to work, but that's not good... In the current state, this upgrade of LVM2 should break more computers with similar, working setups (pending the application of whichever workaround), as they transition from Debian 11 to 12. Regards, Lionel Debroux.
