(I know the questions are stupid but just to confirm)
You:
Downloaded the sources
for wx you ./configure (that ran for forever)
(Configured wxWidgets 2.8.12 for `armv6l-unknown-linux-gnu')
make (runs for twice as long)
(mine is still going but I think the next steps were: - I will check again the morning)
Are things working up to this point?

export PKCS11_INC=/home/pi/crypto <this should be the directory of the headers you downloaded

then in truecrypt dir
make WX_ROOT=/home/pi/wx/ wxbuild <directory to wx
make WXSTATIC=1

Error: Error: The drive uses a sector size other than 512 bytes.
Due to limitations of components available on your platform, partition/device-hosted volumes on the drive can only be mounted using kernel cryptographic services.
Possible solutions:
- Enable use of the kernel cryptographic services (Preferences > System Integration).
- Use a drive with 512-byte sectors.
- Create a file-hosted volume (container) on the drive.

For everyone having trouble mounting their formatted containers, create the volume with NO filesystem. After that's done, mount the file with --filesystem=none, which will merely create a /dev/loop1 device. After that, use the common filesystem formatting tool for your desired filesystem (e.g. mkfs.ext4 /dev/loop1). After that, you should be able to mount it fine.

Thanks to everyone in this thread for helping me get this all working!

chrisprt wrote:For everyone having trouble mounting their formatted containers, create the volume with NO filesystem. After that's done, mount the file with --filesystem=none, which will merely create a /dev/loop1 device. After that, use the common filesystem formatting tool for your desired filesystem (e.g. mkfs.ext4 /dev/loop1). After that, you should be able to mount it fine.

Thanks to everyone in this thread for helping me get this all working!

How do I know what the /dev/loop# number is? Is there a way to list the "active" loop devices or something like that?

If I kill the input (strg+x) there is an empty truecrypt1 and if I try to mount it again using truecrypt, it says it's already mounted.
The device is a complete encrypted extern hdd with NTFS (formatted in Windows, truecrypt).

chrisprt wrote:For everyone having trouble mounting their formatted containers, create the volume with NO filesystem. After that's done, mount the file with --filesystem=none, which will merely create a /dev/loop1 device. After that, use the common filesystem formatting tool for your desired filesystem (e.g. mkfs.ext4 /dev/loop1). After that, you should be able to mount it fine.

Thanks to everyone in this thread for helping me get this all working!

How do I know what the /dev/loop# number is? Is there a way to list the "active" loop devices or something like that?

Thanks.

Sorry for the late reply, but you can use "df -h" to see the active loops.

After hours of trying to get it compiled, it appears there was some inconsistency using the latest version of PKCS11 preventing me from successfully doing make WXSTATIC=1 in the truecrypt sources directory. I returned to the same article we've all been using (http://reinhard-seiler.blogspot.com/201 ... ry-pi.html) and found the discrete "you can download them here" link which is a link to download the binary (already compiled) version.

To mount my encrypted drive, I now run the following (bypasses the device-mapper error):