Opening vs. systemd since the problem appears to be there, but feel free to reassign the component if needed...

This is more of a minor annoyance than a critical bug. I have the root partition of my laptop encrypted via luks. dracut pops up a nice unlock prompt during boot time, but unfortunately it seems to eventually time out after a minute or two and drops to the dracut rescue shell.

The upshot is that if I start my laptop and walk away for a few minutes, then I end up having to reboot it in order to get it to come up the rest of the way. Shouldn't it wait indefinitely for the password, particularly if booting can't proceed without it?