Bug#409875: [Pkg-cryptsetup-devel] Bug#409875: bug #409875
David Härdeman
david at hardeman.nu
Wed Feb 7 23:03:43 CET 2007
On Wed, Feb 07, 2007 at 10:31:27PM +0100, Johannes Schlumberger wrote:
>Hi,
>> Ok, could you create a file called e.g. "map" containing the following line:
>> 0 10000 crypt aes-cbc-essiv:sha256 0123456789abcdef0123456789abcdef 0
>> /dev/md0 0
>
>shure.
>[22:28:31][root at asso:/tmp]# echo '0 10000 crypt aes-cbc-essiv:sha256 \
>0123456789abcdef0123456789abcdef 0 /dev/md0 0' > map
>[22:28:46][root at asso:/tmp]# dmsetup create root map
>device-mapper: reload ioctl failed: Invalid argument
>Command failed
This would suggest that the problem is not with cryptsetup at least.
Something seems wonky with device-mapper in general.
I've updated the testing machine I was using so that it has the same
package versions as your machine and it still works for me.
Just to make sure, do you think you could install the Debian packaged
kernel, boot it and try to setup the mapping with that kernel? (but do
the things mentioned below first)
>the dmesg output differs though, its missing one line.
>
>[22:28:57][root at asso:/tmp]# dmesg | tail -n 3
>agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
>device-mapper: table: 253:2: crypt: Device lookup failed
>device-mapper: ioctl: error adding target to table
If it tries to setup 253:2, that suggests that there are two other
device-mapper devices already setup...what is the output of "ls -al
/dev/mapper", "dmsetup table" and "cat /proc/mounts"? Also, are you
using udev?
--
David Härdeman
More information about the Pkg-cryptsetup-devel
mailing list