Command Timeout after 6.1.4 update

I have three drives that are coming up with a smart status warning "Command timeout".

Threshold is 000 on all three however.

Didnt have this warning prior to the update.

smart report?

same problem.

SMART short test appears clean (attached) other than command time out.

I used to get warnings notifications on array start but it never showed as yellow in the dashboard.

Is there a way to clear this in the webgui so that I can see when something changes in the future and not constantly have to check it?

ST2000DL003-9VT166_5YD4VZA8-20151117-1952.txt

I have recommended ignoring Command Timeout, as it is essentially undefined currently.  It appears to usually (but not always) be 3 coded values, but we have no info as to how they should be interpreted, and I haven't seen any significant correlation with any drive issues.  I personally have not found it useful at all.  I do understand that BackBlaze says there is something significant in Command Timeout changes, but they haven't related publicly what they have found, and their published data doesn't show any correlation that I could see (in a quick scan).

My own recommendations for SMART monitoring are in a feature request here, but that post has been pushed all the way back to the 6th page.

Not anymore, bumped the thread as it is a lot more important.

I also have 2 drives reporting the same error. One of the drives was reporting a bad sector prior to the upgrade and now its reporting 2 (along with the command timeout).

I have recently upgraded to Unraid 6 and i'm loving Docker, VM, and the new gui.

But i also have the same issue here after the update to 6.1.4, my cache drive showed a triangle in 6.1.3 i had a green thumbs up, even tough the smart error was already there. I downgraded tot 6.1.3 the green thumb up remained, o sectors pending.

I tend to like the thumbs up better than the triangle

added smartlog en and screenshots.

tower-smart-20151118-2134.zip

Same for me.

Fine on 6.13, upgraded to 6.14 and have 2 disks showing "Command Timeout" with 000.

I have recently upgraded to Unraid 6 and i'm loving Docker, VM, and the new gui.

 

 

But i also have the same issue here after the update to 6.1.4, my cache drive showed a triangle in 6.1.3 i had a green thumbs up, even tough the smart error was already there. I downgraded tot 6.1.3 the green thumb up remained, o sectors pending.

 

I tend to like the thumbs up better than the triangle

 

added smartlog en and screenshots.

You can chose to ignore those SMART attributes, go to Settings -> Notification Settings, click "Advanced View" and uncheck the corresponding attributes.

Same issue here, on a temporary Seagate NAS 4TB (ST4000VM000).  Connected to the AMD chipset SATA port.

# Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value

1 Raw read error rate 0x000f 119 099 006 Pre-fail Always - 225140136

3 Spin up time 0x0003 091 091 000 Pre-fail Always - 0

4 Start stop count 0x0032 099 099 020 Old age Always - 1768

5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always - 0

7 Seek error rate 0x000f 067 060 030 Pre-fail Always - 6267534

9 Power on hours 0x0032 095 095 000 Old age Always - 4633 (6m, 9d, 1h)

10 Spin retry count 0x0013 100 100 097 Pre-fail Always - 0

12 Power cycle count 0x0032 100 100 020 Old age Always - 49

184 End-to-end error 0x0032 100 100 099 Old age Always - 0

187 Reported uncorrect 0x0032 100 100 000 Old age Always - 0

188 Command timeout 0x0032 100 098 000 Old age Always - 128850984990  <- this keeps changing between 98 and 100 every few minutes on this drive

189 High fly writes 0x003a 100 100 000 Old age Always - 0

190 Airflow temperature cel 0x0022 058 058 045 Old age Always - 42 (min/max 22/42)

191 G-sense error rate 0x0032 100 100 000 Old age Always - 0

192 Power-off retract count 0x0032 100 100 000 Old age Always - 2

193 Load cycle count 0x0032 100 100 000 Old age Always - 1768

194 Temperature celsius 0x0022 042 042 000 Old age Always - 42 (0 7 0 0 0)

197 Current pending sector 0x0012 100 100 000 Old age Always - 0

198 Offline uncorrectable 0x0010 100 100 000 Old age Offline - 0

199 UDMA CRC error count 0x003e 200 200 000 Old age Always - 0

Both the ST4000VM000 are doing it now.  WD drives are fine.  HGST are fine.  Tested on both AMD SATA and the Supermicro HBA.

It really sees to be a seagate thing. 2 Hitachis, 1 WD, and 1 Seagate ST2000DL003 ... Seagate is my only problem child as well.

You can tell unraid to ignore that SMART attribute.

The only issue is the default setting of monitoring that attribute.

You can tell unraid to ignore that SMART attribute.

 

The only issue is the default setting of monitoring that attribute.

In the new approach it is possible to set global and individual per disk settings, this allows to have the attributes enabled globally, but it can be disabled for any Seagate disk in your system, for example.