[arch-general] can't unlock a luks encrypted partition. (urgent).

[Xavier]

On Tue, Oct 13, 2009 at 11:04 PM, Hussam Al-Tayeb <ht990332 at gmail.com> wrote:
>>
>> Nice. I suggest you upgrade to 1.1.0rc2 then (changes to the PKGBUILD
>> should be trivial). I hope it won't break anything for you further. If
>> the problem stays away with 1.1.0, that is solution enough for me. If it
>> returns, we need to really find out what's wrong.
>>
> Done! I updated to 1.1.0-rc2 then I also upgraded to kernel 2.6.31.4
> After rebooting, things are still fine. /dev/sdb1 unlocked correctly :)
>

Could you check the upstream issues to find if one matches your case ?
http://code.google.com/p/cryptsetup/issues/list?can=1&q=&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary&cells=tiles

It seems there are a few issues related to udev and some locking or
racing conditions :
http://code.google.com/p/cryptsetup/issues/list?can=1&q=udev&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary&cells=tiles

I looked at all your mails, and it seems you never showed exactly what
the output of cryptsetup was when it failed.

It's good to know it's fixed in 1.1.0-rc2 but it would be better to know why.