![]() ![]() What's interesting is that the mount is still reporting Sending chunk, but the rclone copy script has long stopped working due to device not configured.07:21:43.990 INFO - Starting Cryptomator 1.3.1 on Windows 7 6.1 (amd64)Ġ7:21:46.059 INFO o.c.launcher.MainApplication - JavaFX application started.Ġ7:21:46.158 INFO o.c. - Settings loaded from C:\Users\Sean\AppData\Roaming\Cryptomator\settings.jsonĠ7:21:47.164 INFO - loaded WinFunctions.dllĠ7:21:47.237 INFO .log - Logging initialized to .log.Slf4jLogĠ7:21:47.281 INFO o.c. - Binding server socket to 127.0.0.1:42427Ġ7:21:47.296 INFO o.e. - Started INFO o.c.ui.controllers.WelcomeController - Current version: 1.3.1, lastest version: 1.3.1Ġ7:21:50.441 INFO o.c.k.WindowsProtectedKeychainAccess - Creating new keychain at path C:\Users\Sean\AppData\Roaming\Cryptomator\keychain.jsonĠ7:21:52.909 INFO o.c.ui.controllers.WelcomeController - Current version: 1.3.1, lastest version: 1.3.1Ġ7:21:53.318 INFO o.c. - Settings saved to C:\Users\Sean\AppData\Roaming\Cryptomator\settings.jsonĠ7:22:33.786 INFO o.c. - Settings saved to C:\Users\Sean\AppData\Roaming\Cryptomator\settings.jsonĠ7:22:38.640 INFO o.c.c.common.ReseedingSecureRandom - Seeding CSPRNG with 55 bytes.Ġ7:22:38.642 INFO o.c.c.common.ReseedingSecureRandom - Seeded CSPRNG.Ġ7:22:38.868 INFO o.c.k.WindowsProtectedKeychainAccess - Creating new keychain at path C:\Users\Sean\AppData\Roaming\Cryptomator\keychain.jsonĠ7:22:42.164 ERROR o.c.ui.controllers.UnlockController - Unlock failed for technical reasons. It looks like the mount reports "device not configured" when it is indeed sending a large chunk.Ĭommand rclone mount aibanezkautschme: gdrive2 -daemon-timeout 100000m -vfs-cache-mode full -vv OK so, there doesn't seem to be an specific error in the mount log. And two, are there any other parameters I'd could try to improve the reliability of the rclone mount when using Drive? I'm aware Drive has been having issues since yesterday, but I'm not in an affected zone (none of my normal rcone sync logs show excess of 4xx errors). So I have two questions: Has anyone here had any success using rclone and Cryptomator this way? Basically using rclone to mount Drive, and then create the Cryptomator vault in the Drive mount. I have created a Cache remote to wrap around my standard, non-encrypted drive, and I mount it like this: rclone mount aibanezkautschme_Cache: gdrive2 -vfs-cache-mode full ![]() Rclone starts printing errors in the lines of "Device not configured". ![]() The biggest problem seems to be that the mount disconnects when under "heavy" load. Unfortunately this is not working well because of how unreliable Google Drive is (bear with me - I know I could get a different service like B2 or even Wasabi, but the monthly cost for 8TB is way out of budget right now, not to mention the Cryptomator iOS app only supports Dropbox, Drive and OneDrive). So I thought of mountaing Google Drive with rclone, creating a Cryptomator vault in the mounted drive, and then use rclone to copy the files from my hard drive into the Cryptomator vault. It allows me to create encrypted "vaults". So after googling for a long time I came across Cryptomator. Currently I upload them with Crypt which works great, but rclone being unavailable on iOS, I can't have access to my files this way (I do have a secondary Android phone, but since I prefer iOS I want them accessible on that platform). For a long time, I have wanted to have access to all my encrypted files in Google Drive on iOS. ![]()
0 Comments
Leave a Reply. |