Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I upgraded from 1.11.0 to 1.12.0 and now I can't open my vault anymore #3334

Open
2 tasks done
andreagrandi opened this issue Feb 16, 2024 · 4 comments
Open
2 tasks done
Labels
os:mac type:bug Something isn't working

Comments

@andreagrandi
Copy link

Please agree to the following

Summary

I'm unable to mount my existing value

What software is involved?

  • Operating System: MacOS 14.3.1
  • Cryptomator: 1.12.0

Volume Type

macFUSE

Steps to Reproduce

  1. Start the application
  2. Try to mount an existing volume

Expected Behavior

I expect the volume to be mounted as usual

Actual Behavior

I get this dialog instead

Screenshot 2024-02-16 at 11 40 43

with this error:

Error Code 4VHF:Q9JM:SGVO
org.cryptomator.integrations.mount.MountFailedException: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_mount failed
	at org.cryptomator.frontend.fuse@4.0.0/org.cryptomator.frontend.fuse.mount.MacFuseMountProvider$MacFuseMountBuilder.mount(MacFuseMountProvider.java:124)
	at org.cryptomator.desktop@1.12.0/org.cryptomator.common.mount.Mounter.mount(Mounter.java:170)
	at org.cryptomator.desktop@1.12.0/org.cryptomator.common.vaults.Vault.unlock(Vault.java:155)
	at org.cryptomator.desktop@1.12.0/org.cryptomator.ui.keyloading.KeyLoadingStrategy.use(KeyLoadingStrategy.java:79)
	at org.cryptomator.desktop@1.12.0/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:70)
	at org.cryptomator.desktop@1.12.0/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:31)
	at javafx.graphics@21.0.1/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$Completion.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.jfuse.api.FuseMountFailedException: fuse_mount failed
	at org.cryptomator.jfuse.mac@0.6.3/org.cryptomator.jfuse.mac.FuseImpl.mount(FuseImpl.java:33)
	at org.cryptomator.jfuse.api@0.6.3/org.cryptomator.jfuse.api.Fuse.mount(Fuse.java:126)
	at org.cryptomator.frontend.fuse@4.0.0/org.cryptomator.frontend.fuse.mount.MacFuseMountProvider$MacFuseMountBuilder.mount(MacFuseMountProvider.java:121)
	... 12 more

Reproducibility

Always

Relevant Log Output

No response

Anything else?

I tried to search for existing errors and found this #2943 but their solution #2943 (comment) doesn't work for me because I'm already using MacFuse 4.5.0

@andreagrandi andreagrandi added the type:bug Something isn't working label Feb 16, 2024
@CapZhang
Copy link

I encountered the same problem. When the software selects FUSE-T in "Virtual Drive", it cannot open my vault.
Select the WebDav method to open normally.

@andreagrandi
Copy link
Author

I tried to upgrade to MacFUSE 4.6.0, restarted a couple of times, gave permissions (in Privacy settings) when asked, restarted again and now it works.

On a very side and off topic note: last time I restarted, my Mac did something bad to the external hard disk (not related to Cryptomator). I heard a CLOCK-CLACK-STLOCK and my external HD is gone 🙄

@CapZhang
Copy link

Thanks for your reply. But I'm using FUSE-T, not MacFUSE, and this issue has not been resolved for me here. Hopefully the developers will take care of this and fix it soon

@andreagrandi
Copy link
Author

Thanks for your reply. But I'm using FUSE-T, not MacFUSE, and this issue has not been resolved for me here. Hopefully the developers will take care of this and fix it soon

I know Fuse-T is the suggested one if we have Apple Silicon CPUs, but I've read too many posts of people complaining about data loss and corruption, to trust it for my files.

@infeo infeo added the os:mac label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
os:mac type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants