You are not logged in.
Hi! After a failed update due to a full boot partition and potentially a bad Nvidia update my system wouldn't boot.
I spent a few hours rebooting from a stick, reverting some packages and using chroot to fix it. After various attempts with `mkinitcpio -P`, `grub-mkconfig` and `grub-install` the system now boots, but to my surprise, it does not ask for a decryption password. It goes directly to a functional state.
Some details: there are two partitions: a 300M boot partition and another one with the OS and my home. The boot partition has a key file to decrypt the main partition. But until two days ago it was asking me for a password to decrypt the boot partition. No more.
How is it possible that the partition is decrypted automatically?
And any ideas on how I could fix this?
Thank you!
Last edited by rokidakota (2025-05-27 09:10:05)
Offline
I compared the /boot/ folder from broken system with another working one, noticed several nested efi or EFI folders, so I deleted those folders and repeated the mkinitcpio and grub commands and now it works as expected.
I still would like to understand how is it possible that the system was booting without prompting a password if the disk is encrypted. Makes me worried about how safe it is.
Offline
Are you talking about LUKS-encrypted disk? You mentioned that you have a keyfile. one possible explanation would be that mkinitcpio is picking up the key file and packing it in initrd image because it "thinks" you want the disk to be unlocked automatically on boot. What is your /etc/crypttab?
This might help: https://wiki.archlinux.org/title/Dm-cry … _a_keyfile
Last edited by bachtiar (2025-06-13 07:35:49)
Offline