I posted to another thread, but I think this is different enough that it could be its own post. (It’s for an entirely different device).
So I compiled Syncthing 2.0.5 for my old Drobo 5N2. I previously had Syncthing 1.3.0 (also compiled myself) running successfully on this device. After the Drobo upgraded the app, the DB migration began and I could see the progress on the temporary GUI:
*** Database migration in progress ***
2025-09-02 18:22:55 INF syncthing v2.0.5 "Hafnium Hornet" (go1.25.0 linux-arm) builder@github.syncthing.net 2025-09-02 19:03:22 UTC (log.pkg=main)
2025-09-02 18:22:56 INF Migrating old-style database to SQLite; this may take a while... (log.pkg=syncthing)
2025-09-02 18:23:01 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
Given the age of the device, its relative “slowness”, and the size of my data, I knew the migration would take quite some time.
After about 40 hours, the DB migration seems to have completed. However, my instance seems to be stuck after the migration with the following message in the log:
My NAS has enough free space. I was previously running version 1.3.0 successfully. I updated the CLI to start with double-hyphens instead of single-hyphens and use the ‘serve’ parameter in the command. I’m not sure what Syncthing is doing now. Is it doing anything? Is there some process that occurs after the “Cleaned out database file for old dropped folder”?
Update: So, I guess I just needed to be patient.Synchting eventually came back up, it just went a loooong time without updating the log. It went almost 3 hours without talking to me.
2025-09-04 10:56:43 INF Cleaned out database file for old, dropped folder (path=folder.0001-<redacted>.db log.pkg=db/sqlite)
2025-09-04 13:46:36 INF Temporary GUI/API closed (address=0.0.0.0:8384 error="http: Server closed" log.pkg=main)
2025-09-04 13:46:37 INF Upgrade available (current=v2.0.5 latest=v2.0.6 log.pkg=main)
2025-09-04 13:46:42 INF Upgraded, should exit now (newVersion=v2.0.6 log.pkg=main)
2025-09-04 13:46:42 INF syncthing v2.0.6 "Hafnium Hornet" (go1.25.0 linux-arm) builder@github.syncthing.net 2025-09-03 07:27:53 UTC (log.pkg=main)
Not exactly sure what it was doing all that time, but it’s now running and performing a sync.
I’ll leave this here, in case it can help others in the future.
Yeah, unclear. There’s pretty much nothing relevant that happens in between those two log lines, certainly nothing that explains to me why it would take three hours.
I am currently experiencing the behavior on a raspberry 4. 1259272 files with 10815 blocks were migrated in 5h24m, version is 2.0.10, last log line so far is “15:33:39 INF Cleaned out database…”, that’s a bit over an hour ago from now.
GUI Task manager shows ~12% CPU load, 750MB out of 3794MB RAM used and two syncthing processes with 41.2 and 17.4 MB RSS and both 0% CPU, position 8 and 9 in decending CPU load order. There is a lot of HDD head positioning. Normally, I would assume syncthing folder scanning, but it might be a SQLite activity or whatever as well.
Will it be safe when this state will be interrupted? I started it over ssh and I worry that my network connection will be reset next night, killing the raspberry session.
,