LUKS decryption is extremely slow at startup after crash

There was a power outage and my system crashed while it was running. Now disk decryption takes an extremely long time at startup (like 5+ minutes) but always loads. I am not sure if this is specifically a Qubes issue or not but I’m wondering how to troubleshoot this issue.

1 Like

Check the boot log in dom0 using journalctl -b command and see where is it stuck for 5 minutes at boot.

1 Like

I’m not sure what happened. It seems to have resolved itself after 2-3 restarts, but now my shutdowns are extremely slow.

1 Like

You can do this to show the log output during shutdown:

1 Like

Solved. This was related to reducing the amount of memory dom0 is using in the Xen kernel parameters. Reducing the maximum amount of memory to 1024 also caused Qubes to fail to boot (not enough memory to decrypt the LUKS partition). I think it was unrelated to the crash.

1 Like

Did you change back maximum amount of memory to that enough to decrypt the LUKS partition without reinstalling Qubes? If yes, how did you modify kernel parameters without having access to dom0 terminal?

1 Like

Autostart troubleshooting | Qubes OS

1 Like

When booting, press e to modify parameters. The parameter dom0_mem needs to be modified. I changed it back to default, dom0_mem=max:4096. Then boot with Control + X.

1 Like