From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Thu, 2 Jun 2016 20:32:12 +0200 (CEST) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1b8XPc-0004RT-55 for dm-crypt@saout.de; Thu, 02 Jun 2016 20:32:08 +0200 Received: from c-50-158-72-35.hsd1.il.comcast.net ([50.158.72.35]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Jun 2016 20:32:08 +0200 Received: from rnicholsNOSPAM by c-50-158-72-35.hsd1.il.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 02 Jun 2016 20:32:08 +0200 From: Robert Nichols Date: Thu, 2 Jun 2016 13:31:53 -0500 Message-ID: References: <574CB690.5030401@partidopirata.com.ar> <574DA5AB.4020406@partidopirata.com.ar> <57502D55.5060700@partidopirata.com.ar> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <57502D55.5060700@partidopirata.com.ar> Subject: Re: [dm-crypt] LVM on LUKS: volumes missing List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 06/02/2016 07:57 AM, fauno wrote: > On 31/05/16 11:54, fauno wrote: >> On 31/05/16 09:52, Robert Nichols wrote: >> >>> Take a look at the decrypted volume with "hexedit -s". It should start >>> out with mostly binary zeros with a little data including the ASCII >>> string "LVM2" at the start of a few of the sectors. Starting at about >>> the 10th sector there should be a lot of ASCII text. (It's a copy of the >>> corresponding file in /etc/lvm/backup, though without the fancy >>> formatting.) >>> >>> If you're seeing random-appearing binary junk there, then the volume is >>> not be decrypted properly. If it's just some of the early sectors that >>> are clobbered and the text starting at the 10th sector is intact, then >>> this should be recoverable. >>> >> >> i've tried reading `hexedit` both on the closed and opened partition and >> everything seems to be random junk. `strings` also can't find anything >> resembling LVM data. > > i'm guessing silence means no one wants to give me the bad news :P By any chance did you reboot into a kernel different from the one that was running before? If so, try the old kernel. In the past, there was a kernel change that affected a non-default LUKS option (whirlpool hash). It's a long shot, but so is anything else at this point. Let's look at about the only other thing that's correctable, and that would be a damaged partition table that has the partition starting in the wrong place. Does the output from "fdisk -l" for that drive look reasonable? If you look at the sectors with "hexedit -s", does the randomness start with the sector where that partition is supposed to begin? -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.