An unexpected error occured

Help Desktop App
1

I keep getting this when trying to create a new vault. Using Mac Mojave and Fuse and locating the vault on my internal hard drive. Help! Thanks, Harry
Data Below:

org.cryptomator.common.vaults.Volume$VolumeException: Unable to mount Filesystem
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:107)
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:58)
	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.fuse.mount.CommandFailedException: ru.serce.jnrfuse.FuseException: Unable to mount FS
	at org.cryptomator.frontend.fuse.mount.MacMounter.mount(MacMounter.java:45)
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:105)
	... 12 more
Caused by: ru.serce.jnrfuse.FuseException: Unable to mount FS
	at ru.serce.jnrfuse.AbstractFuseFS.mount(AbstractFuseFS.java:287)
	at org.cryptomator.frontend.fuse.mount.MacMounter.mount(MacMounter.java:43)
	... 13 more
Caused by: ru.serce.jnrfuse.FuseException: Unable to mount FS, return code = 1
	at ru.serce.jnrfuse.AbstractFuseFS.mount(AbstractFuseFS.java:283)
	... 14 more
org.cryptomator.common.vaults.Volume$VolumeException: Unable to mount Filesystem
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:107)
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:58)
	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.fuse.mount.CommandFailedException: ru.serce.jnrfuse.FuseException: Unable to mount FS
	at org.cryptomator.frontend.fuse.mount.MacMounter.mount(MacMounter.java:45)
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:105)
	... 12 more
Caused by: ru.serce.jnrfuse.FuseException: Unable to mount FS
	at ru.serce.jnrfuse.AbstractFuseFS.mount(AbstractFuseFS.java:287)
	at org.cryptomator.frontend.fuse.mount.MacMounter.mount(MacMounter.java:43)
	... 13 more
Caused by: ru.serce.jnrfuse.FuseException: Unable to mount FS, return code = 1
	at ru.serce.jnrfuse.AbstractFuseFS.mount(AbstractFuseFS.java:283)
	... 14 more
2

Does it help if you update “FUSE for macOS” to the latest version? https://osxfuse.github.io/

3

Hi, thanks for your reply.
I am using Fuse 3.11.0, which the website says is the latest version without success.

4

Please try the workaround described here: [1.5.7] Unable to mount Filesystem: Unexpected error during unlock a newly created Vault (macOS) · Issue #1310 · cryptomator/cryptomator · GitHub

Workaround:

  1. Select the vault in Cryptomator.
  2. Press “Vault Options”.
  3. Select the tab “Mounting”.
  4. “Drive Name” is probably empty, give it some name.
5

Yes, that does work. Thank you for that.
Apparently, this is a bug in the program and is being corrected with the next version which is already available.
Thanks again, Harry