Open krim404 opened 5 months ago
same! I'm having issues with my Seagate Ironwolf Pro 16TB (ST16000NE000-2RW103). Other Seagate drives are fine (so far)
was supposedly fixed in v0.7.2 #527 #522 :
other attributes are weirding out too.
I also have some problems with my Seagate ST12000NM0127 12Tb drive. It's new and I get the following warnings.
I'm not sure what to make of it. For me it seems the 195 attribute is also parsed incorrectly.
having a similar issue with attribute 195 on seagate ST10000NM0046 drives.
Havin this issue with a ST20000NM007D-3DJ103 (Exos X20 20 TB) Its the only field that goes haywire though.
Not to pile on, but, if helpful, also experiencing this issue on my Seagate Exos X18 16TB (ST16000NM000J) drives. Running master#48feee5
.
Per the Seagate SMART specification on attribute 188:
3.11 Attribute ID 188: Command Timeout Count Normalized Command Timeout Count = 100 – Command Timeout Count . This attribute tracks the number of command time outs as defined by an active command being interrupted by a HRESET and COMRESET or SRST or another command.
The normalized value is only computed when the number of commands is in the range 103 to 104. The CommandCount and ErroCount are cleared when Number Of Commands reaches 104. The error count used to compute normalized value is not reported in attribute Raw value. It is reported in vendor info area of Attribute sector, bytes 474:475.
If Command Timeout Count is > 99, normalize value of 1 is reported. The initial Worst Value is set to 0xFD as a special case.
Raw Usage Raw [1 – 0] = Total # of command timeouts, with Max hold of FFFFh Raw [3 – 2] = Total # of commands with > 5 second completion, including those > 7.5 seconds Raw [5 – 4] = Total # of commands with > 7.5 second completion
i found a minor bug: on some of my hdds the normalization of smart details gets completly wrong. Especially on Seagate Drives. In my example the number 0 gets normalized to 100 which results in a false warning.
See attached image.