From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from v6.tansi.org (ns.km31936-01.keymachine.de [87.118.116.4]) by mail.server123.net (Postfix) with ESMTP for ; Wed, 20 Aug 2014 11:09:57 +0200 (CEST) Received: from gatewagner.dyndns.org (77-57-44-24.dclient.hispeed.ch [77.57.44.24]) by v6.tansi.org (Postfix) with ESMTPA id 62E4220DC1EA for ; Wed, 20 Aug 2014 11:09:57 +0200 (CEST) Date: Wed, 20 Aug 2014 11:09:56 +0200 From: Arno Wagner Message-ID: <20140820090956.GA25262@tansi.org> References: <20140819195134.GB18215@tansi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dm-crypt] "not a valid LUKS device" after distro change List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On Wed, Aug 20, 2014 at 00:22:29 CEST, John Wells wrote: > Thanks for your response. This is the result of luksDump on the container: > > # cryptsetup luksDump /dev/FINALFRONTIER_VG/HOME_LV > Device /dev/FINALFRONTIER_VG/HOME_LV is not a valid LUKS device. Ah, sorry. Did not see that access completely failed. That means the header was at least partially overwritten. Can you post or send me a hex-dump of the first 1024 bytes of this device and the other one? Command to do so is, e.g. head -c 1024 /dev/FINALFRONTIER_VG/HOME_LV | hd This will not compromise your security. > I will try to find the time to recreate the entire scenario. Do you think > the current container I'm able to open is at risk of corruption as well? Yes. Something seems to be running amok. Another queston: After Fedora 20 told you both were not valid LUKS devices, could you still open the one in Ubuntu that you could open before? Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718 ---- A good decision is based on knowledge and not on numbers. - Plato