From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 jppMnu0Cgs2H for ; Mon, 31 Dec 2012 12:26:21 +0100 (CET) Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Mon, 31 Dec 2012 12:26:20 +0100 (CET) Received: by mail-ee0-f50.google.com with SMTP id b45so6312621eek.9 for ; Mon, 31 Dec 2012 03:26:19 -0800 (PST) Message-ID: <50E17658.5020800@gmail.com> Date: Mon, 31 Dec 2012 12:26:16 +0100 From: Milan Broz MIME-Version: 1.0 References: <4FE1ACE321FB45CABE8FE1C09A8D060B@ws1xp> In-Reply-To: <4FE1ACE321FB45CABE8FE1C09A8D060B@ws1xp> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] LUKS keyslot invalid List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt On 12/29/2012 11:03 PM, wpc95 wrote: > Running Ubuntu 12.04 (cryptsetup 1.4.0) LUKS claims for 2 of the > encrypted drives, that 'LUKS keyslot 4 is invalid'. Due to the fact that the > option 'repair' was launched with cryptsetup 1.4.1, i have started the > computer with an actual live-linux. But the result with cryptsetup 1.5.0 is > the same as with 1.4.0: it claims, that 'LUKS keyslot 4 is invalid. Invalid > offset 1576471435 [first drive] 3746914134 [second drive] in keyslot 4.' The > repair option says that repair failed with code 22 and a manual repair is > required. Just for the archive - the current repair code is able to fix this problem (it was just simple 4 bytes overwrite, fortunately on unused keyslot metadata). I was just too cautious and did not enabled repair of 512bit (XTS mode) keys. That restriction is now removed, so next time repair code should work. Milan