All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens-Michael Hoffmann <jmho@jmho.de>
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 18:18:23 +0200	[thread overview]
Message-ID: <4450852.6uU5N70hFn@slipstream> (raw)
In-Reply-To: <2467145.0Six7fUZOk@slipstream>

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]

> 
> 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.

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?


kind regards,
Jens-Michael


[-- Attachment #2: Type: text/html, Size: 3118 bytes --]

  reply	other threads:[~2013-04-23 16:18 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 [this message]
2013-04-23 18:09       ` 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=4450852.6uU5N70hFn@slipstream \
    --to=jmho@jmho.de \
    --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.