Unable to mount external volume : Waiting indefinitly
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
#359 Unable to mount external volume : Waiting indefinitly
Hi,
One laptop with a M2 drive crashed. The laptop is dead, but the M2 drive is working.
I put the M2 drive in a SATA M.2 SSD to USB 3.1 external box, then I plugged it in a USB3 slot.
Then I tried to mount it with the option: "Mount partition using system encryption without pre-boot authentication".
On my own laptop the process never stops and always show "Please Wait... The process may take a long time and VeraCrypt may seem unresponsive". Trust me, I waited long and my laptop is powerful.
On two other laptops I tried, I am able to mount it fastly.
So I found a way to mount my volume so this problem is not urgent, but MAYBE it is a bug ...
The laptops which were able to mount VeraCrypt are:
- Windows 10 v.2004 with VeraCrypt 1.24.u6 & Windows 10 v.1909 with VeraCrypt 1.24.u4
- System Encrypted M2 & NVMe
- French language
The laptop which was NOT able to mount VeraCrypt is:
- Windows 10 v.2004 with VeraCrypt 1.24.u6
- System Encrypted NVMe
- 2 others disks M2 & SSD mounted as volumes favorite (I am a big fan & user of VeraCrypt)
- One SD card mounted as Windows volume, not VeraCrypt encrypted
- French language
I don't know which information I can give you.
It may seems not a real problem, but as I almost never see any problem in VeraCrypt I thought it was usefull to share it.
Thanks for your work,
Frédéric
Thank you Frédéric for this report.
This issue is strange. One possibility is that VeraCrypt is blocked in the step where it tries to associate the mounted volume with a drive letter because of some unknow issue related to Windows Mount Manager.
Since there are no logs or debug trace in VeraCrypt, on order to try to know more about this, can you please try to mount the disk on the affect machine using the mount option "Only create virtual device without mounting on selected drive letter" (this option is available when you click "Mount options" in the password dialog)?
If VeraCrypt is able to mount quickly, then my hypothesis is correct and there is an issue in the Windows Mount Manager.
On the other hand it is also blocked, then the problem is at much earlier step, for example while VeraCrypt tries to read the volume header.
Anyway, let's see you test result first. Thank you.