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] Open raid1 with luks encryption after a raid re-create
Date: Mon, 23 Nov 2015 04:35:04 +0100	[thread overview]
Message-ID: <20151123033504.GA12468@tansi.org> (raw)
In-Reply-To: <565241FF.90005@whgl.uni-frankfurt.de>

On Sun, Nov 22, 2015 at 23:30:23 CET, Sven Eschenberg wrote:
[...]
> Now to your question, once you know the offset of the header:
> 1.)Setup a loop device from your image (You can use an offset into
> the image where your loop device starts with sector 0) see --offset
> in losetup man page.

Ah, yes. That would save copying it.

> Inspect loopdevice if the LUKS Header now is on sector 0
> 2.)Try a cryptsetup luksopen in readonly mode

Good idea. With that it may be reasonaly safe to work
with the original disk. I still would make a full
backup before.

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

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

  reply	other threads:[~2015-11-23  3:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 16:29 [dm-crypt] Open raid1 with luks encryption after a raid re-create Luis Alexandre
2015-11-21 18:49 ` Arno Wagner
     [not found]   ` <5651B1CF.7090306@sapo.pt>
2015-11-22 12:52     ` Arno Wagner
2015-11-22 15:05       ` Luís Alexandre
2015-11-22 18:15         ` Arno Wagner
2015-11-22 22:30         ` Sven Eschenberg
2015-11-23  3:35           ` Arno Wagner [this message]
2015-11-23  3:56             ` Sven Eschenberg
2015-11-23  6:26               ` Arno Wagner
2015-11-24 11:15                 ` Luis Alexandre
2015-11-24 12:52                   ` Arno Wagner
2015-11-25 11:49                   ` Sven Eschenberg
2015-11-21 19:05 ` Sven Eschenberg

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=20151123033504.GA12468@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.