From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from v4.tansi.org (ns.km33513-03.keymachine.de [87.118.94.3]) by mail.saout.de (Postfix) with ESMTP for ; Mon, 4 Jul 2011 23:10:25 +0200 (CEST) Received: from gatewagner.dyndns.org (84-74-166-21.dclient.hispeed.ch [84.74.166.21]) by v4.tansi.org (Postfix) with ESMTPA id 08EB0205E01 for ; Mon, 4 Jul 2011 23:10:25 +0200 (CEST) Date: Mon, 4 Jul 2011 23:10:24 +0200 From: Arno Wagner Message-ID: <20110704211024.GC16539@tansi.org> References: <20110704154523.GA21034@apartia.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110704154523.GA21034@apartia.fr> Subject: Re: [dm-crypt] /dev/md1 is not a valid LUKS device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On Mon, Jul 04, 2011 at 05:45:23PM +0200, Louis-David Mitterrand wrote: > Hi, > > After a hardware crash I now get this error: > > root@grml ~ # cryptsetup isLuks /dev/md1 > Device /dev/md1 is not a valid LUKS device > > Am I basically fucked? I assume you have no header backup? If so, possibly, but not necessarily. Is this on an SSD? There the LUKS header could be in the same "sector" as a data area (due large SSD actual sector size) Can you send me the first 700 bytes of the partition as hexdump? You can get them for example like this: hd /dev/md1 | head -n 40 Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier