Forums
Main Category
General (Technical,...
Truecrypt Volume mo...
 
Notifications
Clear all

Truecrypt Volume mounting issue

 
Page 2 / 2
General (Technical, Procedural, Software, Hardware etc.)
Last Post by farmerdude 17 years ago
16 Posts
8 Users
0 Reactions
2,017 Views
RSS
 kovar
(@kovar)
Prominent Member
Joined: 18 years ago
Posts: 805
30/01/2008 8:21 am  

Greetings,

I can host it for you. I'll pm my email address to you. Jamie can host some documents as well, though he might need to create a section for this one.

-David


   
ReplyQuote
 gmarshall139
(@gmarshall139)
Reputable Member
Joined: 21 years ago
Posts: 378
30/01/2008 9:51 am  

http//www.truecrypt.org/docs/

Just scroll down to "linux version"


   
ReplyQuote
iruiper
 iruiper
(@iruiper)
Estimable Member
Joined: 19 years ago
Posts: 145
Topic starter 30/01/2008 4:31 pm  

I had already read those documents, and I followed their instructions without success ( I was able to create a volume inside a file (not using the whole partition), but I kept having the mounting trouble!

I am beginning to believe that the problem is about Helix and not about TrueCrypt itself. Has anybody tried to mount a TrueCrypt volume in Helix?

And coming back to the issue about the naming convention for mounting the device, my Helix mapped the volume as sda (and not sda1) maybe because it was a very small pendrive. When I use bigger storage devices they are always mapped following the naming convention you guys have been talking about. However, with this /media/sda I could access the files, create new ones, etc. so I don't think the problem had anything to do with the physical device mounting process.

Any more thoughts? Thanks for your collaboration!


   
ReplyQuote
 Bregan
(@bregan)
Active Member
Joined: 18 years ago
Posts: 6
04/06/2008 2:47 pm  

Hi,

Sorry for pulling out an old post. However, personally i have had issues mounting truecrypt volumes created using version 5.2 and trying to open them with an older version of truecrypt. 4.3 for this instance. Version 4.3 was unable to detect the truecrypt volume created by version 5.2

From my understanding, the truecrypt version in Helix is version 4.3. And the windows version of truecrypt you used may be a newer version.

Hope this helps

Regards,
Bregan


   
ReplyQuote
iruiper
 iruiper
(@iruiper)
Estimable Member
Joined: 19 years ago
Posts: 145
Topic starter 16/06/2008 8:49 pm  

The problem underneath was that I couldn't even create a new container under Helix. Did anyone eventually get to do it?


   
ReplyQuote
 farmerdude
(@farmerdude)
Estimable Member
Joined: 20 years ago
Posts: 242
25/06/2008 9:32 pm  

Hi iruiper,

Have you read the documents for TrueCrypt and Linux? I don't know which version of Helix you are using, but it is well known and documented that TrueCrypt and the 2.6.18 Linux kernel do not play nice together. If your version of Helix is using the 2.6.18 Linux kernel then this may be the source of your frustration.

Try a newer boot CD that has a new Linux kernel perhaps?

Cheers!

farmerdude

http//www.forensicbootcd.com

http//www.onlineforensictraining.com


   
ReplyQuote
Page 2 / 2
Forum Jump:
  Previous Topic
Next Topic  

Currently viewing this topic 2 guests.

Share: