Error N05M:VLUQ:VLUQ Cannot open my vault #2954

BirdDev · 2023-06-13T12:31:07Z

BirdDev
Jun 13, 2023

OS: Linux / 6.3.6-artix1-1
App: 1.9.1 / appimage-4502

I updated cryptomator today via the arch linux repository (no errors that I am aware of). I then tried to unlock one of my vaults (MyVault).
Cryptomator asked for the vaults password although I saved it earlier for the vault. Unlocking took a lot of time and eventually failed. If I remember correctly, a NoSuchObject exception was thrown (didn't save the info from the error window but I will attach logs). I retried to unlock the vault but now it says the vault file already exists:

Error Code N05M:VLUQ:VLUQ
java.nio.file.FileAlreadyExistsException: /home/mypcuser/.local/share/Cryptomator/mnt/MyVault
	at java.base/sun.nio.fs.UnixException.translateToIOException(Unknown Source)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
	at java.base/sun.nio.fs.UnixFileSystemProvider.createDirectory(Unknown Source)
	at java.base/java.nio.file.Files.createDirectory(Unknown Source)
	at java.base/java.nio.file.Files.createAndCheckIsDirectory(Unknown Source)
	at java.base/java.nio.file.Files.createDirectories(Unknown Source)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.common.mount.Mounter$SettledMounter.prepareMountPoint(Mounter.java:95)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.common.mount.Mounter$SettledMounter.prepare(Mounter.java:73)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.common.mount.Mounter.mount(Mounter.java:133)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.common.vaults.Vault.unlock(Vault.java:150)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.ui.keyloading.KeyLoadingStrategy.use(KeyLoadingStrategy.java:79)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:70)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:60)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:31)
	at javafx.graphics/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)

I then checked whether this affects all vaults but I was able to unlock another vault of mine with success.

Please let me know if I can assist any further. Thanks!

cryptomator0.log
cryptomator1.log
cryptomator2.log
cryptomator3.log
cryptomator4.log
cryptomator5.log
cryptomator6.log
cryptomator7.log
cryptomator8.log
cryptomator9.log
upgrade.log

BirdDev · 2023-06-14T11:57:19Z

BirdDev
Jun 14, 2023
Author

I just noticed that after rebooting my device, unlocking the vault worked again.
But I still think that there is an underlying issue that needs to be resolved.

0 replies

jablonm · 2023-06-21T20:12:33Z

jablonm
Jun 21, 2023

Same for me. I unlocked vault then suddenly it disconnected, after trying to reunlock I got the same error as you. Rebooting everytime is really bothering. It happen very often.

Flatpak
Mint 21.2 running in VMware Workstation
cryptomator0.log

0 replies

mangelozzi · 2023-08-08T07:52:35Z

mangelozzi
Aug 8, 2023

Also getting this issue on Ubuntu, when I come out of suspend sometimes.

Error Code N05M:VLUQ:VLUQ
java.nio.file.FileAlreadyExistsException: /home/michael/.local/share/Cryptomator/mnt/Michael_Secure
	at java.base/sun.nio.fs.UnixException.translateToIOException(Unknown Source)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
	at java.base/sun.nio.fs.UnixFileSystemProvider.createDirectory(Unknown Source)
	at java.base/java.nio.file.Files.createDirectory(Unknown Source)
	at java.base/java.nio.file.Files.createAndCheckIsDirectory(Unknown Source)
	at java.base/java.nio.file.Files.createDirectories(Unknown Source)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.common.mount.Mounter$SettledMounter.prepareMountPoint(Mounter.java:95)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.common.mount.Mounter$SettledMounter.prepare(Mounter.java:73)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.common.mount.Mounter.mount(Mounter.java:133)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.common.vaults.Vault.unlock(Vault.java:150)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.ui.keyloading.KeyLoadingStrategy.use(KeyLoadingStrategy.java:79)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:70)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:60)
	at org.cryptomator.desktop@1.9.1/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:31)
	at javafx.graphics@20.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)

0 replies

RobinJ1995 · 2023-10-03T20:58:52Z

RobinJ1995
Oct 3, 2023

umount -l :)

In the case of the example of @mangelozzi :

sudo umount -l /home/michael/.local/share/Cryptomator/mnt/Michael_Secure

Though this should obviously not be happening to begin with, and umount -l is a workaround that may cause future system instability.
I don't know what happened, but for me this usually happens because of Cryptomator crashing, which used to never happen and now seems to happen pretty much any time an operation touches a lot of files.

