Hello eyerybody,
I use FFS to mirror my NAS (UNC Path) to an external USB3 drive (connected to a windows PC) once a month. FFS is installed as a portable version on the NAS.
So it is possible to run FFS with the same configuration from different PCs. (To start the backup from every PC I own)
Running my setting from my Windows 7 machine runs fine for months now. Now I got a new PC with Windows 8.1 Pro.
Running the same setting on this new machine leads to many windows error codes 21 (device not ready) and sometimes error code 55 (network ressource no longer available) (CopyFileEx). (Error Messages translated back from german :-) ).
This error occures evey 10 seconds to every every 30 minutes without a noticable pattern. The retry button works immediately.
The usb3 drive and the NAS run fine with the new PC using other applications that deal with lots of files for a longer time span (e.g. FileVerifier++)
Is this a Bug of FFS?
Error Code 21 and 55 when using Windows 8.1 NAS and USB3
- Posts: 2
- Joined: 29 Apr 2014
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
> Is this a Bug of FFS?
No. FFS has just the ungrateful job of delivering the bad news. There's some network stability issue - could be due to incorrect setup or even a hardware issue.
No. FFS has just the ungrateful job of delivering the bad news. There's some network stability issue - could be due to incorrect setup or even a hardware issue.
- Posts: 5
- Joined: 4 Apr 2014
do you use UNC paths on your windows 8.1 PRO to do the same type of operations. have you tried mounting the NAS to a drive and seeing if that does the same thing?
- Posts: 2
- Joined: 29 Apr 2014
I will try to change the unc path to a mounted drive letter tomorrow.
I noticed something else: most times I get the code 21. In these cases I have FFS temp files on my usb drive (Mirroring is my syncing setting).
It seems that in these cases not the source (NAS) is the problem but moving the temp file to the correct file on the usb drive.
@Zenju: as I wrote, fileverifier++ managed to check all files (3TB) on the NAS and on the USB drive without having any problems. So I think it's not a network thing.
I noticed something else: most times I get the code 21. In these cases I have FFS temp files on my usb drive (Mirroring is my syncing setting).
It seems that in these cases not the source (NAS) is the problem but moving the temp file to the correct file on the usb drive.
@Zenju: as I wrote, fileverifier++ managed to check all files (3TB) on the NAS and on the USB drive without having any problems. So I think it's not a network thing.
