Skip to content
Snippets Groups Projects
Commit 7762f4df authored by ballen4705's avatar ballen4705
Browse files

Fixed broken links, updated example output 

git-svn-id: https://smartmontools.svn.sourceforge.net/svnroot/smartmontools/trunk@133 4ea69e1a-61f1-4043-bf83-b5c94c648137
parent 7d8a8b1b
No related branches found
No related tags found
No related merge requests found
Show whitespace changes
Inline Side-by-side
Showing
with 231 additions and 299 deletions
www/index.html
+ 231
− 299
View file @ 7762f4df
...@@ -28,9 +28,8 @@ ...@@ -28,9 +28,8 @@
and <font color="#3333ff"><b>smartd</b></font>) to control and <font color="#3333ff"><b>smartd</b></font>) to control
and monitor storage systems using the Self-Monitoring, Analysis and and monitor storage systems using the Self-Monitoring, Analysis and
Reporting Technology System (S.M.A.R.T.) built into most modern ATA 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 and SCSI hard disks. It is derived from the smartsuite package, and includes
includes support for ATA/ATAPI-5 disks. It should run on any modern support for ATA/ATAPI-5 disks. It should run on any modern linux system.<br>
linux system.<br>
<br> <br>
For your convenience, this is a single page, so you can print For your convenience, this is a single page, so you can print
it easily.<br> it easily.<br>
...@@ -39,8 +38,8 @@ it easily.<br> ...@@ -39,8 +38,8 @@ it easily.<br>
<ul> <ul>
<li><a href="#howtodownload">How to download and install smartmontools</a></li> <li><a href="#howtodownload">How to download and install smartmontools</a></li>
<li><a href="#FAQ">Frequently Asked Questions</a></li> <li><a href="#FAQ">Frequently Asked Questions</a></li>
<li><a href="#testinghelp">The code needs to be tested on SCSI <li><a href="#testinghelp">The code needs to be tested on
disks/tapes</a></li> SCSI disks/tapes</a></li>
<li><a href="#differfromsmartsuite">How does smartmontools <li><a href="#differfromsmartsuite">How does smartmontools
differ from smartsuite?</a></li> differ from smartsuite?</a></li>
<li><a href="#references">Useful references on S.M.A.R.T. <li><a href="#references">Useful references on S.M.A.R.T.
...@@ -88,8 +87,8 @@ from <a ...@@ -88,8 +87,8 @@ from <a
these two utilities:<br> these two utilities:<br>
<tt>rpm -ivh --nodeps --force smartmontools-5.0-1.i386.rpm</tt></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-5.0-1</tt> <li>If you want to remove the package (<tt>rpm -e s</tt><tt>martmontools-5.0-1</tt>
) and your system does not have <tt>chkconfig</tt> installed, you may need ) and your system does not have <tt>chkconfig</tt> installed, you may
to use the <tt>--noscripts</tt> option to <tt>rpm -e</tt>.<br> need to use the <tt>--noscripts</tt> option to <tt>rpm -e</tt>.<br>
</li> </li>
</ul> </ul>
...@@ -106,14 +105,15 @@ Note: you probably want the most recent release. </li> ...@@ -106,14 +105,15 @@ Note: you probably want the most recent release. </li>
containing the code. &nbsp;Go to that directory, build, and install:<br> containing the code. &nbsp;Go to that directory, build, and install:<br>
<tt>cd smartmontools-5.0-1<br> <tt>cd smartmontools-5.0-1<br>
make<br> make<br>
make install &nbsp;</tt> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; make install &nbsp;</tt> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[only root can do this]<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[only root can do this]<br>
</li> </li>
</ul> </ul>
</li> </li>
<li><b>Third Method - Download code directly from the CVS archive:</b><br> <li><b>Third Method - Download code directly from the CVS
archive:</b><br>
<ul> <ul>
<li>Download the latest code snapshot from CVS. If prompted <li>Download the latest code snapshot from CVS. If prompted
...@@ -128,24 +128,24 @@ lines below that start "<tt>cvs</tt>" are long! <br> ...@@ -128,24 +128,24 @@ lines below that start "<tt>cvs</tt>" are long! <br>
containing the code. Go to that directory, build, and install:<br> containing the code. Go to that directory, build, and install:<br>
<tt>cd sm5<br> <tt>cd sm5<br>
make<br> make<br>
make install &nbsp;</tt> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; make install &nbsp;</tt> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[only root can do this]<br> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[only root can do this]<br>
</li> </li>
</ul> </ul>
</li> </li>
</ol> </ol>
<b>After installing using Method 1, 2 or 3 above, you can read <b>After installing using Method 1, 2 or 3 above, you can
the man pages, and try out the commands:</b><br> read the man pages, and try out the commands:</b><br>
<blockquote> <blockquote>
<blockquote><tt>man 8 smartctl</tt><br> <blockquote><tt>man 8 smartctl</tt><br>
<tt>man 8 smartd</tt><br> <tt>man 8 smartd</tt><br>
<tt>/usr/sbin/smartctl -etf /dev/hda &nbsp;</tt>[only root can <tt>/usr/sbin/smartctl -etf /dev/hda &nbsp;</tt>[only root
do this]<br> can do this]<br>
<tt>/usr/sbin/smartctl -a /dev/hda &nbsp; &nbsp;</tt>[only root <tt>/usr/sbin/smartctl -a /dev/hda &nbsp; &nbsp;</tt>[only
can do this]</blockquote> root can do this]</blockquote>
</blockquote> </blockquote>
Note that the default location for the manual pages is in <tt>/usr/share/man/man8</tt> Note that the default location for the manual pages is in <tt>/usr/share/man/man8</tt>
. &nbsp;If "<tt>man</tt>" does not find the manual pages, then you may . &nbsp;If "<tt>man</tt>" does not find the manual pages, then you may
...@@ -169,29 +169,30 @@ variable.<br> ...@@ -169,29 +169,30 @@ variable.<br>
My plan is that smartmontools-5.x will support ATA/ATAPI-5 disks. 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 &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 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 "x" will denote revision level, as bugs get found and fixed, and as
get added. &nbsp; If it's possible to maintain backwards compatibility, enhancements get added. &nbsp; If it's possible to maintain backwards
that would be nice, but I don't know if it will be possible or practical.</li> 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> <li><b>Why are you doing this?</b><br>
My research group runs a beowulf cluster with 300 ATA-5 disks. 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 &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> 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 <li><b>I see some strange output from smartctl. &nbsp;What
it mean?</b><br> does it mean?</b><br>
The raw S.M.A.R.T. attributes (temperature, power-on lifetime, The raw S.M.A.R.T. attributes (temperature, power-on lifetime,
and so on) are stored in vendor-specific structures. &nbsp;Sometime these and so on) are stored in vendor-specific structures. &nbsp;Sometime
are strange. &nbsp;Hitachi disks (at least some of them) store power-on these are strange. &nbsp;Hitachi disks (at least some of them) store
lifetime in minutes, rather than hours. &nbsp;IBM disks (at least some power-on lifetime in minutes, rather than hours. &nbsp;IBM disks (at
of them) have three temperatures stored in the raw structure, not just one. least some of them) have three temperatures stored in the raw structure,
And so on. &nbsp;If you find strange output, or unknown attributes, please not just one. And so on. &nbsp;If you find strange output, or unknown attributes,
send an email to <a please send an email to <a
href="ttp://lists.sourceforge.net/mailman/listinfo/smartmontools-support"> href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
smartmontools-support</a> and we'll help you try and figure it out.</li> smartmontools-support</a> and we'll help you try and figure it out.</li>
<li><b>What attributes does smartmontools not yet recognize?<br> <li><b>What attributes does smartmontools not yet recognize?<br>
</b>From a Hitachi disk: (230)(250)<br> </b>From a Hitachi disk: (230)(250)<br>
If you can attach names/meanings to these attributes, please send If you can attach names/meanings to these attributes, please
me a note to <a send me a note to <a
href="ttp://lists.sourceforge.net/mailman/listinfo/smartmontools-support"> href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
smartmontools-support</a>.</li> smartmontools-support</a>.</li>
<li><b>When I run <tt>smartd</tt> , the SYSLOG (<tt>/var/log/messages</tt> <li><b>When I run <tt>smartd</tt> , the SYSLOG (<tt>/var/log/messages</tt>
) contains messages like this:</b><br> ) contains messages like this:</b><br>
...@@ -212,37 +213,45 @@ all ATA and SCSI devices to monitor (matching the pattern <tt>/dev/hd[a-z]</t ...@@ -212,37 +213,45 @@ all ATA and SCSI devices to monitor (matching the pattern <tt>/dev/hd[a-z]</t
</b>I have access to a number of systems with ATA S.M.A.R.T. </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. 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 &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 smartmontools code on SCSI disks. &nbsp;Since it's derived from the
package, it should initially work about the same way with SCSI devices smartsuite package, it should initially work about the same way with
as the smartsuite tools did.<br> SCSI devices as the smartsuite tools did.<br>
<br> <br>
I'd be especially happy if someone would like to take on the 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 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> a beowulf cluster with a few hundred SCSI disks? Please volunteer!<br>
<hr width="100%" size="2"><a name="differfromsmartsuite"></a><b>How does <hr width="100%" size="2"><a name="differfromsmartsuite"></a><b>How does smartmontools
smartmontools differ from smartsuite?<br> differ from smartsuite?<br>
</b>The smartsuite code was originally developed as a Senior Thesis by Michael </b>The smartsuite code was originally developed as a Senior Thesis by
Cornwell at the Concurrent Systems Laboratory (now part of the <a Michael Cornwell at the Concurrent Systems Laboratory (now part of the <a
href="http://ssrc.soe.ucsc.edu">Storage Systems Research Center</a>), Jack href="http://ssrc.soe.ucsc.edu">Storage Systems Research Center</a>), Jack
Baskin School of Engineering, University of California, Santa Cruz. <br> Baskin School of Engineering, University of California, Santa Cruz. <br>
<b><br> <b><br>
</b>Smartmontools was derived directly from smartsuite . It </b>Smartmontools was derived directly from smartsuite . It
differs from smartsuite in that it supports the ATA/ATAPI-5 standard. So 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 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 the S.M.A.R.T. self-test logs, and doesn't print timestamp information in
in the most usable way. The <tt>smartctl</tt> utility in smartmontools the most usable way. The <tt>smartctl</tt> utility in smartmontools
has added functionality (<tt>-q,-Q,</tt><tt>-L,-f, -F and -m</tt> options), has added functionality for this (<tt>-q,-Q,</tt><tt>-L,-f, -F and -m</tt>
updated documentation, and also fixes small technical bugs in smartsuite. options), updated documentation, and also fixes small technical bugs in smartsuite.
&nbsp; See the <a &nbsp; See the <a
href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/smartmontools/sm5/CHANGELOG">CHANGELOG</a> href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/smartmontools/sm5/CHANGELOG">CHANGELOG</a>
file for a summary of what's been done.<br> file for a summary of what's been done. The <tt>smartd</tt> utility differs
from the smartsuite one in a couple of ways. &nbsp;First, it prints somewhat
more informative error messages to the syslog. &nbsp;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. &nbsp;[If the configuration file
does not exist, then it does query all IDE and SCSI devices.] &nbsp;Finally,
it's a well-behaved daemon and doesn't leave open file descriptors and other
detrius behind.<br>
<br> <br>
The other principle difference is that smartmontools is an open-source The other principle difference is that smartmontools is an open-source development
development project, meaning that we keep the files in CVS, and that project, meaning that we keep the files in CVS, and that other developers
other developers who wish to contribute can commit changes to the archive. who wish to contribute can commit changes to the archive. &nbsp;If you would
&nbsp;If you would like to contribute, please write to to <a like to contribute, please write to to <a
href="ttp://lists.sourceforge.net/mailman/listinfo/smartmontools-support"> href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
smartmontools-support</a>.<br> smartmontools-support</a>.<br>
<br> <br>
But the bottom line is that the code in smartmontools is derived directly But the bottom line is that the code in smartmontools is derived directly
...@@ -360,89 +369,12 @@ When the command that caused the error occurred, the device was active or idle. ...@@ -360,89 +369,12 @@ When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: After command completion occurred, registers were:
ER:40 SC:01 SN:15 CL:be CH:2e D/H:e0 ST:51 ER:40 SC:01 SN:15 CL:be CH:2e D/H:e0 ST:51
Sequence of commands leading to the command that caused the error were: Sequence of commands leading to the command that caused the error were:
DCR FR SC SN CL CH D/H CR Timestamp DCR FR SC SN CL CH D/H CR Timestamp<br> 00 00 01 15 be 2e e0 c8 831.599<br> 00 00 01 14 be 2e e0 c8 831.594<br> 00 00 01 13 be 2e e0 c8 831.594<br> 00 00 01 12 be 2e e0 c8 831.594<br> 00 00 01 11 be 2e e0 c8 831.594<br><br>Error 2 occurred at disk power-on lifetime: 458 hours<br>When the command that caused the error occurred, the device was active or idle.<br>After command completion occurred, registers were:<br>ER:40 SC:45 SN:15 CL:be CH:2e 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 da bd 2e e0 c8 829.680<br> 00 00 80 5a bd 2e e0 c8 829.677<br> 00 00 80 da bc 2e e0 c8 829.673<br> 00 00 80 5a bc 2e e0 c8 829.671<br> 00 00 01 58 bc 2e e0 c8 829.671<br><br>Error 3 occurred at disk power-on lifetime: 458 hours<br>When the command that caused the error occurred, the device was active or idle.<br>After command completion occurred, registers were:<br>ER:40 SC:01 SN:47 CL:bc CH:2e 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 01 47 bc 2e e0 c8 826.962<br> 00 00 01 46 bc 2e e0 c8 826.961<br> 00 00 01 45 bc 2e e0 c8 826.961<br> 00 00 01 44 bc 2e e0 c8 826.961<br> 00 00 01 43 bc 2e e0 c8 826.961<br><br>Error 4 occurred at disk power-on lifetime: 458 hours<br>When the command that caused the error occurred, the device was active or idle.<br>After command completion occurred, registers were:<br>ER:40 SC:13 SN:47 CL:bc CH:2e 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 da bb 2e e0 c8 825.038<br> 00 00 80 5a bb 2e e0 c8 825.033<br> 00 00 80 da ba 2e e0 c8 825.030<br> 00 00 80 5a ba 2e e0 c8 824.940<br> 00 00 80 da b9 2e e0 c8 824.937<br><br>Error 5 occurred at disk power-on lifetime: 458 hours<br>When the command that caused the error occurred, the device was active or idle.<br>After command completion occurred, registers were:<br>ER:40 SC:01 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 01 85 19 2c e0 c8 816.487<br> 00 00 01 84 19 2c e0 c8 816.487<br> 00 00 01 83 19 2c e0 c8 816.486<br> 00 00 01 82 19 2c e0 c8 816.486<br> 00 00 01 81 19 2c e0 c8 816.486<br><br>SMART Self-test log, version number 1<br>Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error<br># 1 Short off-line Completed 00% 587 <br># 2 Short off-line Completed 00% 583 <br># 3 Short off-line Completed 00% 551 <br># 4 Short captive Interrupted (host reset) 40% 551 <br># 5 Short off-line Completed 00% 551 <br># 6 Extended off-line Completed: read failure 40% 550 0x002c1985<br># 7 Extended off-line Aborted by host 50% 550 <br># 8 Short off-line Completed 00% 550 <br># 9 Short off-line Completed 00% 537 <br>#10 Extended off-line Completed: read failure 40% 536 0x002c1985<br>#11 Short off-line Completed 00% 536 <br>#12 Short off-line Completed 00% 536 <br>#13 Short off-line Completed 00% 533 <br>#14 Short off-line Completed 00% 532 <br>#15 Short captive Completed 00% 459 <br>#16 Short captive Completed 00% 459 <br>#17 Extended off-line Completed: read failure 40% 455 0x002c1985<br>#18 Extended off-line Aborted by host 50% 455 <br>#19 Short off-line Completed 00% 451 <br>#20 Short off-line Completed 00% 451 <br>#21 Extended off-line Completed: read failure 40% 449 0x002c1985<br></tt></pre>
00 00 01 15 be 2e e0 c8 831.599
00 00 01 14 be 2e e0 c8 831.594
00 00 01 13 be 2e e0 c8 831.594
00 00 01 12 be 2e e0 c8 831.594
00 00 01 11 be 2e e0 c8 831.594
Error 2 occurred at disk power-on lifetime: 458 hours
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER:40 SC:45 SN:15 CL:be CH:2e D/H:e0 ST:51
Sequence of commands leading to the command that caused the error were:
DCR FR SC SN CL CH D/H CR Timestamp
00 00 80 da bd 2e e0 c8 829.680
00 00 80 5a bd 2e e0 c8 829.677
00 00 80 da bc 2e e0 c8 829.673
00 00 80 5a bc 2e e0 c8 829.671
00 00 01 58 bc 2e e0 c8 829.671
Error 3 occurred at disk power-on lifetime: 458 hours
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER:40 SC:01 SN:47 CL:bc CH:2e D/H:e0 ST:51
Sequence of commands leading to the command that caused the error were:
DCR FR SC SN CL CH D/H CR Timestamp
00 00 01 47 bc 2e e0 c8 826.962
00 00 01 46 bc 2e e0 c8 826.961
00 00 01 45 bc 2e e0 c8 826.961
00 00 01 44 bc 2e e0 c8 826.961
00 00 01 43 bc 2e e0 c8 826.961
Error 4 occurred at disk power-on lifetime: 458 hours
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER:40 SC:13 SN:47 CL:bc CH:2e D/H:e0 ST:51
Sequence of commands leading to the command that caused the error were:
DCR FR SC SN CL CH D/H CR Timestamp
00 00 80 da bb 2e e0 c8 825.038
00 00 80 5a bb 2e e0 c8 825.033
00 00 80 da ba 2e e0 c8 825.030
00 00 80 5a ba 2e e0 c8 824.940
00 00 80 da b9 2e e0 c8 824.937
Error 5 occurred at disk power-on lifetime: 458 hours
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER:40 SC:01 SN:85 CL:19 CH:2c D/H:e0 ST:51
Sequence of commands leading to the command that caused the error were:
DCR FR SC SN CL CH D/H CR Timestamp
00 00 01 85 19 2c e0 c8 816.487
00 00 01 84 19 2c e0 c8 816.487
00 00 01 83 19 2c e0 c8 816.486
00 00 01 82 19 2c e0 c8 816.486
00 00 01 81 19 2c e0 c8 816.486
SMART Self-test log, version number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short off-line Completed 00% 587
# 2 Short off-line Completed 00% 583
# 3 Short off-line Completed 00% 551
# 4 Short captive Interrupted (host reset) 40% 551
# 5 Short off-line Completed 00% 551
# 6 Extended off-line Completed: read failure 40% 550 0x002c1985
# 7 Extended off-line Aborted by host 50% 550
# 8 Short off-line Completed 00% 550
# 9 Short off-line Completed 00% 537
#10 Extended off-line Completed: read failure 40% 536 0x002c1985
#11 Short off-line Completed 00% 536
#12 Short off-line Completed 00% 536
#13 Short off-line Completed 00% 533
#14 Short off-line Completed 00% 532
#15 Short captive Completed 00% 459
#16 Short captive Completed 00% 459
#17 Extended off-line Completed: read failure 40% 455 0x002c1985
#18 Extended off-line Aborted by host 50% 455
#19 Short off-line Completed 00% 451
#20 Short off-line Completed 00% 451
#21 Extended off-line Completed: read failure 40% 449 0x002c1985
</tt></pre>
<tt> </tt> <tt> </tt>
<hr width="100%" size="2">Page maintained by <a <hr width="100%" size="2">Page maintained by <a
href="mailto:smartmontools-support@lists.sourceforge.net">Bruce Allen</a><br> href="mailto:smartmontools-support@lists.sourceforge.net">Bruce Allen</a><br>
<big> </big></div> <big> </big></div>
<br> <br>
<br>
</body> </body>
</html> </html>
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment

AEI Privacy Policy Imprint