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: Fri, 22 Aug 2014 13:55:16 +0200	[thread overview]
Message-ID: <20140822115516.GC3837@tansi.org> (raw)
In-Reply-To: <53F708A8.8050705@freesources.org>

On Fri, Aug 22, 2014 at 11:08:56 CEST, Jonas Meurer wrote:
> Hi John, 
> Am 21.08.2014 um 22:46 schrieb John Wells:
[...]
> As Arno already wrote, the hexdump from your meant-to-be LUKS container
> on HOME_LV in FINALFRONTIER_VG doesn't look too promising. I've never
> heard about 'GNU Parted Loopback 0' before, but it sounds like something
> caused Parted to overwrite your LUKS header.

Not necessarily. The other container had that in it the one time as 
well, but it fixed itself ...
 
> Last hope is to find the LUKS header with an offset on the partition.
> Try to search for 'LUKS' by grepping the output of 'strings
> /dev/FINALFRONTIER_VG/HOME_LV'. If you don't find the string 'LUKS'
> followed by something describing your cipher and hash algorithm, I fear
> that this second partition is lost.

I second searching for that. It may not be the only way though.
Easy way to search:

hd <partition> | grep "LUKS"

That gives you hex offset(s) to examine further. 

> According to your hexdump it's not astonishing at all that neither of
> the distros do recognize the FINALFRONTIER_VG/HOME_LV logical volume as
> LUKS container. It simply doesn't start with a LUKS header.
> 
> The question rather is: what action resulted in the LUKS header being
> overwritten. In the past the partition configuration in the Ubuntu
> installer was kind of confusing, and some people trashed their existent
> LUKS containers by reformatting them as new LUKS container, but it
> doesn't look like that happened to you.

I think it is configuration mis-detection and with a randomized
component.
 
> I don't want to join the rant against modern Linux distros, LVM and MD-1
> format here. In fact there've been quite some serious bugs in Linux
> (vanilla kernel, userspace tools as well as distro implementations) in
> the past, and ranting about how fucked up everything is today compared
> to the good all days doesn't help to fix them. I prefer to isolate,
> identify and fix the bugs and improve the user experience that way :)

I am not ranting about bugs, I am ranting about broken architecture
and KISS violations. Having seens some commercial software 
source code, I do know that there, it often is even worse. There
are just to many peiople creating software that are not good at
it, and FOSS is really no exception.

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-22 11:55 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
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 [this message]
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=20140822115516.GC3837@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.