I was wrong: sha1 didn't solved it really. I now have all modules loaded that i
need (new ones loop, cbc and blkcipher) were missing and now it works one day
and the other day not.
Seems to me like some kind of race condition between loading the modules and
crytosetups try to open the device.
For me, loading the module sha1 solved the problem completely.
Maybe anyone else can confirm that
--
fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
https://bugs.launchpad.net/bugs/91405
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
