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] Restored luks2 header to wrong drive!
Date: Tue, 5 May 2020 16:33:48 +0200	[thread overview]
Message-ID: <20200505143348.GA28077@tansi.org> (raw)
In-Reply-To: <CAMaNm6GM=xJy0QfyBgPvLyuJ0-BNm+Yo9xt3ewOw1gb1TASb_Q@mail.gmail.com>

Not so fast!

ext2/3/4 does several superblock backups over the whole drive and
the directories are also distributed (but not replicated). 
As the LUKS2 header is not that large, most data and structure 
should be recoverable.

First step: Make a sector-image of the drive. Only work on the copy.
Second step: Find out how to recover an ext4 with overwritten start.
     -> This is not the right mailing-list for that question.  
        But there should be fairly generic instruction out there.
        Maybe there is an ext2/3/4 FAQ or recovery HOWTO?   

Regards,
Arno

On Tue, May 05, 2020 at 15:39:07 CEST, Default User wrote:
>    Well, thank you for your reply Michael.
>    Now I guess there is nothing left to do but grieve.
>    It is too late for me, but maybe someday, computer backups and
>    encryption will be "less art and more science".
>    Just a note: maybe LUKS could someday add a feature that would check
>    before restoring a luks2 header, and alert the user that they are
>    trying to restore to a different disk than the header was backed up
>    from, or to a disk that does not appear to contain LUKS encrypted
>    data.
>    : (

> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> https://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:[~2020-05-05 14:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05  3:07 [dm-crypt] Restored luks2 header to wrong drive! Default User
2020-05-05  9:20 ` Michael Kjörling
2020-05-05 13:39   ` Default User
2020-05-05 13:51     ` Robert Nichols
2020-05-05 13:57     ` Milan Broz
2020-05-05 14:00     ` Carlos E. R.
2020-05-05 14:33     ` Arno Wagner [this message]
2020-05-05 16:29 ` Chris Murphy
2020-05-05 16:50   ` Default User

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=20200505143348.GA28077@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.