Unable to mount volume on lunix with latest versions
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
Hello,
When I try to mount my encrypted volume using veracrypt versions post 1.17 I get the following error(see attached image)!
But I can mount the same volume using veracript 1.17 or 1.16!!
I've tried several linux distributions but I get the same error with versions above 1.17.
What's wrong?
Last edit: Brahim 2018-08-10
This is a strange issue and it would mean that something was introduced
in 1.18 that broke compatibility with your volume. I don't recall seeing
a similar issue and I don't see what can be the cause but we will try to
find out.
First, what version of VeraCrypt did you use to create the volume? Is it
possible for you to share the encryption algorithm and the hash PRF used
to create the volume?
Also, are you mounting a file container or a disk partition?
Is it possible for you for try to mount the volume on a Windows machine?
Did you try mounting the volume using cryptsetup? Since version 1.67,
cryptsetup supports mounting VeraCrypt volumes.
With your answers, hopefully we can understand the situation better.
Thank you for your answer.
1- I don't remember the version I've used to create the volume, but I think it was either 1.16 or 1.17. For the algorithm, it's AES(Twofish(Serpent)) and the hash PRF it's SHA-512 (See Attached screenshot with all infos);
2- It's a file container;
3- I can mount the volume in windows (scrrenshot captured in windows) and in linux I can mount it with veracrypt 1.16/1.17. I haven't treid to mount the volume using cryptsetup.
As a test, I created a new volume in windows using veracrypt 1.22 but I can't mount it using the same version on linux!!!
Regards
Last edit: Brahim 2018-08-11
Problem Solved..
The issue was caused by the 'tc" extension in the file's name, by removing this extension I can now mount the volume..
It's strange why it can be mounted in windows with this extension and not in Linux?!!
Thank Mounir IDRASSI for your help.
Glad to see that you found the cause.
Indeed, if the file container has .tc extension, VeraCrypt on Linux,
starting from version 1.20, automatically checks "TrueCrypt Mode"
checkbox in the password dialog to accelerate things for TrueCrypt users
and certainly you didn't notice that it was checked and that's why the
mount failed.
The easiest solution is to simply uncheck the "TrueCrypt Mode" in the
password dialog or as you did avoid using .tc extension altogether.
Thank you for your support, And Thank you for this great App.