Is it possible for data corruption to be somehow transferrable?
I had an old hard drive with tons of files that was having a lot of issues seeking/accessing them (super slow rates, etc.). After copying them byte for byte to another drive, the new drive has the same difficulties accessing them.
Neither drives were fragmented so I am completely at a loss.
>>62158275
The files themselves are missing bits here and there. Hence, the butterfly effect. Or something.
When the files open they are perfectly fine but just the process of opening or accessing them takes ages.
For example, a 7KB txt file just took 15 seconds to open.
Another example, opening a folder makes it stall out for 1-2 minutes.
This would be totally understandable if the HDD was failing but this is a brand new one I just copied the data onto.
>>62158275
>how come when I copy corrupt data from one hard drive to another it isn't magically fixed?
>>62158275
Your operating system doesn't have the capabilities of repairing your files, no matter how many times you copy them.
>>62158433
Poor choice of words. It's fine once opened it's just the accessing part that is the problem.
It's the symptoms you'd have if your hard drive motor was failing but this is occurring on both the old and new hard drive.
If it's not fragmentation could it be partition table or file system issues of some kind? It's coming from an old NTFS partition.
>>62158695
Try opening the 7KB text file and copying it's content to a new file and check if that one takes 15 seconds to open up.
>>62158874
It opens up fine the second time.
Same with the folders. After they're opened once they open fine afterwards.
>>62158975
to me it sounds like the partition table.
Try checking the drive for errors
Last resort is to create a new partition (probably on the new drive) and copy the files over so that they are recreated on the new table rather than having an exact clone of the buggy table.
>>62159101
really tired. MFT*
>>62158275
If you cloned the whole fucking drive, if the old drive's filetable was fucked then your "new" one is as well.
Format the new drive, and then copy over the actual files you need from the old one.
>>62159101
>>62159110
>>62159128
Actually the partition was newly created. The files were copied byte for byte onto it (via FastCopy)
>>62159757
Look at them in a hex editor. Are they messed up some invisible way?