diff --git a/www/index.html b/www/index.html
index 36000145a3408594633dd7f8a1fa46bf26172d6d..d7a7a8b75cee7b2526e80e15a45dea8903e543ca 100644
--- a/www/index.html
+++ b/www/index.html
@@ -4,441 +4,448 @@
<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">
</head>
<body>
-
-<div align="center">
-<h1><font color="#3333ff">smartmontools HOME PAGE
- </font> <a href="http://sourceforge.net"><img
+
+<div align="center">
+<h1><font color="#3333ff">smartmontools HOME PAGE
+ </font> <a href="http://sourceforge.net"><img
src="http://sourceforge.net/sflogo.php?group_id=64297&type=5"
width="210" height="62" border="0" alt="SourceForge.net Logo"
align="middle">
- </a> </h1>
- </div>
-
-<div align="left">This is the home page for smartmontools. The smartmontools
+ </a> </h1>
+ </div>
+
+<div align="left">This is the home page for smartmontools. 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
+ 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>
- <br>
- For printing convenience, everything except for the
+ <br>
+ For printing convenience, everything except for the
<a href="#sampleoutput">example output</a> is on a single page.<br>
-
-<hr width="100%" size="2">
+
+<hr width="100%" size="2">
<ul>
- <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
+ <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
+ <li><a href="#differfromsmartsuite">How does
smartmontools differ from smartsuite?</a></li>
- <li><a href="#references">Useful references
+ <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 example output
-from smartmontools <b>smartctl</b></a></li>
- <li><a
- href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/smartmontools/">Smartmontools
- CVS archive</a> and <a
- href="http://sourceforge.net/projects/smartmontools">SourceForge projects
- group page</a></li>
- <li><a
- href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
- Mailing list and archives</a> for smartmontools support<br>
- </li>
-
+ <li><a href="#sampleoutput">Example output from
+ smartmontools <b>smartctl</b> utility</a></li>
+ <li><a
+ href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/smartmontools/">Smartmontools
+ CVS Archive</a> and <a
+ href="http://sourceforge.net/projects/smartmontools">Sourceforge Projects
+Group page</a></li>
+ <li><a
+ href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
+ Mailing List and Archives</a> for smartmontools support<br>
+ </li>
+
</ul>
- <b><br>
- </b>
+ <b><br>
+ </b>
<hr width="100%" size="2"><b><br>
- </b><b><a name="howtodownload"></a></b><b> How to
+ </b><b><a name="howtodownload"></a></b><b> How to
download and install smartmontools<br>
- </b>There are three different ways to get and install
- smartmontools. You can use any one of these three procedures.
- Just after "Method 3" below are some instructions for trying
+ </b>There are three different ways to get and install
+ smartmontools. You can use any one of these three procedures.
+ Just after "Method 3" below are some instructions for trying
out smartmontools once you have completed the installation.<br>
-
+
<ol>
- <li><b>First Method - Install from the RPM file:</b><br>
+ <li><b>First Method - Install from the RPM file:</b><br>
-
+
<ul>
- <li>Download the latest binary RPM file (<tt>*.rpm</tt>)
- from <a
- href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>
+ <li>Download the latest binary RPM file (<tt>*.rpm</tt>)
+ from <a
+ href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>
. Don't get the SRPM file (<tt>*.src.rpm</tt>).</li>
- <li>Install it using RPM. <i>You must be
-root to do this</i>:<br>
- <tt> su root</tt> <i>(enter root
-password)</i><br>
- <tt> rpm -ivh smartmontools-5.0-1.i386.rpm<br>
- </tt>For most users, this is all that is needed.<br>
- </li>
- <li>If you receive an error message, you have
-probably previously installed the <tt>smartsuite</tt> package, or
-RedHat's <tt>kernel-utils</tt> package, which provide older
-versions of the <tt>smartd</tt> and <tt> smartctl</tt>
- utilities. In this case you should use the <tt> --nodeps</tt>
-or <tt> --force</tt> arguments of rpm to replace these
+ <li>Install it using RPM. <i>You must be
+ root to do this</i>:<br>
+ <tt> su root</tt> <i>(enter root
+ password)</i><br>
+ <tt> rpm -ivh smartmontools-5.0-1.i386.rpm<br>
+ </tt>For most users, this is all that is needed.<br>
+ </li>
+ <li>If you receive an error message, you have
+probably previously installed the <tt>smartsuite</tt> package, or
+RedHat's <tt>kernel-utils</tt> package, which provide older
+versions of the <tt>smartd</tt> and <tt> smartctl</tt>
+ utilities. 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></li>
- <li>If you want to remove the package (<tt>rpm -e s</tt><tt>martmontools</tt>)
- and your system does not have <tt>chkconfig</tt> installed, you may need
- to use: <tt><br>
- rpm -e</tt> <tt>--noscripts</tt> <tt>s</tt><tt>martmontools</tt><br>
- </li>
+ <tt> rpm -ivh --nodeps --force smartmontools-5.0-1.i386.rpm</tt></li>
+ <li>If you want to remove the package (<tt>rpm -e s</tt><tt>martmontools</tt>)
+ and your system does not have <tt>chkconfig</tt> installed, you may
+need to use: <tt><br>
+ rpm -e</tt> <tt>--noscripts</tt> <tt>s</tt><tt>martmontools</tt><br>
+ </li>
-
+
</ul>
- </li>
- <li><b>Second Method - Install from the source tarball</b>:<br>
+ </li>
+ <li><b>Second Method - Install from the source
+tarball</b>:<br>
-
+
<ul>
- <li>Download the latest source-code tarball from
- <a
- href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>.
+ <li>Download the latest source-code tarball
+from <a
+ href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>.
Note: you probably want the most recent release. </li>
- <li>Uncompress the tarball:<br>
- <tt> tar zxvf smartmontools-5.0-1.tar.gz</tt></li>
- <li>The previous step created a directory called
- smartmontools-5.0-1 containing the code. Go to that directory,
+ <li>Uncompress the tarball:<br>
+ <tt> tar zxvf smartmontools-5.0-1.tar.gz</tt></li>
+ <li>The previous step created a directory called
+ smartmontools-5.0-1 containing the code. Go to that directory,
build, and install:<br>
- <tt> cd smartmontools-5.0-1<br>
- make<br>
- make install </tt>
- <i>[only
-root can do this]</i><br>
- </li>
+ <tt> cd smartmontools-5.0-1<br>
+ make<br>
+ make install </tt>
+ <i>[only
+ root can do this]</i><br>
+ </li>
-
+
+
</ul>
- </li>
- <li><b>Third Method - Download code directly from
+ </li>
+ <li><b>Third Method - Download code directly from
the CVS archive:</b><br>
-
+
<ul>
- <li> Download the latest code snapshot from
-CVS. If prompted for a password, simply press the Enter key. Note
- that the two lines below that start "<tt>cvs</tt>" are long!
+ <li> Download the latest code snapshot from
+ CVS. If prompted for a password, simply press the Enter key. Note
+ that the two lines below that start "<tt>cvs</tt>" are long!
<br>
- <tt> cvs -d:pserver:anonymous@cvs.smartmontools.sourceforge.net:/cvsroot/smartmontools
- login</tt> <tt><br>
- cvs -z3 -d:pserver:anonymous@cvs.smartmontools.sourceforge.net:/cvsroot/smartmontools
- co sm5</tt><br>
- </li>
- <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<br>
- make install </tt> <i> [only root
+ <tt> cvs -d:pserver:anonymous@cvs.smartmontools.sourceforge.net:/cvsroot/smartmontools
+ login</tt> <tt><br>
+ cvs -z3 -d:pserver:anonymous@cvs.smartmontools.sourceforge.net:/cvsroot/smartmontools
+ co sm5</tt><br>
+ </li>
+ <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<br>
+ make install </tt> <i> [only root
can do this]<br>
- </i> </li>
+ </i> </li>
-
+
</ul>
- </li>
-
+ </li>
+
</ol>
- <b>After installing using Method 1, 2 or 3 above,
+ <b>After installing using Method 1, 2 or 3 above,
you can read the man pages, and try out the commands:</b><br>
-
-<blockquote>
+
+<blockquote>
+
<blockquote><tt> man 8 smartctl</tt><br>
- <tt> man 8 smartd</tt><br>
- <tt> /usr/sbin/smartctl -etf /dev/hda </tt><i>[only
- root can do this]</i><br>
- <tt> /usr/sbin/smartctl -a /dev/hda
+ <tt> man 8 smartd</tt><br>
+ <tt> /usr/sbin/smartctl -etf /dev/hda </tt><i>[only
+ root can do this]</i><br>
+ <tt> /usr/sbin/smartctl -a /dev/hda
</tt><i>[only root can do this]</i><br>
- <br>
-
- <p> Note that the default location for the manual pages is in <tt>/usr/share/man/man8</tt>
- . If "<tt>man</tt>" does not find the manual pages, then you
- may need to add <tt>/usr/share/man</tt> to your <tt>MANPATH</tt> environment
- variable.<br>
- <a href="#cvshelp"><br>
- <br>
- <b>How to use CVS to get any version of smartmontools</b></a><br>
- </p>
- </blockquote>
- </blockquote>
-
+ <br>
+
+ <p> Note that the default location for the manual pages is in <tt>/usr/share/man/man8</tt>
+ . If "<tt>man</tt>" does not find the manual pages, then you
+ may need to add <tt>/usr/share/man</tt> to your <tt>MANPATH</tt> environment
+ variable.<br>
+ <a href="#cvshelp"><br>
+ <br>
+ <b>How to use CVS to get any version of smartmontools</b></a><br>
+ </p>
+ </blockquote>
+ </blockquote>
+
<hr width="100%" size="2"><br>
- <br>
- <a name="FAQ"></a><b>Frequently-asked questions<br>
- </b>If your question is not here, please <a
+ <br>
+ <a name="FAQ"></a><b>Frequently-asked questions<br>
+ </b>If your question is not here, please <a
href="mailto:smartmontools-support@lists.sourceforge.net"> email me</a>.<br>
-
+
<ul>
- <li><b>What do I do if I have problems, or need
-support? Suppose I want to become a developer, or suggest some
+ <li><b>What do I do if I have problems, or need
+support? Suppose I want to become a developer, or suggest some
new extensions?</b><br>
- Please send an email to the <a
- href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
- smartmontools-support mailing list</a>. Note that you won't
- get the mail sent to the list unless you subscribe to it. Please
+ Please send an email to the <a
+ href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
+ smartmontools-support mailing list</a>. Note that you won't
+ get the mail sent to the list unless you subscribe to it. Please
take a look through the archives to see if your question has been answered.<br>
- </li>
- <li><b>What are the future plans for smartmontools?</b><br>
- My plan is that smartmontools-5.x will support ATA/ATAPI-5
- disks. 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. The "x" will denote revision level, as bugs get found
-and fixed, and as enhancements get added. 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. We have more than 20 TB of data stored on the
-system. It's nice to have advanced warning when a disk is
-going to fail.</li>
- <li><b>I see some strange output from smartctl. What
- does it mean?</b><br>
- The raw S.M.A.R.T. 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. If you find strange output,
-or unknown attributes, please send an email to <a
- href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
- 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: (230)(250)<br>
- If you can attach names/meanings to these attributes,
- please send me a note to <a
- href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
+ </li>
+ <li><b>What are the future plans for smartmontools?</b><br>
+ My plan is that smartmontools-5.x will support ATA/ATAPI-5
+ disks. 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. The "x" will denote revision level, as bugs get
+found and fixed, and as enhancements get added. 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. We have more than 20 TB of data stored on the
+system. It's nice to have advanced warning when a disk is going
+to fail.</li>
+ <li><b>I see some strange output from smartctl.
+ What does it mean?</b><br>
+ The raw S.M.A.R.T. 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. If you find strange output, or unknown
+attributes, please send an email to <a
+ href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
+ 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: (230)(250)<br>
+ If you can attach names/meanings to these attributes,
+ please send me a note to <a
+ href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
smartmontools-support</a>.</li>
- <li><b>When I run <tt>smartd</tt> , the SYSLOG
+ <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>). The
- log messages appear because your system doesn't have most of these
+ <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>). The
+ log messages appear because your system doesn't have most of these
devices.<br>
- The latest release of smartd can use a configuration file
- <tt>/etc/smartd.conf</tt> to specify which devices to include
-or exclude from start-up search.</li>
- <li><b><a name="cvshelp"></a>How can I use CVS to get different
+ The latest release of smartd can use a configuration file
+ <tt>/etc/smartd.conf</tt> to specify which devices to include
+ or exclude from start-up search.</li>
+ <li><b><a name="cvshelp"></a>How can I use CVS to get different
versions of smartmontools?<br>
- </b>One of the really cool things about CVS is that you can
-get <i>any </i>version of the code you want, from the first release
- up the the most current development version. And it's trivial, because
- each release is <u>tagged</u> with a name like <tt>RELEASE_5_0_22</tt>.
+ </b>One of the really cool things about CVS is that you can
+get <i>any </i>version of the code you want, from the first release
+ up the the most current development version. And it's trivial, because
+ each release is <u>tagged</u> with a name like <tt>RELEASE_5_0_22</tt>.
You can see what the different names are by looking at the <a
- href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/smartmontools/">Smartmontools
- CVS archive.</a> You'll see the tag names in the little scroll
-window where it says "Show only the files with Tag". All you need
-to do is:<br>
- <tt> cvs -d:pserver:anonymous@cvs.smartmontools.sourceforge.net:/cvsroot/smartmontools
- login</tt> <tt><br>
- cvs -z3 -d:pserver:anonymous@cvs.smartmontools.sourceforge.net:/cvsroot/smartmontools
- co -r RELEASE_5_0_17</tt><tt> sm5</tt><br>
- If prompted for a password, just do <ENTER>. This will create
- a subdirectory called <tt>sm5/</tt> containing the code. Go
-to that directory, build, install, and enjoy:<br>
- <tt> cd sm5<br>
- make<br>
- make install </tt> <i> [only root can do this]</i></li>
- <li><b>What's the story on IBM S.M.A.R.T. disks?</b><br>
- Apparently some of the older S.M.A.R.T. firmware on IBM disks can
- interfere with the regular operation of the disk. If you have this
+ href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/smartmontools/">Smartmontools
+ CVS archive.</a> You'll see the tag names in the little scroll
+ window where it says "Show only the files with Tag". All you need
+ to do is:<br>
+ <tt> cvs -d:pserver:anonymous@cvs.smartmontools.sourceforge.net:/cvsroot/smartmontools
+ login</tt> <tt><br>
+ cvs -z3 -d:pserver:anonymous@cvs.smartmontools.sourceforge.net:/cvsroot/smartmontools
+ co -r RELEASE_5_0_17</tt><tt> sm5</tt><br>
+ If prompted for a password, just do <ENTER>. This will create
+ a subdirectory called <tt>sm5/</tt> containing the code. Go to
+ that directory, build, install, and enjoy:<br>
+ <tt> cd sm5<br>
+ make<br>
+ make install </tt> <i> [only root can do this]</i></li>
+ <li><b>What's the story on IBM S.M.A.R.T. disks?</b><br>
+ Apparently some of the older S.M.A.R.T. firmware on IBM disks can
+ interfere with the regular operation of the disk. If you have this
problem, here is an <a
- href="http://www.geocities.com/dtla_update/">IBM DISK FIRMWARE UPGRADE</a>
+ href="http://www.geocities.com/dtla_update/">IBM DISK FIRMWARE UPGRADE</a>
that fixes the problem. <br>
- </li>
-
+ </li>
+
</ul>
-
-<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. I'd be very grateful to find someone who
-could help me test the smartmontools code on SCSI disks. Since
-it's derived from the smartsuite package, it should initially work
+
+<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. I'd be very grateful to find someone who
+could help me test the smartmontools code on SCSI disks. 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>
- <br>
- I'd be especially happy if someone would like to take
- on the task, as a developer, of maintaining the SCSI code. 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>The smartsuite code was originally developed as a Senior
-Thesis by Michael Cornwell at the Concurrent Systems Laboratory (now
-part of the <a href="http://ssrc.soe.ucsc.edu">Storage Systems Research
-Center</a>), Jack Baskin School of Engineering, University of California,
-Santa Cruz. <br>
- <b><br>
- </b>Smartmontools was derived directly from smartsuite
- . It differs from smartsuite in that it supports the ATA/ATAPI-5 standard.
- So for example <tt>smartctl</tt> from smartsuite has no facility
-for printing the S.M.A.R.T. self-test logs, and doesn't print timestamp
-information in the most usable way. The <tt>smartctl</tt> utility
-in smartmontools has added functionality for this (<tt>-q,-Q,</tt><tt>-L,-f,
--F and -m</tt> options), updated documentation, and also fixes small
-technical bugs in smartsuite. See the <a
- href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/smartmontools/sm5/CHANGELOG">CHANGELOG</a>
- file in CVS for a summary of what's been done. The <tt>smartd</tt> utility
- differs from the smartsuite <tt>smartd</tt> in major ways. First,
- it prints somewhat more informative error messages to the syslog. Second,
- on startup it looks for a configuration file <tt>/etc/smartd.conf</tt>,
- and if <tt>smartd</tt> finds this file, it monitors the list of devices
- therein, rather than querying all IDE and SCSI devices on your system. [If
- the configuration file does not exist, then it does query all IDE and SCSI
- devices.] Finally, it's a well-behaved daemon and doesn't leave open
- file descriptors and other detrius behind. In addition, the <tt>smartmontools</tt>
- version of <tt>smartd</tt> can be instructed (via Directives in the configuration
- file) to monitor for changes in a number of different disk properties:
- the SMART status, failure or prefailure attributes going below threshold,
- new errors appearing in the ATA Error Log or the SMART Self-Test Log,
-and so on.<br>
- <br>
- The other principle difference is that smartmontools is an open-source
- development project, meaning that we keep the files in CVS, and that
- other developers who wish to contribute can commit changes to the archive.
+ <br>
+ I'd be especially happy if someone would like to
+take on the task, as a developer, of maintaining the SCSI code.
+ 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>The smartsuite code was originally developed as a Senior
+Thesis by Michael Cornwell at the Concurrent Systems Laboratory (now part
+of the <a href="http://ssrc.soe.ucsc.edu">Storage Systems Research Center</a>),
+ Jack Baskin School of Engineering, University of California, Santa Cruz.
+ <br>
+ <b><br>
+ </b>Smartmontools was derived directly from smartsuite
+ . It differs from smartsuite in that it supports the ATA/ATAPI-5 standard.
+ So for example <tt>smartctl</tt> from smartsuite has no facility for
+ printing the S.M.A.R.T. self-test logs, and doesn't print timestamp information
+ in the most usable way. The <tt>smartctl</tt> utility in smartmontools
+ has added functionality for this (<tt>-q,-Q,</tt><tt>-L,-f, -F and -m</tt>
+ options), updated documentation, and also fixes small technical bugs
+in smartsuite. See the <a
+ href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/smartmontools/sm5/CHANGELOG">CHANGELOG</a>
+ file in CVS for a summary of what's been done. The <tt>smartd</tt>
+utility differs from the smartsuite <tt>smartd</tt> in major ways.
+ First, it prints somewhat more informative error messages to the
+syslog. Second, on startup it looks for a configuration file <tt>/etc/smartd.conf</tt>,
+ and if <tt>smartd</tt> finds this file, it monitors the list of devices
+ therein, rather than querying all IDE and SCSI devices on your system.
+ [If the configuration file does not exist, then it does query all
+IDE and SCSI devices.] Finally, it's a well-behaved daemon and doesn't
+leave open file descriptors and other detrius behind. In addition, the
+<tt>smartmontools</tt> version of <tt>smartd</tt> can be instructed (via
+Directives in the configuration file) to monitor for changes in a number
+of different disk properties: the SMART status, failure or prefailure
+attributes going below threshold, new errors appearing in the ATA Error
+Log or the SMART Self-Test Log, and so on.<br>
+ <br>
+ The other principle difference is that smartmontools is an open-source
+ development project, meaning that we keep the files in CVS, and that
+ other developers who wish to contribute can commit changes to the archive.
If you would like to contribute, please write to to <a
- href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
+ href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
smartmontools-support</a>.<br>
- <br>
- But the bottom line is that the code in smartmontools is derived
- directly from smartsuite and is similar. The smartsuite package can
- be found <a href="http://sourceforge.net/projects/smartsuite/">here</a>.
- <br>
-
+ <br>
+ But the bottom line is that the code in smartmontools is derived
+ directly from smartsuite and is similar. The smartsuite package
+can be found <a href="http://sourceforge.net/projects/smartsuite/">here</a>.
+ <br>
+
<hr width="100%" size="2"><br>
- <a name="references"></a><big><b>Useful references
+ <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>
- man 8 smartctl<br>
- 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>
- </big>
+ </b>If you are having trouble understanding the
+ output of smartctl or smartd, please first read the manual pages:<tt><br>
+ man 8 smartctl<br>
+ 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>
+ </big>
<ul>
- <li>The <a
- href="http://www.t13.org/project/d1321r1c.pdf"> ATAPI/ATA-5 Revision
- 1 specification</a> (start with Section 8.41)<br>
- </li>
- <li><a href="http://www.t13.org/#FTP_site">Earlier
- and later revisions of the ATAPI/ATA Specs</a></li>
- <li>The original S.M.A.R.T. specification is SFF-8035i
- from the <a href="http://www.sffcommittee.com/ns/">SFF Committee</a>
- . Here is their <a
+ <li>The <a
+ href="http://www.t13.org/project/d1321r1c.pdf"> ATAPI/ATA-5 Revision
+ 1 specification</a> (start with Section 8.41)<br>
+ </li>
+ <li><a href="http://www.t13.org/#FTP_site">Earlier
+ and later revisions of the ATAPI/ATA Specs</a></li>
+ <li>The original S.M.A.R.T. specification is
+SFF-8035i from the <a href="http://www.sffcommittee.com/ns/">SFF Committee</a>
+ . Here is their <a
href="ftp://ftp.seagate.com/sff/INF-8035.TXT"> "link"</a> .</li>
- <li>The <a href="http://cmrr.ucsd.edu/smart/">UCSD SMART Project</a>
-has some interesting publications:<br>
-
+ <li>The <a href="http://cmrr.ucsd.edu/smart/">UCSD SMART Project</a>
+ has some interesting publications:<br>
+
<ul>
- <li><a
- href="http://cmrr.ucsd.edu/smart/tech_papr/HamerlySmartPaper.pdf">Bayesian
+ <li><a
+ href="http://cmrr.ucsd.edu/smart/tech_papr/HamerlySmartPaper.pdf">Bayesian
Approaches to Failure Prediction for Disk Drives</a></li>
- <li><a
- href="http://cmrr.ucsd.edu/smart/tech_papr/SmtPapTransReliFinalWeb.pdf">Improved
- Disk-Drive Failure Warnings</a> <br>
- </li>
-
+ <li><a
+ href="http://cmrr.ucsd.edu/smart/tech_papr/SmtPapTransReliFinalWeb.pdf">Improved
+ Disk-Drive Failure Warnings</a> <br>
+ </li>
+
</ul>
- </li>
- <li><font color="#0000ff"><a
+ </li>
+ <li><font color="#0000ff"><a
href="http://seagate.com/docs/pdf/whitepaper/drive_reliability.pdf"
- target="_blank">Estimating Drive Reliability in Desktop Computers and Consumer
+ target="_blank">Estimating Drive Reliability in Desktop Computers and Consumer
Electronics Systems</a></font> (Seagate)<br>
- </li>
- <li><font color="#0000ff"><a
+ </li>
+ <li><font color="#0000ff"><a
href="http://seagate.com/docs/pdf/whitepaper/enhanced_smart.pdf"
- target="_blank">Enhanced SMART - Get S.M.A.R.T. For Reliability</a></font>
+ target="_blank">Enhanced SMART - Get S.M.A.R.T. For Reliability</a></font>
(Seagate)<br>
- </li>
- <li><font color="#0000ff"><a
+ </li>
+ <li><font color="#0000ff"><a
href="http://www.seagate.com/docs/pdf/whitepaper/smart_u8.pdf"
target="_blank">Playing it S.M.A.R.T.</a><font color="#008080" size="2"
face="Verdana"> </font></font>(Seagate)<br>
- </li>
- <li><font color="#0000ff"><a
+ </li>
+ <li><font color="#0000ff"><a
href="http://www.seagate.com/docs/pdf/whitepaper/Enhanced_DST_Tech_Paper.pdf"
target="_blank">Enhanced Drive Self-Test</a><font color="#008080"
size="2" face="Verdana"> </font></font>(Seagate)<br>
- </li>
- <li><a
+ </li>
+ <li><a
href="http://www.maxtor.com/products/DiamondMax/software/maxsafe.pdf"
target="_blank">Drive reliability and safety system: MaxSafe</a> (Maxtor)<br>
- </li>
- <li><u>Specifying Reliability in the Disk Drive Industry: No More MTBF's</u>,
- Jon G. Elerath (IBM Storage Systems Division) in <i>Proceedings of the
-IEEE 2000 Annual Reliability and Maintainability Symposium, pg 194, 0-7803-5848-1/00/$10.00.</i><br>
- </li>
-
+ </li>
+ <li><u>Specifying Reliability in the Disk Drive Industry: No More
+MTBF's</u>, Jon G. Elerath (IBM Storage Systems Division) in <i>Proceedings
+of the IEEE 2000 Annual Reliability and Maintainability Symposium, pg 194,
+0-7803-5848-1/00/$10.00.</i><br>
+ </li>
+
</ul>
-
-<hr width="100%" size="2"><a name="sampleoutput"></a><b>Example output from
- smartmontools smartctl utility:</b>
+
+<hr width="100%" size="2"><a name="sampleoutput"></a><b>Example output from
+ smartmontools smartctl utility:</b>
<ul>
- <li> <a href="http://smartmontools.sourceforge.net/MAXTOR-0.html">MAXTOR
-4K080H4</a> 80 GB 5400 RPM<br>
- </li>
- <li> <a
- href="http://smartmontools.sourceforge.net/MAXTOR-1.html">MAXTOR 4K080H4</a>
+ <li> <a
+ href="http://smartmontools.sourceforge.net/MAXTOR-0.html">MAXTOR 4K080H4</a>
+80 GB 5400 RPM<br>
+ </li>
+ <li> <a
+ href="http://smartmontools.sourceforge.net/MAXTOR-1.html">MAXTOR 4K080H4</a>
80 GB 5400 RPM (has failing SMART status)<br>
- </li>
- <li><a href="http://smartmontools.sourceforge.net/MAXTOR-2.html">MAXTOR
-4K080H4</a> 80 GB 5400 RPM (has had failing SMART test in the
+ </li>
+ <li><a href="http://smartmontools.sourceforge.net/MAXTOR-2.html">MAXTOR
+4K080H4</a> 80 GB 5400 RPM (has had failing SMART test in the
past. Look at the Seek Error Rate)<br>
- </li>
- <li> <a href="http://smartmontools.sourceforge.net/MAXTOR-3.html">MAXTOR
-6L080J4</a> 80 GB 7200 RPM<br>
- </li>
- <li> <a href="http://smartmontools.sourceforge.net/MAXTOR-4.html">MAXTOR
-6L080J4</a> 80 GB 7200 RPM<br>
- </li>
+ </li>
+ <li> <a
+ href="http://smartmontools.sourceforge.net/MAXTOR-3.html">MAXTOR 6L080J4</a>
+ 80 GB 7200 RPM<br>
+ </li>
+ <li> <a
+ href="http://smartmontools.sourceforge.net/MAXTOR-4.html">MAXTOR 6L080J4</a>
+ 80 GB 7200 RPM<br>
+ </li>
+ <li> <a
+ href="http://smartmontools.sourceforge.net/IC35L120AVVA07-0-0.html">IBM IC35L120AVVA07</a>
+IBM 120 GB 7200 RPM<br>
+ </li>
<li> <a
- href="http://smartmontools.sourceforge.net/IC35L120AVVA07-0-0.html">IBM
-IC35L120AVVA07</a> IBM 120 GB 7200 RPM<br>
- </li>
- <li> <a
- href="http://smartmontools.sourceforge.net/IC35L120AVVA07-0-1.html">IBM
-IC35L120AVVA07</a> IBM 120 GB 7200 RPM</li>
- <li> <a
- href="http://smartmontools.sourceforge.net/HITACHI_DK23BA-20-0.html">HITACHI_DK23BA-20</a>
+ href="http://smartmontools.sourceforge.net/IC35L120AVVA07-0-1.html">IBM IC35L120AVVA07</a>
+IBM 120 GB 7200 RPM</li>
+ <li> <a
+ href="http://smartmontools.sourceforge.net/HITACHI_DK23BA-20-0.html">HITACHI_DK23BA-20</a>
Hitachi 20 GB Laptop Disk<br>
- </li>
-
+ </li>
+
</ul>
-
-<hr width="100%" size="2">
+
+<hr width="100%" size="2">
<ul>
-
+
</ul>
-
-<ul>
+<ul>
+
</ul>
- Page maintained by <a
+ Page maintained by <a
href="mailto:smartmontools-support@lists.sourceforge.net">Bruce Allen</a><br>
- <big> </big></div>
- <br>
+ <big> </big></div>
+ <br>
+ <br>
<br>
<br>
<br>