Description of problem:

After rebooting in connection with an update to kernel 5.11.11-300.fc34 my system will no longer boot into the root fs (ext4) on a LVM volume which is located on a LUKS partition.

I have just updated to kernel 5.11.12-300.fc34, and the problem still persists, but 5.11.7-300-fc34 can still boot the system without issues, I missed the .8 to .10 kernel, so I can't give any status that time frame.

Both in the booting an none booting cases plymouth asks for the password to the partition, and proceeds, but in the non booting case the boot stops after finishing the cryptsetup job, and seems to be waiting for devices to show up, which might be LVM related

Version-Release number of selected component (if applicable):


How reproducible:
Always


Steps to Reproduce:
1. Boot
2. Select a none booting kernel setup in grub
3. Enter password for partition when prompted
4. Booting stops

Actual results:
System will not boot

Expected results:
System will boot


Additional info:
This laptop was originally installed with F32, then updated to F33, and now for some months F34.