From: Milan Broz <gmazyland@gmail.com>
To: a@xelera.eu, dm-crypt@saout.de
Subject: Re: [dm-crypt] luks container created on a system won't luksOpen on another
Date: Thu, 10 Sep 2015 16:14:39 +0200 [thread overview]
Message-ID: <55F1904F.3050401@gmail.com> (raw)
In-Reply-To: <20150910134700.GC27298@x12yad.0.lon.net.0x0b.net>
On 09/10/2015 03:47 PM, andrea rota wrote:
> hi,
>
> i recently created a new LUKS container via cryptsetup luksFormat on a
> workstation and migrated some data to it; when connecting the same HDD
> (eSATA) to a different box (a CuBox-i2eX) i am unable to luksOpen the
> container. i checked the dm-crypt FAQ and i must be missing something
> obvious as all the checks suggested there seem fine.
Hi,
it should work
This could be the problem I guess:
> name : __xts-aes-neonbs
...
So it is using NEON acceleration on ARM.
There was a bug in NEON kernel implementation, see
http://www.saout.de/pipermail/dm-crypt/2015-February/004632.html
Could you read that thread and try workaround I mentioned there?
http://www.saout.de/pipermail/dm-crypt/2015-February/004631.html
Milan
next prev parent reply other threads:[~2015-09-10 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 13:47 [dm-crypt] luks container created on a system won't luksOpen on another andrea rota
2015-09-10 14:14 ` Milan Broz [this message]
2015-09-10 15:19 ` andrea rota
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=55F1904F.3050401@gmail.com \
--to=gmazyland@gmail.com \
--cc=a@xelera.eu \
--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.