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 Wy9q65LgRQAw for <dm-crypt@saout.de>;
 Sun, 16 Dec 2012 19:35:02 +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 <dm-crypt@saout.de>; Sun, 16 Dec 2012 19:35:01 +0100 (CET)
Received: by mail-ee0-f50.google.com with SMTP id b45so3021347eek.37
 for <dm-crypt@saout.de>; Sun, 16 Dec 2012 10:35:01 -0800 (PST)
Message-ID: <50CE1452.20406@gmail.com>
Date: Sun, 16 Dec 2012 19:34:58 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <002801cdd971$867e5310$937af930$@nexus-informatik.ch>
 <50CD9351.1060800@gmail.com> <50CDA753.3020403@gmail.com>
 <CALceyLEx70of8AFkKZgGXGQDhmA4VNbvGHkrrFpsiD9_aFkRXQ@mail.gmail.com>
In-Reply-To: <CALceyLEx70of8AFkKZgGXGQDhmA4VNbvGHkrrFpsiD9_aFkRXQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Can't mount my LUKS crypted disk after kernel update
 / reboot
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: Philipp Durrer <philipp@nexus-informatik.ch>
Cc: dm-crypt@saout.de

On 12/16/2012 07:11 PM, Philipp Durrer wrote:

> dmsetup table --showkeys

Hm, I should said do compare but do NOT send this to list
(it contains volume key).

You should reencrypt your devices now...
(including truecrypt device you have mapped, because they are no longer
secure)

> unknown partition table doesn't look good to me, but I can see this error for other md drives aswell.

That's fine, it should be LUKS device without partition
(this message is misleading and should be removed from kernel IMO)

I thihk LUKS/dmcrypt  works as expected here, something was corrupted in MD or ext4.


> I did check the keyslot with the keyslot_checker in misc, did report that everything looks fine.
> Did aswell check the disk with hd tool and looks fine aswell all random data up to 0x20000 where data begins.

check plain (unlocked) luks device as well, maybe you will see some pattern
which explains that why overwritten (it apparently missing ext4 or any known signature
to blkid)

Milan