error message at boot "udev-event: unable to create db file [...]

Bug #83719 reported by Ulrich Lukas
2
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: udev

I'm using dm-crypt / cryptsetup an up-to-date Feisty installation.

After the latest upgrade, there is an error message displayed at boot after I type in the passphrase for the first "early crypto disc" (/etc/init.d/cryptdiscs-early).

The message says:
"udevd-event[2492]: udev_db_add_device: unable to create db file '/dev/.udev/db/block@dm-0': No such file or directory"

When I cd to the directory "/dev/.udev/db/", "ls -l block@dm-0" shows: "/dev/.udev/db/block@dm-0 -> mapper/sdata"

The subdirectory "/dev/.udev/db/mapper" to which the symlink points doesn't exist.

Who/which process/script/package creates that directory? Are there some udev-rules broken in the latest package?
If I create the directory "/dev/.udev/db/mapper" manually, it disappears after a reboot.

Tags: rejected
Revision history for this message
Ulrich Lukas (ulrich-lukas) wrote :

Just annother observation:

When I issue the cryptsetup command like this: "cryptsetup luksDelKey /dev/sda1 5"
(to erase keyslot no. 5), the program asks for "any remaining LUKS passphrase".

When I type in a correct passphrase, the command works as expected (although slower than before the latest upgrade). But when I provide a wrong passphrase, the following error message appears which seems related to the issue:

"Warning: /dev/.static/dev/mapper/temporary-cryptsetup-9322,rendezvous: wait for udev processing timed out"

Revision history for this message
Ulrich Lukas (ulrich-lukas) wrote :

OK, today's upgrade fixed this.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.