Comment 3 for bug 154679

Same problem here since the upgrade to gutsy. Luks volumes can only be mounted the first time the device is connected, subsequent attempts fail with "special device /dev/mapper/luks_crypto_(...) does not exist".

After manually creating the device mapper device, e.g. with

# cryptsetup luksOpen /dev/sdb3 secure

the /dev/mapper/secure volume is automatically mounted correctly.

I think the problem is also not related to the volume having the same device name for every connect in gutsy. For me feisty behaved the same way: my external harddrive was always accessible as /dev/sdb, no matter how often I reconnected it.