Red completed successfully dialog

[DaveQB]

Happy Spinrite owner and user for about 15 years. Haven't missed an episode of SN since I started listening circa episode 150 (circa 2008).

I cannot find this in the FAQ. Happy to be pointed to it if I have missed it.

Upon completing a level 4 of a HDD, I had the regular completed dialog but with a red background. I thought there was an issue, so moved on to inspect the result and all good apart from 5 command timeouts.

Am I right in thinking we have 3 completed scenarios
1. Completed with the blue background = all good
2. Completed with the red background = mostly good
3. Completed with error dialog = failed

Thank you.

 

[PHolder]

The red dialog was actually my idea, and is a new feature in SpinRite 6.1. It's meant to allow the "screen blanker" to change colour to get your attention about something happening that you probably would want to be aware of. Did you check the logfile.. maybe an error was recovered?

I'm guessing that if you never interacted with the UI during the run, that the internal variable that indicates it should be a red dialog on the screen blanker remains set and thus you see it at the end.

TL;DR: @Steve Will probably have to comment definitively, but I'm guessing the red indicates at some point it popped up something for your attention. It could be those timeouts, or maybe it was overheating (according to S.M.A.R.T. and it delayed to recover to a lower temp, or something like that.)

 

[DaveQB]

I'm guessing that if you never interacted with the UI during the run

Correct.


Interesting. New feature. Explains why I am only noticing now. I thought, "how unobservant am I!?"
I wish I grabbed a screenshot now. Bugger.

I checked the Details Technical Log. The command timeout is all I noticed. I can share screenshots; it is still open (a VM with a HDD passed through).

 

[PHolder]

I presume a command timeout must be enough then. Hopefully at some point Steve will come along and give us some additional insight.

If there are pics you think would be beneficial, please share away. (Just be aware the site has a limit of 500k for each picture, so you may need to take steps to get the size down.)

 

[DaveQB]

Starting the level 4 again on this drive. I might have a screenshot in 4 hours that I can post in the morning.
Thanks.

 

[DaveQB]

6 command timeout errors this run. 5 the first run.

 

[peterblaise]

Level 5 ?

;-)

 

[peterblaise]

Does the log tell you what sectors to work on?

If the data is important:

SPINRITE NORAMTEST DYNASTAT 1 LEVEL 5 NOREWRITE PORT 0 #123456 #250000

If the data is NOT important:

SPINRITE NORAMTEST DYNASTAT 0 LEVEL 5 PORT 0 #123456 #250000

... where PORT 0 #123456 #250000 is the drive
location and sector numbers taken from prior
logs.

Or just make the adjustments manually.

Share the log and we'll help.

 

[PHolder]

6 command timeout errors

I presume the command time out is the drive doing something that is keeping it busy... maybe it's having to do a lot of retries to read a certain sector, or maybe there are sectors that have been remapped in a way that take it longer to get to them. It's good to know it's happening, as it's a sign the drive is probably not absolutely 100% happy in its life.

 

[DaveQB]

Does the log tell you what sectors to work on?

If the data is important:

SPINRITE NORAMTEST DYNASTAT 1 LEVEL 5 NOREWRITE PORT 0 #123456 #250000

If the data is NOT important:

SPINRITE NORAMTEST DYNASTAT 0 LEVEL 5 PORT 0 #123456 #250000

... where PORT 0 #123456 #250000 is the drive
location and sector numbers taken from prior
logs.

Or just make the adjustments manually.

Share the log and we'll help.

Thanks. No other issues reported. No sectors mentioned, nothing. Save for the commend timeouts, it is a perfect result
Two runs on this drive, on level 4 and similar results both times.

Booting from an ISO, it does report is can't save the log file anywhere :-( I might have to try and get a floppy img of 6.1..

 

[DanR]

Drive make and model?

 

[peterblaise]

@Steve - it would be nice if the upcoming SpinRite 6.1 R5 were to log the sectors under scrutiny during command timeouts, minor troubles, and command aborted, and any other Sector Events:

|==========================================================================|
| Final Sector Event Counts |
|--------------------------------------------------------------------------|
| command timeout: 999,999 command aborted: 999,999 |
| comm/cable errs: 0 not recoverable: 0 |
| minor troubles: 999,999 sect neverfound: 0 |
| dynastat recovr: 0 defective sectr: 0 |
|==========================================================================|

 

[DaveQB]

Drive make and model?

Another. This time, a bit more juicy info:

This drive is a:


ATA-8: WDC WD5000AADS-00S9B0, 01.00A01, max UDMA/133
976773168 sectors, multi 0: LBA48 NCQ (depth 32), AA
configured for UDMA/133
Direct-Access ATA WDC WD5000AADS-0 0A01 PQ: 0 ANSI: 5


But I think I have my answer. There are indeed 3 status' of a drive after a run now.
1. Good
2. Good but some issues (the red "OK" dialog I am seeing now)
3. No good.