From: Ondrej Kozina <okozina@redhat.com>
To: Felix Wagner <felix@wagner-felix.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] help
Date: Thu, 25 Feb 2016 17:18:00 +0100 [thread overview]
Message-ID: <56CF2938.2010102@redhat.com> (raw)
In-Reply-To: <20160225160849.21765320@othir.localdomain>
Hi Felix,
don't loose all hope yet!
On 02/25/2016 04:08 PM, Felix Wagner wrote:
> So i thought well It didn't work so lets try again:
>
> cryptsetup-reencrypt -v -c
> aes-xts-plain64 /dev/disk/by-uuid/2ea1bb9e-a4a0-48c8-bc67-a694fa6c8cf7
> Reencryption will change: volume key, set cipher to aes-xts-plain64.
> Enter passphrase for key slot 0:
> Key slot 0 unlocked.
> LUKS header
> backup of device /dev/disk/by-uuid/2ea1bb9e-a4a0-48c8-bc67-a694fa6c8cf7
> created.
^^^^^^^^
First of all, you actually may have the LUKS header backup! The
cryptsetup-reencrypt created one for you automatically. Look for
LUKS-foobar.org file in the directory where you initiated the
cryptsetup-reencrypt.
If... (well rather big fat _IF_ because this is really important) the
reencryption didn't write any data yet you may restore your LUKS header
using the .org backup created by cryptsetup-reencrypt.
But again _don't_ do the header recovery unless you're 100% sure that
reencryption didn't write (aka already reencrypted) any ciphertext
sectors! So, what's in your reencrypt log file (look for LUKS-foobar.log
in same directory where is also the header backup)?
Regards
Ondra
next prev parent reply other threads:[~2016-02-25 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 15:08 [dm-crypt] help Felix Wagner
2016-02-25 16:18 ` Ondrej Kozina [this message]
2016-02-25 17:25 ` Ondrej Kozina
2016-02-25 16:37 ` Milan Broz
2016-02-25 17:05 ` Felix Wagner
2016-02-25 17:20 ` Milan Broz
2016-02-25 17:35 ` Felix Wagner
2016-02-25 17:49 ` Felix Wagner
2016-02-25 17:55 ` Milan Broz
2016-02-25 17:58 ` Felix Wagner
-- strict thread matches above, loose matches on Subject: below --
2016-02-25 14:50 Felix Wagner
2016-01-10 17:07 Eugen Rogoza
2012-04-20 15:58 [dm-crypt] Help Simon Bing
2012-04-22 8:59 ` 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=56CF2938.2010102@redhat.com \
--to=okozina@redhat.com \
--cc=dm-crypt@saout.de \
--cc=felix@wagner-felix.com \
/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.