From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <htd@fancy-poultry.org>
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9])
	by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Thu, 27 Aug 2009 16:52:27 +0200 (CEST)
Date: Thu, 27 Aug 2009 16:57:03 +0200
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20090827145703.GA11409@fancy-poultry.org>
References: <edb9e59e5c4f859db5b16ace4e9d92ff.squirrel@webmail.kapps.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <edb9e59e5c4f859db5b16ace4e9d92ff.squirrel@webmail.kapps.fr>
Subject: Re: [dm-crypt] volume unrecognized
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 27.08.2009, Jacques-Olivier KAPPS wrote: 

> Now I can map the device with luksOpen, but the volume itself is
> unrecognized.

Maybe the underlying filesystem got corrupted.

> I certainly can open the device with luksOpen because I choosed the same
> password in the installation process, but my guess is that the ubuntu
> installer erased and replaced the luks headers of my partition by new
> ones, what do you think?

That would explain the whole situation. When the partition gets prepared
via LUKS/dmcrypt, the filesystem is gone, and you'll have to format again.

> Do you have any advice?

Recreate the partition by using the latest backup. You have one, right?