I took a look and the diagnostic is showing an error in the local tracking database. This can happen if there is a disk error during database writing, sudden power loss, unexpected application termination, etc.
The easiest way to recover is to deauthorize odrive and then re-login. This backs-up (renames) the current odrive folder and then creates a new one, for a fresh start on the local system with fresh local databases.
You can then copy in the backup data and it should start working again.
Here are the steps:
- Deauthorize the desktop client (odrive menu->Authorized User->Deauthorize). Note the user information here so that you can make sure you login with the proper user in step 2.
- Go through the setup process and log back in as the same user.
- Once odrive fully initializes, go to the new odrive folder, which should now have all placeholder (.cloudf) files inside. The local cache has now been reset.
- Go to the backup odrive folder that was created during deauthorization. It will be located in your user home folder and have a name like
odrivebackup-[current date and time].
- Move all of the folders inside this backup folder (your linked storage folders) to the fresh odrive folder. The folder names in the backup folder and the names of the .cloudf files in the new odrive folder should be exactly the same. If the are not, then stop here and let me know.
- Once you move the folder over they will end up replacing the .cloudf files in there (odrive will remove the placeholders when it sees that the “real” folders are now present). odrive will go through everything and determine what has been synced and what hasn’t and reconcile anything that needs to be processed.
Please let me know if you have any questions on these steps.