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 GOYrUrX9FE0M for <dm-crypt@saout.de>;
 Sun, 16 Dec 2012 11:50:01 +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 11:49:59 +0100 (CET)
Received: by mail-ee0-f50.google.com with SMTP id b45so2887401eek.37
 for <dm-crypt@saout.de>; Sun, 16 Dec 2012 02:49:59 -0800 (PST)
Message-ID: <50CDA753.3020403@gmail.com>
Date: Sun, 16 Dec 2012 11:49:55 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <002801cdd971$867e5310$937af930$@nexus-informatik.ch>
 <50CD9351.1060800@gmail.com>
In-Reply-To: <50CD9351.1060800@gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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: =?ISO-8859-1?Q?Javier_Juan_Mart=EDnez_Cabez=F3n?= <tazok.id0@gmail.com>
Cc: dm-crypt@saout.de, philipp@nexus-informatik.ch

On 12/16/2012 10:24 AM, Javier Juan Mart=EDnez Cabez=F3n wrote:
>=20
> I think I answer too fast before, sorry.
>=20
> Did strings answer something known in the device?
>=20
> Are you sure that this is true?   aes-xts-essiv:sha256
> Which cipher did you use with cryptsetup 1.1?

Please do not confuse it even more, this is LUKS, not plain device
where default cipher changed.

So it is LUKS and if there was no header rewrite, parameters are correct,
(there was no reformat and cipher parameter is in LUKS header).

If it is properly unlocked, master key is correct as well.

So I guess there were no LUKS format and dmcrypt had no obvious problems
in this kernel, I would say, the problem is not in this layer.

cryptsetup userspace should not be problem, to verify it
run dmsetup table --showkeys and compare output with old/new version
- if it is same there is definitely no problem in
userspace / LUKS


So IMHO the problem is in MD layer, ext4, or in some unexpected device
rewrite during update or so.

- check syslog, mainly time before/after upgrade.
Maybe it was broken already there.=20

- check blkid -p on the device - does it detect some known signature?

- boot to old kernel, does it work? Or it is broken?

(And read the FAQ, there is a lot of other hints.)

>>> md126 : active raid0 sda5[0] sdb5[1]
>>> 5832190976 blocks super 1.2 512k chunks
...

>>> cryptsetup luksDump /dev/md126

So this is your device, RAID0. Read first kb and
check what's there now with blkid etc.

Milan