Victoria program finds scan bad areas during tests

[loninapleton]

I'm trying to learn how to use Victoria. There is a sequence of running scan in sever modes which I did with
the screen shot showing the third scan pass.

Can anything be done about the listed scan bad areas?

Is this where the "Edit" option at top of screen is used?

Attachments

[diybit]

This drive is perhaps not so bad! You have wrongly set the timeout to 100ms.
It's not rare that some block of 256 bytes take about 100-200ms to be read, and so even longer with a 2048 block size.
I suggest you retest those "bad" parts, and be sure your drive is not doing other things while scanning.
Let this timeout to default that is probably 10000ms to really see what is going on with this drive, the OS will anyway give up with CRC after about 5-7 seconds in case of true bad sector.

[carterodell]

It is possible to fix the stated faulty scan locations by using the "Edit" button located at the top of the screen in Victoria.

Be careful and think through the consequences of your edits before pressing the "edit" button. It is highly recommended that you create a backup of your data prior to making any changes in Victoria.

[diybit]

As I know, "Disk Editor" is to edit the content of sectors, and not to "repair" them, and if I right remember, an error is return in case of reading a bad sector, so you probably can't even write contents if bad, and so this button is useless for you.

I have forgot to mention that SMART should have pending sectors if those are true bad sectors.

[pclab]

Victoria should be used to diagnose a drive, not to "repair" it. If it shows errors, usually I keep the drive for parts or then recycle it.
I never trust on a drive that already shows errors.