Le 19/06/2018 à 22:40, Guilhem Moulin a écrit : > Could you run the following on both the broken and backup initrd and > send the diff? > > lsinitramfs /path/to/initrd.img | grep ^lib/modules/ | sort See initramfs_dep_vs_most.diff.gz. The dep output is not working, and the most output is working.
> Also, please edit /usr/share/initramfs-tools/hooks/cryptroot and enable > debuging withing populate_CRYPTO_MODULES: > > populate_CRYPTO_MODULES() { > set -x > […] > set +x > } > > Then run `update-initramfs -u` and attach the error output. I wish you good luck, since the output (see update_initramfs_output.txt) seems to be mixed, as if multiple tasks were running concurrently. I try to run this multiple times to get a nicer output, without success. > FWIW 2.0.3-2 was tested with MODULES=dep, too. I wonder how your system > differs from our test environments. OK, that's good news :)
initramfs_dep_vs_most.diff.gz
Description: application/gzip
+ local mod value cipher blockcipher ivhash + [ sda3_crypt = sda3_crypt ] + dmsetup table+ cut -d -f4 -- sda3_crypt + value=aes-xts-plain64 + printf %s aes-xts-plain64 + cut -d- -f1 + cut -d: -f1 + cipher=aes + [ -z aes ] + CRYPTO_MODULES=aes + printf %s aes-xts-plain64 + cut -d- -f1 + cut -d: -f1 + blockcipher=aes + [ -n aes ] + [ aes != plain ] + CRYPTO_MODULES=aes aes + printf %s aes-xts-plain64 + cut -d: -s -f2 + ivhash= + [ -n ] + [ sda4_crypt = sda4_crypt ] + cut -d -f4 + dmsetup table -- sda4_crypt + value=aes-xts-plain64 + printf %s aes-xts-plain64 + cut -d- -f1 + cut -d: -f1 + cipher=aes + [ -z aes ] + CRYPTO_MODULES=aes aes aes + printf %s aes-xts-plain64 + cut -d- -f1 + cut -d: -f1 + blockcipher=aes + [ -n aes ] + [ aes != plain ] + CRYPTO_MODULES=aes aes aes aes + printf %s aes-xts-plain64 + cut -d: -s -f2 + ivhash= + [ -n ] + set +x