[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1463
  • Last Modified:

Invalid argument error - TrueCrypt on Linux Mint

Hello,

I needed a cross platform file encryption system for Windows 7 and Linux Mint, so I tried TrueCrypt.

I created an encrypted file-type volume under Win 7, and can mount read, write and dismount the volume. All good.

Copied the encrypted file to Linux Mint.

I can't mount it using TrueCrypt in Mint, I get the following error after successfully getting past the requests for the decryption password and then admin password:

"device-mapper: resume ioctl failed: Invalid argument. Command Failed"
0
LarryZ
Asked:
LarryZ
  • 5
  • 2
1 Solution
 
pjedmondCommented:
This is possibly because your Linux Mint Distro is trying to use a kernel module to mount the partition.

Try adding :

-m=nokernelcrypto

to your TrueCrypt command line?

Might be useful if you give the full command line that you are using, plus whether you are using a fully encrypted drive or merely an encrypted file?
0
 
LarryZAuthor Commented:
Thank you pjedmond. I had already tried -m=nokernelcrypto, after seeing it online somewhere.

I have just determined that the error was caused by an excessive size of the TrueCrypt file/volume.  I had sized it at 10 GB in Win 7, but my entire Linux virtual machine was only 8 GB. I noticed that the TrueCrypt file size was much smaller when moved to Linux. I guess the move truncated the encrypted file without notifying me.  If I create a 4 GB TrueCrypt file in Win 7, it seems to move to Linux okay and will successfully mount in TrueCrypt.
0
 
LarryZAuthor Commented:
I am still having some Linux permissions issues with the TrueCrypt file though. I'll post a comment here later if needed.
0
When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot has fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

 
LarryZAuthor Commented:
I have two profiles in Linux Mint. Both are Administrator profiles.

Profile 1 was used to install Linux Mint and its password works for superuser.
Profile 2 (wife) was added by Profile 1 shortly thereafter.

If I create a 2 GB TrueCrypt file-based volume when logged in as Profile 1, and place it in Profile 1's document folder, I can mount it, and add or delete files.

If I try to copy or move it to Profile 2's document folder, I can't mount it. TrueCrypt accepts the encryption pw, but won't accept either Profile 1's pw or Profile 2's pw when asking for the user or admin password.

If I create another 2 GB TrueCrypt file-based volume when logged in as Profile 2, and place it in Profile 2's document folder, I can't mount it either. TrueCrypt accepts the encryption pw, but won't accept either Profile 1's pw or Profile 2's pw when asking for the user or admin password.

I'd like to get TrueCrypt working in Linux Mint Profile 2, since all the files to be encrypted reside there.

Any help would be appreciated.
0
 
LarryZAuthor Commented:
For the benefit of others that may have the same problem, I have done more research and found a solution.

The fix is to first create a new user group called truecrypt, and add users Profile 1 and Profile 2 to it.

Next use "sudo visudo" in a terminal window to edit the file to give TrueCrypt the root privileges it needs to mount the container.

See  https://www.linuxquestions.org/questions/linux-software-2/truecrypt-cant-obtain-root-privileges-655139/
0
 
LarryZAuthor Commented:
I did not get a solution from experts this time, although EE has been extremely helpful on previous postings. Thanks.
0
 
pjedmondCommented:
Ooops - should have got back to you on this one. If the truecrypt file is being truncated, that implies an issue with one of the file systems involved.

FAT32 typically has a 4GB size limit, so it may be that although it worked on Windows you were not using all of the container, and the bit that you needed to read was OK. However attempting to copy it over failed at the 4GB point resulting in a corrupt file.

It coult also be a BIOS limitation as well on one or other of the systems.

Just a thought?
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now