Hmmm... Scott assigned this bug to the cryptsetup package, but I still believe it's an upstart / initscripts issue.
Cryptsetup does its job good, but I believe there is an order or synchronization issue with the way the initscripts or Upstart call cryptsetup / fsck / mount of encrypted filesystems (i.e. try to mount them before activating the encrypted volumes).
Hmmm... Scott assigned this bug to the cryptsetup package, but I still believe it's an upstart / initscripts issue.
Cryptsetup does its job good, but I believe there is an order or synchronization issue with the way the initscripts or Upstart call cryptsetup / fsck / mount of encrypted filesystems (i.e. try to mount them before activating the encrypted volumes).