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. If i wait long enough before entering the password for the root partition it always works, if i am to fast most of the time it does not. I checked the code in my initrd and there is a call to udevsettle to wait until everything is ready, shouldn't it wait for loaded modules, too?
-- 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 bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
