Re: [dm-crypt] dm-crypt hanging on attempts to manipulate an encrypted device

[Milan Broz <mbroz@redhat.com>]

On 04/18/2010 01:17 PM, Pedro Fernandes Macedo wrote:
> I have a 1TB USB disk that I use for backups and has recently hit a
> snag.  The encrypted device was working fine, but it now is failing on a
> weird way: after plugging it in yesterday and doing a luksOpen,
> the "automatic header conversion from 0.99 to 0.991 triggered" message
> appeared. After that, every single attempt at opening the device or add
> keys hangs after the key is entered. This is a device that was in use
> all the time and was working until I unplugged it (for safety) for some
> changes to my raid setup. 

The automatic upgrade of version indicates that header was created
with old version of cryptsetup...

Do you remember which cryptsetup was used to format device?
(Or version of distro release, if it is CentOS, I'll check it.)

> MK iterations:  0

This is wrong and something very bad happened with the header.
Anyway, if the keyslots are ok, it can be probably still fixed easily.

> This is on Centos 5.4 64 bit, cryptsetup-luks-1.0.3-5.el5 (and no custom
> packages; all from the original repository).

Please can you report this to upstream bugzilla (bugzilla.redhat.com,
cryptsetup-luks component)?

I'll try to help you there, if the code is misinterpreting some old metadata
it must be fixed both upstream and in RHEL (and I can handle both together
if problem is understood).

But I will need binary copy of header
dd if=/dev/<your_luks_device> of=/backup.img bs=512 count=1032

(If you agree, please submit that bug for RHEL5.4 and send me
the header - best in private mail, or encrypted using my gpg key,
id is 0xBB21822F on keyservers)

(and probably I will need your help to test passphrase later)

Milan
--
mbroz@redhat.com