Silk Road forums

try it without the capitalization. if that still fails, type ls -a and paste the output here

actually scratch that, do this:


cd /Applications/TrueCrypt.app/Contents/MacOS (or whatever the path is for you)
ln -s TrueCrypt /usr/local/bin/truecrypt (optional but lets you call truecrypt from other directories)

now you can use the truecrypt commands from before probably:

truecrypt --restore-headers /path/to/the/usb/device (edit: I think you must type TrueCrypt if you skipped the ln -s step)

I think he is either typing the commands wrong somehow, or they are in a different format on OSX. I think his USB device is still fine because Truecrypt must have detected it for him to attempt to mount it. If recovering the header from the embedded backup doesn't work, when we find out how to do that on OSX, then you can try to mount it without a filesystem and repair it. If that doesn't work I give up.

also make sure you are not capitalizing truecrypt or anything...

I think mac is actually based on BSD kernel

try this limitless:

truecrypt -m headerbak /dev/usb_device_name

yes enter the command in terminal

truecrypt --restore-headers /path/to/the/usb/device

perhaps you could just put the name of the USB device , on Linux it would be something like

truecrypt --restore-headers /media/device_name

also note that truecrypt has no - in front of it

First thing is to try and mount it read only, it looks like that can work in some cases. Select it in truecrypt as normal, but when you get to the password input section, click on the options button. This expands some additional things, check mount volume as read only. That will possibly let you access the content on the USB. If it does, I suggest storing it to an encrypted file container temporarily, and then formatting the USB device and re-encrypting it with truecrypt, making sure to select some filesystem that is compatible with whatever OS you are using, then you can put your content back on it and wipe the temporary encrypted file container. That is the first thing to try anyway. It looks like it can also be caused by corruption, in which case you may be fucked unfortunately. It also looks like it can be caused by trying to mount a filesystem that is not compatible with your operating system. That is just what I can gather from a quick google search, let me know how that works for you and if it doesn't I will try to find something else for you to try.

There was another study that showed that study was actually inconclusive for some reason. Looks like we need more studies.