hi, the more i think about the problem, the stranger it gets: - all "layers" are ok (raid, lvm, luksDump) - the key is the verified against a backup and identical - the command luksOpen fails since i made some changes to the system I studied the first 0x1000 raw-bytes of the raid and verified them against the LUKS standard paper - there is valid data only - thats what luksDump says, too. (btw: nice idea, using 'LUKS 0xBABE' and 0x0DEAD hexcodes). I don`t think, that someone broke into the system and changed the key. I don`t think, the USB stick or the old usb-driver had a communication error that reproduces always the same error in my keyfile with older linux drivers. So what`s left ? My try, to install the wlan stick. I am sure, it has nothing to do directly with this driver (isn`t loaded anymore) but it may be a side effect of my install and deinstall process. The system behaviour may have changed... Is the encryption module working ? Yes - seems so: cat /proc/crypto name : sha256 driver : sha256-generic module : sha256 priority : 0 type : digest blocksize : 64 digestsize : 32 name : aes driver : aes-generic module : aes priority : 100 type : cipher blocksize : 16 min keysize : 16 max keysize : 32 BUT: i get the same failed message from cryptsetup WITH or WITHOUT aes.ko loaded cryptsetup luksOpen /dev/mapper/vg-crypted_raid raid -d/mnt/key.md0.orig Aufruf fehlgeschlagen. The systems not to be able to find the Masterkey. Maybe i have an incompatible kernel module ? server:~# modinfo aes filename: /lib/modules/2.6.18-5-xen-686/kernel/crypto/aes.ko description: Rijndael (AES) Cipher Algorithm license: Dual BSD/GPL vermagic: 2.6.18-5-xen-686 SMP mod_unload 686 REGPARM gcc-4.1 depends: uname -a Linux server 2.6.18-5-xen-686 #1 SMP Mon Dec 24 20:49:58 UTC 2007 i686 GNU/Linux The linux boot partition, i used to create the raid, doesn`t exist anymore - too bad. I set it up approx. 1/2 year ago with stable repositories of debian with an - i guess - ubuntu 6.10. And - ofcourse - deleted it, after my 2nd server worked. So i guess, this is the right direction to search for an solution: systemchanges. Are there any incompatibilities known for dmsetup / crypsetup versions ? Do i need a special Kernel ? Are there any more tools / files for a deeper analyzation available ? Is there a special linux distribution (feudora 8 and ubuntu 7.10 live cds doesn`t work) which works out f the box with encrypted raids ? ???? strange. DP --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
