On Mon 03 Mar 2025 at 17:55:59 (-0800), David Christensen wrote: > I have always wondered if the decimal numbers in the smartctl(8) > "RAW_VALUE" column are actual event counts, or a decimal > representation of some binary bit field whose correct interpretation > only the manufacturer knows (?).
One where that is true is 188, Command_Timeout. I don't think I recall seeing any others. kirk:188 Command_Timeout -O--CK 100 096 000 - 137441116198 '0x2000210026' kirk:188 Command_Timeout -O--CK 100 096 000 - 154621313067 '0x240026002b' kirk:188 Command_Timeout -O--CK 100 096 000 - 167506411567 '0x270029002f' kirk:188 Command_Timeout -O--CK 100 096 000 - 167506411569 '0x2700290031' lulu:188 Command_Timeout -O--CK 100 099 000 - 12885098499 '0x300030003' toto:188 Command_Timeout -O--CK 100 099 000 - 8590065705 '0x200020029' Some people on the list have reported raw value triples, but all the singleton values that I've encountered have decomposed to simple hex triples like those (of my disks) above. I have no idea what they mean. > I typically look at the "VALUE" column, as it usually represents an > integer percentage that starts at 100 (%) and diminishes towards 0 (%) > as the drive degrades. That said, I have seen starting values of 120, > 200, and possibly 255 (?). So, again, only the manufacturer knows. I've read that 254 is the maximum. Presumably 255 has some reserved significance. Cheers, David.
