FS#20417 - [truecrypt] 7 '--filesystem=ntfs-3g' Option Not Working
Attached to Project:
Arch Linux
Opened by Natanji (Natanji) - Monday, 09 August 2010, 10:11 GMT
Last edited by Paul Mattal (paul) - Monday, 27 September 2010, 02:13 GMT
Opened by Natanji (Natanji) - Monday, 09 August 2010, 10:11 GMT
Last edited by Paul Mattal (paul) - Monday, 27 September 2010, 02:13 GMT
|
Details
Description:
Since upgrading Truecrypt 6.3a-1 -> 7.0-1, the following command: truecrypt --filesystem=ntfs-3g /dev/sda1 /mnt/tc produces this error message: Unknown option: ntfs-3g The command has worked fine until now and is required to mount NTFS volumes (wuthout it, truecrypt tries to mount the volume as FAT32). I guess most Truecrypt volumes are NTFS, so this is a very serious problem. Additional info: * package version(s): 7.0-1 Steps to reproduce: Try mounting a NTFS volume with --filesystem=ntfs or --filesystem=ntfs-3g. |
This task depends upon
Closed by Paul Mattal (paul)
Monday, 27 September 2010, 02:13 GMT
Reason for closing: Fixed
Additional comments about closing: This is resolved in truecrypt 7.0a, now in [extra].
Monday, 27 September 2010, 02:13 GMT
Reason for closing: Fixed
Additional comments about closing: This is resolved in truecrypt 7.0a, now in [extra].
truecrypt /.../volume.tc /media/truecrypt1
I.e. excluding the filesystem type. Does it work for you?
A workaround seems to be to mount the truecrypt container without mounting the filesystem, then mount the /dev/mapper/truecryptX device manually using mount -t ntfs-3g /dev/mapper/truecryptX /mnt/<wherever>.