-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi sebastian mount the snapshot of the pv volume as loop device. test if it is fine with cryptsetup isLuks /dev/loop0 (or loop1, if thats the one you mounted...) (it shouldn't give you any output, but if you do the same on a non luks partition it's telling you :) ) now do a cryptsetup luksDump /dev/loop0 and have a look at the "Payload offset". (don't know if you really should do the next step, i would prefer it... perhaps you should use a ramdisk to dump this header... in that case do mkdir mkdir /tmp/x && mount -t tmpfs tmpfs /tmp/x but be careful , after a reboot the data is gone :) ) do a backup of the old header, just in case... dd if=/dev/crashedpv of=/root/oldheader count=(the offset you got with luksdump) or if you chose the ramdisk dd if=/dev/crashedpv of=/tmp/x/oldheader count=(the offset you got with luksdump) and now copy the header of the backup pv to the crashed pv dd if=/dev/loop0 of=/dev/crashedpv count=(offset again) now cryptsetup isLuks /dev/hopefullynotcrashedpv shouldn't complain anymore :) Jan Sebastian Bork schrieb: > I seem to have toasted the crypto pv volume on our companies file > server by accidentially killing of the luks key in the first (and > only slot). The device is no longer recognized as LUKS now. > However, I have a snapshot of the same pv, containing a working vg > and several lvs. The data on this snapshot is some weeks old and > therefore nearly useless as a backup. Is there any way to extract > the key from the slot of the working dm-crypt pv (the same as used > for the defective one) and add it to the defective crypto pv, to > get back the data on it? *Please* help! > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF7gZqBpRI6A8tC0MRAt03AJ43vr4OJirU5sEgcL3DpjWEOc+SWACgu36O bRXh6/HAjt5ct6GgpFFqkVs= =djZF -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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
