Veracrypt running for long time

I am trying to decrypt a 1GB partition in external drive encrypted using veracrypt. I think there might be some problems. I first ran with an incorrect password, I did not get any response that the password is wrong but the decryption process was running for more than 10 mins. I realized I entered wrong password, cancelled the process and started a new process with correct password and its running for more than 10 mins now.

I installed veracrypt on debian 12 minimal. I am using the veracrypt 1.26.7 command line tool.

  1. Shouldn’t veracrypt complain that I am using wrong password when I use one? The process keeps running whatever password I enter.
  2. Is there any way to check validity of my password without having to decrypt the partition.
  3. I am assuming that it should not take more than 10 mins to decrypt 1GB of partition. What are the factors impacting the decryption speed?

(Edit) 4. The qube has 4 cores but the veracrypt process is using only one core. I could see that the CPU consumption is 25%. Is there any way to force veracrypt to use more cores? Would it speedup the process?

It depends on how did you encrypt the drive.
You could configure key derivation function to be such that it’d take an hour to decrypt the partition.
It’s used against brute-force attacks:
Key derivation function - Wikipedia

@apparatus Thank you for the response. Is there any way for me to know if the password is correct. I used two different passwords and both times, the process was running for a long time without any feedback.

There is no way to check if the password is correct except for decrypting the drive.

Did you successfully decrypt your veracrypt drive before? In your Qubes OS or in another system? How much time did it take?

@apparatus I created the partition few months ago. I don’t remember decrypting it.

It seems that only one core is fully loaded,
Can you check the process that is consuming the CPU using top in qube’s terminal? Maybe it’s not veracrypt?
Based on this the veracrypt should support parallelization by default:
VeraCrypt - Free Open source disk encryption with strong security for the Paranoid
So I don’t know what’s happening. Maybe it’s stuck somewhere due to a bug.

I did use top. it shows 99% for veracrypt which is one processor. The overall CPU consumption is 25% (1 out of 4).

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                                               
    787 root      20   0   13212   5008   4352 R  99.7   0.1  49:30.84 veracrypt

I guess you can try to specify all the encryption options so it won’t try to find the correct ones itself:

You cannot tell which hash algorithm was used for key derivation. Even VeraCrypt itself does not know. When you type in a password, VeraCrypt performs key derivation with every possible hash function that is supported, and then tries each one until it successfully decrypts the volume header.