You are not logged in.

#1 2011-02-12 09:58:07

legolas558
Member
Registered: 2009-09-08
Posts: 97

Cannot mount Truecrypt volume (device-mapper error)

I have a 1TB external USB disk (externally powered) and I have created 3 partitions on it:

Disk /dev/sdb: 1000.2 GB, 1000202043392 bytes
255 heads, 63 sectors/track, 121600 cylinders, total 1953519616 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048   696322047   348160000    7  HPFS/NTFS
/dev/sdb2      1683384320  1744824319    30720000   83  Linux
/dev/sdb3      1744824320  1953517567   104346624    7  HPFS/NTFS

The last partition, /dev/sdb3, has been formatted with Truecrypt 7.0a and I'd like to mount it, but truecrypt reports the following error:

device-mapper: reload ioctl failed: No such file or directory
Command failed

I am getting the same error with my custom kernel and with stock Arch Linux kernel; what can it be? Can somebody please help me to narrow down this issue?

Thanks


.-.   ,---,---.--.
| |__  \ \ \ \`//.
`----'`--'`--'`--'

Offline

#2 2011-02-12 09:58:48

legolas558
Member
Registered: 2009-09-08
Posts: 97

Re: Cannot mount Truecrypt volume (device-mapper error)

Also running dmsetup ls as root after the above-mentioned error will result in:

sudo dmsetup ls
truecrypt1_1    (254, 0)
truecrypt1_0    (254, 1)


.-.   ,---,---.--.
| |__  \ \ \ \`//.
`----'`--'`--'`--'

Offline

#3 2011-02-12 19:07:15

metzengerstein
Member
Registered: 2010-06-04
Posts: 60

Re: Cannot mount Truecrypt volume (device-mapper error)

Can you post the output of "dmsetup info /dev/mapper/truecrypt1_1" and the same with truecrypt1_0 ?
Sure you are trying to mount the mapping instead of the encrypted device (/dev/sdb3)?

Offline

#4 2011-02-15 06:18:11

legolas558
Member
Registered: 2009-09-08
Posts: 97

Re: Cannot mount Truecrypt volume (device-mapper error)

Ehm..I am trying to mount the device (/dev/sdb3), not the mapper! Although I can see that with file-based truecrypt container the mapper gets mounted. Shan't truecrypt create the mapper and mount that for me in case I select a device?

This is the information of the two mappings created (2_0 and 2_1 since I had already mounted a file-based container):

Name:              truecrypt2_0
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        0
Event number:      0
Major, minor:      254, 2
Number of targets: 1

Name:              truecrypt2_1
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        1
Event number:      0
Major, minor:      254, 1
Number of targets: 1

None of them gets mounted after I get the mentioned error; maybe truecrypt is expecting a dm feature which I have not enabled in my kernel?


.-.   ,---,---.--.
| |__  \ \ \ \`//.
`----'`--'`--'`--'

Offline

Board footer

Powered by FluxBB