Repaired library after power outage - now SeaDrive is broken

Hello, after a power outage I needed to repair my seafile libraries. This worked so far. However now on my SeaDrive clients the synchronization stops after a few hours with “internal server error” and this is shown in the server log (see below). When I run seaf-fsck.sh --repair 3d20984b-e7ca-46f8-bfac-d2132f1a44af it shows no errors. How can this be resolved?

[2022-07-08 08:01:25] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 08:56:51] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:04:05] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:06:59] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:10:06] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:14:43] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:15:40] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:15:40] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:16:20] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:21:59] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:22:45] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:23:30] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:24:10] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:25:09] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:26:05] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:27:35] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:28:43] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:29:16] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:30:01] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:30:36] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:31:07] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

[2022-07-08 09:31:12] path /repo/3d20984b-e7ca-46f8-bfac-d2132f1a44af/commit/HEAD/ internal server error: Fast forward merge for repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af is failed: stop updating repo 3d20984b-e7ca-46f8-bfac-d2132f1a44af after 3 retries

Please provide some background on your server and clients. Is this a Windows or Linux server? What version? What OS are the clients running on and what version of SeaDrive is being used? -Thank you

In SeaDrive the user can logout and re-login into his account, without removing the cache folder. That should fix the corrupted metadata and everything should work fine. After that you may have to restart SeaDrive.

The Seafile server runs on Ubuntu with the official docker image v9.0.6. The clients are using SeaDrive v2.0.22 on Windows 10.

This seems to work, thank you. For some removing the cache folder was necessary, otherwise the error started reappearing shortly after.

It appears the seadrive and seadrive_root directories need to be deleted to completely fix this.