Table of Contents

Software

Java

Firefox

TrueCrypt

Mounting an encrypted NTFS volume under Linux can be a bit problematic. For starters, unlike in Windows, when you do not dismount your volume properly under Linux it gets corrupted very easily. The next time you mount it you will see it only as read-only. However, that is still the easier problem, because at least you see that the volume is read-only and the solution is simple: try to mount the volume in TrueCrypt under Windows and Windows will ask you if it should fix the file system errors. Windows' NTFS tools are much better at this than Linux's, so let Windows fix the errors.

The other problem is when the volume looks to be writable, but any write attempt is met with a Permission denied message. The problem here is the NTFS driver under Linux. You need to install ntfs-3g and then tell TrueCrypt to use it (note the missing dash in the ebuild name):

emerge -av ntfs3g

You can let TrueCrypt know it should use ntfs-3g in two ways. From the command line you can pass it along as the –filesystem parameter (together with a few other useful flags):

truecrypt --filesystem=ntfs-3g --fs-options="sync,utf8,uid=$UID,umask=0007" /path/to/truecrypt/volume /path/to/mount/point

However, while TrueCrypt has a Mount Options field where you could write this as well, if you do you will be greeted with an error message saying something about “bad fs, bad option.” Therefore, if you want to mount a read-write NTFS volume via the TrueCrypt GUI, simply create a symlink in /sbin named mount.ntfs that links to mount.ntfs-3g:

cd /sbin
sudo ln -s mount.ntfs-3g mount.ntfs

The next time you mount your NTFS volume through the GUI it will be fully writable.

 
software.txt · Last modified: 2009/09/15 06:29 by marco1475
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki