Your message dated Thu, 19 Jun 2008 14:58:05 +0200
with message-id <[EMAIL PROTECTED]>
and subject line done in 1.0.6-2
has caused the Debian Bug report #478268,
regarding cryptsetup: LUKS device no more recognized at boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
478268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478268
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.0.6-1
Severity: critical
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.
=====
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 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
Thx, bye,
Gismo / Luca
Footnotes:
[1] I vaguely remember having experienced this bug with a 2.6.25-rcX
version when I upgraded cryptsetup, but then I thought it was
related to #466573 [2] and since I hadn't a lot of free time I
switched to a released kernel until the bug appeared on
2.6.24-1-amd64, too. Sorry for not having investigated more before
[2] http://bugs.debian.org/466573
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cryptsetup depends on:
ii dmsetup 2:1.02.24-4 The Linux Kernel Device Mapper use
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libdevmapper1.02.1 2:1.02.24-4 The Linux Kernel Device Mapper use
ii libpopt0 1.10-3 lib for parsing cmdline parameters
ii libuuid1 1.40.8-2 universally unique id library
cryptsetup recommends no packages.
-- no debconf information
pgp2W6e6Uyjrx.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 2:1.0.6-2
this bug has been fixed in 2:1.0.6-2
--- End Message ---
