Fluxgen

After reinstalling the Syncthing container (which was necessary because the Docker image was broken), the Syncthing container no longer works. I receive a warning message: "2024-03-20 17:56:08,284 DEBG 'start-script' stdout output: [start] 2024/03/20 17:56:08 WARNING: Error opening database: read /config/syncthing/data/index-v0.14.0.db/000037.log: input/output error (is another instance of Syncthing running ?)" Before it was running smoothly. I haven't changed anything. How can I solve the problem?

Yes, I did. I'm running three. Krusader, Syncthing and PhotoPrism. Thanks for your advise. I'll do so

Sorry, again. I forgot to post the new diagnostics: fluxgen-diagnostics-20240320-1829.zip

To late. I set the value to 50GB. But since my cache pool still shows 300GB of free space, this shouldn't be a problem, even if it might not solve the actual problem. By the way, thank you for the instructions! In principle it worked and fixed the problem! The containers are running again. However, I now have a new problem because a container is not working (like before). I guess I should post this somewhere else? The Sync-Thing instance is not reachable; in the log I get a warning message: "2024-03-20 17:56:08,284 DEBG 'start-script' stdout output: [start] 2024/03/20 17:56:08 WARNING: Error opening database: read /config/syncthing/data/index-v0.14.0.db/000037.log: input/output error (is another instance of Syncthing running ?)"

Perhaps? Can't that be checked? And why would that happen if I just reboot? I will still try the suggested solution. Thanks

Sorry, I forgot the diagnostics: fluxgen-diagnostics-20240320-1645.zip

After I restart my server, I get the message in the docker tab: Docker Service failed to start. I didn't change anything before, just restarted. I've read that for some people a full cache pool was the reason for the problem. However, I assume that this is not the case in my case. Since I don't know the subject very well, I need help. Any ideas?