Re: Corrupted luks partition, help needed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Milan and thank you for your answer.

I thought that the information shown in luksDump is enough to use those keys for decoding. I thought the extra 128KB per keyslot are for checksum verification, so if they are modified then checksum fails and key is not selected. However, since I know this is the correct key, is there any way to force the usage of it even if checksum fails?

Thanks again,

Panagiotis Malakoudis

On Thu, Jun 3, 2010 at 6:51 PM, Milan Broz <mbroz@xxxxxxxxxx> wrote:
On 06/03/2010 05:32 PM, Panagiotis Malakoudis wrote:
> I have a luks partition which was corrupted by failed disk i/o.
> Examining the partition, the first 512 bytes of the LUKS header is
> correct, then there is a corruption which I am not really sure how many
> sectors affected. Giving the correct key always returns: "No key
> available with this passphrase.". Since the first 512 bytes are correct,
> I guess all key information is unharmed. Is there a way to decrypt the
> partition, even loosing some sectors of data?

If any part of the used keyslot (which is located after visible header,
- in you case starting at sector 8 to sector 264 (hope I calculated it properly),
is modified or lost, you lost that keyslot completely.

Because you have only one active keyslot, you probably lost the whole disk:-(
(Only backup of this keyslot area can help here.)

Milan

_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt

[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux