[Pkg-cryptsetup-devel] Bug#466573: Bug#466573: Bug#466573: cryptsetup: 2.6.25-rc2 does not boot due to "Error allocating crypto tfm"

David Härdeman david at hardeman.nu
Wed Feb 20 23:08:15 UTC 2008

On Wed, Feb 20, 2008 at 12:37:29PM +0100, Jonas Meurer wrote:
>On 19/02/2008 David Härdeman 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.
>It seems like blkcipher module was renamed to crypto_blkcipher in
>2.6.25. See http://marc.info/?l=linux-kernel&m=120350670529028&w=2
>for reference.
>Not sure though, whether this is the real issue here, as according to
>Didiert the crypto_blkcipher module is included in the initramfs.

Didier, as a test, could you try booting with the "break" parameter, 
that should at least drop you into a shell even if cryptsetup refused 

Then you can do a "modprobe crypto_blkcipher", followed by "exit" which 
will continue the boot process. If that sorts it out, we at least know 
which module isn't being loaded properly.

David Härdeman

More information about the Pkg-cryptsetup-devel mailing list