Via TeraCopy 3.17, I copied a 8TB drive of media files from an internal drive, to a new external USB C drive. Connection was direct to USB 3.2 motherboard connection.
Next, I did a File Content compare in FFS 13.9 - between the source and destination. It raised ~3700 errors shown in the title. I note that when I got the first error during the scan, I asked it to "ignore all".
It seems the USB chassis - which has been reliable, is going off-line momentarilly; although there is no indicator of this on Windows... because when I checked about 10 of the directories it complained about all the files are there. The FFS interface shows the same file on each side. In fact, there are the same number of files on both sides and the size values seem identical.
Questions:
1) What might be the cause for the error?
2) Access is clearly there and so are the files. Is there a way to one-by-one "refresh" the compare results? (BTW: I could not find any tutorial, FAQ and manual reference to the orange lighting bolt on yellow BG... nor what happens when I click on it. There needs to be more documentation FFS: The "View Help" link is an overview only...
ERROR_NO_SUCH_DEVICE: A device which does not exist was specified.
- Posts: 3
- Joined: 4 Jan 2025
- Posts: 3
- Joined: 4 Jan 2025
Above post was prematurely submitted... apologies:
3) It is not clear to me that if I "Synchronize" what will happen. Will it check to see that files are indeed there and when it sees them, move to the next file and so-on; or will it blindly start replacing files again?
3) It is not clear to me that if I "Synchronize" what will happen. Will it check to see that files are indeed there and when it sees them, move to the next file and so-on; or will it blindly start replacing files again?
-
- Posts: 4866
- Joined: 11 Jun 2019
You'll need to clarify something about these '3700' errors. Are they actual errors reported by FFS or are they files determined to be different by FFS and you are calling them errors?
- Posts: 3
- Joined: 4 Jan 2025
These are the number of file errors that FFS indicated as "ERROR_NO_SUCH_DEVICE: A device which does not exist was specified."
BTW... this morning I reran it using UNC paths (rather than local drive letters). I had opened both the source and target drives in explorer. This time I got only one error; and the target (external USB drive) explorer window got closed by windows. (I noticed the same on the first run.)
My theory is that the the drive is disconnecting and then FFS report the "no such device" error. Frankly, I think there should be some delayed retry function. During the first run, where I was getting the errors quite often, I never saw the drive off-line. I noted the explorer window got closed... but I was always able to see the drive and then re-open the window.
BTW... this morning I reran it using UNC paths (rather than local drive letters). I had opened both the source and target drives in explorer. This time I got only one error; and the target (external USB drive) explorer window got closed by windows. (I noticed the same on the first run.)
My theory is that the the drive is disconnecting and then FFS report the "no such device" error. Frankly, I think there should be some delayed retry function. During the first run, where I was getting the errors quite often, I never saw the drive off-line. I noted the explorer window got closed... but I was always able to see the drive and then re-open the window.
-
- Posts: 4866
- Joined: 11 Jun 2019
FFS does have a delay for automatic retries if you look at the comparison settings. You found the root issue, the drive is losing connection somehow. Could be a bad USB cable or port, or it wasn't plugged in fully, or buggy USB drivers, etc.
