Migration fails

Existing vault cannot be migrated. I use:

macOS 11.4
Cryptomator 1.5.15
macFUSE 4.1.2

I get the following error message:

org.cryptomator.cryptofs.migration.api.NoApplicableMigratorException
	at java.base/java.util.Optional.orElseThrow(Unknown Source)
	at org.cryptomator.cryptofs.migration.Migrators.migrate(Migrators.java:111)
	at org.cryptomator.ui.migration.MigrationRunController.lambda$migrate$2(MigrationRunController.java:117)
	at org.cryptomator.ui.common.Tasks$TaskImpl.call(Tasks.java:140)
	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)

The hints and tips on Github and here in the forum for the same errors, do not help. What I have done so far:

  • changed vault (switching)
  • removed vault and added it again
  • removed all vaults
  • created a completely new vault (works)
  • updated macFUSE
  • sync checked

There are other old vaults where migration worked. Just not for this one. Mobile (iOS), however, the vault and files can still be opened. According to the masterkey.cryptomator file, this is version 3.

...,"version":3}

Any tips or ideas?

Thanks,
Spezi

Indeed, version 3 is very old, see Vault Format History — Cryptomator 1.5.0 documentation.

Unfortunately, this is a multi-step process.

  1. Use Cryptomator 1.2.4 to get from vault format 3 to vault format 5.
  2. Use Cryptomator 1.4.17 to get from vault format 5 to vault format 6.
  3. Use Cryptomator 1.5.15 to get from vault format 6 to vault format 7.

Hi Tobias

Thank you very much for your help. I was not aware that my vault is that old! :sweat_smile:

That worked out great. I had also to download 1.1.4 as explained by you here, because I have received an other error. Now all files are available again.

Thank you for this great product and the excellent support. :heart: In return I bought a support certificate. :wink:

Best,
Spezi

2 Likes