Firstly, Ive been using and recommending FFS for years. Thanks everyone involved.
Lately I've been trying to sync some external drives as usual, this was working seemingly till I upgraded to 12.5. Now suddenly, no matter what when I'd start a sync it will do 2 files (almost always after 2.10mb) then fails/crashes to the point I have to force quit the app and start all the way over.
After trying this many times I did a fresh stock install of MacOS (Ventura on an M1 macbook) + fresh install of FFS 12.5 - same result! I tried rolling back a few versions to 12.1...same result!
I even dusted off my older intel Macbook running older version of FFS and....same result!!
It would seem to be an issue on my drives...perhaps the .ffs_lock files left from failed syncs are the culprit? I've used these same drives with FFS weeks ago no problem and Im only trying to sync 130GB. One of the drives is an encrypted APFS filesystem if that's relevant.
Any insights to what's going on or perhaps an alternate free sync software would be very helpful!
I gotta sync these drives ASAP!
Thanks!
Sync always fails and crashes immediately after 2 files
- Posts: 2
- Joined: 20 Aug 2023
-
- Posts: 4867
- Joined: 11 Jun 2019
FFS should be detecting old/stale lock files from previous syncs. I would also bet on failing drive(s). Can you use GSmartControl to check the SMART data? Not all externals will show that data
- Posts: 2
- Joined: 20 Aug 2023
I have the exact same problem and no idea what a GSmart Control is. Was using an older version, just updated, same result.
-
- Posts: 4867
- Joined: 11 Jun 2019
- Posts: 2
- Joined: 20 Aug 2023
Have you googled how not to be a knob on social media? Well smart a** even with the previous search bins deleted the program keeps hanging.
- Posts: 1202
- Joined: 8 May 2006
Explain?even with the previous search bins deleted
Did GSmartControl find an issue with the drive?
- Posts: 2
- Joined: 20 Aug 2023
I tried installing GSmartControl but got hung up on some annoying homebrew SSL errors and I suspect it wouldn't work for my external drives/mac anyway. I tried DriveDX as well and that wasnt able to read SMART info on any my drives.
It does appear that there is something about this drive that makes it unable to work with FFS, which is good to know and Im cloning it.
Fortunately the drive works well enough to come up with a FFS file comparison, copy folders in finder, clone in carbon copy cloner, etc...so not all the way broken, but it does fail immediately when mirroring in FFS.
Perhaps there could be an internal FFS workaround or a more descriptive warning/error in FFS for this sort of situation.
Thanks for the help. Everyone else STFU :)
It does appear that there is something about this drive that makes it unable to work with FFS, which is good to know and Im cloning it.
Fortunately the drive works well enough to come up with a FFS file comparison, copy folders in finder, clone in carbon copy cloner, etc...so not all the way broken, but it does fail immediately when mirroring in FFS.
Perhaps there could be an internal FFS workaround or a more descriptive warning/error in FFS for this sort of situation.
Thanks for the help. Everyone else STFU :)
- Posts: 1202
- Joined: 8 May 2006
If a drive is suspect, even though you are able to "copy" or "clone"..., even though it "worked", does not necessarily mean that it correctly. I.e., the possibility exists that while the copy may have worked, the actual data is invalid (i.e., corrupted).Fortunately the drive works well enough
So you should try & verify exactness between your copy & known valid copy of said file(s).
(If they agree, then you can say, "it worked, well enough".)
