From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] After reboot: "Command failed with code 22: Device /dev/md2 is not a valid LUKS device."
Date: Tue, 23 Apr 2013 20:09:06 +0200 [thread overview]
Message-ID: <20130423180906.GA19435@tansi.org> (raw)
In-Reply-To: <4450852.6uU5N70hFn@slipstream>
On Tue, Apr 23, 2013 at 06:18:23PM +0200, Jens-Michael Hoffmann wrote:
> >
> > Just out of curiosity: Is the cipher and key size combination (aes-xts-
> > plain64, 256 bit) the default or why did I have not to specify it to create
> > the mapping? (IIUC the metadata of plain mappings is not stored?)
>
> Never mind, I just realized that that was part of the destroyed luks device,
> so I guess the default cipher/key size of "cryptsetup create" is used now.
Indeed.
> Is there perhaps any way for converting the plain mapping into a luks
> mapping or would I just have to create a new luks device and copy data
> over?
While theoretically such a conversion may be possible, you
would have to write the converter yourself. So yes, copying
to a new LUKS container is the way to go.
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
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
prev parent reply other threads:[~2013-04-23 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 15:13 [dm-crypt] After reboot: "Command failed with code 22: Device /dev/md2 is not a valid LUKS device." Jens-Michael Hoffmann
2013-04-23 15:52 ` Arno Wagner
2013-04-23 16:08 ` Jens-Michael Hoffmann
2013-04-23 16:18 ` Jens-Michael Hoffmann
2013-04-23 18:09 ` Arno Wagner [this message]
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=20130423180906.GA19435@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.