Mount failed: Driver answer that something is wrong

Good day!

I have been experiencing the following issue for some time now and after a bit of research and troubleshooting I was redirected here from trying to open a GitHub Issue.

PROBLEM

Unlocking a vault will almost always fail the first time with the error message below

Cryptomator Error Message
org.cryptomator.common.vaults.Volume$VolumeException: Unable to mount Filesystem
	at org.cryptomator.common.vaults.DokanyVolume.mount(DokanyVolume.java:57)
	at org.cryptomator.common.vaults.Vault.unlock(Vault.java:129)
	at org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:103)
	at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:80)
	at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:43)
	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.MountFailedException: java.lang.IllegalStateException: Mount failed: Driver answer that something is wrong.
	at org.cryptomator.frontend.dokany.MountFactory.mount(MountFactory.java:128)
	at org.cryptomator.common.vaults.DokanyVolume.mount(DokanyVolume.java:52)
	... 11 more
Caused by: java.lang.IllegalStateException: Mount failed: Driver answer that something is wrong.
	at com.dokany.java.DokanyDriver.start(DokanyDriver.java:72)
	... 5 more


cryptomator.0.log
1 12:30:49.059 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.8 on Windows 10 10.0 (amd64)
2 12:30:49.617 [JavaFX Application Thread] INFO  o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
3 12:30:49.646 [JavaFX Application Thread] INFO  org.cryptomator.jni.FunctionsLoader - loaded WinFunctions.dll
4 12:31:06.502 [JavaFX Application Thread] WARN  o.c.keychain.KeychainManager - LOAD
5 12:31:06.504 [JavaFX Application Thread] INFO  o.c.k.WindowsProtectedKeychainAccess - Unable to load existing keychain file, creating new keychain.
6 12:31:07.508 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
7 12:31:34.977 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
8 12:31:38.903 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
9 12:31:40.317 [JavaFX Application Thread] INFO  o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.5.8, lastest version: 1.5.8
10 12:31:46.763 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
11 12:31:55.114 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
12 12:32:20.654 [JavaFX Application Thread] WARN  o.c.keychain.KeychainManager - LOAD
13 12:32:21.660 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
14 12:32:26.703 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
15 12:32:32.299 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
16 12:32:37.789 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
17 12:32:43.466 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
18 12:32:44.401 [JavaFX Application Thread] WARN  o.c.keychain.KeychainManager - LOAD
19 12:32:46.617 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
20 12:32:49.862 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
21 12:32:51.603 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
22 12:32:53.804 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
23 12:32:57.922 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
24 12:33:01.311 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json
25 12:33:14.179 [App Background Thread 004] INFO  org.cryptomator.common.vaults.Vault - Storing file name length limit of 220
26 12:33:14.736 [App Background Thread 004] INFO  com.dokany.java.DokanyDriver - Dokany version: 140
27 12:33:14.737 [App Background Thread 004] INFO  com.dokany.java.DokanyDriver - Dokany driver version: 400
28 12:33:14.755 [App Background Thread 005] WARN  com.dokany.java.DokanyDriver - Error while mounting
29 java.lang.IllegalStateException: Mount failed: Driver answer that something is wrong.
30     at com.dokany.java.DokanyDriver.start(DokanyDriver.java:72)
31     at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
32     at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
33     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
34     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
35     at java.base/java.lang.Thread.run(Unknown Source)
36 12:33:14.756 [App Background Thread 004] ERROR o.c.frontend.dokany.MountFactory - Mounting failed.
37 java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Mount failed: Driver answer that something is wrong.
38     at java.base/java.util.concurrent.FutureTask.report(Unknown Source)
39     at java.base/java.util.concurrent.FutureTask.get(Unknown Source)
40     at org.cryptomator.frontend.dokany.Mount.mount(Mount.java:36)
41     at org.cryptomator.frontend.dokany.MountFactory.mount(MountFactory.java:119)
42     at org.cryptomator.common.vaults.DokanyVolume.mount(DokanyVolume.java:52)
43     at org.cryptomator.common.vaults.Vault.unlock(Vault.java:129)
44     at org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:103)
45     at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:80)
46     at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:43)
47     at javafx.concurrent.Task$TaskCallable.call(Task.java:1425)
48     at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
49     at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
50     at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
51     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
52     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
53     at java.base/java.lang.Thread.run(Unknown Source)
54 Caused by: java.lang.IllegalStateException: Mount failed: Driver answer that something is wrong.
55     at com.dokany.java.DokanyDriver.start(DokanyDriver.java:72)
56     ... 5 common frames omitted
57 12:33:14.756 [App Background Thread 004] ERROR o.c.ui.unlock.UnlockWorkflow - Unlock failed for technical reasons.
58 org.cryptomator.common.vaults.Volume$VolumeException: Unable to mount Filesystem
59     at org.cryptomator.common.vaults.DokanyVolume.mount(DokanyVolume.java:57)
60     at org.cryptomator.common.vaults.Vault.unlock(Vault.java:129)
61     at org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:103)
62     at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:80)
63     at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:43)
64     at javafx.concurrent.Task$TaskCallable.call(Task.java:1425)
65     at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
66     at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
67     at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
68     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
69     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
70     at java.base/java.lang.Thread.run(Unknown Source)
71 Caused by: org.cryptomator.frontend.dokany.MountFailedException: java.lang.IllegalStateException: Mount failed: Driver answer that something is wrong.
72     at org.cryptomator.frontend.dokany.MountFactory.mount(MountFactory.java:128)
73     at org.cryptomator.common.vaults.DokanyVolume.mount(DokanyVolume.java:52)
74     ... 11 common frames omitted
75 Caused by: java.lang.IllegalStateException: Mount failed: Driver answer that something is wrong.
76     at com.dokany.java.DokanyDriver.start(DokanyDriver.java:72)
77     ... 5 common frames omitted
78 12:33:15.189 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\User\AppData\Roaming\Cryptomator\settings.json

