On a completely different note I realised that my suggestion on running fsck on the partition containing the encrypted volume is dangerously wrong.
Warning:
- In any scenario, never use file system repair software such as fsck directly on an encrypted volume, or it will destroy any means to recover the key used to decrypt your files. Such tools must be used on the decrypted (opened) device instead.
- For the LUKS2 format:
- GRUB’s support for LUKS2 is limited; see GRUB#Encrypted /boot for details. Use LUKS1 (
cryptsetup luksFormat --type luks1) for partitions that GRUB will need to unlock.- The LUKS2 format has a high RAM usage per design, defaulting to 1GB per encrypted mapper. Machines with low RAM and/or multiple LUKS2 partitions unlocked in parallel may error on boot. See the
--pbkdf-memoryoption to control memory usage.[1]