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 DEVLINKS=/dev/mapper/Ubuntut-Oneiric_var_encrypted /dev/Ubuntu/Oneiric_var_encrypted /dev/block/253:14 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874774 Title: could not mount /dev/mapper/cryptswap1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/874774/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
