EDIT: the problem is the same as enter the wrong password for LUKS decryption. Instead of reasking for password, Fedora/systemd will stupidly try to boot.
After setting up LUKS auto-decryption when booting, I ran into an issue almost immediately. When I try to boot with the latest kernel, I get an unbootable loop of grub just trying 3 different jobs and timing out (will edit with more info later).
[FAILED] Failed to start systemd-cryptsetup@luks\x... -
See `systemctl status "systemd-cryptdsetup@luks\\x2d7785009c\\x2d7ca\\x2d4be4\\\x2d88a5\\x2dd2b19d1de91c.service for details.
[DEFEND] Dependency failed for cryptsetup.target - Local Encrypted Volumes.
[ OK ] Reached target sysinit.target
[ OK ] Reached target basic.target
[ --* ] (1 of 2) Job dracut-initqueue.service/start
[ --* ] (2 of 2) Job dev-disk-by
After 1 minute, this gets looped
[ --* ] (1 of 2) Job dracut-initqueue.service/start
Warning dracut-initqueue timeout
...
[ --* ] (2 of 2) Job dev-disk-by
Warning dracut-initqueue timeout
...
After another minute, I get this
Starting dracut-emergency.service
Warning: /dev/disk... does not exist
Generating /run/initrams/rdsoreport.txt
Entering emergy mode. Exit the shell to continue
Cannot open access to console, the root account is locked.
Press Enter to continue
Like of course there are no disks, it’s because the TPM got unsealed, so cryptsetup should’ve asked me for my password instead of continuing to boot!
And when I try to boot with the older kernel, I have to manually enter my password. What gives?
I’ve attached the instructions I followed below.