From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id PQRAjADagJ2H for <dm-crypt@saout.de>;
 Thu, 18 Jul 2013 20:30:53 +0200 (CEST)
Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com
 [IPv6:2a00:1450:4013:c01::231])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 18 Jul 2013 20:30:53 +0200 (CEST)
Received: by mail-ea0-f177.google.com with SMTP id j14so1917893eak.22
 for <dm-crypt@saout.de>; Thu, 18 Jul 2013 11:30:51 -0700 (PDT)
Message-ID: <51E83448.8010401@gmail.com>
Date: Thu, 18 Jul 2013 20:30:32 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <1374168809.51551.YahooMailBasic@web163904.mail.gq1.yahoo.com>
In-Reply-To: <1374168809.51551.YahooMailBasic@web163904.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] LUKS keyslot invalid - Please help!
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Ywellc <ywellc@yahoo.com>
Cc: dm-crypt@saout.de


On 18.7.2013 19:33, Ywellc wrote:
> I receive an error message stating that LUKS Keyslot 4, 6, and 7 is invalid.  I ran the command again with the debug option:
>
> Invalid keyslot size 8388608 (offset 1032, stripes 0) in keyslot 4 (beyond data offset 2056) and similar for 6 and 7.

So it means that LUKS header is corrupted. If it is really only keyslot 4,6,7
(and you are using keyslot 0, which is most common) maybe you can fix it.

1) _Backup_ header area (dd first 4MB of disk to some safe place)

2) try to run "cryptsetup repair" on device
(Please use crypsetup 1.6.1 - download some boot/live cd with distro which use it,
e.g. recent Fedora.)

If this fails, you need to run keyslot checker (if real used keyslot
is corrupted as well and you have no header backup, no chance...)
(I am sure someone on list here will help you to do this.)

For more info see section 4.1 (and references) in FAQ
http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Backup_and_Data_Recovery

Milan