Since the Syncthing DB structure was modified, my Syncthing docker container (Linuxserver.io ) malforms the database with no apparent reason (server shutdown, etc.) - again and again. Each time, I have to (recommended fix) remove the index folder, re-scan, and remove all the sync-conflicts that have piled up until I notice the problem again.

For a productive server, this issue is really more than annoying... According to the Syncthing forum, this might be related to the docker containers (both Linuxserver.io and binhex) using the SQLite. The SQLite Go backend seems not really well tested, so the recommended solution is to use the original Syncthing package (or something closer to it) instead.

Is there a docker container for Syncthing with a non-SQL backend? Or is it possible to install the original Syncthing package on Unraid?

I'm not aware of syncthing being able to use anything other than sqlite?

Anyway I've been using the binhex container for 4 years and never had a single corruption event.

There must be something wrong with your system.

https://docs.syncthing.net/users/faq.html#my-syncthing-database-is-corrupt

I suggest running a memtest from the boot screen for 24 hours to rule out the potential for bad ram.

Sorry for not responding earlier - Caught up in work...

@Kilrah I do not know. In the Syncthing forum, it was mentioned that the dockers might be the problem because they use SQLite, and this REST Backend is not well tested. So I assumed that native SyncThing does not use SQLite.

I will soon reinstall my notebooks, so maybe I should switch from linuxserver.io to binhex as your experience has been solid.

@MowMdown Interesting - I will do that. So far, I am not aware of RAM problems otherwise. There was no good time slot so far to fit in a down-time of 24 hrs, take the server offline, unplug everything, and connect it to a screen. It is productively used, and has data backups - But it is a private server with no mirror hardware. But I will find time for that test, hopefully soon.