|Version 30 (modified by 23 months ago) ( diff ),
Table of Contents
- Case Studies
- SMART Testing
- SMART Attributes
In this section we provide documentation upon basic and general understanding of smartmontools. Have a look on the FAQ Page too, where you find information concerning more specific issues.
If you are having trouble understanding the output of smartctl or smartd, please first read the manual pages installed on your system:
man 8 smartctl man 8 smartd man 8 update-smart-drivedb man 5 smartd.conf
Here are on-line versions of the smartmontools man pages:
Note that these are the manual pages for the current version of smartmontools in the developers SVN repository; they might not correspond to the (possibly older) version of smartmontools installed on your system. So the manual pages installed on your system should be regarded as definitive for your installation.
Monitoring Hard Drive Health on Linux with smartmontools ("Random Bits", Jan 2009)
Step by step for beginners. Clear instruction with very nice layout :-)
- smartctl Example Reports
- Graphical Monitoring with Munin: Agony of a dying disk (plus buggy disk firmware)
- Types of tests
- Handling and configuration
If you find strange output, or unknown attributes, please look in the below listed pages with vendor specific info.
When you don't find an answer to your question there, send an email to smartmontools-support and we'll help you try and figure it out.
Different vendors, different interpretation..
The RAW values of SMART attributes (temperature, power-on lifetime, and so on) are stored in vendor-specific structures.
Sometime these are strange. Hitachi disks (at least some of them) store power-on lifetime in minutes, rather than hours.
IBM disks (at least some of them) have three temperatures stored in the raw structure, not just one. And so on.
Bruce Allen said on smartmontools-support list (2007-08-31): The raw values for certain Attributes have vendor-specific meanings and are hard to interpret unless you know exactly how the vendor uses them on that specific disk model. The bit pattern might be a mix of flags, counters, and bitmasks, for example, leading to large and strange numbers. I wouldn't worry about the raw values very much. The normalized values (VALUE/WORST/THRESH) should have a sensible interpretation.
Franc Zabkar has a special interest in deciphering raw values. Read some of his elaborated postings on smartmontools-support mailing list.
External Information Resources
See Links page.
All content in this wiki is published under GNU GPL.