From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Thu, 2 Dec 2010 18:04:05 +0100 (CET) Message-ID: <4CF7D181.7020907@redhat.com> Date: Thu, 02 Dec 2010 18:04:01 +0100 From: Milan Broz MIME-Version: 1.0 References: <4CF7AA62.2060601@mbjr.hu> <4CF7C759.4030305@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Is partial LUKS recovery possible? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mario 'BitKoenig' Holbe Cc: dm-crypt@saout.de On 12/02/2010 05:28 PM, Mario 'BitKoenig' Holbe wrote: > Milan Broz wrote: >> On 12/02/2010 04:45 PM, Mario 'BitKoenig' Holbe wrote: >>> It is not easy to check if your dm-crypt mapping is correct (i.e. feeded >>> with the correct key, the correct device offset, etc.) if, like in your >>> case, there is damage in the beginning of the partition - that decrypts >> If you know, that there was an fs, it is easy, just run >> blkid -p /dev/mapper/ >> and it should detect fs signature. > > Nope. blkid just probes the primary superblock, which is damaged if the > beginning of the partition is damaged. Ah so, I should read it properly. You can probably use offset option in blkid, so it scans for backup superblock but that is not so easy. Milan