VERSIONS

  • Windows 10 Enterprise LTSC (Version 1809 Build 17763.1518)
  • Cryptomator v1.5.8-x64 (and a couple previous versions as well)

HOW TO REPRODUCE

  • Select vault
  • Click the Unlock... button
  • Enter vault’s password and click the Unlock button

TROUBLESHOOTING STEPS TAKEN SO FAR

REINSTALLATION
  1. Uninstalled from Control Panel -> Programs And Features
  2. Rebooted
  3. Deleted the C:\Program Files\Cryptomator folder
  4. Deleted the %appdata%\Roaming\Cryptomator folder
  5. Rebooted again
  6. Reinstalled Cryptomator-1.5.8-x64.exe
CREATING A NEW VAULT
  1. Click the Add Vault button
  2. Follow instructions
  3. Follow steps to reproduce

WORKAROUND

It will almost always fail the first time but will almost always work the second time around.

It has become muscle memory to wait for the error message to pop, to press cancel and re-enter my password. :man_shrugging:

Not having a lot of time lately, I never got around to report it, thinking I surely am not the only one experiencing this and that the subsequent version would fix it but we are a few versions past that and althought it seems there were a few similar reports, I was not able to find a solution that fixed it for me.

Any help appreciated.

Thank you!

Seems to me like a problem with dokany, not with cryptomator.
So I recommend to reinstall dokany and upgrade to the latest version (choose DokanSetup_redist.exe)

Good day @Michael,

Thank you for your fast reply.

Following your suggestion, I think I might have found the source of the problem. I say might because additonnal troubleshooting steps will be needed to acertain it, steps that I unfortunately won’t be able to take today.

The gist of it

Of the software installed on my laptop, Cryptomator is not th only one requiring Dokan.

Linux File Systems for Windows by Paragon Software also uses dokan to mount my linux partitions as Windows drives so that they can be picked up by the Backblaze Personal Backup client.

When there is only Cryptomator installed and regardless if I use Cryptomator supplied Dokan or the latest DokanSetup_redist.exe, the problem did not occur during the limited tests I made.

But installing Linux File Systems for Windows seems to add an old version of Dokan to the mix, which seems to confuse Cryptomator.

The potential culprits

Detailed properties of C:\Windows\System32\drivers\dokan.sys

image


Trying to reinstall Cryptomator and/or latest Dokan does not seem to overwrite the old Paragon Software files. As a matter of fact, even uninstalling Linux File System for Windows will not clean those up. I had to manually erase them for my tests.


I will try and find some time this week to make sure this theory confirms and then proceed to find the best way to report it to all instances.

Thanks again for your help

1 Like
© 2020 Skymatic GmbH • Privacy PolicyImpressum