On 03/30/2010 08:52 PM, Ali Reza Sajedi wrote: > Hello All, > > upgrading from cryptsetup 1.0.6 to 1.1.0 has led to the above message > everytime I attempt to unlock the device. > > There are many discussions going on on the matter in various forums. > However, unfortunately, I couldn't find a solution to switch out the > message. Does it work after that message? (If you run with --debug, do you see that operation was repeated successfully?) If so, some udev rule is doing something nasty. Again. you can try kill udev and try to reproduce - I bet it will work without problem. The usual problem is that some udev rules are written such way, that run scan of device on every event. And they even try to scan internal keyslot device. If you want experiment: - run cryptsetup luksOpen with --debug - run udevadm monitor and try to identify which rule is triggered and locks the device (Usualy it is blkid reacting to some event.) Check if there is some filtering on temporary cryptsetup device. Check if there is "+watch" which generates events when device is closed. Try to disable these lines. Recent packages should be "fixed". Submit bug to your distro to package which owns this rule... (udev, DeviceKit-disks aka udisks or so) Unfortunatelly discussion with udev developers is currently not too helpful. Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
