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] "not a valid LUKS device" after distro change
Date: Wed, 20 Aug 2014 11:09:56 +0200	[thread overview]
Message-ID: <20140820090956.GA25262@tansi.org> (raw)
In-Reply-To: <CADt3ZtscYzfFb2nhAfz8VYwMFf0jzWx8w5OzycfX2h7oaaPe9A@mail.gmail.com>

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

  reply	other threads:[~2014-08-20  9:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 20:58 [dm-crypt] "not a valid LUKS device" after distro change John Wells
2014-08-19 19:51 ` Arno Wagner
2014-08-19 22:22   ` John Wells
2014-08-20  9:09     ` Arno Wagner [this message]
2014-08-20 16:18       ` John Wells
2014-08-20 21:15         ` Arno Wagner
2014-08-21 14:00           ` John Wells
2014-08-21 14:25             ` Robert Nichols
2014-08-21 15:55               ` John Wells
2014-08-21 16:13                 ` Jonas Meurer
2014-08-21 20:46                   ` John Wells
2014-08-21 22:54                     ` Arno Wagner
2014-08-22  3:52                       ` John Wells
2014-08-22  5:30                     ` Heinz Diehl
2014-08-22 11:46                       ` Arno Wagner
2014-08-22  9:08                     ` Jonas Meurer
2014-08-22 11:55                       ` Arno Wagner
2014-08-22 12:55                         ` Jonas Meurer
2014-10-28 15:34                           ` John Wells
2014-10-28 15:35                             ` John Wells
2014-10-28 18:34                               ` Arno Wagner
2014-10-28 23:03                             ` Jonas Meurer
2014-10-29  0:57                               ` Arno Wagner
2014-10-29 23:49                             ` Sven Eschenberg
2014-10-30  0:37                               ` John Wells
2014-08-21 17:01                 ` Robert Nichols
2014-08-21 14:29             ` Arno Wagner

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=20140820090956.GA25262@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.