From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Thu, 10 Sep 2015 16:14:41 +0200 (CEST) Received: by wicfx3 with SMTP id fx3so24928777wic.0 for ; Thu, 10 Sep 2015 07:14:40 -0700 (PDT) References: <20150910134700.GC27298@x12yad.0.lon.net.0x0b.net> From: Milan Broz Message-ID: <55F1904F.3050401@gmail.com> Date: Thu, 10 Sep 2015 16:14:39 +0200 MIME-Version: 1.0 In-Reply-To: <20150910134700.GC27298@x12yad.0.lon.net.0x0b.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] luks container created on a system won't luksOpen on another List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: a@xelera.eu, dm-crypt@saout.de 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