windows 10 on all machines. On my laptop, it shows remote device is 11k files out of synch and that local folder is up to date. remote device is stuck at 95% with no up or downloads. This is what has happened multiple times now and i have to remove the remote device and start all over again. takes 9 hours to scan my files.
What can i do to resync it without removing the remote device and starting all over? no errors that i can see
thanks
Show us what you see when you click on the Out of Sync Items link.
Check the reason on the device that isn’t syncing.
Where would i check for this “reason”? That is my original question as well, trying to find the reason its not syncing.
There are no errors on either machine.
Thanks
I am on a normal LAN with only a few devices. No firewall or antivirus is blocking the connection either. I can put a new file in the synced folder and that shows up, but not the out of sycn 26GB worth of files.
Generally the receiving side will have a line for “Failed items” that shows the things it couldn’t sync, and why. If not, Debugging Syncthing — Syncthing documentation
Going through the logs of both machines, there is no failed to send or failed to sync. I dumped a few files on there to see if it would transfer, and it does, so I know the connection can be made.
However, I do see one line when it first booted up, where the host machine forcibly close the connection, but after that one line, all is normal and syncs just fine except the 11k files out of sync. Roughly 26gb of files, eome maybe latge, but i cant tell.
No ping issues or firewall or virus software issues either. Host machine says laptop is at 85% synced while the laptop says the host is at 95%
Please show full screenshots of the web GUI from both devices. Also, if you’re trying to use advanced options, such as syncing ownership or extended attributes, please read the documentation, because there are some prerequisites required in order to use them.
I’m also seeing that you’re still on v1.30.0 on one of the devices. Please try upgrading to the newest version of Syncthing (which is v2.1.6 at the moment) and see if there’s any difference (especially since v1 is outdated and uses a completely different database).
I’ll try to get full screenshots, but it is difficult because of the resolutions that I run on the screens mess with the UI. Also I do not have any advanced options set, just doing the good old basic setup.
I will update all of them to the same version, and see what happens. Give me a bit to finish up some breakfast, and I will get those screenshots as soon as I can. Thanks for the reply
You know that sensible browsers have built in tools to screenshot whole pages nowadays? (not just the parts visible on screen)
One thing I’d try first: wait. If one device shows another remote at 95 percent with 0 Bytes remaining out of sync, that means there are unsynchronized deletions left to do. Before the remote does that, it stays in the “Scanning” or “Preparing to sync” states for a while. I recently had this with a rather slow remote, and it took quite a while to watch from my end how it first got “stuck” in this state, then after some time started slowly decreasing the outstanding file count.
Just a hint, as this slowness (without even transferring any more data) can be pretty unexpected.
yeah, im not running in a browser : ) but i can use snipping tool to try and get a better screenshot.
Well, one thing i DID do that seems to help… update from 1.2 to 2.2 and now the drive is actually doing something. Ill keep waiting and see if it gets stuck again.
i always forget to update software because i have trauma from windows update hahaha
i will keep you guys posted.
ok, so after updating the host to the newest version to match the other version, it seemed to transfer everything over… NOW i have 10117 files that have conflicts and everytime i try to open the dialog box for resolve now, it freezes and crashes the program.
Any other way to resolve these conflicts?
thanks for all the help
Same problem here - since years - I had some hope that the error will vanish with new syncthing versions, but no.
On my side, this problem seems to be related to apps like Joplin which seem to create and delete temporary 0 byte files in a very fast way. Interestingly some devices show a 100% clean sync state, while others show 95% or more percentage of sync.
The only workaround I found is to create these 0 Byte files. Wait for the sync and afterwards delete them. I am doing this once a year and I am already thinking of automating this workaound, if no solution arives.
(syncthing 2.1.7 on Debian, Ubuntu, Windows, Android) - (the Ubuntu synthing installation just sees the cryptified versions of the sync files)
This a different problem, unless you also have thousands of files stuck in sync (like the user who created this topic). I also use Joplin and used to have some “ghost” files stuck in sync from time to time, but nothing like that since upgrading to v2.x on all devices.
I think you may want to try removing and recreating the affected folders from scratch, so that we can be sure that it’s not something caused by the old database that was later migrated to the new format when upgrading to Syncthing v2. Alternatively, remove the database (on each device separately) and let Syncthing recreate it automatically.
For all y’all with files not syncing, data is required to conclude anything: Debugging Syncthing — Syncthing documentation
Oh, it´s growing over time. In a few month it grewed to only >400 files, as I stopped using joplin. Usally I ended up in a year with more than >1000 0 Byte files.
As these files exists on neither of the synced systems (exactly that´s the error!), I have no clue, where to start with the debugging.
A possible solution might be a feature, to reset sync status for this folder on all systems, and restart the sync process afterwards. Manually stopping sync of that folder on all systems and restarting them one after another didn´t work.
When it comes to debugging in this case, it doesn’t matter whether the file physically exists or not 
. You can still follow the procedures as described at the Docs page linked above by Jakob.
Pausing the folder won’t have any effect, you would either need to completely remove and re-add it within Syncthing (possibly on all devices), or delete the whole database and let Syncthing rebuilt it from scratch.
