From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.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 be00Xc-enin5 for <dm-crypt@saout.de>;
 Sun, 15 Jan 2012 15:13:10 +0100 (CET)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Sun, 15 Jan 2012 15:13:09 +0100 (CET)
Received: from int-mx12.intmail.prod.int.phx2.redhat.com
 (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25])
 by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q0FED8NF032549
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
 for <dm-crypt@saout.de>; Sun, 15 Jan 2012 09:13:08 -0500
Received: from [10.36.7.52] (vpn1-7-52.ams2.redhat.com [10.36.7.52])
 by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id
 q0FED72V020877
 for <dm-crypt@saout.de>; Sun, 15 Jan 2012 09:13:08 -0500
Message-ID: <4F12DEF2.4040403@redhat.com>
Date: Sun, 15 Jan 2012 15:13:06 +0100
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <CAMYA1yNp_j1aTjqyO1mM5rkZiE=fk7AySjNvHgSLKqFEh29isA@mail.gmail.com>
 <20120114211722.GA31590@tansi.org>
In-Reply-To: <20120114211722.GA31590@tansi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Problem recovering encrypted partitions
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: dm-crypt@saout.de

On 01/14/2012 10:17 PM, Arno Wagner wrote:

> first thing is to check that the LUKS headers are still there:
>
>    cryptsetup isLuks<device>

Just nitpicking - I would better suggest to use

blkid -p <device>

It will also detect crypto but also it will print if
there is some other signature.

You should see something like

# blkid -p /dev/sda2
/dev/sda2: UUID="..." VERSION="1" TYPE="crypto_LUKS" USAGE="crypto" ...

(-p means bypass cache, for old blkid just remove this switch
if not supported)

Milan