On Sat, Jun 23, 2018 at 6:50 PM, Guilhem Moulin <guil...@debian.org> wrote: > In fact it's not related to the ‘decrypt_gnupg’ keyscript, the > “size=256” wrongly translates to `cryptsetup --size=256`, which sets the > size of the device to 256 512-bytes sectors instead of setting the key > size.
This makes more sense, and it actually explains the wrong size of the volume. As a workaround, I removed the size= option from crypttab. It works as expected, although it generates a warning when updating the initramfs and at boot: cryptsetup: WARNING: Option 'size' missing in crypttab for plain dm-crypt mapping root. Please read /usr/share/doc/cryptsetup/README.initramfs and add the correct 'size' option to your crypttab(5). You may want to change the specified README.initramfs path to reflect the new packages names (i.e. /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz). Thanks
