ISTM that your benchmark graph is very unattractive.
The numerous dips would suggest that the drive is having difficulty reading, and that this difficulty exists from outside zone to inner zone. I’m not an expert, but I suspect that the drive may have a weak head. Alternatively, it could be that other Windows tasks are interfering with the test.
I would perform a complete surface scan using MHDD. MHDD is a DOS based utility that will identify “slow” sectors, ie those that require several retries before they can be read without error.
Google turns up the following examples of benchmark results that look much cleaner than your own:
HD Tune benchmark graphs for WD10EARS-00MVWB0:
http://img822.imageshack.us/img822/6484/97803426.png
http://img405.imageshack.us/img405/9994/hdtunebenchmarkwdcwd10e.png
HD Tune benchmark graphs for WD20EARS-00MVWB0:
http://i93.photobucket.com/albums/l53/popeye0/WD20EARS/015_WD20EARS.jpg
http://img.danawa.com/images/descFiles/2/836/1835470_1_1290686431.jpg ISTM that your benchmark graph is very unattractive.
The numerous dips would suggest that the drive is having difficulty reading, and that this difficulty exists from outside zone to inner zone. I’m not an expert, but I suspect that the drive may have a weak head. Alternatively, it could be that other Windows tasks are interfering with the test.
I would perform a complete surface scan using MHDD. MHDD is a DOS based utility that will identify “slow” sectors, ie those that require several retries before they can be read without error.
Google turns up the following examples of benchmark results that look much cleaner than your own:
HD Tune benchmark graphs for WD10EARS-00MVWB0:
http://img822.imageshack.us/img822/6484/97803426.png
http://img405.imageshack.us/img405/9994/hdtunebenchmarkwdcwd10e.png
HD Tune benchmark graphs for WD20EARS-00MVWB0:
http://i93.photobucket.com/albums/l53/popeye0/WD20EARS/015_WD20EARS.jpg
http://img.danawa.com/images/descFiles/2/836/1835470_1_1290686431.jpg
ISTM that you should be expecting a read transfer rate of about 113MB/s at the outermost zone and about 50MB/s at the innermost. This corresponds to a difference of about 2:1 between the outer and inner diameters of the drive. Since you are reading from one partition and then writing to another partition on the same drive, you would expect that the maximum possible read/write transfer rate would be halved, ie 56MB/s at the outer zone, and 25MB/s at the inner zone. If you are copying from outer zone to inner zone, then the figure would be somewhere in between. I suspect that your initial high result could be due to the effect of caching, either by the drive itself, or by your OS. Afterwards the figure should settle down to the sustained transfer rate specification of your drive, ie the data rate to and from the platters, rather than the data rate into and out of cache memory.
BTW, if we imagine a curve of best fit in place of your jagged benchmark graph, we could estimate a maximum of 113MB/s at the outermost zone, and about 90MB/s at the innermost zone. This is not the typical 2:1 ratio that we would expect to find. Instead, it appears to me that your WD10EARS drive may actually be a WD20EARS that has been short stroked. I say this because if you examine the 1000GB point on the WD20EARS graphs, the transfer rate is about 90MB/s, which corresponds to the transfer rate at the end of your own WD10EARS drive. To me this suggests that your drive should be performing much faster than other WD10EARS drives, if not for the apparent head problem.