can not mount cryptsetup drive

Asked by Tien Nguyen

Binary package hint: cryptsetup

I understand that this is bug report forum, but I think this could be a bug so I choose to post it here.

I just got into mounting problem with one of my encrypted USB pen drive. I do not remember what happened but I use to be able to mount the drive OK after entering the password. Now the mount failed. Here is the output of my "cryptsetup status"

/dev/mapper/luks_crypto_1044ef9b-e035-4a2c-83af-1b5168beb581 is active:
cipher: aes-cbc-essiv:sha256
keysize: 128 bits
device: /dev/mmcblk0p1
offset: 1032 sectors
size: 7951080 sectors
mode: read/write

Here is the result of mount command:

sudo mount /dev/mapper/luks_crypto_1044ef9b-e035-4a2c-83af-1b5168beb581 ~/fs/tmp
mount: you must specify the filesystem type

I can suck it in and reformat but I would like to learn how to deal with this problem. So far I found one other incident reported here:

http://ubuntuforums.org/showthread.php?p=6755311#post6755311

Regards,

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu cryptsetup Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #331040.

Revision history for this message
Daniel Hahler (blueyed) said :
#1

Does /dev/mapper/luks_crypto_1044ef9b-e035-4a2c-83af-1b5168beb581 contain a valid filesystem after all?
Try "sudo fdisk -l /dev/mapper/luks_crypto_1044ef9b-e035-4a2c-83af-1b5168beb581" to get a partition table eventually.

Revision history for this message
Tien Nguyen (tienhn) said :
#2

It is EXT3 Linux file system. Here is the fdisk output:

Disk /dev/mapper/luks_crypto_1044ef9b-e035-4a2c-83af-1b5168beb581: 4070 MB, 4070952960 bytes
255 heads, 63 sectors/track, 494 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000f3806

                                                        Device Boot Start End Blocks Id System
/dev/mapper/luks_crypto_1044ef9b-e035-4a2c-83af-1b5168beb581p1 1 494 3968023+ 83 Linux

Revision history for this message
Daniel Hahler (blueyed) said :
#3

Thanks for reporting back, setting as Triaged.
Please provide any more info that would be useful, like e.g. your Ubuntu version and the version of the involved packages.

Revision history for this message
Tien Nguyen (tienhn) said :
#4

I am using Ubuntu 8.10 on 64 bit platform. The system is completely up to date with the latest kernel etc.

Please let me know any specific info or log file that you would like me to provide. Will be happy to post them.
Thanks,

Revision history for this message
Tien Nguyen (tienhn) said :
#5

Here is a screen shot of the gparted error message.

Revision history for this message
Reinhard Tartler (siretart) said :
#6

sorry, but this bug report is not helpful at all.

"[I] do not remember what happened but I use to be able to mount the drive OK after entering the password. Now the mount failed."

To me this looks like you either damanaged your filesystem or re-run 'cryptsetup create' on your device. In either case, without exact instructions how to reproduce the problem, there is nothing we can do for you.

I'm therefore converting this issue to a launchpad question.

Revision history for this message
Launchpad Janitor (janitor) said :
#7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.