Created attachment 1880537 [details] journalctl for a sample bad boot Description of problem: The boot hangs when using systemd 251~rc3-1.fc37. Booting works with systemd 251~rc2-2.fc37. Some encrypted devices aren't mounted and cryptsetup hangs when trying to do it manually to finish up the boot. Downgrading using a live image got things working again. How reproducible: It happens every boot, but might not happen with all systems.
https://koji.fedoraproject.org/koji/taskinfo?taskID=87360713 has a scratch builds with one patch reverted. Could you test if it fixes the issue?
Could you describe your storage layout? Is the device for /boot (part of) the LUKS device? Also, please attach a boot log taken with "systemd.log_level=debug". One possible issue is lvm2-monitor.service which is obviously started too early ("WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.").
/boot is not encrypted. I'll test things sometime today. I have the 251-1 release installed right now, but haven't tried rebooting yet. I'll try it at a convenient point today. If that doesn't work, I'll try the scratch build you pointed to.
The 251-1 release still has the problem. I'm about to test the scratch build.
The scratch build worked for me.
This should be fixed, but please test.
I tested systemd-251.1-1.fc37.x86_64 and it worked fine. Thanks for fixing this.
The fix that Zbigniew provided simply reverted a patch from v251. That's fine, but meanwhile I've come up with a patch that fixes the LUKS issue (for me, at least) without re-introducing the breakage in multipath setups that v250 and earlier releases suffered from. Therefore, if you can, please test with the code in https://github.com/systemd/systemd/pull/23489. Unfortunately I don't know how to provide test binaries for Fedora, any help would be appreciated.