On Mon, 06 Aug 2018 at 21:15:10 +0800, Ben Hutchings wrote: > Sometimes driver modules have been reorganised and this has resulted > in missing modules. But this wouldn't explain other files being > missing. cryptsetup's initramfs boot scripts should be present either way, but inclusion of the cryptsetup binaries (and crypto modules) depend on whether the hook detected that some device has to be unlocked at initramfs stage. (Unless /etc/cryptsetup-initramfs/conf-hook contains "CRYPTSETUP=y", which indeed forces initramfs integration.) Dirk, which “cryptsetup related parts” are missing from the 4.17 bpo initramfs with cryptsetup 2:1.7.3-4? Does `update-initramfs -u` print any warning about unknown module and/or root FS? Can you confirm that adding "CRYPTSETUP=y" to /etc/cryptsetup-initramfs/conf-hook (and compiling your initramfs image with MODULES="most" — the default) fixes the issue? -- Guilhem.
Attachment:
signature.asc
Description: PGP signature