All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LVM on LUKS: volumes missing
Date: Fri, 3 Jun 2016 23:42:20 +0200	[thread overview]
Message-ID: <20160603214220.GC6423@tansi.org> (raw)
In-Reply-To: <57502D55.5060700@partidopirata.com.ar>

One thing is that these problems are pretty hard to debug.
Another is that LVM massively complicates things.

Now, if the LUKS container opens cleanly, anything
in it should be decrypted correctly (if it is LVM
atop of LUKS) and decryption with the wrong key is
not actually a possibility. 

That also means you should be able to use LVM
recovery techniques (I assume they exist) on this.

Unfortunately, I cannot help you with LVM as I do not use 
it. I consider it a badly engineered, overly complicated 
thing that decreases reliablity and makes problem 
diagnostics very hard.  Unfortunately, it provides some
increases in convenience and that seems to be all most people
care about, atleast until they are confronted with the hard
realities of reliable engineering, namely that KISS
is more important than any other concern. As LVM
violates that (along with the new RAID superblock
formats, udev, systemd and some other engineering 
abominations that have found their way into mainstream
Linux recently) I do not tolerate LVM on any of my
systems. 

Regards,
Arno


On Thu, Jun 02, 2016 at 14:57:57 CEST, 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
> 
> 
> -- 
> :D
> 




> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt


-- 
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

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  parent reply	other threads:[~2016-06-03 21:42 UTC|newest]

Thread overview: 19+ 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  7:53   ` [linux-lvm] " Ondrej Kozina
2016-05-31 13:17   ` fauno
2016-06-02 13:22     ` Ondrej Kozina
2016-06-02 13:39       ` fauno
2016-06-02 13:52         ` fauno
2016-06-02 14:50         ` Zdenek Kabelac
2016-06-02 15:09           ` fauno
2016-06-02 15:20             ` Zdenek Kabelac
2016-05-31 12:52 ` Robert Nichols
2016-05-31 14:54   ` fauno
2016-06-02 12:57     ` fauno
2016-06-02 18:31       ` Robert Nichols
2016-06-03 21:42       ` Arno Wagner [this message]
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=20160603214220.GC6423@tansi.org \
    --to=arno@wagner.name \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.