FreeFileSync Forum

I did some more playing around, and I think I understand what is going on. This is a brand new laptop, and I had copied all my folders over from the old laptop, which is synched to the NAS. So I then ran an FFS compare to make sure that I got everything. Since all the files matched, there was ...

If there are any file mismatches, I get the green check mark after doing the Sync. So the red X seems to indicate no mismatches ("nothing to do"), but I would expect more of positive indicator. I believe that I used to get the green check in such cases, but I just upgraded to the latest version, so ...

When I hover or click, it says
"Stopped
Items processed: 0 (0 bytes)
Total time: 00:00:00"

Good point. Attached is a screenshot, where I ran just one of my GUI batch comparisons, no errors (as shown in the log) but the red X is there. You can see that all of them have the same red X from prior runs.

Thanks!

But what error? The log says everything completed successfully. If there's something actually wrong, I want to know about it, but I don't want to see the error icon if everything worked ok

I have never noticed this behavior before, but now when I run a compare (based on file time/date) and all the files compare successfully, the "unattended error" icon (red circle with an 'x' in it) appears. If I look at the log, it says that the comparison finished successfully, with the correct ...

Also, you could have set the locations and/or filters to only compare 10TB in the first place


Sorry, but I don't see how this addresses my issue in any way. Maybe I'm missing something. I have more than 20TB to compare, and I want to compare all of it. What is the point of saying "stop compare ...

I am building a new NAS and have over 20TB of files to copy from the old one. After copying them all over, just to be paranoid, I wanted to do a byte-by-byte compare before retiring the old NAS. FFS is great for this: I simply do a Compare operation using "File contents". This takes several days ...

FWIW, I booted the exact same laptop under Mint Linux and installed FreeFileSync for Linux. The FFS compare and sync ran flawlessly for almost 2 days, with well over 10TB of data. FFS on Windows was never able to run anywhere near that long without a network error, so this is definitely a Windows ...

I am trying to sync from my NAS to a USB drive, so that I can keep an offsite copy of my backups from the NAS. The problem is that a bunch of the NAS files are 500GB+ image backups (some are even 1TB+), and Windows seems to have some kind of bug wherein it gets occasional network errors on large ...

No, they aren't all .zip files. It has happened with a bunch of different files and file types, and it seems to change sometimes from Compare to Compare op. My Synology NAS has the latest version of its DSM OS installed. If the USB directory entries were somehow corrupted during the initial copy ...

Thanks, but I don't see how the NAS could cause incorrect dates on the USB drive. If the incorrect date were on the NAS files, I would definitely suspect the NAS. It's even less likely to be the NAS, given the strange behavior I just saw where the act of viewing the file properties in Windows ...

Attached are two screenshots in a PDF file, showing the FFS compare results for a file, then the Windows Explorer file properties for that file. You can see that the Modified date in Explorer does not match the Date shown in FFS, which uses the Created date instead.
FFS_screenshots.pdf
Note that I ...

Thanks for your response. Yes, it's very strange. FFS decides that it needs to sync the file because it (incorrectly) sees mismatching dates on two files, one on the NAS and one on the USB drive. As a specific example, in the difference list after running an FFS Compare op, FFS shows a NAS file with ...

This happened to me in 2020 on an old laptop, then it worked fine again until today. It was working fine even this morning, then this afternoon the weirdness came back. I tried it on three different laptops, with FFS v12.1 and v12.2. Very strange. I'm not sure if something changed in FFS or in ...

I just heard back from Synology that this date problem is a known issue with copying from NAS to USB within DSM. Next time I'll just copy with Windows, even though it will be slower (due to the 1Gbps ethernet limit).

Thanks for your help.

Ah, that could make sense, though (like you) I wonder then how Windows got the correct date. I would have to check if this only happens with JPG files. In any case, I have raised the issue with Synology support, so we'll see. What I also found very odd is that, if I pressed "compare" again in FFS, a ...

Maybe I figured something out. For speed reasons, I had performed the file copy from the NAS to the USB drive via the DSM console, plugging the USB directly into the NAS. I just tried that again with a much smaller subset of the files (40GB instead of 10+ TB), and the same problem results. So maybe ...

Yes, Windows Explorer shows the exact same modified date on the NAS and the USB. The dates show by FFS are off by 10+ years, not just a few seconds. For example, one file was modified in 2012 and last accessed yesterday -- the latter time/date is shown in FFS.

It's a WD Elements 14TB external USB ...

I just copied a large group of old USB backup drives to a folder on my 24TB Synology NAS and then to a 14TB USB drive, formatted with NTFS. When I use FreeFileSync (v12.0 on Win64) to compare the NAS folder to the USB drive contents, it compares using the Accessed Date on the USB instead of the ...

I have been using FFS regularly for a long time to sync between my Win10 laptop and my NAS. It has always worked great, and I love it. Today, for the first time, something odd happened, both with version 10.19 and 10.20 (which I downloaded to see if it would fix the problem). Mind you, this has been ...