1

My WD MyWorldBook is pretty old as you can tell, so I've taken it upon myself to transfer everything to my PC before it inevitably keels over, but when I go to copy everything, Windows gets stuck discovering the size/amount of files, the size just goes up and up and up until 30 minutes later it's sized up to be 650GB and climbing!!! Even though it is absolutely not that big. If I go into a specific folder within the ones I am trying to copy over and attempt to copy it, It works just fine for some reason discoverers files in an instant and copies.

What's going on here? Is the NAS finally corrupted or Is it a windows related thing?

user9100871
  • 11

2 Answers2

0

I'm assuming that when you mount the drive it shows files and folders, but when you try to copy, it does the slowdown. This could be caused by a number of things, but the simpler solution would be to setup a new folder on the PC in which to copy the files. Then start copying files a few at a time - say 10 folders. If that works, then do another 10. At some point, You will probably come across the file or folder that's causing the problem. Ignore it and continue copying the other files. When you're satisfied all the other files are copied, run checkdisk on the WD and see if it fixes that file. You may find that it is permanently corrupted and unrecoverable.

user76732
  • 643
0

"Even though it is absolutely not that big."

Something really is that big!

"If I go into a specific folder within the ones I am trying to copy over and attempt to copy it, It works just fine for some reason discoverers files in an instant and copies."

That's because you're copying folders that happen to be smaller and/or have fewer files. One or more of the remaining folders contain that 650+ GB of data. It's in there somewhere, most likely hidden in a subfolder that you never suspected.

"What's going on here? Is the NAS finally corrupted or Is it a windows related thing?"

Probably neither. It's a Windows-related issue in as far as Windows Explorer isn't the right tool for copying this much data. If you ran Robocopy, it would start immediately as it doesn't check all of the files first (which is why Robocopy doesn't give you a progress bar but Windows Explorer does... when it eventually starts!)

chkdisk isn't relevant here. The obvious first steps haven't been covered yet.

Forget WinDirStat, it hasn't been updated since 2007 and is about 10x slower than TreeSize.

I don't think there's any data corruption at all, WinDirStat is just extraordinarily slow. Once TreeSize has identified the massive subfolder, you can easily exclude it when copying your files.

Mr Ethernet
  • 4,459