Hi, got fresh wd red 4tb and fired victoria scan 30mins after power up. I'm wondering if 200ms green blocks is withing expectation considering its a brand new disc. From what I've found on web, other guys scans of their fresh hdds didnt have green blocks, just few 50ms grey blocks (although I havent found many screenshots)

In a Windows environment it is always possible that some background task may be competing for the attention of the CPU. You might like to repeat the scan using MHDD in DOS.

BTW, there is a big drop in the transfer rate at the 250GB mark. I don't know what to make of that. Obviously it's moving to a slower zone, but I would have thought that the decline would be much more gradual.

_________________
A backup a day keeps DR away.

Alright, I'll do mhddd in dos. But let's assume that there will be same/similiar green 200ms blocks, what could it mean? It's expected for them to appear sometimes on new 4tb hdd, or I just got bit-less-than-standard-quality piece of hdd?

Few things happened:

1. MHDD scan detected two <500ms blocks



Called seller, told my new hdd has dozens of slow 50-500ms blocks and they agreed to replaceme.

2. before replacement, I've zeroed first with wd data lifeguard, then zeroed again in hddscan, hddscan results showed a lot more of green blocks and orange (2-3x more)

3. after replacement, I've launched mhdd straight away, results are very similiar to mhdd scan of previous hdd:



SMART gives no interesting info (no errors with cable, no reallocated sectors etc)

I don't know what to think. Few options:

a). replacement hdd is from the same batch as previous (substandard batch?)
b). just super unlucky
c). my motherboard controller is wonky (asrock p67 extreme4, bought in 2011, tried with different sata2 port and cables are short in length and new, also for this mhdd scan, I've plugged off all other hdd/ssd, so only this replacement hdd was detected in mhdd)
d). thats just how wd red 4tb are now

Any thoughts?