From: Christopher Wolf <smartmon@th...> - 2003-12-04 02:11:46
All three of the drives (2 Seagates and a new Maxtor) in my Debian 3.0
system report "Not in smartctl database" for version 5.21
Presumably, this means the attributes are not reported correctly.
But will the drive, smartctrl and smartd still report pending failure
correctly? Or may that information also be interpreted incorrectly?
From: Bruce Allen <ballen@gr...> - 2003-12-04 10:05:29
> All three of the drives (2 Seagates and a new Maxtor) in my Debian 3.0
> system report "Not in smartctl database" for version 5.21
> Presumably, this means the attributes are not reported correctly.
Only the names and the format of the raw values may be incorrect.
> But will the drive, smartctrl and smartd still report pending failure
I've updated the smartmontools FAQ as below.
# My ATA drive is not in the smartctl/smartd database. Does this break
anything? How do I get it added?
If your drive is not in the database, then the names of the Attributes
(displayed in the ID# column of smartctl -A /dev/hd?) and the format of
the the raw Attribute values shown in the RAW_VALUE column may be
incorrect. This is mostly cosmetic: the essential drive health
monitoring/testing functionality of smartmontools does not depend upon the
To have your drive added to the database, first use the command: smartctl
-t short /dev/hd? to run a short self-test on the drive, and wait a few
minutes for the test to complete. The timestamp in the self-test log will
help us to determine whether Attribute 9 is being used to store the
lifetime in hours, minutes, or seconds. Then email the output from:
smartctl -a /dev/hd? to smartmontools-support as an email attachment. If
you need to use any of the vendor-specific display options (-v options)
with this drive or if any of the Attributes are behaving strangely please
include that information as well.
Get latest updates about Open Source Projects, Conferences and News.