0 replies

skibum75 · 2023-10-22T13:01:13Z

skibum75
Oct 22, 2023

Using AppImages
Linux Mint 21.2 Cinnamon on hardware
5.15.0-69-generic

Experienced similar symptoms with both AppImages 10.0 and 10.1, crashing about 45 minutes into a sync.
I still had Cryptomator 1.9.1 on hand which had worked fine in the past; I rolled back to that and was able to finish my run.
Prepping for travel travel so no time to fiddle with LOG level.

The crash log "search for diagnosis" feature brought me here, which is a nice feature.

Everything seemed flowing well then boom, pipeline lost and CM crashed. Here is a short chunk of where it fails:


20:42:36.284 [JavaFX Application Thread] INFO  o.c.ui.unlock.UnlockWorkflow - Unlock of 'zzz.work' failed.
20:42:36.284 [JavaFX Application Thread] ERROR o.c.ui.unlock.UnlockWorkflow - Unlock failed for technical reasons.
java.nio.file.FileAlreadyExistsException: /home/zzz/.local/share/Cryptomator/mnt/zzz.work
	at java.base/sun.nio.fs.UnixException.translateToIOException(Unknown Source)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)
	at java.base/sun.nio.fs.UnixFileSystemProvider.createDirectory(Unknown Source)
	at java.base/java.nio.file.Files.createDirectory(Unknown Source)
	at java.base/java.nio.file.Files.createAndCheckIsDirectory(Unknown Source)
	at java.base/java.nio.file.Files.createDirectories(Unknown Source)
	at org.cryptomator.desktop@1.10.1/org.cryptomator.common.mount.Mounter$SettledMounter.prepareMountPoint(Mounter.java:95)
	at org.cryptomator.desktop@1.10.1/org.cryptomator.common.mount.Mounter$SettledMounter.prepare(Mounter.java:73)
	at org.cryptomator.desktop@1.10.1/org.cryptomator.common.mount.Mounter.mount(Mounter.java:137)
	at org.cryptomator.desktop@1.10.1/org.cryptomator.common.vaults.Vault.unlock(Vault.java:150)
	at org.cryptomator.desktop@1.10.1/org.cryptomator.ui.keyloading.KeyLoadingStrategy.use(KeyLoadingStrategy.java:79)
	at org.cryptomator.desktop@1.10.1/org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:70)
	at org.cryptomator.desktop@1.10.1/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:60)
	at org.cryptomator.desktop@1.10.1/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:31)
	at javafx.graphics@20.0.2/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)
20:46:48.393 [JavaFX Application Thread] INFO  o.cryptomator.launcher.Cryptomator - JavaFX application stopped.
20:46:48.394 [main] INFO  o.cryptomator.launcher.Cryptomator - UI shut down
20:46:48.395 [main] INFO  o.cryptomator.launcher.Cryptomator - Exit 0

0 replies

GarlicHiker · 2024-01-08T19:11:49Z

GarlicHiker
Jan 8, 2024

OS Linux Mint 21.2 Cinnamon, Kernel 5.15.0-91-generic, Cryptomator 1.11.1 (deb-1).
Unfortunately, I experience the same issue on regular basis. It happens for all my vaults whenever I put my laptop to sleep mode with unlocked vaults, regardless of the amount of data being transferred...
Very annoying :(

0 replies

mangelozzi · 2024-04-04T18:11:26Z

mangelozzi
Apr 4, 2024

Can it not automatically unmount if there is a problem? And then continue to mount it as normal

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error N05M:VLUQ:VLUQ Cannot open my vault #2954

{{title}}

Replies: 7 comments

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Error N05M:VLUQ:VLUQ Cannot open my vault #2954

BirdDev Jun 13, 2023

Replies: 7 comments

BirdDev Jun 14, 2023 Author

jablonm Jun 21, 2023

mangelozzi Aug 8, 2023

RobinJ1995 Oct 3, 2023

skibum75 Oct 22, 2023

GarlicHiker Jan 8, 2024

mangelozzi Apr 4, 2024

BirdDev
Jun 13, 2023

BirdDev
Jun 14, 2023
Author

jablonm
Jun 21, 2023

mangelozzi
Aug 8, 2023

RobinJ1995
Oct 3, 2023

skibum75
Oct 22, 2023

GarlicHiker
Jan 8, 2024

mangelozzi
Apr 4, 2024