Syncthing 2.0: DB cannot be accessed?

Support
1

Hi, after the latest update my syncthing server would not start and the log file keeps repeating

syncthing | 2025-08-21 17:24:48 INF syncthing v2.0.2 “Hafnium Hornet” (go1.24.6 linux-amd64) root@buildkitsandbox 2025-08-17 16:48:08 UTC [modernc-sqlite, noupgrade] (log.pkg=main) syncthing | 2025-08-21 17:24:49 ERR Error opening database (error=“openbase (PRAGMA journal_mode = WAL): disk I/O error (5386)” log.pkg=main)

Here is my docker-compose file:

services: syncthing: image: lscr.io/linuxserver/syncthing:latest container_name: syncthing hostname: syncthing #optional environment:

  • PUID=1000
  • PGID=1000
  • TZ=Europe/Vienna volumes:
  • /srv/mergerfs/Datenpool/Docker/syncthing/config:/config
  • /srv/mergerfs/Datenpool/xxx/syncthing:/xxx ports:
  • 8384:8384
  • 22000:22000/tcp
  • 22000:22000/udp
  • 21027:21027/udp restart: unless-stopped

strangely, the data is stored in /config. Outcomenting the xxx data folder or replacing it with a link to the /config folder for data storage did not improve the situation. Neither did deleting the index folders in the /config.

I would be glad, if you could help me out!

BW, Ben

2

That’s typically a hardware failure.

3

thank you for your input! I have tried to transfer files into the same directory, it works flawless? Also, the drives are operating in a parity mode in mergerfs, so I do not think, a hardware failure is very likely?

4

Unknown, but in any case it is an error returned by the operating system.

5

Could it be something with rights to write/read? I am on an openmediavault?

It is quite strange, as everything worked perfectly fine until the upgrade.

6

The problem was mergerfs: The solution was to remove cache.files=off from the mergerfs options in the OMV GUI.

1 Like
7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.