Arch Linux

mindness

Member

Registered: 2009-01-20

Posts: 2

cryptsetup / device-mapper issues

Upgrading
- kernel from 2.6.34-2 to 2.6.35.4-1
- cryptsetup from 1.1.2-1 to 1.1.3-1
- device-mapper from 2.02.66-1 to 2.02.70-1 (the newest versions)
(did a full system upgrade so others too, but I don't find those relevant nor do I know them all)

Now I can no longer open all my LUKS volumes. The system has encrypted root w/ LUKS, it opens the root device and others as follows:
/dev/sda1 is /boot (unencrypted)
/dev/sda2 is encrypted swap, made on every boot as told in /etc/crypttab. works
/dev/sda3 is encrypted root, opened on boot, asks password, works

/dev/sdb1 is encrypted hard disk, works
/dev/sdc1 is encrypted hard disk, fails
/dev/sdd1 is encrypted hard disk, fails
/dev/sde1 is encrypted hard disk, fails

[root@x]$ cryptsetup luksOpen /dev/sde1 sde
Enter passphrase for /dev/sde1:
device-mapper: reload ioctl failed: Invalid argument
Failed to setup dm-crypt key mapping for device /dev/sde1.
Check that kernel supports aes-xts-plain cipher (check syslog for more info).
Failed to read from key storage.

dmesg says:
device-mapper: table: 254:3: crypt: Device lookup failed
device-mapper: ioctl: error adding target to table

The error is same for sd{c,d,e}1. If I don't open sdb1 before trying some of the other three, it just changes 254:3 to 254:2 from the error message. Nothing else.

/var/log/messages.log
kernel: device-mapper: ioctl: error adding target to table

To me it seems I have xts cipher working:

cat /proc/crypto
driver       : arc4-generic
module       : arc4
priority     : 0
refcnt       : 3
selftest     : passed
type         : cipher
blocksize    : 1
min keysize  : 1
max keysize  : 256

name         : xts(aes)
driver       : xts(aes-asm)
module       : kernel
priority     : 200
refcnt       : 3
selftest     : passed
type         : givcipher
async        : no
blocksize    : 16
min keysize  : 32
max keysize  : 64
ivsize       : 16
geniv        : eseqiv

name         : xts(aes)
driver       : xts(aes-asm)
module       : xts
priority     : 200
refcnt       : 3
selftest     : passed
type         : blkcipher
blocksize    : 16
min keysize  : 32
max keysize  : 64
ivsize       : 16
geniv        : <default>

name         : aes
driver       : aes-asm
module       : aes_x86_64
priority     : 200
refcnt       : 5
selftest     : passed
type         : cipher
blocksize    : 16
min keysize  : 16
max keysize  : 32

name         : aes
driver       : aes-generic
module       : aes_generic
priority     : 100
refcnt       : 1
selftest     : passed
type         : cipher
blocksize    : 16
min keysize  : 16
max keysize  : 32

name         : stdrng
driver       : krng
module       : kernel
priority     : 200
refcnt       : 2
selftest     : passed
type         : rng
seedsize     : 0

lsmod (some relevant parts)
dm_crypt               12200  2
dm_mod                 64727  5 dm_crypt
aes_x86_64              7412  4
aes_generic            26170  1 aes_x86_64
xts                     2429  2
sha1_generic            2103  4

Removing swap doesn't affect anything. The same thing also happens in a different fileserver I upgraded, that one running i686 but mostly the design and stuff are the same on that. Tried to google this stuff, but found nothing of use (doesn't mean there is no help, though). Help much appreciated.