[Pkg-cryptsetup-devel] Bug#466573: Bug#466573: cryptsetup: 2.6.25-rc2 does not boot due to "Error allocating crypto tfm"
david at hardeman.nu
Tue Feb 19 21:10:10 UTC 2008
On Tue, Feb 19, 2008 at 06:38:49PM +0100, Didier Raboud wrote:
>using kernel 2.6.25-rc2-amd64 from Debian-Kernel, I can't boot on my system because it is
>not possible to open my LUKS root (/).
>The encountered error is the following (boot option quiet):
>-------- Boot Log transcription --------
>Enter LUKS passphrase:
>device-mapper: table: 254:0: crypt: Error allocating crypto tfm
>Command failed: No key available with this passphrase.
This probably means that the necessary crypto modules are not present in
the initramfs image or that they weren't loaded as appropriate.
Could you uncompress the initramfs image and check the contents?
This can be done by e.g.:
1) mkdir /tmp/init
2) cp /boot/initrd.img-something /tmp/init/initrd.gz
3) cd /tmp/init
4) gunzip initrd.gz
5) cpio -i < initrd
Then you can poke around in the uncompressed source tree...the modules
are under /lib/modules/something/...
More information about the Pkg-cryptsetup-devel