diagnostic duration of WD green versus red disk

  • Thread starter Thread starter pedro1492
  • Start date Start date
P

pedro1492

I was testing the hard drives from a PC what blew up (well the power supply
did - a big blue flash followed by burnt smell).
First I tested a WD red 3 TB. The long diagnostic took about 6 hours.
Then I tested a WD green 1 TB, but same diagnostic took about 4 hours.
So the red test is going twice as fast. What gives? Does this suggest
that the green drive was stuck on SATA 150 rate, or it just spins slow
as buggery?
BTW I was using Seatools, as it shows the power-on hours.
 
I was testing the hard drives from a PC what blew up (well the
power supply did - a big blue flash followed by burnt smell).
Click to expand...
First I tested a WD red 3 TB. The long diagnostic took about 6 hours.
Then I tested a WD green 1 TB, but same diagnostic took about 4 hours.
So the red test is going twice as fast. What gives? Does this suggest
that the green drive was stuck on SATA 150 rate,
Click to expand...

No, the SATA rate shouldn't affect the time that particular test takes much.
or it just spins slow as buggery?
Click to expand...

More that the slower spin rate is most of the reason for the slower test.
 
No, the SATA rate shouldn't affect the time that particular test takes much.

More that the slower spin rate is most of the reason for the slower test.
Click to expand...

I put on the jumper that forces SATA to the string telephone rate, and
repeated the test - it was approx 1% longer. So you are correct green
is mechanically challenged.
 
I was testing the hard drives from a PC what blew up (well the power supply
did - a big blue flash followed by burnt smell).
First I tested a WD red 3 TB. The long diagnostic took about 6 hours.
Then I tested a WD green 1 TB, but same diagnostic took about 4 hours.
So the red test is going twice as fast. What gives? Does this suggest
that the green drive was stuck on SATA 150 rate, or it just spins slow
as buggery?
BTW I was using Seatools, as it shows the power-on hours.
Click to expand...

If you use the smartmontools, ot tells you the expected
time for a full (long) SMART selftest. If you have no
load on the disk, these should be pretty accurate. But to be
sure, you need to look at the individual attributes anyways,
the vedor thresholds are typically over-optimistic.

For somethign with a gui, the "Hard Disk Sentinel" is a good
choice.

Arno
 
Back
Top