hey, On 28/09/2009 anton ivanov wrote: > Well, headers seem to be ok. cryptsetup luksDump finds it without any problem. > > xxd /dev/sdc1 |head -n 10 > 0000000: 4c55 4b53 babe 0001 6165 7300 0000 0000 LUKS....aes..... > 0000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 0000020: 0000 0000 0000 0000 6362 632d 6573 7369 ........cbc-essi > 0000030: 763a 7368 6132 3536 0000 0000 0000 0000 v:sha256........ > 0000040: 0000 0000 0000 0000 7368 6131 0000 0000 ........sha1.... > 0000050: 0000 0000 0000 0000 0000 0000 0000 0000 ................ > 0000060: 0000 0000 0000 0000 0000 0408 0000 0010 ................ > 0000070: e00b 50a0 0042 ae4a cd71 ccff 4b8a b701 ..P..B.J.q..K... > 0000080: 8872 f723 19d5 c1d6 945c 8aed c3b4 703b .r.#.....\....p; > 0000090: a2e2 a755 961d b2e9 fd06 59f3 0ecd 42a6 ...U......Y...B. > > > The problem is that the first sector of disk, where partition table is > hold was altered with this damned swap partition of 2gb. > > Maybe there is any way on how to create artificial partition table > manually that will be correct for dm-crypt to work? And then write it > to this drive using dd or smth. if only the partition table at beginning of /dev/sdc is damaged, and not the luks header at beginning of /dev/sdc1, you could find out the sector where /dev/sdc1 beginns, loop-mount /dev/sdc with offset and try to luksOpen the loop device: # losetup -o <bytes> /dev/loop0 /dev/sdc # cryptsetup luksOpen /dev/loop0 sdc1_crypt greetings, jonas
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
