I've ben using FreeFileSync for a while and have encountered issues when synchronising folders on two external hard disks.
FreeFileSync lists a difference between two directories on both drives, but when I tell it to synchronise the directories I get the error message below for each file on the 'destination' drive that FreeFileSync is trying to overwrite or replace by the updated version from the 'source' drive. Effectively it's trying to move the file to the Bin but for some reason it cannot even though I have all access on both drives.
CocoaError 512: “<filename>” couldn’t be moved to the Bin. – The operation couldn’t be completed. (OSStatus error -36.) [NSFileManager::trashItemAtURL]
MacBook Pro M1 Pro
macOS Sonoma 14.1
CocoaError 512 when synchronising on Mac
- Posts: 4
- Joined: 13 Nov 2023
- Posts: 4
- Joined: 13 Nov 2023
Update...
After closing FreeFileSync I manually copied the files from the 'source' directory on the 'source' drive to the 'destination' directory on the 'destination' drive. macOS asked if I want to replace the files on the destination drive and I confirm this. After a short while this process in completed.
But when I start FreeFileSync again and start comparing both directories the program seems to 'see' that all the files that I had just copied over manually are different and should be synchronised. If I tell to do so the program again is unable to synchronise the files with the same error message.
It's baffling that the program notices a difference in two directories when shortly before that I have synchronised both directpries manually by copying over the files from 'source' to 'destination'.
And before you ask...
No, I did not accidentally confuse 'source' with 'destination'.
After closing FreeFileSync I manually copied the files from the 'source' directory on the 'source' drive to the 'destination' directory on the 'destination' drive. macOS asked if I want to replace the files on the destination drive and I confirm this. After a short while this process in completed.
But when I start FreeFileSync again and start comparing both directories the program seems to 'see' that all the files that I had just copied over manually are different and should be synchronised. If I tell to do so the program again is unable to synchronise the files with the same error message.
It's baffling that the program notices a difference in two directories when shortly before that I have synchronised both directpries manually by copying over the files from 'source' to 'destination'.
And before you ask...
No, I did not accidentally confuse 'source' with 'destination'.
- Posts: 1202
- Joined: 8 May 2006
Might the directory name or file name contain a period?
Might a directory exist with the same name as the filename?
Might a directory exist with the same name as the filename?
- Posts: 4
- Joined: 13 Nov 2023
None of that. No duplicate names for files or directory's and no weird character or leading "." in the directory or file names.
- Posts: 1
- Joined: 25 Nov 2023
the problem is that FFS can't access the trash. So go to 'Actions' / sync parameters and use the 'permanent' option for deleting files
- Posts: 4
- Joined: 13 Nov 2023
Thanks for the tip.the problem is that FFS can't access the trash. So go to 'Actions' / sync parameters and use the 'permanent' option for deleting files stefkeuutfryslan, 25 Nov 2023, 12:14
I changed it today and will keep an eye out to see if this solves the problem when I synchronise both external drives again in the future.
