All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: Clemens Fruhwirth <clemens@endorphin.org>
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: Sat, 30 Dec 2006 14:13:42 +0100	[thread overview]
Message-ID: <20061230131342.GF4981@deprecation.cyrius.com> (raw)
In-Reply-To: <87vejt64kc.wl%clemens@endorphin.org>

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

> dmsetup create mappingname dm-table-file
> 
> If that does not work, we are seeing a dm-crypt layer problem here.

This works:

foobar:~# cat map
0 1954808 crypt aes-cbc-essiv:sha256 a0671e89e060742caf3f9a3e7d762b24 0 /dev/sdb2 1032
foobar:~# dmsetup create x map
foobar:~# mount /dev/mapper/x /mnt
foobar:~# ls -l /mnt
total 20
drwx------ 2 root root 16384 Dec 30  2006 lost+found
-rw-r--r-- 1 root root     5 Dec 30  2006 x
foobar:~#

-- 
Martin Michlmayr
http://www.cyrius.com/

  reply	other threads:[~2006-12-30 13:13 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 [this message]
2007-01-02 17:00           ` Clemens Fruhwirth
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=20061230131342.GF4981@deprecation.cyrius.com \
    --to=tbm@cyrius.com \
    --cc=403426@bugs.debian.org \
    --cc=bdb-reportbug@forbidden.co.uk \
    --cc=clemens@endorphin.org \
    --cc=dm-devel@redhat.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.