Had a power outage last night and now syncthing won’t start. It keeps exiting with error 1. When inspecting the systemd logs I found:
FATAL: Error opening database: open //.config/syncthing/index-v0.14.0.db/LOCK: read-only file system (is another instance of Syncthing running?)
As syncthing went down in an uncontrolled fashion, I went ahead and removed the LOCK file and attempted to restart, but it is still exiting with error code 1. I added -verbose to the start parameters, but that hasn’t yielded anything useful.
Here is its current start logging:
INFO: syncthing v1.0.0 “Erbium Earthworm” (go1.11.4 linux-amd64) email@example.com 2018-12-26 16:23:05 UTC [noupgrade]
INFO: My ID: <snipped, I don’t know if its safe to post the id>
INFO: Single thread SHA256 performance is 417 MB/s using crypto/sha256 (409 MB/s using minio/sha256-simd).
VERBOSE: Starting up (//.config/syncthing)
systemd: syncthing.service: Main process exited, code=exited, status=1/FAILURE
I’ve examined the drive and it appears to be okay. I checked the logs for any fsck message but the drive passed on the reboot. I’ve manually run fsck and no corrections were noted, the drive is clean.
What can I do to get more information to debug a startup failure?