Syncthing 1.2.5 -> 1.2.6 Upgrade

I’m curious if anybody else has seen this, I saw an update for Syncthing was available from the TrueNAS catalog early yesterday morning and its been Deploying now for over 21 hours.

Apparently, this is a the release for Syncthing 2.0 and this from the release notes jumped out at me:

Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups.

I use Syncthing on both my TrueNAS machines to keep my off-site NAS up-to-date (~40-50TiB). I’m not sure whether that qualifies me as a “larger setup” but 21 hours is pretty lengthy so, I think it must be pretty large?

The container logs seem to indicate that it’s in the middle of a migration script and it seems to be making progress, so I’ve been reluctant to stop it.

2025-08-12 15:23:25.030129+00:002025-08-12 10:23:25 INF syncthing v2.0.0 "Hafnium Hornet" (go1.24.6 linux-amd64) docker@github.syncthing.net 2025-08-11 20:16:10 UTC [noupgrade, stnoupgrade] (log.pkg=main)
2025-08-12 15:23:25.043946+00:002025-08-12 10:23:25 INF Archiving a copy of old config file format (path=/var/syncthing/config/config.xml.v37 log.pkg=syncthing)
2025-08-12 15:23:26.066159+00:002025-08-12 10:23:26 INF Migrating old-style database to SQLite; this may take a while... (log.pkg=syncthing)
2025-08-12 15:23:26.116876+00:002025-08-12 10:23:26 INF Migrated folder (folder=3ttp5-tkee3 files=214 blocks=135 duration=0s filesrate=4376.51036900629 log.pkg=syncthing)

...

2025-08-13 12:35:29.123661+00:002025-08-13 07:35:29 INF Still migrating folder (folder=fusoz-ccehv files=206000 blocks=116705186 duration=21h10m50s filesrate=2.7016092391443016 log.pkg=syncthing)
2025-08-13 12:50:14.801111+00:002025-08-13 07:50:14 INF Still migrating folder (folder=fusoz-ccehv files=207000 blocks=117527845 duration=21h25m36s filesrate=2.683553549689402 log.pkg=syncthing)

I don’t really know what I’m expecting from this post. Maybe some discussion with other Synthing users about this upgrade? How long did your upgrade take? Did any of you stop the container mid-upgrade script, if so how did that work out for you?

That really is a huge Syncthing installation. For reference, Syncthing’s anonymized reporting is available here and shows that 12.9GiB is the median amount of data synced per device.

If this doesn’t finish in a time you’d consider sane, it may well be worth posting to the Syncthing forums. The developers might be interested in performance at that level.

Edit to add: I’ve intentionally not updated yet. My installation is in the 20GiB range so I don’t think I’d have a useful comparison to offer.

1 Like

Ooh, thanks for the link to the analytics. I’m probably in the 99th percentile for size! That’s probably beyond huge.

That makes sense. I figured I’d start here in the hopes there’s folks who are using Syncthing like I am or if there was some sort of configuration that was specific to the TrueNAS App Catalog that might be contributing to things.

I snooped around the Syncthing forums and didn’t see anybody else complaining about it taking a long time like I have.

If it helps at all, I do have a 3rd TrueNAS machine that is mostly for tinkering on and its Syncthing upgrade only took a few minutes. It’s syncing a single dataset/folder, but it’s still pretty sizable at 3.22TiB. I don’t know how well Syncthing 2.0 is working, yet since the other two machines haven’t finished their respective upgrades!

For anybody interested, I did wind up posting in the Syncthing forums:

Syncthing 2.0: Migration running for 27 hours (and counting?)

TL;DR: It’s going to take quite a while for this upgrade to complete for @briancmoses!

1 Like

So this is expected behavior, to hang on deployed? i just done the update and have the same issue, so i should just leave it on deployed?

i also have a bout 30TB (at a guess, cant access UI)

I’m having the same problem - just hanging on Deployed. I have about 2tb files that sync and Syncthing has been in “Deploy” mode for about 24 hours. Very frustrating to say the least.

The expected behavior should probably be for it to sit at “Deploying” while Syncthing does its database migration.

There might be other reasons why being stuck at “Deploying” would be expected, but I am not aware of them.

What a nightmare this has turned out to be !!! I just tried to rollback and the app was stuck in a boot loop (switching between deploy and stopped), but wouldnt let me re-upgrade either as the app needs to be running to upgrade. Finally got it upgraded again, but now i still cant access my files on my VM as i use Syncthing to copy them to my NAS.

You mentioned tracking the progress, how do you do that? when i click logs it just comes up with this screen

If you compare your logs to what I’ve shared here and in more detail over on the Syncthing forums, you’ll see that they’re quite different.

I wasn’t doing anything special to track progress, it should be writing that progress to the console with regular updates every 1000 files or so.