From: Clemens Fruhwirth <clemens@endorphin.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: 403426@bugs.debian.org, dm-devel@redhat.com,
Brian Brunswick <bdb-reportbug@forbidden.co.uk>
Subject: Re: Bug#403426: kernel corrupts LUKS partition header on arm
Date: Tue, 02 Jan 2007 18:00:07 +0100 [thread overview]
Message-ID: <87odph5ppk.wl%clemens@endorphin.org> (raw)
In-Reply-To: <20061230131342.GF4981@deprecation.cyrius.com>
At Sat, 30 Dec 2006 14:13:42 +0100,
Martin Michlmayr <tbm@cyrius.com> wrote:
>
> * Clemens Fruhwirth <clemens@endorphin.org> [2006-12-30 11:50]:
> > > Is there anything else I should try?
> > > foobar:~# cryptsetup luksOpen /dev/sda5 x
> > > Enter LUKS passphrase:
> > > device-mapper: table: 254:0: crypt: Device lookup failed
>
> Strange. I haven't changed cryptsetup but now I don't get this
> message anymore. I simply get:
>
> foobar:~# cryptsetup luksOpen /dev/sdb2 x
> Enter LUKS passphrase:
> Enter LUKS passphrase:
> Enter LUKS passphrase:
> Command failed: No key available with this passphrase.
>
> But I'm sure I've typed the passphrase correctly, and it works on my
> x86 box (on which I created the LUKS partition).
Does luksDump report the same things on both architecture?
--
Fruhwirth Clemens - http://clemens.endorphin.org
for robots: sp4mtrap@endorphin.org
next prev parent reply other threads:[~2007-01-02 17:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061217022906.2434.60658.reportbug@LKG8A754B.example.org>
2006-12-20 16:15 ` Bug#403426: kernel corrupts LUKS partition header on arm Martin Michlmayr
2006-12-29 10:52 ` Clemens Fruhwirth
2006-12-29 16:38 ` Martin Michlmayr
2006-12-29 20:24 ` Martin Michlmayr
2006-12-30 10:50 ` Clemens Fruhwirth
2006-12-30 13:13 ` Martin Michlmayr
2007-01-02 17:00 ` Clemens Fruhwirth [this message]
2007-01-02 18:04 ` Martin Michlmayr
2007-01-02 18:34 ` Clemens Fruhwirth
2007-01-03 16:59 ` Clemens Fruhwirth
2007-01-03 19:14 ` Martin Michlmayr
2007-01-03 19:32 ` Clemens Fruhwirth
2007-01-03 19:37 ` Martin Michlmayr
2007-01-04 11:56 ` Clemens Fruhwirth
2007-01-04 15:09 ` Martin Michlmayr
2007-01-05 8:36 ` Gordon Farquharson
2007-01-05 9:59 ` Martin Michlmayr
2007-01-06 6:38 ` Gordon Farquharson
2007-01-07 5:47 ` Gordon Farquharson
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=87odph5ppk.wl%clemens@endorphin.org \
--to=clemens@endorphin.org \
--cc=403426@bugs.debian.org \
--cc=bdb-reportbug@forbidden.co.uk \
--cc=dm-devel@redhat.com \
--cc=tbm@cyrius.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.