View previous topic :: View next topic |
Author |
Message |
petterg Guru
Joined: 25 Mar 2004 Posts: 500 Location: Oslo, Norway
|
Posted: Mon Feb 10, 2014 10:30 am Post subject: [Solved] Truecrypt mount fail |
|
|
I installed a new server last week. The issue I have with it is that it fails to mount truecrypt containers.
(It seemed to successfully create the volume.)
First try to mount looks like this:
Code: |
~ # truecrypt -t -v /home/tc/test.tc /root/tc
Enter password for /home/tc/test.tc:
Enter keyfile [none]:
Protect hidden volume (if any)? (y=Yes/n=No) [No]:
Error: device-mapper: reload ioctl on truecrypt1 failed: Invalid argument
Command failed
|
To work around that I try with a mountoption:
Code: |
~ # truecrypt -t -m=nokernelcrypto -v /home/tc/test.tc /root/tc
Enter password for /home/tc/test.tc:
Enter keyfile [none]:
Protect hidden volume (if any)? (y=Yes/n=No) [No]:
Error: mount: /dev/loop0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
~ # dmsg
[48587.841008] device-mapper: table: 254:0: crypt: unknown target type
[48587.841015] device-mapper: ioctl: error adding target to table
[48604.269164] EXT2-fs (loop0): error: can't find an ext2 filesystem on dev loop0.
[48604.269341] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[48604.269450] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[48604.269616] FAT-fs (loop0): invalid media value (0x24)
[48604.269626] FAT-fs (loop0): Can't find a valid FAT filesystem
[48604.269748] FAT-fs (loop0): invalid media value (0x24)
[48604.269751] FAT-fs (loop0): Can't find a valid FAT filesystem
[48604.270278] EXT2-fs (loop0): error: can't find an ext2 filesystem on dev loop0.
[48604.270371] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[48604.270459] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[48604.270547] FAT-fs (loop0): invalid media value (0x24)
[48604.270550] FAT-fs (loop0): Can't find a valid FAT filesystem
[48604.270637] FAT-fs (loop0): invalid media value (0x24)
[48604.270640] FAT-fs (loop0): Can't find a valid FAT filesystem
[48604.272585] ISOFS: Unable to identify CD-ROM format.
[48604.272804] NTFS-fs warning (device loop0): is_boot_sector_ntfs(): Invalid boot sector checksum.
[48604.272815] NTFS-fs error (device loop0): read_ntfs_boot_sector(): Primary boot sector is invalid.
[48604.272818] NTFS-fs error (device loop0): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[48604.272822] NTFS-fs error (device loop0): ntfs_fill_super(): Not an NTFS volume.
|
What am I missing?
(Error is exactly the same, no matter if the truecrypt container is created using ext2, ext3, ext4 or fat.)
Last edited by petterg on Tue Feb 11, 2014 11:24 am; edited 1 time in total |
|
Back to top |
|
|
Greens n00b
Joined: 23 Aug 2013 Posts: 27
|
Posted: Mon Feb 10, 2014 1:46 pm Post subject: |
|
|
Not sure on the answer, but if you have the choice you should use dm-crypt/LUKS, far more standardized and gets more support with Linux. |
|
Back to top |
|
|
petterg Guru
Joined: 25 Mar 2004 Posts: 500 Location: Oslo, Norway
|
Posted: Mon Feb 10, 2014 11:05 pm Post subject: |
|
|
Thanks for the idea. However I struggle to find information if dm-crypt/luks will do what I'm looking for: I need one encryptet container for each user, that the user will be able to mount (and unmount) in his home area without having root access. Is there a way to do so with dm-crypt? |
|
Back to top |
|
|
petterg Guru
Joined: 25 Mar 2004 Posts: 500 Location: Oslo, Norway
|
Posted: Tue Feb 11, 2014 11:24 am Post subject: |
|
|
Solved by enabling cryptoloop block device in kernel config.
Still I'm open to alternatives to truecrypt |
|
Back to top |
|
|
mhogomchungu n00b
Joined: 18 May 2013 Posts: 19
|
Posted: Sun Feb 16, 2014 8:32 pm Post subject: |
|
|
petterg wrote: | Thanks for the idea. However I struggle to find information if dm-crypt/luks will do what I'm looking for: I need one encryptet container for each user, that the user will be able to mount (and unmount) in his home area without having root access. Is there a way to do so with dm-crypt? |
yes,zuluCrypt[1] can do that.
By default,the mount point that will be used is "/run/media/private/$USER" where "USER" is a user's username.The mount point will be private to the user who opened the volume.It is also possible to set a compile time switch to have the mount point in user's home directories.
zuluCrypt is designed to be used by normal users without requiring a root's password.
[1] http://code.google.com/p/zulucrypt/ |
|
Back to top |
|
|
shi^Yo n00b
Joined: 22 Oct 2004 Posts: 9 Location: Cyprus
|
Posted: Sun Apr 13, 2014 8:08 pm Post subject: Thanksb |
|
|
Thanks for coming back for the solution!
petterg wrote: | Solved by enabling cryptoloop block device in kernel config.
|
|
|
Back to top |
|
|
|