Hello all!
I am new in the Forum and am currently using the "Donation Edition" of FreeFileSync.
Each time I reopen the app after a couple of days from my last syncronization, I receive a warning message telling me that the destination folders in my NAS are not found.
The only way to make the app working is just click on the folders path in the right panel and it goes on.
Is someone experiencing the same issue? Any idea to fix?
Thank you in advance,
Gianfranco
Destination folders not found
- Posts: 2
- Joined: 5 Nov 2025
-
- Posts: 2977
- Joined: 22 Aug 2012
Depending on your NAS settings, after some time of inactivity the HDs in your NAS stop spinning and your NAS goes asleep.
When you wake the NAS for a sync, your disks need to spin-up. This takes some time. Normally up to ~10 seconds per disk. Because spinning-up a disk requires more from the NASs power supply than in static load, in a multi-disk NAS disks commonly spin up in sequence, not simultaneously.
Only after all disks have spun-up your NAS is available as a network drive.
The total spin-up time is normally notably larger than the time-out after which FreeFileSync reports a resource is unavailable.
When you wake the NAS for a sync, your disks need to spin-up. This takes some time. Normally up to ~10 seconds per disk. Because spinning-up a disk requires more from the NASs power supply than in static load, in a multi-disk NAS disks commonly spin up in sequence, not simultaneously.
Only after all disks have spun-up your NAS is available as a network drive.
The total spin-up time is normally notably larger than the time-out after which FreeFileSync reports a resource is unavailable.
- Posts: 2
- Joined: 5 Nov 2025
Thank you for your swift ad useful reply. Indeed, I received the same warning this morning. A a double click on the shortcut icons to the NAS in the desktop has made the app working.
It must be something related to MacOS, since it never occurred when syncing in Windows environment.
Have a nice day!
Gianfranco
It must be something related to MacOS, since it never occurred when syncing in Windows environment.
Have a nice day!
Gianfranco