Re: luks container created on a system won't luksOpen on another

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt



[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux