All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Wells <jbwellsiv@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] "not a valid LUKS device" after distro change
Date: Wed, 20 Aug 2014 12:18:33 -0400	[thread overview]
Message-ID: <CADt3ZtscbX-rmMt++aXme9Oiu3sxiBW_MD_CGJM_b=t+iMaerQ@mail.gmail.com> (raw)
In-Reply-To: <20140820090956.GA25262@tansi.org>

[-- Attachment #1: Type: text/plain, Size: 5188 bytes --]

Thanks Arno.

Something definitely looks amiss:
$ sudo   head -c 1024 /dev/FINALFRONTIER_VG/HOME_LV | hd
00000000  47 4e 55 20 50 61 72 74  65 64 20 4c 6f 6f 70 62  |GNU Parted
Loopb|
00000010  61 63 6b 20 30 00 00 00  00 00 00 00 00 00 00 00  |ack
0...........|
00000020  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
*
00000400

$ sudo head -c 1024 /dev/MORE_VG/MORE_LV  | hd
                                                                         ��ޭ
00000000  4c 55 4b 53 ba be 00 01  61 65 73 00 00 00 00 00
 |LUKS....aes.....|
00000010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000020  00 00 00 00 00 00 00 00  78 74 73 2d 70 6c 61 69
 |........xts-plai|
00000030  6e 36 34 00 00 00 00 00  00 00 00 00 00 00 00 00
 |n64.............|
00000040  00 00 00 00 00 00 00 00  73 68 61 31 00 00 00 00
 |........sha1....|
00000050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000060  00 00 00 00 00 00 00 00  00 00 10 00 00 00 00 40
 |...............@|
00000070  4e 94 98 c0 51 a9 25 bb  74 73 88 a4 a7 6e c7 d3
 |N...Q.%.ts...n..|
00000080  6f 18 71 fa 94 9a f4 5e  d1 e8 5b 1a 34 3a 9f 9f
 |o.q....^..[.4:..|
00000090  1d 79 1f 61 f5 dd 98 09  e1 d6 2e ed c4 29 af 1a
 |.y.a.........)..|
000000a0  23 c9 59 da 00 00 77 a1  36 63 63 31 38 38 64 62
 |#.Y...w.6cc188db|
000000b0  2d 63 63 64 62 2d 34 63  38 66 2d 39 37 62 32 2d
 |-ccdb-4c8f-97b2-|
000000c0  65 34 31 31 39 38 65 63  36 65 34 34 00 00 00 00
 |e41198ec6e44....|
000000d0  00 ac 71 f3 00 01 df d7  79 85 dd f0 29 59 98 63
 |..q.....y...)Y.c|
000000e0  0b 69 80 fe 48 61 8c 40  5b 3b 57 0f 82 9c ae 90  |.i..Ha.@
[;W.....|
000000f0  36 57 45 e2 03 82 26 c5  00 00 00 08 00 00 0f a0
 |6WE...&.........|
00000100  00 00 de ad 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000110  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000120  00 00 00 00 00 00 00 00  00 00 02 00 00 00 0f a0
 |................|
00000130  00 00 de ad 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000140  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000150  00 00 00 00 00 00 00 00  00 00 03 f8 00 00 0f a0
 |................|
00000160  00 00 de ad 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000170  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000180  00 00 00 00 00 00 00 00  00 00 05 f0 00 00 0f a0
 |................|
00000190  00 00 de ad 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
000001a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
000001b0  00 00 00 00 00 00 00 00  00 00 07 e8 00 00 0f a0
 |................|
000001c0  00 00 de ad 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
000001e0  00 00 00 00 00 00 00 00  00 00 09 e0 00 00 0f a0
 |................|
000001f0  00 00 de ad 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000200  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000210  00 00 00 00 00 00 00 00  00 00 0b d8 00 00 0f a0
 |................|
00000220  00 00 de ad 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000230  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|
00000240  00 00 00 00 00 00 00 00  00 00 0d d0 00 00 0f a0
 |................|
00000250  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
 |................|

Yes, even though Fedora 20 will mount neither volume, Ubuntu 14.04 will
mount the /dev/MORE_VG/MORE_LV partition.

Thanks,
John


On Wed, Aug 20, 2014 at 5:09 AM, Arno Wagner <arno@wagner.name> wrote:

> 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
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>

[-- Attachment #2: Type: text/html, Size: 6626 bytes --]

  reply	other threads:[~2014-08-20 16:18 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
2014-08-20 16:18       ` John Wells [this message]
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='CADt3ZtscbX-rmMt++aXme9Oiu3sxiBW_MD_CGJM_b=t+iMaerQ@mail.gmail.com' \
    --to=jbwellsiv@gmail.com \
    --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.