The failure is caused by the upstart and cryptsetup scripts trying to match the DEVNAME against /etc/crypttab entries that are in DEVLINKS format. E.g:
Upstart's "/etc/init/cryptdisks-udev.conf" passes the environment variable DEVNAME to crypttab_start_one_disk() in "/lib/cryptsetup/cryptdisks.functions".
Unless "/etc/crypttab" has an entry for "/dev/dm-14" the match will fail. It would be unwise to use /dev/dm-14" in 'crypttab' since the disk-mapper is dynamically allocated and could change.
I've fixed it with a few additional lines that tries to match against any of the DEVLINKS. I'll attach a patch and a debdiff here later once I've fixed some other bugs on that system.
The failure is caused by the upstart and cryptsetup scripts trying to match the DEVNAME against /etc/crypttab entries that are in DEVLINKS format. E.g:
DEVNAME=/dev/dm-14 /dev/mapper/ Ubuntut- Oneiric_ var_encrypted /dev/Ubuntu/ Oneiric_ var_encrypted /dev/block/253:14
DEVLINKS=
Upstart's "/etc/init/ cryptdisks- udev.conf" passes the environment variable DEVNAME to crypttab_ start_one_ disk() in "/lib/cryptsetu p/cryptdisks. functions" .
Unless "/etc/crypttab" has an entry for "/dev/dm-14" the match will fail. It would be unwise to use /dev/dm-14" in 'crypttab' since the disk-mapper is dynamically allocated and could change.
I've fixed it with a few additional lines that tries to match against any of the DEVLINKS. I'll attach a patch and a debdiff here later once I've fixed some other bugs on that system.