From: Tom Metro <tmetro+<smartmontools@gm...> - 2007-08-06 19:06:15
During recent hot weather I was notified by smard:
smartd: Device: /dev/sdb, Failed SMART usage Attribute: 190
A search on the mailing list didn't turn up anything useful, but Google
turned up this page:
which suggests that it is the "Airflow temperature" attribute on Seagate
drives, and how to interpret the numbers.
I presume that a goal of the smartmontools project is to replace as many
Unknown_Attributes with the correct labels. The drive in question is
Device Model: ST3320620AS
Serial Number: 5QF0N9JV
Firmware Version: 3.AAC
User Capacity: 320,072,933,376 bytes
Device is: Not in smartctl database [for details use: -P showall]
I seem to recall downloading the latest version a while ago and
determining that the drive has already been added to the database, but...
Quoting from the FAQ:
> My ATA drive is not in the smartctl/smartd database.
> If your drive is not in the database, pleaes check here to be sure
> that you are using the latest smartmontools release.
Obtaining the absolute latest version of an application is becoming less
and less practical as we become more reliant on packages provided by
operating system distributions.
And doing so seems largely unnecessary when the only component that
likely needs to change is a non-executable data file.
There should be a web UI for querying the database (or simply a link
directly to the database file that can be downloaded and searched), so
users can determine whether a drive already exists in the database
without having to install the latest smartmontools.
And for those who package smartmontools, the drive database should be
split out from the main application package so it can be independently
updated from other repositories that specialize in maintaining packages
for "volatile" data.
Also in the FAQ:
> Why is my disk temperature s reported by smartd as 150 Celsius?
> The way in which the Raw values are printed, and the names under
> which the Attributes are reported, is governed by the various '-v
> Num,Description' Directives described in the smartd man page.
This implies that -v can be used to set an arbitrary label for an
arbitrary attribute ID, and indeed the man page is a bit vague on that
as well, but it seems the -v switch only accepts a small list of
specific enumerated options (with the exception of 3 options where the
ID portion can be an arbitrary value).
Shouldn't there be a switch to permit overriding the label of a
vendor-specific attribute that is either absent or incorrect in the
I'd like to be able to apply a correct label for ID 190 on the above
system without having to replace the distribution supplied package for