DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: fauno <fauno@partidopirata.com.ar>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LVM on LUKS: volumes missing
Date: Tue, 31 May 2016 11:54:35 -0300	[thread overview]
Message-ID: <574DA5AB.4020406@partidopirata.com.ar> (raw)
In-Reply-To: <nik1e4$8ts$1@ger.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 869 bytes --]

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.


-- 
:{


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 585 bytes --]

  reply	other threads:[~2016-05-31 14:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 21:54 [dm-crypt] LVM on LUKS: volumes missing fauno
2016-05-31  7:53 ` Ondrej Kozina
2016-05-31 12:52 ` Robert Nichols
2016-05-31 14:54   ` fauno [this message]
2016-06-02 12:57     ` fauno
2016-06-02 18:31       ` Robert Nichols
2016-06-03 21:42       ` Arno Wagner
2016-06-03 22:46         ` Robert Nichols
2016-06-04  8:06           ` Arno Wagner
2016-06-07 14:24             ` fauno
  -- strict thread matches above, loose matches on Subject: below --
2016-05-30 21:26 fauno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=574DA5AB.4020406@partidopirata.com.ar \
    --to=fauno@partidopirata.com.ar \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox