On 28/04/2008 Luca Capello wrote: > Hi there! > > With the (not so new) cryptsetup version [1], whichever LUKS passhprase > I enter at boot I get the same error with 3 different kernels > (2.6.24-1-amd64, 2.6.25-rc8-amd64 and 2.6.25-trunk-amd64): > > ===== > device-mapper: table: 254:0: crypt: unknown target type > device-mapper: ioctl: error adding target to table > device-mapper: ioctl: device doesn't appear to be in the dev hash table. > > Command failed: No key available with this passhprase. > =====
Hey Luca, is /dev/sda2 an encrypted root partition? If this is the case, then I believe that some issues with the initramfs scripts are the reason here. do you get a busybox rescue prompt after the cryptsetup failure? If so, please give us the output of 'cat /proc/modules'. You could also try running 'modprobe dm-mod dm-crypt sha256 aes' and then rerun /scripts/local-top/cryptroot. > This is a bug in cryptsetup_2:1.0.6-1: simply downgrading to the > previous version (2:1.0.6~pre1+svn45-1) is enough to solve it. > > Since I thought this could be caused by the default hash being changed > to ripemd160, I (re)read the cryptsetup NEWS.Debian and then guessed I > was OK (I use LUKS and the entire disk encryption has been set up by the > Debian Installer). However, this doesn't seem the case, hence the > severity set to critical. As you use luks encryption, the hash doesn't matter here. cryptsetup ignores hash settings for luks devices. To me it seems like some module is missing/not being loaded. But I might be wrong. > As in /usr/share/doc/cryptsetup/README.initramfs.gz, since I use LUKS my > /etc/crypttab contains a very simple line: > > sda2_crypt /dev/sda2 none luks That one looks correct. greetings, jonas
signature.asc
Description: Digital signature
