I am unable to unlock my vaults - "drive is inaccessible"

[App_User]

It looks like I’ve finally been chosen by RNG. I receive the following (exact) error when trying to open either vault:

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

I’m currently using Sync.com, so I won’t be able to use Cyberduck. I did give Cryptomator permission to access the removable volume that my vaults are stored in.

The main thing that changed is that I’ve upgraded from macOS Mojave to macOS Big Sur.

I’ve updated the app from version 1.5.8 to 1.5.10 after checking for updates.

Please let me know if there’s any other info that I can provide that might help.

Let me know if there’s an option to pay for support, as I’d like to be able to regain access to my files again.

[Michael]

@App_User

The main thing that changed is that I’ve upgraded from macOS Mojave to macOS Big Sur.

Big Sure and Fuse is known to cause problems. (Search for Big Sure in this board) There’s a fix coming soon and a workaround in this thread

Big Sur - Cannot open vault anymore

Recently updated to Big Sur Beta (I know, Betas break things) and it seems to have broken Cryptomator. I’ve uninstalled both Cryptomator and FUSE, reinstalled both, deleted the vault, and re-added, and nothing. It seems to unlock vaults just fine, but then I hit the “reveal” button and nothing happens. I try to lock, and nothing happens. I manually try to open the volume location specified in the app, and it says the location doesn’t exist. This also causes issues when restarting since I am …

[App_User]

Sorry for not searching for similar threads. Do you know if there are any risks associated to switching to WebDAV in the meantime, whether it’s losing files or exposing them in some way to other devices on your network?

[Michael]

Dokan vs Webdav Testing

Thanks you so much Michael. "There is no conversion needed as this setting does not affect the encryption. It’s just the virtual file system. You can switch the settings and change from WebDAV to dokany (and vice versa) at any time. Just change the app configuration and restart the app." Is there any risk switching back and forth? Should I backup the files first?

Why should the files be exposed just because you switch the virtual file system? That would make cryptomator useless, wouldn’t it?
So no, there’s no risk of exposing files if you switch the volume type. But keep the WebDAV restrictions in mind.

[App_User]

That’s a good point. I don’t know much about network security, so I thought that using a port was not as safe.

Where can I learn more about WebDAV restrictions?

Edit: This is the error that I see when opening Vault via WebDAV, but it’s fixed after restarting the app.

java.lang.IllegalStateException: Already unlocked.
	at org.cryptomator.common.vaults.Vault.unlock(Vault.java:131)
	at org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:107)
	at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:90)
	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)

[Michael]

@App_User

Where can I learn more about WebDAV restrictions?

Well, you can have a look at the known issues category.
You’ll find this: https://community.cryptomator.org/t/4-gib-file-size-limit-on-virtual-drive
and this: https://community.cryptomator.org/t/virtual-drive-shows-capacity-of-system-partition-c
(these are the 2 restrictions I’m actually aware of)

[infeo]

Another, quite recent issue appears on MacBooks with ARM chips:

Apple Silicon: Crashes on WebDAV when altering files