[Pkg-cryptsetup-devel] Bug#403426: kernel corrupts LUKS partition header on arm

[Clemens Fruhwirth]

At Fri, 29 Dec 2006 21:24:34 +0100,
Martin Michlmayr <tbm at cyrius.com> wrote:
> 
> * Clemens Fruhwirth <clemens at endorphin.org> [2006-12-29 11:52]:
> > Please try the version from subversion
> > http://luks.endorphin.org/svn/cryptsetup
> 
> With 1.0.4 plus the attached 2 patches from SVN I no longer get any
> corruption but I also cannot access my encrypted data.  

That's good :)

> 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
> device-mapper: ioctl: error adding target to table
> device-mapper: ioctl: device doesn't appear to be in the dev hash table.
> Failed to setup dm-crypt key mapping.
> Check kernel for support for the aes-cbc-essiv:sha256 cipher spec and verify that /dev/sda5 contains at least 133 sectors.
> Failed to read from key storage

Are you sure we don't see any device mapper problems here? You might
just go over to a box where LUKS works (when the LUKS partition does
not contain anything security relevant to you), and do

dmsetup table mappingname > dm-table-file

open it up, and find the 7th entry that says something like x:y
(major:minor device number of your underlaying device). Replace this
by your correct device path on the arm box, copy that file over to arm
and set it up as

dmsetup create mappingname dm-table-file

If that does not work, we are seeing a dm-crypt layer problem here.

> Enter LUKS passphrase:

I just commited a patch that prevents password retrying with I/O
errors.
-- 
Fruhwirth Clemens - http://clemens.endorphin.org 
for robots: sp4mtrap at endorphin.org