Commit 66a7aa47 authored by ballen4705's avatar ballen4705
Browse files

Web sources

git-svn-id: 4ea69e1a-61f1-4043-bf83-b5c94c648137
parent 31e5b350
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<title>smartmontools Home Page</title>
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
<meta name="author" content="Bruce Allen">
<meta name="description"
content="SMART S.M.A.R.T. linux disk monitoring">
<div align="center">
<h1> </h1>
<div align="center">
<h1> </h1>
<h1><font color="#3333ff">smartmontools HOME PAGE &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;
</font><a href=""><img
width="210" height="62" border="0" alt=" Logo"
<h3><font color="#3333ff"> </font></h3>
<div align="left">This is the home page for smartmontools. &nbsp;The smartmontools
package contains two utility programs (<font color="#3333ff"><b>smartctl</b></font>
and <font color="#3333ff"><b>smartd</b></font>) to control and
monitor storage systems using the Self-Monitoring, Analysis and Reporting
Technology System (S.M.A.R.T.) built into most modern ATA and SCSI hard
disks. It is derived from the smartsuite package, and includes support
for ATA/ATAPI-5 disks. It should run on any modern linux system.<br>
For your convenience, this is a single page, so you can print it easily.<br>
<hr width="100%" size="2">
<li><a href="#howtodownload">How to download and install smartmontools</a></li>
<li><a href="#FAQ">Frequently Asked Questions</a></li>
<li><a href="#testinghelp">The code needs to be tested on SCSI disks/tapes</a></li>
<li><a href="#differfromsmartsuite">How does smartmontools differ
from smartsuite?</a></li>
<li><a href="#references">Useful references on S.M.A.R.T.
and ATA/ATAPI-5, -6, and -7</a></li>
<li><a href="#sampleoutput">Some sample output from smartmontools</a></li>
CVS archive</a> and <a
href="">SourceForge projects
group page</a></li>
Mailing list and archives</a> for smartmontools support<br>
<hr width="100%" size="2"><b><br>
</b><b><a name="howtodownload"></a></b><b> How to download and install
</b>There are three different ways to get and install smartmontools.
&nbsp;You can use any one of these three procedures. &nbsp;Just after "Method
3" below are some instructions for trying out smartmontools once you have
completed the installation.<br>
<li><b>First Method - Install from the RPM file:</b><br>
<li>Download the latest binary RPM file (<tt>*.rpm</tt>) from
. &nbsp;Don't get the SRPM file (<tt>*.src.rpm</tt>).</li>
<li>Install it using RPM. &nbsp;You must be root to do this:<br>
<tt>su root</tt> &nbsp;(enter root password)<br>
<tt>rpm -ivh smartmontools-5.0-1.i386.rpm</tt></li>
<li>If you receive an error message, you have probably previously
installed the <tt>smartsuite</tt> package, or RedHat's kernel-utils package,
which provide older versions of the <tt>smartd</tt> and <tt>smartctl</tt>
utilities. &nbsp;In this case you should use the <tt>--nodeps</tt> or
<tt> --force</tt> arguments of rpm to replace these two utilities:<br>
<tt>rpm -ivh --nodeps --force smartmontools-5.0-1.i386.rpm</tt><br>
<li><b>Second Method - Install from the source tarball</b>:<br>
<li>Download the latest source-code tarball from <a
<li>Uncompress the tarball (note: you probably want the most
recent release)<br>
<tt>tar zxvf smartmontools-5.0.tar.gz</tt></li>
<li>The previous step created a directory called smartmontools-5.0
containing the code. &nbsp;Go to that directory, build, and install:<br>
<tt>cd smartmontools-5.0<br>
make install &nbsp;</tt> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[only root can do this]<br>
<li><b>Third Method - Download code directly from the CVS archive:</b><br>
<li>Download the latest code snapshot from CVS. If prompted for a
password, simply press the Enter key. &nbsp;Note that the two lines below
that start "<tt>cvs</tt>" are long! <br>
login</tt> <tt><br>
cvs -z3
co sm5</tt><br>
<li>The previous step created a subdirectory called <tt>sm5/</tt>
containing the code. Go to that directory, build, and install:<br>
<tt>cd sm5<br>
make install &nbsp;</tt> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[only root can do this]<br>
<b>After installing using Method 1, 2 or 3 above, you can read the
man pages, and try out the commands:</b><br>
<blockquote><tt>man 8 smartctl</tt><br>
<tt>man 8 smartd</tt><br>
<tt>smartctl -etf /dev/hda &nbsp;</tt>[only root can do this]<br>
<tt>smartctl -a /dev/hda &nbsp; &nbsp;</tt>[only root can do this]</blockquote>
<hr width="100%" size="2"><br>
<a name="FAQ"></a><b>Frequently-asked questions<br>
</b>If your question is not here, please <a
href=""> email me</a>.<br>
<li><b>What do I do if I have problems, or need support? &nbsp;Suppose
I want to become a developer, or suggest some new extensions?</b><br>
Please send an email to the <a
smartmontools-support mailing list</a>.<br>
<li><b>What are the future plans for smartmontools?</b><br>
My plan is that smartmontools-5.x will support ATA/ATAPI-5 disks.
&nbsp;Eventually, we'll do smartmontools-6.x to support ATA/ATAPI-6 disks,
smartmontools-7.x for the ATA/ATAPI-7 standard, and so on. &nbsp;The
"x" will denote revision level, as bugs get found and fixed, and as enhancements
get added. &nbsp; If it's possible to maintain backwards compatibility,
that would be nice, but I don't know if it will be possible or practical.</li>
<li><b>Why are you doing this?</b><br>
My research group runs a beowulf cluster with 300 ATA-5 disks. &nbsp;We
have more than 20 TB of data stored on the system. &nbsp;It's nice to
have advanced warning when a disk is going to fail.</li>
<li><b>I see some strange output from smartctl. &nbsp;What does it
The raw S.M.A.R.T. attributes (temperature, power-on lifetime, and
so on) are stored in vendor-specific structures. &nbsp;Sometime these are
strange. &nbsp;Hitachi disks (at least some of them) store power-on lifetime
in minutes, rather than hours. &nbsp;IBM disks (at least some of them) have
three temperatures stored in the raw structure, not just one. And so on.
&nbsp;If you find strange output, or unknown attributes, please send an email
to <a
smartmontools-support</a> and we'll help you try and figure it out.</li>
<li><b>What attributes does smartmontools not yet recognize?<br>
</b>From a Hitachi disk: (221)(223)(225)(230)(250)<br>
If you can attach names/meanings to these attributes, please send me
a note to <a
<li><b>When I run <tt>smartd</tt> , the SYSLOG (<tt>/var/log/messages</tt>
) contains messages like this:</b><br>
<tt>smartd: Reading Device /dev/sdv <br>
modprobe: modprobe: Can't locate module block-major-65<br>
</tt>This is because when <tt>smartd</tt> starts, it looks for all
ATA and SCSI devices to monitor (matching the pattern <tt>/dev/hd[a-z]</tt>
or <tt>/dev/sd[a-z]</tt>). &nbsp;The log messages appear because your
system doesn't have most of these devices.<br>
A future release of smartd will have a command-line option to specify which
devices to include or exclude from start-up search.<br>
<hr width="100%" size="2"><b><a name="testinghelp"></a>Help needed in testing
smartmontools, especially on SCSI disks/systems<br>
</b>I have access to a number of systems with ATA S.M.A.R.T. disks,
but I don't have any access to systems with SCSI S.M.A.R.T. devices. &nbsp;I'd
be very grateful to find someone who could help me test the smartmontools
code on SCSI disks. &nbsp;Since it's derived from the smartsuite package,
it should initially work about the same way with SCSI devices as the smartsuite
tools did.<br>
I'd be especially happy if someone would like to take on the task,
as a developer, of maintaining the SCSI code. &nbsp;Do you have a beowulf
cluster with a few hundred SCSI disks? Please volunteer!<br>
<hr width="100%" size="2"><a name="differfromsmartsuite"></a><b>How does smartmontools
differ from smartsuite?<br>
</b>Initially, only in that it supports the ATA/ATAPI-5 standard.
&nbsp;So for example <tt>smartctl</tt> from smartsuite has no facility
for printing the self-test logs, and doesn't print timestamp information
in the most usable way. But smartmontools is derived directly from smartsuite
and is very similar. <br>
The other principle difference is that I'd like to have smartmontools
be a true open-source project, meaning that we keep the files in CVS,
and that other developers who wish to contribute can commit changes to
the archive.<br>
<hr width="100%" size="2"><br>
<a name="references"></a><big><b>Useful references on S.M.A.R.T.
and the ATA/ATAPI standards<br>
</b>If you are having trouble understanding the output of smartctl
or smartd, please first read the manual pages:<tt><br>
&nbsp;&nbsp;&nbsp; man 8 smartctl<br>
&nbsp;&nbsp;&nbsp; man 8 smartd</tt><br>
If you'd like to know more about S.M.A.R.T., then the following
references may be helpful:<br>
<li>The <a href="">ATAPI/ATA-5
Revision 1 specification</a></li>
<li><a href="">Earlier and later revisions
of the ATAPI/ATA specifications</a></li>
<li>The S.M.A.R.T. specification is SFF-8035i (rev E). &nbsp;I
can not find an on-line reference. It can be obtained from the <a
href="">Small Form Factors Committee</a>
. Here is their <a href="">"link"</a>
<hr width="100%" size="2"><a name="sampleoutput"></a><b>Sample output from
<tt> </tt>
<pre><tt>root# smartctl -a /dev/hda<br>Device: HITACHI_DK23BA-20 Supports ATA Version 5<br>Serial Number: 12H7M8<br>Firmware Version: 00E0A0D2<br>ATA minor number (version support) 0x15<br>Drive supports S.M.A.R.T. and is enabled<br>Check S.M.A.R.T. Passed.<br><br>General Smart Values: <br>Off-line data collection status: (0x00) Offline data collection activity was<br> never started<br><br>Self-test execution status: ( 114) The previous self-test completed having<br> the read element of the test failed<br><br>Total time to complete off-line <br>data collection: (1530) Seconds<br><br>Offline data collection <br>Capabilities: (0x1b)SMART EXECUTE OFF-LINE IMMEDIATE<br> Automatic timer ON/OFF support<br> Suspend Offline Collection upon new<br> command<br> Offline surface scan supported<br> Self-test supported<br><br>Smart Capablilities: (0x0003) Saves SMART data before entering<br> power-saving mode<br> Supports SMART auto save timer<br><br>Error logging capability: (0x01) Error logging supported<br><br>Short self-test routine <br>recommended polling time: ( 2) Minutes<br><br>Extended self-test routine <br>recommended polling time: ( 26) Minutes<br><br>Vendor Specific SMART Attributes with Thresholds:<br>Revision Number: 16<br>Attribute Flag Value Worst Threshold Raw Value<br>( 1)Raw Read Error Rate 0x000d 100 100 050 23<br>( 3)Spin Up Time 0x0007 100 100 050 0<br>( 4)Start Stop Count 0x0032 100 100 050 182<br>( 5)Reallocated Sector Ct 0x0033 100 100 010 7<br>( 7)Seek Error Rate 0x000f 100 100 050 506<br>( 9)Power On Hours 0x0032 100 100 060 437<br>( 10)Spin Retry Count 0x0013 100 100 050 0<br>( 12)Power Cycle Count 0x0032 100 100 050 182<br>(192)Power-Off Retract Count 0x0032 100 100 050 11<br>(195)Hardware ECC Recovered 0x001a 100 080 050 80<br>(196)Reallocated Event Count 0x0032 100 100 001 7<br>(197)Current Pending Sector 0x0032 098 097 001 2<br>(198)Offline Uncorrectable 0x0010 097 097 001 3<br>(199)UDMA CRC Error Count 0x003e 200 200 000 0<br>(221)Unknown Attribute 0x000a 100 100 050 0<br>(223)Unknown Attribute 0x0012 100 100 050 0<br>(225)Unknown Attribute 0x0032 098 098 050 2113943230<br>(230)Unknown Attribute 0x0032 100 100 060 12873<br>(250)Unknown Attribute 0x000a 100 070 050 432<br><br>SMART Error Log<br>SMART Error Logging Version: 1<br>ATA Error Count: 3<br><br>Acronyms used below:<br>DCR = Device Control Register<br>FR = Features Register<br>SC = Sector Count Register<br>SN = Sector Number Register<br>CL = Cylinder Low Register<br>CH = Cylinder High Register<br>D/H = Device/Head Register<br>CR = Content written to Command Register<br>ER = Error register<br>STA = Status register<br><br>Timestamp is time (in seconds) since the command that caused an error was accepted,<br>measured from the time the disk was powered-on, during the session when the error occured.<br>Note: timestamp "wraps" after 1193.046 hours = 49.710 days = 2^32 seconds.<br><br>Error Log Structure 1:<br>Error occured at disk power-on lifetime: 424 hours<br>When the command that caused the error occured, the device was active or idle.<br>After command completion occured, registers were:<br>ER:40 SC:05 SN:79 CL:19 CH:2c D/H:e0 ST:51<br>Sequence of commands leading to the command that caused the error were:<br>DCR FR SC SN CL CH D/H CR Timestamp<br> 00 00 08 76 19 2c e0 c8 57586.716<br> 00 00 08 c6 79 19 e0 c8 57586.691<br> 00 00 08 36 9d 01 e0 ca 57586.690<br> 00 00 80 76 20 2c e0 c8 57586.676<br> 00 00 80 f6 1f 2c e0 c8 57586.672<br><br>Error Log Structure 2:<br>Error occured at disk power-on lifetime: 424 hours<br>When the command that caused the error occured, the device was active or idle.<br>After command completion occured, registers were:<br>ER:40 SC:71 SN:85 CL:19 CH:2c D/H:e0 ST:51<br>Sequence of commands leading to the command that caused the error were:<br>DCR FR SC SN CL CH D/H CR Timestamp<br> 00 00 78 7e 19 2c e0 c8 57583.243<br> 00 00 80 76 19 2c e0 c8 57581.389<br> 00 00 80 f6 18 2c e0 c8 57581.385<br> 00 00 80 76 18 2c e0 c8 57581.380<br> 00 00 80 f6 17 2c e0 c8 57581.376<br><br>Error Log Structure 3:<br>Error occured at disk power-on lifetime: 424 hours<br>When the command that caused the error occured, the device was active or idle.<br>After command completion occured, registers were:<br>ER:40 SC:7d SN:79 CL:19 CH:2c D/H:e0 ST:51<br>Sequence of commands leading to the command that caused the error were:<br>DCR FR SC SN CL CH D/H CR Timestamp<br> 00 00 80 76 19 2c e0 c8 57581.389<br> 00 00 80 f6 18 2c e0 c8 57581.385<br> 00 00 80 76 18 2c e0 c8 57581.380<br> 00 00 80 f6 17 2c e0 c8 57581.376<br> 00 00 80 76 17 2c e0 c8 57581.372<br><br>SMART Self-test log, version number 1<br><br>Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error<br># 1 Short off-line Completed: read failure 20% 391 0x0003e00a<br># 2 Short captive Interrupted (host reset) 40% 390 <br># 3 Short captive Interrupted (host reset) 40% 390 <br># 4 Short off-line Completed: read failure 20% 390 0x0003e00a<br># 5 Extended off-line Completed: read failure 40% 247 0x002c1979<br></tt></pre>
<tt> </tt>
<hr width="100%" size="2">Page maintained by <a
href="">Bruce Allen</a><br>
<big> </big></div>
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment