No, I can confirm that it is not a problem with the software and may not related to the disk drive (if the disk drive is 100% healthy and the extended test did not show any problems).
The problem is likely the USB adapter/docking station/enclosure itself which works "between" the computer and the WD Gold hard disk drive.
There is good chance that the docking station (more precisely its USB-ATA bridge chip) overheats during an excessive data transfer caused by read/write commands for so long time (as I see on the image, 60 hours). When this chip "stuck" then it does not respond for the operating system. As a result, Windows may issue a timeout error (as you can see) and any software/applications (Hard Disk Sentinel in this case
) also does not receive any response from the device, so the software seems "not responding" as it is waiting for the disk drive.
It is completely normal and expected in this case I'm afraid.
If possible, maybe you can try
- add extra cooling for the USB docking station. Some users placed notebook cooling pad below the USB docking station / external drive to make additional airflow which can help to make stable operation
- make smaller tests: instead of testing the whole drive at once, you can try to test only (for example) 1/4 area of the disk at once to prevent too much stress of the docking station. For this, please select Disk menu -> Surface test, the proper test type and drive and before starting the test, select the Configuration tab. There you can select the Limit testing to specific data blocks
and specify the First block / Last block
For example, if you set First block = 0, last block = 2499, then the test will process the first 1/4 only.
Then First block = 2500, last block = 4999, then the test will process the second 1/4 only.
The Disk menu -> Extended self test is different: it runs "inside" the hard disk drive: Hard Disk Sentinel starts the test, reads the progress and results only. As it does not cause TB's of data transferred via the mentioned USB chip, it does not cause overheat - this is why there were no problems in that case.
This is exactly why it may be good option to test both ways: by the Extended self test, we can verify the drive "internals" and by the surface test, we can verify even other components in the storage chain (eg. USB adapter/docking station) too.