External HDD question (Windows OS)

The HDDs are formatted as NTFS drives. They're about 75% filled up at this point.

I have ruled out the s/w as a cause for this because I get the same problem even if I am copying the entire folder using Windows' normal copy/paste feature and the files are over several GB.
Although you said the HDDs are formatted as NTFS, your problem really sounds like a FAT format problem. FAT has a max file size of 4GB.

Are you able to copy files of less than 4GB OK?
Interesting idea, but Windows should produce a clear error message when failing to copy a file larger than 4GB to a FAT32 partition.
 
When I am sync'ing a large volume of files, usually over several GB, the target/destination HDD gets stuck at some point. I can't do much with it at that point.
Is it "stuck" no matter how long you let it sit? For example, if you were to let it sit there for an hour, would it eventually finish?

One common cause of confusion is that when you copy files to a drive, Windows will normally try to cache writes to the drive. (I believe it doesn't do this for USB FAT drives by default, but it does for NTFS drives).

So when you start a copy you see the progress bar moving along at a pretty good clip that's limited only by the speed at which it can read the file from the source drive. That can be very fast indeed if the source drive is something like an SSD.

However if the target drive is slower, then at some point if the file is large enough Windows will run out of RAM memory to cache the writes into. At that point the transfer suddenly slows down to the speed of the target drive, and the progress bar seems to stop moving (or moves only very slowly). If the output drive has a very slow connection (i.e., USB 2) then it can get "stuck" this way for a long time as the data trickles out to the drive. It'll be faster for a better connection (i.e., USB 3) but it can still seem quite slow compared to data coming from an SSD, for example.

Attempts to do something else with the target drive (i.e., open an Explorer window to see what files have been copied) can be impacted as well since the I/O requests needed to access the drive get queued up behind the ones already issued for the copy.

If the "stuck" condition you're seeing eventually clears itself if you leave it sit for long enough, then I'd suspect that this is what you're seeing.
 
The HDDs are formatted as NTFS drives. They're about 75% filled up at this point.

I have ruled out the s/w as a cause for this because I get the same problem even if I am copying the entire folder using Windows' normal copy/paste feature and the files are over several GB.
Although you said the HDDs are formatted as NTFS, your problem really sounds like a FAT format problem. FAT has a max file size of 4GB.

Are you able to copy files of less than 4GB OK?
Yes, several of my video files on that drive are over 4GB. Possibly as large as 28GB if I remember correctly.
 
When I am sync'ing a large volume of files, usually over several GB, the target/destination HDD gets stuck at some point. I can't do much with it at that point.
Is it "stuck" no matter how long you let it sit? For example, if you were to let it sit there for an hour, would it eventually finish?
I left it there for at least an hour several times. At least one time, I left it overnight.

When the program gets stuck, say when it's 45% done, from that point, it is at that stuck file without further progress. The estimated remaining time keeps increasing from few minutes to hours and days. I know it's not going anywhere.
One common cause of confusion is that when you copy files to a drive, Windows will normally try to cache writes to the drive. (I believe it doesn't do this for USB FAT drives by default, but it does for NTFS drives).
Understood.
So when you start a copy you see the progress bar moving along at a pretty good clip that's limited only by the speed at which it can read the file from the source drive. That can be very fast indeed if the source drive is something like an SSD.
Correct. When I use FreeFileSync to backup specific files/directories to a 2TB external SSD, it takes a few seconds for few GB files.
However if the target drive is slower, then at some point if the file is large enough Windows will run out of RAM memory to cache the writes into. At that point the transfer suddenly slows down to the speed of the target drive, and the progress bar seems to stop moving (or moves only very slowly). If the output drive has a very slow connection (i.e., USB 2) then it can get "stuck" this way for a long time as the data trickles out to the drive. It'll be faster for a better connection (i.e., USB 3) but it can still seem quite slow compared to data coming from an SSD, for example.
It has nothing to do with the file size in question though. Sometimes, large files are copied at the beginning of the copy process. when it is stuck, it could be a small (relatively), say a 30MB .NEF file.
Attempts to do something else with the target drive (i.e., open an Explorer window to see what files have been copied) can be impacted as well since the I/O requests needed to access the drive get queued up behind the ones already issued for the copy.

If the "stuck" condition you're seeing eventually clears itself if you leave it sit for long enough, then I'd suspect that this is what you're seeing.
The only way to clear it is to stop the copy job (the program up to a minute to respond and gracefully stop). I run Windows Disk Optimization. If that doesn't progress, then I run disk error check.

I go back to FreeFileSync and everything moves at a good speed again.

Thanks
 
I actually use Robocopy (Windows built-in program). With the correct options, it will do a full backup the first time you run it, while subsequent runs will look after new or changed files. Very quick if you opt for multi-threaded execution.
I heard of Robocopy tool (may have used it in the past) but was not aware of it being built-in with Windows. I will check it out.
Check out the Robocopy/help information. It looks complicated, but if you want to see my preferred options, send me a PM. Robocopy works by interrogating the file attributes, e.g. “Archive” comparisons.

I have my data separated into several main folders…
  • Old data (refreshed occasionally).
  • Photos (updated regularly and periodically backed up).
  • Current data (updated frequently and also backed up quite often).
“Updating” is carried out using Robocopy, and happens very quickly. Typically, a days work is updated to an external SSD in a couple of seconds. I have been using this method for years with no issues.

”Backing up” means a simple Windows copy to external HDDs.
 
Last edited:
I meant *memory* as in RAM.
OK. I misread that. I'll pay attention to how much of RAM is used next time this happens.

Thanks
No, you may have a chip with a flaky bit. A mem-check program does a few read-write cycles to every byte of ram you have and verifies that what was written matches what was read.
 
I meant *memory* as in RAM.
OK. I misread that. I'll pay attention to how much of RAM is used next time this happens.
No, you may have a chip with a flaky bit. A mem-check program does a few read-write cycles to every byte of ram you have and verifies that what was written matches what was read.
I had an intermittent RAM problem once that manifested itself as failures to verify my backups. I spent a lot of time diagnosing that problem because I assumed at first that it was some sort of disk issue. Eventually I tracked it down using a memory testing program. Since then I've made a point of only buying systems with ECC memory.
 
I meant *memory* as in RAM.
OK. I misread that. I'll pay attention to how much of RAM is used next time this happens.
No, you may have a chip with a flaky bit. A mem-check program does a few read-write cycles to every byte of ram you have and verifies that what was written matches what was read.
I had an intermittent RAM problem once that manifested itself as failures to verify my backups. I spent a lot of time diagnosing that problem because I assumed at first that it was some sort of disk issue. Eventually I tracked it down using a memory testing program. Since then I've made a point of only buying systems with ECC memory.
OK. I will check memory
 
Try using resource monitor to view the activity for your drive. It should show which file(s) are open, current data transfer rate, disk response time, etc.
OK. Thanks
 
Question:

When I am sync'ing a large volume of files, usually over several GB, the target/destination HDD gets stuck at some point. I can't do much with it at that point.
I have encountered something similar making hard drive bit images using Macrium, from Paramount Software in the UK. One of the HDDs I was trying to back up would repeatedly fail about 22% into the operation.

The cause turned out to be bad sectors on the (1tb) source disk. I replaced the source disk for the grand sum of GBP £18 (Ebay, lightly used , perfect secondhand SATAIII 1tb disk). Lo and behold, problem gone, perfect backups.

You may find a piece of free software called CrystalDiskInfo useful for checking your source disk.
 
Last edited:
Thanks for the tip .

I will try that software
 
Thanks for the tip .

I will try that software
The download page is here:

https://crystalmark.info/en/

You'll get a report on your disk's or disks' condition, like this:

feb8fcb826864ba996596fa6c3d54abd.jpg

Don't confuse Crystal Disk with Crystal Mark. Good luck.
 
Last edited:
In case no one has mentioned it, chksk /r. It will take some time to run.
Good point Robert. I run chkdsk like this:

> chkdsk c: /f /r /x

However, prior to doing that I run:

> sfc /scannow

That specifically checks and tries to repair areas of the disk used for system files where bad sectors would be an extra problem. This is all very time-consuming and sometimes one needs to go round the loop a couple of times. When a HDD is dying bad sectors can recur within days.
 
I use FreeFileSync on my M1 Mac, but I run it everyday so usually only a few megabytes or a few gigabytes each time. You might try changing to a daily schedule so that the copies are smaller.

On my PC I use the free Syncback to do the same. I like it much more than FreeFileSync, but Syncback is not available for Macs.
 
Thanks
 
In case no one has mentioned it, chksk /r. It will take some time to run.
Good point Robert. I run chkdsk like this:

> chkdsk c: /f /r /x

However, prior to doing that I run:

> sfc /scannow

That specifically checks and tries to repair areas of the disk used for system files where bad sectors would be an extra problem. This is all very time-consuming and sometimes one needs to go round the loop a couple of times. When a HDD is dying bad sectors can recur within days.
When I open disk properties in Windows Explorer, go to Tools tab, and select 'Error Checking', isn't that running chkdsk?

Thanks
 
When I open disk properties in Windows Explorer, go to Tools tab, and select 'Error Checking', isn't that running chkdsk?
No, I don't think so - at least not in its full incarnation. I believe running it (or clicking the tools button) inside windows merely causes it to report on your bad sector situation, but does not actually fix anything.

When chkdsk c: /f /r /x is run in a Command or Powershell window a program stub is deposited which will be run at the next boot in an attempt to map out the bad sectors so that the operating system does not try to use them.
 

Keyboard shortcuts

Back
Top