-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work with full disk encryption #3
Comments
Looks good, and thanks for testing with LUKS. I'm out for the holidays but will be back and fix this within a few days. |
Hello, first of all great work and thanks for making it public. I've just stumbled uppon exactly the same issue and fixed it the same way. The only difference is that I'm not using LUKS but plain dmcrypt. I've created this pull request for a very simple fix. I'm no scripting expert so please review it before accepting it. |
commit 6cf6877 |
This latest commit should solve this issue. Logic was added to add the ramroot hook after any encrypt hook in Also the latest version is in the AUR. |
Expected behavior:
On boot, the device encrypted with LUKS should prompt for the decryption key before asking me if I want to load the root filesystem into RAM.
What happens
Everything sort of messes up and then I'm tossed into emergency mode, since the root filesystem hasn't been decrypted yet
How to fix
I solved this by moving the
ramroot
hook after theencrypt
hook in/etc/mkinitcpio.conf
and rebuilding the initramfs. Maybe add some logic for detecting ifencrypt
is loaded, and insertramroot
after that.The text was updated successfully, but these errors were encountered: