WD royl selfscan, use MHDD test, there are dozens of green blocks of color <150ms, have any good way to deal with it?

Selfscan with MHDD? Omg, Dmitry, since when?

You can always write scripts to start selfscan with mhdd

I know you know that we know... in this case most probably the term 'selfscan' was misunderstood.

he probably means surface scan "F4" right?

_________________
Zero Alpha: zeroalpha.com.au
Find Cheap Donor Drives App: https://www.zeroalpha.com.au/donor-drive-app Updated February 2026

I think he/she knows what he/she is talking about.

Anyways, the way I read the questions is that after a selfscan the drive was checked with Mhdd and has allot of sectors with <150ms, the operator want's to know if there is anything that can be done to get faster reads on those sectors. I am not a selfscan guy, so I can not help

BlackST, Rameez, seams that the OP requires your type of expertise and deeper knowledge of SS here.

quasimodo：You understand correctly! WD royl selfscan normal completion!With mhdd test, there are dozens or more of the green block with <150ms, Who have
a better approach?

depending on what your main goal is, you could add them to the G-list if there are not to many of them. Have you been able to determine on which head the slower sectors reside on?

More than to G-list I suggest to :

1) ERASE (zerofill) HDD first as new adaptives are being used and rescan : most probably the problem is solved
2) if no joy, instead of adding to G, add to P all "delays".
3) depending on many things, at the end of SS you have defects added to G and still P empty : in this case shift G to P... voila - the drive is fixed

... or the drive has really bad surface.

BlackST: Run selfscan before cleared the P-List, selfscan completed, P-list a large amount of data, you can run the user area of the calibrate it?

It is normal that p-list is filled and you have a lot of entries - the drive is large! . Yes, you can try internal format after - if I understood correctly. Sometimes some adaptation of the script or a custom made one can help, it depends on surface conditions. BTW, if there are errors still 'concentrated' on definite areas, why not work on zones ?