Unexpected error after cloning drive

Help
1

After cloning my SSD nVME M.2 to another, larger SSD I am unable to open my vault. I receive an unexpected error. I tried uninstalling Cryptomator and Dokan Library and reinstalling but that didn’t make a difference. Thoughts?

org.cryptomator.common.vaults.Volume$VolumeException: Unable to mount Filesystem
at org.cryptomator.common.vaults.DokanyVolume.mount(DokanyVolume.java:48)
at org.cryptomator.common.vaults.Vault.unlock(Vault.java:151)
at org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:100)
at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:81)
at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:44)
at javafx.concurrent.Task$TaskCallable.call(Task.java:1425)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.cryptomator.frontend.dokany.DokanyMountFailedException: Error while mounting.
at org.cryptomator.frontend.dokany.MountFactory.mount(MountFactory.java:130)
at org.cryptomator.frontend.dokany.MountFactory.mount(MountFactory.java:116)
at org.cryptomator.common.vaults.DokanyVolume.mount(DokanyVolume.java:43)
… 11 more
Caused by: com.dokany.java.DokanyException: Mount timed out
at com.dokany.java.DokanyMount.mount(DokanyMount.java:121)
at org.cryptomator.frontend.dokany.MountFactory.mount(MountFactory.java:126)
… 13 more

2

Interesting…when I selected the checkbox for Custom Mount Flags (I didn’t change any of the text for the flags) and assigned a specific drive letter it mounted fine.

3

Welcome to the Cryptomator Community :slightly_smiling_face:

you ran into the following issue:

Your system does not release a lock “quick” enough, such that Cryptomator thinks Mounting failed. In this comment of the issue a general workaround is described.