From: Milan Broz <gmazyland@gmail.com>
To: sven@whgl.uni-frankfurt.de
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Weird cryptsetup-1.6.x problem
Date: Thu, 29 Aug 2013 07:27:38 +0200 [thread overview]
Message-ID: <521EDBCA.3050100@gmail.com> (raw)
In-Reply-To: <6478140fa65e8ec766e267d6f2682e43.squirrel@ssl.verfeiert.org>
On 28.8.2013 23:48, Sven Eschenberg wrote:
> Hi List,
>
> After upgrading one of my systems I ran into the following rather strange
> problem:
>
> I use an initramfs which uses cryptsetup for the initial mapping, later
> during boot more mappings are added.
>
> After upgrading to a 1.6.x version of cryptsetup the system does boot
> fine, with old initramfs (still holding old cryptsetup), but a new kernel
> with updated cinitramfs won't boot. Unfortunately I don't have the exact
> same kernel with both initramfses at hand, so the kernel was upgraded too.
>
> cryptsetup fails and states command failed, code 22, which afaik means
> invalid parameter. That could indicate that something from the kernel is
> missing, but I checked back and AES, XTS, ripmed, dmcrypt target are all
> in the kernel (even not modular, to ease startup).
If it is kernel, there must be error message in syslog (use some kernel
parameter to display log to console, depends on used init system).
It looks like that some module is missing in initramfs...
(Unfortunately all I get from kernel device-mapper if it fails is -EINVAL,
that's why userspace cannot sometimes display better info.
Anyway, running cryptsetup with --debug can provide more info as well.
Milan
next prev parent reply other threads:[~2013-08-29 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 21:48 [dm-crypt] Weird cryptsetup-1.6.x problem Sven Eschenberg
2013-08-29 5:27 ` Milan Broz [this message]
2013-08-29 17:10 ` 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=521EDBCA.3050100@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=sven@whgl.uni-frankfurt.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.