Thanks for finally answering, but why do you say so? I don't see the same error message anywhere in that thread, and the other bug is quite old. My problem started in Intrepid.
Here are some additional details I can think of. The most interesting thing is probably that this does not happen consistently. Any ideas what might cause the drive to mount correctly about half the times and not mount at other times? When the error pops-up, the drive is LUKS-opened correctly, it is possible to manually mount it like "sudo mount /dev/mapper/luks_crypto_ac639614-9758-4555-9c97-90d4796d9c8b /mnt". However, "gnome-mount -vbd /dev/mapper/luks_crypto_ac639614-9758-4555-9c97-90d4796d9c8b" gives the following output: gnome-mount 0.8 ** Message: Given device '/dev/mapper/luks_crypto_ac639614-9758-4555-9c97-90d4796d9c8b' is not a volume or a drive. Output of "sudo fdisk -l /dev/sdb": Disk /dev/sdb: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x5b6ac646 Device Boot Start End Blocks Id System /dev/sdb1 1 38913 312568641 c W95 FAT32 (LBA) Can this be a problem? The partition is marked as "W95 FAT32 (LBA)" (I didn't change it, this is how it was supplied), but I encrypted the partition (not the whole drive) and formatted the encrypted partition as ReiserFS. -- "special device /dev/dm-0 does not exist" when mounting an encrypted drive https://bugs.launchpad.net/bugs/296750 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
