1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in

root/trunk/www/index.html @ 2170

Revision 2170, 58.6 KB (checked in by chrfranke, 7 years ago)

Updated NEWS, updated hostname and links for new SourceForge? CVS service.

Line 
1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
3<head>
4 <title>smartmontools Home Page (last updated $Date: 2006/05/19 16:50:36 $)</title>
5 <link rev="made" href="mailto:smartmontools-support&#64;sourceforge.net" />
6 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
7 <meta name="description" content="smartmontools Home Page" />
8 <meta name="keywords" content="S.M.A.R.T., SMART, FreeBSD, Linux, NetBSD, Solaris, Windows, disk, monitor, monitoring" />
9</head>
10<body>
11
12<!-- $Id: index.html,v 1.199 2006/05/19 16:50:36 chrfranke Exp $ -->
13
14<div align="center">
15  <img src="smart_logo.gif" border="0" width="105" height="59" alt="SMART LOGO" />
16  <br />
17  <h1><font color="#3333ff">smartmontools Home Page</font></h1>
18</div>
19
20<p>Welcome! This is the home page for the smartmontools package.</p>
21
22<font color="#ff0000">
23<b>NEWS:</b>
24</font>
25<ul>
26<li><font color="#ff0000">Smartmontools 5.36 (stable) was released 2006-04-16, see
27<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/NEWS?revision=RELEASE_5_36&amp;view=markup">
28NEWS</a> and
29<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/CHANGELOG?revision=RELEASE_5_36&amp;view=markup">
30CHANGELOG</a> for details.
31</font></li>
32<li><font color="#ff0000">SourceForge CVS architecture has changed 2006-05-12, please read
33notes <a href="#CVSInstall">below</a> if you install smartmontools from CVS.</font></li>
34</ul>
35<font color="#ff0000">
36Please report problems (or success!) with the new release to the
37<a href="http://lists.sourceforge.net/lists/listinfo/smartmontools-support">
38smartmontools-support mailing list</a>.
39</font>
40
41
42<p>The smartmontools package contains two utility programs
43(<font color="#3333ff"><b>smartctl</b></font> and
44<font color="#3333ff"><b>smartd</b></font>) to control and monitor storage
45systems using the Self-Monitoring, Analysis and Reporting Technology
46System (SMART) built into most modern ATA and SCSI hard
47disks.&#160; In many cases, these utilities will provide advanced warning
48of disk degradation and failure.</p> 
49
50<p>Smartmontools is originally derived from the Linux <a
51href="http://sourceforge.net/projects/smartsuite/">smartsuite
52package</a>, and includes support for ATA/ATAPI-3 to -7 disks and SCSI
53disk and tape devices.  It should run on any modern Darwin (Mac OSX),
54Linux, FreeBSD, NetBSD, OpenBSD, Solaris, OS/2, eComStation or <a
55href="#windows">Windows</a> system. Alternatively, it can also be run
56from one of the <a href="#bootable">bootable CDs or floppies containing
57smartmontools</a>.</p>
58
59<p>For printing convenience, everything except for the <a
60href="#sampleoutput">example output</a> is on a single page.</p>
61
62<hr size="2" />
63
64<ul>
65<li><a href="http://www.linuxjournal.com/article.php?sid=6983">
66Monitoring Hard Disks with SMART (Linux Journal, January 2004, page 74)</a></li>
67<li><a href="#howtodownload">How to download and install
68smartmontools</a></li>
69<li><a href="#PROBLEMS">Serious Problem Reports (system lockup, etc.)</a></li>
70<li><a href="#FAQ">Frequently Asked Questions</a></li>
71<li><a href="#scsi">SCSI disks and tapes (TapeAlert)</a></li>
72<li><a href="#testinghelp">FireWire, USB, and SATA disks/tapes</a></li>
73<li><a href="#differfromsmartsuite">How does smartmontools differ from
74smartsuite?</a></li>
75<li><a href="#references">Useful references on SMART and ATA/ATAPI-5,
76-6, and -7</a></li>
77<li><a href="#sampleoutput">Example output from smartmontools</a>
78<b>smartctl</b> utility</li>
79<li><a href="http://smartmontools.cvs.sourceforge.net/smartmontools/">CVS
80repository</a> and <a href="http://sourceforge.net/projects/smartmontools/">SourceForge's
81Project Page</a></li>
82<li>Mailing List <a href="http://lists.sourceforge.net/lists/listinfo/smartmontools-support">Information</a>
83and <a href="http://sourceforge.net/mailarchive/forum.php?forum=smartmontools-support">Archives</a>
84(Archive has <b>Search Box</b> in top left corner). <a href="#altmail">Alternative</a> (and usually up to date) archives.</li>
85<li>Current <a href="man/smartctl.8.html">smartctl</a>, <a href="man/smartd.8.html">smartd</a>, and <a href="man/smartd.conf.5.html">smartd.conf</a> HTML man pages generated from CVS.</li>
86</ul>
87
88<hr size="2" />
89
90<b><a name="howtodownload"></a>How to download and install
91smartmontools</b>
92
93<p>There are different ways to get and install
94smartmontools.&#160; You can use any of the procedures below
95(the fourth is for Debian Linux only).&#160; Just after "Method 6" below are
96some instructions for trying out smartmontools once you have completed
97the installation. The
98<b><a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/INSTALL?view=markup">
99INSTALL</a></b> file contains additional information.
100</p>
101<b>First Method (Redhat/Fedora Linux) - Install from the RPM file</b>
102<ul>
103<li>Download the latest binary RPM file (<tt>*.rpm</tt>) from <a href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>.&#160;
104Don't get the SRPM file (<tt>*.src.rpm</tt>).<br/> SuSE users: use one of the SuSE-specific RPM files.</li>
105<li>Install it using RPM.&#160; <i>You must be root to do this</i>:
106<pre>su root (enter root password)
107rpm -ivh smartmontools-5.32.i386.rpm</pre>
108For most users, this is all that is needed.</li>
109<li>If you receive an error message, you have probably previously
110installed the <tt>smartsuite</tt> package, or RedHat's
111<tt>kernel-utils</tt> package, which provide older versions of the
112<tt>smartd</tt> and <tt>smartctl</tt> utilities.&#160; In this case you
113should use the <tt>--nodeps</tt> or <tt>--force</tt> arguments of rpm to
114replace these two utilities:
115<pre>rpm -ivh --nodeps --force smartmontools-5.32.i386.rpm</pre></li>
116<li>If you want to remove the package (<tt>rpm -e smartmontools</tt>)
117and your system does not have <tt>chkconfig</tt> installed, you may need
118to use:
119<pre>rpm -e --noscripts smartmontools</pre></li>
120</ul>
121
122<b>Second Method (Linux/Solaris/FreeBSD/NetBSD/OpenBSD/Cygwin) - Install from the source tarball</b>
123<ul>
124<li>Download the latest source tarball from <a
125href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>.
126Note: you probably want the most recent stable release. Stable releases have
127even-numbered extensions, and unstable experimental releases have
128odd-numbered extensions.</li>
129<li>Uncompress the tarball:
130<pre>tar zxvf smartmontools-5.32.tar.gz</pre></li>
131<li>The previous step created a directory called <tt>smartmontools-5.32</tt>
132containing the code.&#160; Go to that directory, build, and install:
133<pre>cd smartmontools-5.32
134./configure
135make
136make install
137</pre></li>
138<li> Note that the <tt>./configure</tt> step above is not possible for releases &lt;=5.1-18, you
139have to edit the Makefile by hand to change installation paths. For releases &gt;=5.19, <tt>./configure</tt>
140can take optional arguments. These optional arguments are fully explained in the
141<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/INSTALL?view=markup">INSTALL</a>
142file. The most important one is <tt>--prefix</tt> to change the default installation directories.<p>
143<i>Please note that the default installation location changed in versions &gt;=5.31.</i>
144If you don't pass any arguments to <tt>./configure</tt> all files will reside under
145<b>/usr/local</b> to not interfere with files from your distribution. For more detailed
146information please also refer to the
147<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/INSTALL?view=markup">INSTALL</a>
148document.
149</p>
150</li>
151<li>To compile from another directory (avoids overwriting virgin files from the smartmontools package)
152replace <tt>./configure [options]</tt> by:
153<pre>
154mkdir objdir
155cd objdir
156../configure [options]
157</pre></li>
158<li>To install to another destination (useful for testing and to avoid overwriting an existing smartmontools installation)
159replace <tt>make install</tt> by:
160<pre>
161make DESTDIR=/home/myself/smartmontools-test install
162</pre>
163Use a full path: <tt>~/smartmontools-test</tt> won't work.
164</li>
165<li>Unless the destination directory is your home directory (or a location that you have write permission)
166only root can do <tt>make install</tt></li>
167</ul>
168
169<b><a name="CVSInstall"></a>
170Third Method (Darwin/FreeBSD/Linux/NetBSD/OpenBSD/Solaris/Cygwin) - Install from the CVS repository</b>
171<ul>
172<li><p><font color="#ff0000">Due to the new the SourceForge CVS
173architecture, the hostname for CVS access has changed from
174<tt>cvs.sourceforge.net</tt> to <tt>smartmontools.cvs.sourceforge.net</tt>.
175To update a copy of smartmontools checked out before 2006-05-12, change all
176the <tt>*/CVS/Root</tt> files accordingly.
177</font></p></li>
178
179<li><p>One of the really cool things about CVS is that you can get
180<i>any</i> version of the code you want, from the first release up the
181the most current development version.&#160; And it's trivial, because
182each release is <u>tagged</u> with a name like
183<tt>RELEASE_5_1_18</tt>.&#160; You can see what the different names are
184by looking at the <a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/">
185CVS repository</a>.&#160; You'll see the tag names in the little scroll
186window where it says "Show only files with tag".&#160; All you need to
187do to get the latest development code is
188(but note that the development code may be unstable, and that the
189documentation and code may be inconsistent):</p>
190
191<pre>cvs -d:pserver:anonymous@smartmontools.cvs.sourceforge.net:/cvsroot/smartmontools login (when prompted for a password, just press Enter)
192cvs -d:pserver:anonymous@smartmontools.cvs.sourceforge.net:/cvsroot/smartmontools co sm5</pre></li>
193
194<li>To instead get the 5.1-16 release:
195
196<pre>cvs -d:pserver:anonymous@smartmontools.cvs.sourceforge.net:/cvsroot/smartmontools co -r RELEASE_5_1_16 sm5</pre></li>
197
198<li><p>This will create a subdirectory called <tt>sm5/</tt> containing the
199code.&#160; Go to that directory, build, and install:</p>
200<pre>cd sm5
201./autogen.sh
202./configure
203make
204make install
205</pre>
206
207<ul>
208<li>See notes under <b>Second method - install from source tarball</b> for different options to <tt>./configure</tt>
209and other useful remarks.</li>
210<li>Skip <tt>./autogen.sh</tt> and <tt>./configure</tt> for tagged releases
211&lt;= 5.1-18 (RELEASE_5_X_Y, where X = 0 or 1 and Y = 0 to 18).</li>
212<li>If you get the current sources (<tt>cvs co</tt> with no arguments or do <tt>cvs up
213-A</tt>) then you <i>will</i>  need those two additional steps.</li>
214</ul></li>
215
216<li>To update your sources to the 5.1-18 release:
217<pre>cd sm5
218cvs up -r RELEASE_5_1_18</pre></li>
219
220<li>To update any tagged release to the latest development code:
221
222<pre>cd sm5
223cvs up -A</pre></li>
224</ul>
225
226<b>Fourth Method (Debian Linux) - Install the Debian package</b>
227<ul>
228<li>
229The latest version of the smartmontools package in <i>.deb</i> format is
230available at the  <a href="http://packages.debian.org/unstable/utils/smartmontools.html">Debian smartmontools
231package page</a>.
232This package is for the (unreleased) <a href="http://www.debian.org/releases/">unstable</a>
233distribution.</li>
234<li>If you're running Debian <a
235href="http://www.debian.org/releases/stable/">stable</a> please download the
236package from <a
237href="http://honk.physik.uni-konstanz.de/~agx/linux-i386/debian/smartmontools/">here</a>.</li>
238<li>
239You can then install the package using:
240<pre>
241dpkg -i smartmontools_5.1.18-1.agx0_i386.deb
242</pre>
243But the preferred method is to add the following line to your
244<tt>/etc/apt/sources.list</tt>:
245<pre>deb http://honk.physik.uni-konstanz.de/~agx/linux-i386/debian smartmontools/
246</pre>
247and type <pre>
248apt-get update &amp;&amp; apt-get install smartmontools
249</pre> this will automatically download and install the package.
250</li>
251</ul>
252
253<b><a name="CygwinInstall"></a>
254Fifth Method (Windows with <a href="http://www.cygwin.com/">Cygwin</a>
255installed) - Install the Cygwin package
256</b>
257<ul>
258<li>Starting with CVS snapshot 2005-11-15, smartmontools is part of
259the <a href="http://cygwin.com/packages/">Cygwin distribution</a>.
260A list of available smartmontools packages and their contents is
261<a href="http://cygwin.com/packages/smartmontools/">here</a>.
262</li>
263<li><p>To update your installation, click on the "Install or update now!"
264link on the <a href="http://cygwin.com/">Cygwin web page</a>.
265This downloads <tt>setup.exe</tt> to your system.
266Then, run setup and answer all of the questions.
267Select smartmontools package in the "Utils" category.</p>
268</li>
269<li><p>The optional source package (<tt>smartmontools-*-src.tar.bz2</tt>)
270can be used to build both the Cygwin and the Windows binary packages
271on Cygwin.
272Refer to the file <tt>/usr/share/doc/Cygwin/smartmontools-*.README</tt>
273for details.</p>
274</li>
275</ul>
276
277<b><a name="WindowsInstall"></a>
278Sixth Method (Windows) - Install the Windows package
279</b>
280<ul>
281<li>Download the latest Windows package (<tt>*.win32.zip</tt>) from
282<a href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>.
283</li>
284<li><p>Unzip the files into a directory of your choice.
285A directory in the PATH is recommended for the <tt>*.exe</tt> files.</p>
286</li>
287</ul>
288
289
290<b>After installing it using Method 1, 2, 3, 4 or 5 above, you can read the
291man pages, and try out the commands:</b>
292
293<pre>
294man smartd.conf
295man smartctl
296man smartd
297/usr/sbin/smartctl -s on -o on -S on /dev/hda (only root can do this)
298/usr/sbin/smartctl -a /dev/hda (only root can do this)</pre>
299
300<p>Note that the default location for the manual pages are
301<tt>/usr/share/man/man5</tt> and <tt>/usr/share/man/man8</tt>.&#160; If
302"<tt>man</tt>" doesn't find them, then you may need to add
303<tt>/usr/share/man</tt> to your <tt>MANPATH</tt> environment
304variable.</p>
305
306<p>The Windows package (see Method 6 above) provides preformatted man pages
307in <tt>*.html</tt> and <tt>*.txt</tt> format.</p>
308
309<hr size="2" />
310
311<a name="PROBLEMS"></a><b>Serious Problem Reports</b>
312<p>If a serious problem gets reported to us, it gets added to the
313<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/WARNINGS?view=markup">
314WARNINGS</a> file in smartmontools. So far there are only a few problem systems listed.</p>
315
316<hr size="2" />
317
318<a name="FAQ"></a><b>Frequently Asked Questions</b>
319
320<p>If your question is not here, please <a href="mailto:smartmontools-support&#64;lists.sourceforge.net">email
321me</a>.</p>
322
323<ul>
324<li><b>Is the smartmontools File Download/Mail List/Mail Archive/CVS server broken?</b>
325
326<p>SourceForge is a free service, which supports a very large number of
327users and projects. Please check the <a
328href="http://sourceforge.net/docman/display_doc.php?docid=2352&amp;group_id=1">
329SourceForge Site Status Page</a> to see the maintenance schedule and to
330learn if SourceForge is experiencing unscheduled system outages or other
331problems.</p>
332
333<p>
334<a name="altmail"></a>Alternative mailing-list archives are provided by
335<a href="http://gmane.org/find.php?list=smartmontools">Gmane</a> and MARC (<a
336href="http://marc.theaimsgroup.com/?l=smartmontools-support">smartmontools-support</a>
337and <a
338href="http://marc.theaimsgroup.com/?l=smartmontools-database">smartmontools-database</a>).</p>
339
340</li>
341
342<li><b>What do I do if I have problems, or need support?&#160; Suppose
343I want to become a developer, or suggest some new extensions?</b>
344
345<p>First, search the support mailing list archives to see if your
346question has been answered. Instructions are in the following
347paragraph.  If you don't find an answer there, then please send an
348email to the <a
349href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">smartmontools-support
350mailing list</a>.  This is a moderated forum: you are not
351required to subscribe to the list in order to post your question.
352</p>
353
354<p>To search the email archives, first go to the <a
355href="http://sourceforge.net/mailarchive/forum.php?forum=smartmontools-support">
356mailing list archive</a>.  In the top left corner you will see a
357search box: use <b>Mailing List</b> as the type of search. This tool
358works very well.</p>
359
360<p>Note that from time to time SourceForge has mailing list problems
361and you'll get a message telling you that <i>Either your mailing list
362name was misspelled or your mailing list has not been archived yet. If
363this list has just been created, please retry in 2-4 hours</i>.  If
364this happens, you'll have to try again later.  Or use <a
365href="#altmail">alternative</a> (and usually up to date) email
366archives.
367</p>
368
369</li>
370
371<li><b>What are the future plans for smartmontools?</b>
372
373<p>My plan is that smartmontools-5.x will support ATA/ATAPI-5
374disks.&#160; Eventually, we'll do smartmontools-6.x to support
375ATA/ATAPI-6 disks, smartmontools-7.x for the ATA/ATAPI-7 standard, and
376so on.&#160; The "x" will denote revision level, as bugs get found and
377fixed, and as enhancements get added.&#160; If it's possible to maintain
378backwards compatibility, that would be nice, but I don't know if it will
379be possible or practical.</p></li>
380
381<li><b>Why are you doing this?</b>
382
383<p>My research group at U. Wisconsin - Milwaukee runs a <a
384href="http://www.lsc-group.phys.uwm.edu/beowulf/medusa/">beowulf
385cluster</a> with 600 ATA-5 and -6 disks (300 IBM and 300
386Maxtor).&#160; We have more than 50 TB of data stored on the
387system.&#160; I also help out with a <a
388href="http://pandora.aei.mpg.de/merlin/"> cluster</a> at the Albert
389Einstein Institute that has 540 IBM ATA-6 disks (65 TB
390total). It's nice to have advanced warning when a disk is going to
391fail.</p></li>
392
393<li><b>Where can I find distribution-specific bug reports?</b>
394<p>
395The smartmontools package supports a number of different operating
396systems. Some of those operating systems are also distributed by
397multiple sources, and some of these maintain a database of bug
398reports.  Here are links:
399</p>
400
401<ul>
402<li><a href="https://bugzilla.redhat.com/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;bug_status=MODIFIED&amp;bug_status=CLOSED&amp;field0-0-0=product&amp;type0-0-0=substring&amp;value0-0-0=smartctl&amp;field0-0-1=component&amp;type0-0-1=substring&amp;value0-0-1=smartctl&amp;field0-0-2=short_desc&amp;type0-0-2=substring&amp;value0-0-2=smartctl&amp;field0-0-3=status_whiteboard&amp;type0-0-3=substring&amp;value0-0-3=smartctl&amp;field0-0-4=product&amp;type0-0-4=substring&amp;value0-0-4=smartd&amp;field0-0-5=component&amp;type0-0-5=substring&amp;value0-0-5=smartd&amp;field0-0-6=short_desc&amp;type0-0-6=substring&amp;value0-0-6=smartd&amp;field0-0-7=status_whiteboard&amp;type0-0-7=substring&amp;value0-0-7=smartd&amp;field0-0-8=product&amp;type0-0-8=substring&amp;value0-0-8=smartsuite&amp;field0-0-9=component&amp;type0-0-9=substring&amp;value0-0-9=smartsuite&amp;field0-0-10=short_desc&amp;type0-0-10=substring&amp;value0-0-10=smartsuite&amp;field0-0-11=status_whiteboard&amp;type0-0-11=substring&amp;value0-0-11=smartsuite&amp;field0-0-12=product&amp;type0-0-12=substring&amp;value0-0-12=smartmontools&amp;field0-0-13=component&amp;type0-0-13=substring&amp;value0-0-13=smartmontools&amp;field0-0-14=short_desc&amp;type0-0-14=substring&amp;value0-0-14=smartmontools&amp;field0-0-15=status_whiteboard&amp;type0-0-15=substring&amp;value0-0-15=smartmontools">Redhat/Fedora Bugzilla Database (Linux)</a> </li>
403<li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=pkg&amp;data=smartmontools&amp;archive=no">Debian Bug Database (Linux)</a></li>
404<li><a href="http://bugs.gentoo.org/buglist.cgi?bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;field0-0-0=product&amp;type0-0-0=substring&amp;value0-0-0=smartmontools&amp;field0-0-1=component&amp;type0-0-1=substring&amp;value0-0-1=smartmontools&amp;field0-0-2=short_desc&amp;type0-0-2=substring&amp;value0-0-2=smartmontools&amp;field0-0-3=status_whiteboard&amp;type0-0-3=substring&amp;value0-0-3=smartmontools">Gentoo Bug Database (Linux)</a></li>
405<li><a href="http://www.netbsd.org/cgi-bin/query-pr-list.pl?text=smartctl&amp;state=open&amp;state=feedback&amp;state=analyzed&amp;state=suspended">NetBSD smartctl bug database</a></li>
406<li><a href="http://www.netbsd.org/cgi-bin/query-pr-list.pl?text=smartd&amp;state=open&amp;state=feedback&amp;state=analyzed&amp;state=suspended">NetBSD smartd bug database</a></li>
407<li><a href="http://www.netbsd.org/cgi-bin/query-pr-list.pl?text=smartmontools&amp;state=open&amp;state=feedback&amp;state=analyzed&amp;state=suspended">NetBSD smartmontools bug database</a></li>
408</ul>
409<p>
410If you can provide additional distribution or OS-specific bug-database links, please send an email to smartmontools-support.
411</p></li>
412
413<li><b>I see some strange output from smartctl.  What does it mean?</b>
414
415<p>The raw SMART attributes (temperature, power-on lifetime, and so
416on) are stored in vendor-specific structures.&#160; Sometime these are
417strange.&#160; Hitachi disks (at least some of them) store power-on
418lifetime in minutes, rather than hours (see next question below).&#160; IBM disks (at least some
419of them) have three temperatures stored in the raw structure, not just
420one.&#160; And so on.&#160; If you find strange output, or unknown
421attributes, please send an email to <a href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support"> 
422smartmontools-support</a> and we'll help you try and figure it
423out.</p></li>
424
425
426<li><b>Why is my disk temperature s reported by smartd as 150 Celsius?</b>
427<p>
428It's not.  Please read the end of the <b>smartd</b> man page (NOTES).
429For example, in the message: <br/>
430<b>'Device: /dev/hda, SMART Attribute: 194 Temperature_Celsius changed from 94 to 93'</b><br/>
431the value given is the 'Normalized' not the 'Raw' Attribute value (the
432disk temperature in this case is about 22 Celsius).  The
433<b>'-R'</b> and <b>'-r'</b> Directives modify this behavior, so that
434the information is printed with the Raw values as well, for example:
435<br/>
436<b>'Device: /dev/hda, SMART Attribute: 194 Temperature_Celsius changed from 94 [Raw 22] to 93 [Raw 23]'</b><br/>
437Here the Raw values are the actual disk temperatures in Celsius.  The
438way in which the Raw values are printed, and the names under which the
439Attributes are reported, is governed by the various
440<b>'-v Num,Description'</b> Directives described in the <b>smartd</b>
441man page. Please see the <b>smartctl</b> manual page for further
442explanation of the differences between Normalized and Raw Attribute
443values.
444</p>
445</li>
446
447<li><b>What are the operating system requirements?</b>
448<p>
449Please see the first section of the
450<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/INSTALL?view=markup">
451INSTALL</a> file.
452</p>
453</li>
454
455<li><b>What Attributes does smartmontools not yet recognize?</b>
456
457<p>From Maxtor disks (99), (100), and (101).  These are not used by
458Maxtor in SMART revision 5.  They will be used in SMART revision 6,
459but the engineering group has not yet decided what to monitor with
460these Attributes.
461</p>
462</li>
463
464<li><b>My Maxtor/Hitachi/Fujitsu disk is only a few days old, yet smartctl reports its age (Attribute 9) as thousands of hours!</b>
465
466<p>On recent disks, Maxtor has started to use Attribute 9 to
467store the power-on disk lifetime in minutes rather than hours.  In this case, use
468the:<br/>
469<tt>-v 9,minutes</tt><br/>
470option to correctly display hours and minutes.
471</p>
472<p>Some models of Fujitsu disks use Attribute 9 to store
473the power-on disk lifetime in seconds. In that case, use the:<br/>
474<tt>-v 9,seconds</tt><br/>
475option to correctly display hours, minutes and seconds.</p>
476</li>
477
478<li><b>The power-on timer (Attribute 9 raw value) on my Maxtor disk acts strange.</b>
479
480<p>There are three related problems with Maxtor's SMART firmware:
481</p>
482
483<p>
484<b>1 - </b> On some Maxtor disks, the raw value of Attribute 9 (Power
485On Time) is <i>supposed</i> to be minutes. But it advances at an
486unpredictable rate, always more slowly than one count per minute.
487This is because when the disk is in idle mode, the counter stops
488advancing.  This is only supposed to happen in standby mode.  This
489will be corrected in Maxtor product lines released after October 2004.
490</p>
491
492<p>
493<b>2 - </b> In Maxtor disks that use the raw value of Attribute 9 as a
494minutes counter, only two bytes (of the six available) are used to
495store the raw value.  So it resets to zero once every 65536=2^16
496minutes, or about once every 1092 hours. This is fixed in all Maxtor
497disks manufactured after July 2003, where the raw value was extended
498to four bytes.
499</p>
500
501<p>
502<b>3 - </b> In Maxtor disks that use the raw value of Attribute 9 as a
503minutes counter, the hour time-stamps in the self-test and ATA error
504logs are calculated by right shifting 6 bits.  This is equivalent to
505dividing by 64 rather than by 60.  As a result, the hour time stamps
506in these logs advance 7% more slowly than they should.  Thus, if you
507do self-tests once per week at the same time, instead of the
508time-stamps being 168 hours apart, they are 157 hours apart.  This is
509also fixed in all Maxtor disks manufactured after July 2003.
510</p>
511</li>
512
513<li><b>The time stamps in the self-test log of my Western Digital (WD) disk
514don't correspond to the power-on time when the test was run</b>
515
516<p>
517The self-test log timestamps in many WD disks roll back to zero every
5181092 hours (65536 minutes).  This problem is due to a WD firmware bug.
519The power-on lifetime in hours is correctly stored in Attribute
5209. However when the power-on lifetime is calculated for self-test log
521entries, the lifetime in minutes is put into a 16-bit register then
522divided by 60.  The 16-bit register overflows and wraps around every
5231092 hours.
524</p>
525
526<p>For WD drives that exhibit this firmware bug, the relationship between
527Attribute 9's raw value (H) and the time-stamps in the self-test log (h) are given by:<br/>
528Let H = power on hours as shown by Attribute 9 (correct)<br/>
529Let M = 60*H (power on minutes, correct)<br/>
530Let m = M mod 65536 (incorrect value of power on minutes)<br/>
531Let h = m/60 (incorrect value of power on hours, shown in self-test log)
532</p>
533</li>
534
535<li><b>The (normalized) WORST Attribute values of my Western Digital
536(WD) disk are <u>larger</u> than the (normalized) CURRENT Attribute
537values</b>
538<p>Western Digital firmware initializes SMART Attributes 10, 11, and
539199 after either 120 spin-ups or 8 power-on hours.  Until that time,
540they have the uninitialized value 253.
541</p>
542</li>
543
544<li><b>Where can I find manufacturer-specific disk-testing
545utilities?</b>
546
547<p>A good listing of such utilities can be found <a
548href="http://www.benchmarkhq.ru/english.html?/be_hdd2.html">here</a>.
549Unfortunately most of these are for MS operating systems, but most can
550be run from an MS-DOS boot disk or from the UBCD (Ultimate Boot CD,
551see <a href="#bootable">below</a>).
552</p>
553
554<p>Note: if you do run one of these utilities, and it identifies the
555meanings of any SMART Attributes that are not known to smartmontools,
556please report them to the mailing list above.
557</p>
558
559<p>These utilities have an important role to fill.  If your disk has
560bad sectors (for example, as revealed by running self-tests with
561smartmontools) and the disk is not able to recover the data from those
562sectors, then the disk will <i>not</i> automatically reallocate those
563damaged sectors from its set of spare sectors, because
564forcing the reallocation to take place may entail some loss of data.
565Because the commands that force such reallocation are
566<i>Vendor Specific</i>, most manufactuers provide a utility for this
567purpose. It may cause data loss but can repair damaged sectors (at
568least, until it runs out of replacement sectors).
569</p>
570</li>
571
572<li><b>When I run <tt>smartd</tt>, the SYSLOG <tt>/var/log/messages</tt>
573contains messages like this:</b>
574<pre>smartd: Reading Device /dev/sdv
575modprobe: modprobe: Can't locate module block-major-65</pre>
576
577<p>This is because when <tt>smartd</tt> starts, if there is no
578configuration file, it looks for all ATA and SCSI devices to monitor
579(matching the pattern <tt>/dev/hd[a-t]</tt> or
580<tt>/dev/sd[a-z]</tt>).&#160; The log messages appear because your
581system doesn't have most of these devices.</p>
582
583<p>The solution is simple: use the <tt>smartd</tt> configuration file
584<tt>/etc/smartd.conf</tt> to specify which devices to monitor.</p></li>
585
586<li><b>What's the story on IBM SMART disks?</b>
587
588<p>Apparently some of the older SMART firmware on IBM disks can
589interfere with the regular operation of the disk.&#160; If you have this
590problem, here are some links:<br/>
591<a href="http://www.geocities.com/dtla_update/">Geocities Site</a>,
592<a href="http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42215">IBM Site #1</a>,
593<a href="http://www-1.ibm.com/support/docview.wss?uid=psg1MIGR-42215">IBM Site #2</a><br/>
594to an IBM Firmware Upgrade that fixes the problem.
595</p></li>
596
597<li><b>How can I check that the package hasn't been tampered with?</b>
598
599<p>Since the <tt>smartmontools</tt> utilities run as root, you might
600be concerned about something harmful being embedded within
601them. Starting with release 5.19 of <tt>smartmontools</tt>, the .rpm
602files and tarball have been GPG signed. The tarball's fingerprint is
603given in a file on the release page with a name like
604<tt>smartmontools-5.32.tar.gz.asc</tt>.  Please verify these using
605the
606<a href="SmartmontoolsSigningKey_2005.txt">Smartmontools GPG Signing Key (current)</a>
607<a href="SmartmontoolsSigningKey.txt">Smartmontools GPG Signing Key (before 2005)</a>
608</p></li>
609
610<li><b>Is there a bootable standalone CD or floppy that contains smartmontools?</b>
611
612<p>If you have a system that is showing signs of disk trouble (for
613example, it's unbootable and the console is full of disk error
614messages) it can be handy to have a version of smartmontools that can
615be run off of a bootable CD or floppy to examine the disk's SMART data and run
616self-tests.  This is also useful if you want to run Captive Self-Tests
617(the <b><tt>-<font size="+2">C</font></tt></b> option of
618<b><tt>smartctl</tt></b> ) on disks that can not easily be unmounted,
619such as those hosting the Operating System files. Or you can use
620this to run <tt>smartctl</tt> on computers that don't use Linux as the
621day-to-day operating system.</p>
622
623<p><a name="bootable"></a>Here is a list of such bootable CDs:</p>
624<ul>
625<li><a href="http://www.lnx-bbc.org/">LNX-BBC Bootable CD</a> </li>
626<li><a href="http://www.stresslinux.org/">Stresslinux Bootable CD</a></li>
627<li><a href="http://www.tux.org/pub/people/kent-robotti/looplinux/rip/">RIP (Recovery Is Possible) Bootable CD</a></li>
628<li><a href="http://www.sysresccd.org/">SystemRescueCd</a></li>
629<li><a href="http://www.gpstudio.com/stux/">STUX Bootable CD</a></li>
630<li><a href="http://www.knopper.net/knoppix/index-en.html">Knoppix Bootable CD</a>
631(Version 3.6 contains smartmontools 5.32, older versions contain
632<a href="#differfromsmartsuite">smartsuite</a>)</li>
633<li><a href="http://www.grml.org/">Grml Bootable CD</a>
634(Knoppix and Debian based CD without KDE and OpenOffice but about 800
635<a href="http://www.grml.org/features/list.html">packages</a> added)</li>
636<li><a href="http://smartlinux.sourceforge.net/">S.M.A.R.T. Linux</a>
637(a bootable FLOPPY containing smartmontools!)</li>
638<li><a href="http://ubcd.sourceforge.net/">Ultimate Boot CD</a>
639(The "Full" version of UBCD 3.0 contains
640<a href="http://www.inside-security.de/insert_en.html">INSERT</a> with smartmontools 5.32
641<a href="http://ubcd.sourceforge.net/insert/start.html#TOCChanges">added</a>)</li>
642<li><a href="http://www.911cd.net/forums/lofiversion/index.php/t13459.html">Smartctl Plugin</a>
643for <a href="http://www.nu2.nu/pebuilder/">BartPE bootable live windows CD</a></li>
644</ul>
645<p>
646Please let me know if there are others, and I will add them to this
647list.
648</p>
649</li>
650
651<li><b>Can I monitor ATA disks behind SCSI RAID controllers?</b>
652
653<p>
654From release 5.1-18, smartmontools fully supports 3ware SCSI RAID
655controllers that use ATA disks internally. To pass commands through
656the 3ware controller, use the smartmontools <b>-d 3ware,N</b> option
657or Directive.
658</p>
659<p>
6603ware Linux device drivers (<tt>3w-xxxx</tt>) versions <b>1.02.00.036</b>
661and earlier do not return the SMART HEALTH STATUS (smartmontools
662<b>-H</b>) of the disks. In addition, the ENABLE AUTOMATIC OFFLINE and
663ENABLE ATTRIBUTE AUTOSAVE commands (smartmontools <b>-o on</b> and
664<b>-S on</b>) can not be passed through the driver to the disks.
665Later driver versions support <i>all</i> of these commands.  You may:
666</p>
667<ul>
668<li>use version <b>1.02.00.037</b> or greater of the <tt>3w-xxxx</tt> driver, or</li>
669<li><a href="3w-xxxx.txt">patch</a> earlier 3ware <tt>3w-xxxx</tt> drivers so that
670these commands reach the disks, or</li>
671<li> use an <b>unpatched</b> earlier <tt>3w-xxxx</tt> driver (which won't pass these
672commands to the disks but will instead print
673harmless warning messages to SYSLOG).</li>
674</ul>
675<p>
676To see if your system's <tt>3w-xxxx</tt> driver has been patched, give the
677command:<br/>
678<tt>smartctl -H -S on -o on -d 3ware,? /dev/sd?</tt>
679<br/>
680If you
681have an unpatched kernel, you'll see warning messages prompting you to
682patch the kernel.</p>
683<p>
684The 3ware <tt>3w-xxxx</tt> version 1.02.00.037 driver first appeared
685in kernel version 2.6.0-test5-bk11 on 24 September 2003 and in kernel
686version 2.4.23-bk2 on 3 December 2003.  It was officially released on
687the 3ware web site on December 19, 2003 as part of their
688driver/firmware/utility package version 7.7.0.
689</p>
690
691<p>
692Note (added 29 July 2004): starting with smartmontools (experimental)
693release 5.33, one can also access SMART data from drives behind 3ware
694controllers using the (character) devices /dev/twe0-15.  This should
695work correctly even with older versions of the 3w-xxxx driver. One can
696also access SMART data from drives behind 3ware 9000-series
697controllers (3w-9xxx driver) using the (character) devices
698/dev/twa0-15.
699</p>
700
701</li>
702
703<li><a name="windows"></a><b>Does it work on Windows?</b>
704
705<p>Yes, finally it does. A windows port of smartctl 5.26 by
706<a href="http://sourceforge.net/users/chrfranke/">Christian Franke</a>
707was first checked in 2004/02/23 on CVS branch
708<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/?pathrev=RELEASE_5_26_WIN32_BRANCH">
709RELEASE_5_26_WIN32_BRANCH</a> and has been merged to the CVS trunk later.</p>
710
711<p>The <a href="http://www.cygwin.com/">Cygwin</a> environment can be
712used to built both Cygwin and Windows (using <a href="http://www.mingw.org/">MinGW</a>)
713versions of smartctl and smartd.
714Installation instructions for binary distributions can be found
715<a href="#CygwinInstall">here</a> and <a href="#WindowsInstall">here</a>.</p>
716
717<p>Some code showing how to access SMART data under Windows 98, NT 4,
7182000, and XP can be found <a
719href="ftp://ftp.heise.de/pub/ct/listings/0207-218.zip">here</a>.
720An example program from Microsoft can be found
721<a href="http://download.microsoft.com/download/winddk/sample3/9x/W9X/EN-US/SmartApp.exe">
722here</a> (the related knowledge base article 208048 is no longer available).
723Reference information about the I/O requests to access SMART data is
724<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/storage/hh/storage/k307_8c974d08-3752-4442-82a5-cc13835ba482.xml.asp">
725here</a> and
726<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/storage/hh/storage/k307_2b043284-934c-4440-a4a4-6078f1bc845d.xml.asp">
727here</a>.
728A related newsgroup thread (with pointers to additional documentation,
729etc.) is <a
730href="http://groups.google.com/groups?hl=en&amp;lr=&amp;ie=UTF-8&amp;oe=UTF-8&amp;th=18cdac9d90f6bda1&amp;rnum=1">here</a>.
731</p>
732</li>
733
734<li><b>Why did the release version scheme change?</b>
735
736<p>It was non-standard.  So with the move to GNU Autoconf and GNU
737Automake it changed from 5.X-Y (where X and Y are one or more digits)
738to 5.Y. Starting with the first release, and moving forward in time, the releases are
739numbered as follows:<br/>
740<tt>
7415.0-1,&nbsp;
7425.0-2,&nbsp;
743...,&nbsp;
7445.0-45,&nbsp;
7455.1-1,&nbsp;
746...,&nbsp;
7475.1-18,&nbsp;
7485.19,&nbsp;
7495.20,&nbsp;
750...
751</tt>
752</p>
753</li>
754
755<li><a name="FAQ-database"></a><b>My ATA drive is not in the smartctl/smartd database.  Does this break anything? How do I get it added?</b>
756<p>
757 If your drive is not in the database, then the
758 <i>names</i> of the Attributes (displayed in the <tt>ATTRIBUTE_NAME</tt> column of
759 <tt>smartctl -A /dev/hd?</tt>) and the <i>format</i> of the the raw Attribute
760 values shown in the <tt>RAW_VALUE</tt> column may be incorrect.  This
761 is mostly cosmetic: the essential drive health monitoring/testing
762 functionality of <b>smartmontools</b> does <i>not</i> depend upon the
763 database.
764</p>
765
766<p>
767<b>
768 If your drive is not in the database, pleaes check <a
769 href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>
770 to be sure that you are using the latest smartmontools release.  Each
771 new release has additional drives added to the database.  Please do
772 not submit a new drive for the database without checking to see if it
773 is already in the database of the current smartmontools release
774 version.
775</b>
776</p>
777
778<p>
779<b> If your drive is not in the database of the current release,</b>
780 to have it added to the database, first use the command:<br/>
781 <tt>smartctl -t short /dev/hd?</tt><br/> to run a short self-test on
782 the drive, and wait a few minutes for the test to complete.  Then
783 email the entire output from:<br/> <tt>smartctl -a /dev/hd?</tt><br/>
784 to <a
785 href="https://lists.sourceforge.net/lists/listinfo/smartmontools-database">smartmontools-database</a>
786 as a plain-text ASCII email attachment (file type: ".txt").  The timestamp
787 in the self-test log will help us to determine whether Attribute 9 is
788 being used to store the lifetime in hours, minutes, or seconds.
789</p>
790<p>
791If you need to use any of the vendor-specific display options
792 (<tt>-v</tt> options) with the drive, or if any of the Attributes are
793 behaving strangely, please include that information as well.
794</p>
795</li>
796
797<li><b>My ATA drive is failing its self-tests, but its SMART health status is 'PASS'. What's going on?</b>
798
799<p>
800If your ATA drive supports self-tests, you should run them on a
801regular basis, for example one per week:
802<br/><tt>smartctl -t long /dev/hd?</tt><br/>
803After the test has completed, you should examine the results with:
804<br/><tt>smartctl -l selftest /dev/hd?</tt><br/>
805</p>
806
807<p>
808If the drive fails a self-test, but still has 'PASS' SMART health
809status, this usually means that there is a corrupted sector on the
810disk, which can not be read.  If the disk were able to read that
811sector of data, even once, then the disk firmware would mark the
812sector as 'bad' and then allocate a spare sectors to replace it.  But
813if the disk can't read the sector even once, then it won't reallocate
814the sector, in hopes of being able, at some time in the future, to
815read the data from it.  See <a
816href="http://smartmontools.sourceforge.net/BadBlockHowTo.txt">BadBlockHowTo</a>
817for instructions about how to force this sector to reallocate (Linux
818only).
819</p>
820<p>
821The disk still has passing health status because the firmware has not
822found other signs of trouble, such as a failing servo.
823</p>
824<p>
825Such disks can often be repaired by using the disk manufaturer's 'disk
826evaluation and repair' utility.  Beware: this may force reallocation
827of the lost sector and thus corrupt or destroy any file system on the
828disk. See <a
829href="http://smartmontools.sourceforge.net/BadBlockHowTo.txt">BadBlockHowTo</a>
830for generic Linux instructions.
831</p>
832
833</li>
834
835<li><b>smartd is warning that my ATA disk has unreadable or uncorrectable or pending sectors. What's going on?</b>
836
837<p>
838Disk drives store data in blocks (sectors) of 512 bytes.  Each 512
839bytes has additional bytes appended to it (usually 40 to 60) which are
840used internally by the disk firmware for error checking/detection and
841correction.  These are called ECC bytes.
842</p>
843<p>
844Sometimes the data in a sector gets corrupted.  This can happen
845because a speck of dust scratched the disk, or because the disk was
846powered down while writing data to that sector, or for other reasons.
847Usually the ECC bytes can be used to correct the corrupted data.
848However if the ECC bytes are inconsistent or can't be used to correct
849the bad data, then the 512 bytes of data are lost.  Such a sector is
850called unreadable or uncorrectable.
851</p>
852<p>
853If your disk has an unreadable sector, this means that some of your
854data can't be retrieved.  You can force the disk to replace the
855unreadable sector with a spare good sector, but only at the price of
856losing the 512 bytes of data forever.
857</p>
858<p>
859Disks with uncorrectable sectors can often be repaired by using the
860disk manufaturer's 'disk evaluation and repair' utility (see previous
861FAQ entry).  Beware: this may force reallocation of the lost sector
862and thus corrupt or destroy any file system on the disk. See <a
863href="http://smartmontools.sourceforge.net/BadBlockHowTo.txt">BadBlockHowTo</a>
864for generic Linux instructions.
865</p>
866<p>
867Normally when an uncorrectable sector is found, the disk puts this
868onto a 'pending sector list' to indicate that it should be replaced
869with a spare good sector.  However this replacement won't take place
870until either the disk can read the data on the bad sector, or is
871commanded to write new data to that bad sector.
872</p>
873
874</li>
875
876
877<li><b>My computer's BIOS has a SMART enable/disable setting.  What
878does it do, and how should I set it?</b>
879<p>
880Some type of BIOS can check the SMART health status of a disk at
881bootup: the equivalent of '<tt>smartctl -H /dev/hd?</tt>'.  This one-time check on
882bootup is done if the BIOS SMART setting is set to 'ENABLE', and is
883not done if the setting is set to 'DISABLE'.
884</p>
885
886<p>
887If this one-time check is done, and the disk's health status is found
888to be 'FAIL', then typically the BIOS will display an error message
889and refuse to boot the machine.
890</p>
891
892<p>
893For the proper functioning of smartmontools, either BIOS setting may
894be used.
895</p>
896</li>
897
898
899<li><b>My Fedora Core Linux system displays the startup message: smartd [FAILED]</b>
900<p>
901Fedora Core is distributed with a smartd configuration file
902/etc/smartd.conf that monitors the first IDE disk /dev/hda.  If this
903device does not exist (or lacks SMART capability) you will get the
904error message above.  Look in SYSLOG (/var/log/messages) for
905additional details about what is going wrong.
906</p>
907<p>
908The solution: If your system has only SCSI disks, or has IDE disk(s)
909on a non-primary controller, just edit /etc/smartd.conf to reflect the
910correct location of the drive(s).  Please also read the 'smartd.conf'
911man page for additional information.
912</p>
913</li>
914
915<li><b>Attribute 194 (Temperature Celsius) behaves strangely on my Seagate disk</b>
916<p>
917Some Seagate disks store the current temperature Celsius in both the
918RAW and NORMALIZED Attribute 194 values, and the maximum lifetime
919temperature in Celsius in the WORST value.  Since cooler is better,
920this means that in this case, <i>lower</i> NORMALIZED Attribute values
921are farther from failure, and that over time the WORST Attribute
922values get <i>larger</i>, not <i>smaller</i> (as with other
923Attributes).
924</p>
925</li>
926
927<li><b>What's this smartctl message mean?: Warning: ATA error count 9 inconsistent with error log pointer 5</b>
928<p>
929The ATA error log is stored in a circular buffer, and the ATA
930specifications are unambiguous about how the entries should be
931ordered.  This warning message means that the disk's firmware does not
932strictly obey the ATA specification regarding the ordering of the
933error log entries in the circular buffer.  Smartmontools will correct
934for this oversight, so this warning message can be safely ignored by
935users.  (On the other hand, firmware engineers: please read the ATA
936specs more closely then fix your code!).
937</p>
938</li>
939</ul>
940
941<hr size="2" /><a name="scsi"></a><b>SCSI disks and tapes
942(TapeAlert)</b>
943<p>Smartmontools for SCSI disks and tapes (including medium changers) is
944discussed on a separate <a href="smartmontools_scsi.html">page</a>.
945</p>
946
947<hr size="2" /><a name="testinghelp"></a><b>FireWire, USB, and SATA
948disks/systems</b>
949<p>As for USB and FireWire (ieee1394) disks and tape drives, the news
950is not good. They appear to Linux as SCSI devices but their
951implementations do not usually support those SCSI commands needed by
952smartmontools. The ieee1394 consortium recently certified the <span
953 style="font-style: italic;">first</span> external enclosure (containing
954a ATA disk and a protocol bridge) as being compliant to the relevant
955standards. Such devices have already been on the market for about 3
956years and they tend to only support the bare minimum of commands
957needed for device operation (i.e. SMART support is an unsupported
958extra).<br />
959</p>
960<p>Smartmontools should work correctly with SATA drives under both
961Linux 2.4 and 2.6 kernels, <i>if</i> you use the standard IDE drivers
962in <tt>drivers/ide</tt>. If you use the new <tt>libata</tt> drivers,
963it won't work correctly because <tt>libata</tt> doesn't yet support
964the needed ATA-passthrough ioctl() calls.  Jeff Garzik, the
965<tt>libata</tt> developer, says that this support will be added to
966libata in the future.  When this happens, we'll add support to
967smartmontools for a new SATA/libata device type <tt>'-d sata'</tt>.
968Typically, to force an SATA disk to run using the standard
969(non-libata) drivers, you must use the BIOS to select "legacy mode"
970for the controller.  If the IDE driver doesn't support your particular
971SATA controller, or the controller doesn't have a legacy interface,
972then only libata can be used.  Unless the hard disk controller on the
973system motherboard is Intel, VIA or nVidia, standard IDE drivers may
974not work
975</p>
976<p>Note: an unofficial <a
977href="http://groups.google.com/groups?hl=en&amp;lr=&amp;ie=UTF-8&amp;safe=off&amp;threadm=2yY8S-4ps-33%40gated-at.bofh.it&amp;rnum=1&amp;prev=/groups%3Fq%3DLinville%2520ioctls%2520SMART%26num%3D100%26hl%3Den%26lr%3D%26ie%3DUTF-8%26safe%3Doff%26sa%3DN%26tab%3Dwg">
978patch to libata</a> that allows smartmontools to be used
979with the standard '-d ata' device type was posted to the linux
980kernel mailing list at the end of August 2004. The patch is included in the
981<a href="http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/">libata-dev
982patchset</a> that can be applied to a recent Linux kernel (>= 2.6.9). With a
983SATA disk driven by a libata driver, smartmontools can now be used by specifying both the
984device type 'ata' and the SCSI device corresponding to this disk, for example,
985<tt>smartctl -i -d ata /dev/sda</tt>.
986The patch is still under development and it is probably best to make sure that
987the disk is idle before trying smartmontools.
988</p>
989
990
991<hr size="2" /><a name="differfromsmartsuite"></a><b>How does
992smartmontools differ from smartsuite?</b>
993
994<p>The smartsuite code was originally developed as a Senior Thesis by
995Michael Cornwell at the Concurrent Systems Laboratory (now part of the
996<a href="http://ssrc.soe.ucsc.edu/">Storage Systems Research
997Center</a>), Jack Baskin School of Engineering, University of
998California, Santa Cruz.
999You can find some information about the original smartsuite project here:
1000<a href="http://www.ucsc.edu/news_events/press_releases/archive/99-00/09-99/smart_software.htm">Press Release 1</a>,
1001<a href="http://www.santa-cruz.com/archive/1999/September/22/local/stories/5local.htm">Press Release 2</a>,
1002<a href="http://www.ucsc.edu/currents/99-00/09-27/smart.html">Press Release 3</a>.
1003</p>
1004
1005<p>
1006<a href="http://csl.cse.ucsc.edu/smart.shtml">According to UCSC</a>
1007smartsuite is no longer maintained; the last release was in 2001.
1008</p>
1009
1010<p>Smartmontools was derived directly from smartsuite.&#160; It differs
1011from smartsuite in that it supports the ATA/ATAPI-5 standard.&#160; So
1012for example <tt>smartctl</tt> from smartsuite has no facility for
1013printing the SMART self-test logs, and doesn't print timestamp
1014information in the most usable way.&#160; The <tt>smartctl</tt> utility
1015in smartmontools has added functionality for this (<tt>-q, -l selftest,-S,
1016-T, -v and -m</tt> options), updated documentation, and also fixes small
1017technical bugs in smartsuite. [One example: smartsuite does not actually use the
1018ATA SMART RETURN STATUS command to find out the health status of a disk.  It instead tries to infer this from the
1019SMART Attribute values.]&#160; See the
1020<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/CHANGELOG?view=markup">CHANGELOG</a>
1021file in CVS for a summary of what's been done.&#160; The <tt>smartd</tt>
1022utility differs from the smartsuite <tt>smartd</tt> in major ways.&#160;
1023First, it prints somewhat more informative error messages to the syslog.
1024&#160; Second, on startup it looks for a configuration file
1025<tt>/etc/smartd.conf</tt>, and if <tt>smartd</tt> finds this file, it
1026monitors the list of devices therein, rather than querying all IDE and
1027SCSI devices on your system.&#160; (If the configuration file does not
1028exist, then it does query all IDE and SCSI devices.)&#160; Also, it's
1029a well-behaved daemon and doesn't leave open file descriptors and other
1030detrius behind.&#160; In addition, the <tt>smartmontools</tt> version of
1031<tt>smartd</tt> can be instructed (via Directives in the configuration
1032file) to monitor for changes in a number of different disk properties:
1033the SMART status, failure or prefailure attributes going below
1034threshold, new errors appearing in the ATA Error Log or the SMART
1035Self-Test Log, and so on. <tt>smartd</tt> can also send an email warning or run a
1036user-specified executable if it detects a problem with the disk.
1037</p>
1038
1039<p>The other principle difference is that smartmontools is an
1040OpenSource development project, meaning that we keep the files in CVS,
1041and that other developers who wish to contribute can commit changes to
1042the archive. If you would like to contribute, please write to to <a
1043href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">smartmontools-support</a>.</p>
1044
1045<p>But the bottom line is that the code in smartmontools is derived
1046directly from smartsuite and is similar.&#160; The smartsuite package
1047can be found <a href="http://sourceforge.net/projects/smartsuite/">here</a>.</p>
1048
1049<hr size="2" /><a name="references"></a><b><big>Useful references on
1050SMART and the  ATA/ATAPI standards</big></b>
1051
1052<p><big>If you are having trouble understanding the output of smartctl
1053or smartd, please first read the manual pages installed on your
1054system:</big></p>
1055
1056<pre>
1057man 8 smartctl
1058man 8 smartd
1059man 5 smartd.conf
1060</pre>
1061
1062<p>
1063Here are on-line versions of the smartmontools man pages:<br/> <a
1064href="man/smartctl.8.html">smartctl manual page</a><br/> <a
1065href="man/smartd.8.html">smartd manual page</a><br/> <a
1066href="man/smartd.conf.5.html">smartd.conf manual page</a><br/> Note
1067that these are the manual pages for the <b><i>current version</i></b>
1068of smartmontools in the developers CVS repository; they might not
1069correspond to the (possibly older) version of smartmontools installed
1070on <i>your</i> system.  So the manual pages installed on your system
1071should be regarded as definitive for your installation.</p>
1072
1073<p><big>If you'd like to know more about SMART, then the following
1074references may be helpful:</big></p>
1075
1076<ul>
1077<li><a href="http://www.linuxjournal.com/article.php?sid=6983">Monitoring Hard Disks with SMART (Linux Journal, Jan 2004)</a></li>
1078<li><a href="http://lea-linux.org/cached/index/Hardware-hard_plus-smart.html">Soyez Smart (Francais) from GNU Linux Magazine France n�68,</a></li>
1079<li><a href="http://www.linux-user.de/ausgabe/2004/10/056-smartmontools/">Vorbeugen statt Crash (Deutsch)</a>
1080from <a href="http://www.linux-user.de/ausgabe/2004/10">LinuxUser 2004/10</a></li>
1081<li><a href="http://www.linux-magazine.com/issue/49/Monitoring_Hard_Disks_with_smartmontools.pdf">Crash Prevention
1082(English version of above)</a> from <a href="http://www.linux-magazine.com/issue/49">Linux Magazine Dec 2004</a></li>
1083<li><a href="http://www.wikipedia.org/">Wikipedia</a> articles about SMART:
1084<a href="http://en.wikipedia.org/wiki/Self-Monitoring%2C_Analysis_and_Reporting_Technology">English</a>,
1085<a href="http://de.wikipedia.org/wiki/Self-Monitoring%2C_Analysis_and_Reporting_Technology">Deutsch</a>,
1086<a href="http://es.wikipedia.org/wiki/SMART">Espa&#241;ol</a>,
1087<a href="http://it.wikipedia.org/wiki/Self-Monitoring%2C_Analysis_and_Reporting_Technology">Italiano</a>,
1088<a href="http://ja.wikipedia.org/wiki/Self-Monitoring%2C_Analysis_and_Reporting_Technology">Japanese</a>,
1089<a href="http://nl.wikipedia.org/wiki/S.M.A.R.T.">Nederlands</a>,
1090<a href="http://pl.wikipedia.org/wiki/S.M.A.R.T._%28informatyka%29">Polski</a>,
1091<a href="http://ru.wikipedia.org/wiki/%D0%A2%D0%B5%D1%85%D0%BD%D0%BE%D0%BB%D0%BE%D0%B3%D0%B8%D1%8F_SMART">Russian</a>,
1092<a href="http://sk.wikipedia.org/wiki/S.M.A.R.T">Sloven&#269;ina</a>
1093</li>
1094 <li>The <a href="http://www.t13.org/project/d1321r3-ATA-ATAPI-5.pdf"> ATAPI/ATA-5
1095Revision 3 specification</a> (start with Section 8.41)</li>
1096 <li>The <a href="http://www.t13.org/docs2002/d1410r3b.pdf"> ATAPI/ATA-6
1097Revision 3b specification</a></li>
1098 <li>The  ATAPI/ATA-7 specification (Draft 4b)
1099  <a href="http://www.t13.org/docs2004/d1532v1r4b-ATA-ATAPI-7.pdf">Volume 1 (has SMART documentation)</a>,
1100  <a href="http://www.t13.org/docs2004/d1532v2r4b-ATA-ATAPI-7.pdf">Volume 2</a>,
1101  <a href="http://www.t13.org/docs2004/d1532v3r4b-ATA-ATAPI-7.pdf">Volume 3</a></li>
1102 <li>The <a href="http://www.t13.org/docs2005/D1699r1f-ATA8-ACS.pdf">ATAPI/ATA-8 Command Set
1103specification (Draft 1f)</a></li>
1104 <li><a href="http://www.t13.org/#FTP_site">Other revisions
1105of the ATAPI/ATA Specs</a></li>
1106<li>SCSI References:
1107<ul>
1108 <li>The <a href="http://www.t10.org">homepage of the T10 project</a>.</li>
1109 <li>The <a href="ftp://ftp.t10.org/t10/drafts/s2/">SCSI-2 draft</a> by the T10 project.</li>
1110 <li>See also other subdirectories <a href="ftp://ftp.t10.org/t10/drafts/">here</a>.</li>
1111</ul>
1112</li>
1113<li>
1114  The original SMART specification is SFF-8035i from the <a href="http://www.sffcommittee.com/ns/">
1115  Small Form Factors (SFF) Committee</a>.&#160; 
1116  <ul>
1117    <li>
1118      Here is the SFF <a href="ftp://ftp.seagate.com/sff/INF-8035.TXT"> "link"</a>
1119     (they have "expired" the document).
1120    </li>
1121    <li>
1122      Version 1.0 of <a href="ftp://ftp3.ds.pg.gda.pl/people/macro/S.M.A.R.T./SFF-8035i.pdf">
1123      SFF-8035i "Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.)". </a>
1124    </li>
1125    <li>
1126      Revision 2.0 of <a href="ftp://ftp3.ds.pg.gda.pl/people/macro/S.M.A.R.T./8035R2_0.PDF">
1127      SFF-8035i "Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.)". </a>
1128    </li>
1129    <li>
1130      Revision 1.4 of <a href="ftp://ftp3.ds.pg.gda.pl/people/macro/S.M.A.R.T./8055.PDF">
1131      SFF-8055i "S.M.A.R.T. Applications Guide for the ATA and SCSI Interfaces" </a>
1132    </li>
1133  </ul>
1134</li>
1135<li>From the <a href="http://cmrr.ucsd.edu/smart/">UCSD SMART Project</a>:
1136<ul> 
1137 <li><a href="http://cmrr.ucsd.edu/smart/tech_papr/HamerlySmartPaper.pdf">Bayesian
1138Approaches to Failure Prediction for Disk Drives</a></li>
1139  <li><a href="http://cmrr.ucsd.edu/smart/tech_papr/SmtPapTransReliFinalWeb.pdf">Improved
1140Disk-Drive Failure Warnings</a></li>
1141 </ul>
1142 </li>
1143 <li>From the Seagate Corporation:
1144 <ul>
1145<!--  <li><a href="http://www.seagate.com/newsinfo/docs/disc/drive_reliability.pdf" target="_blank">
1146Estimating Drive Reliability in Desktop Computers and Consumer Electronics Systems</a></li> -->
1147  <li><a href="http://www.seagate.com/docs/pdf/whitepaper/enhanced_smart.pdf" target="_blank">Enhanced SMART - Get SMART For Reliability</a></li>
1148  <li><a href="http://www.seagate.com/docs/pdf/whitepaper/smart_u8.pdf" target="_blank">Playing it SMART</a></li>
1149  <li><a href="http://www.seagate.com/docs/pdf/whitepaper/Enhanced_DST_Tech_Paper.pdf" target="_blank">Enhanced Drive Self-Test</a></li>
1150 </ul>
1151 </li>
1152 <li><u>Specifying Reliability in the Disk Drive Industry: No More
1153MTBF's</u>, Jon G. Elerath (IBM Storage Systems Division) in
1154<i>Proceedings of the IEEE 2000 Annual Reliability and Maintainability
1155Symposium, pg 194, 0-7803-5848-1/00/$10.00.</i></li>
1156 <li><a href="http://smartlinux.sourceforge.net/smart/">Zbigniew Chlondowski's SMART Information Site.</a>
1157This includes a useful list of <a href="http://smartlinux.sourceforge.net/smart/attributes.php">Attributes
1158and their meanings.</a>
1159</li>
1160</ul>
1161
1162<hr size="2" /><a name="sampleoutput"></a><b>Example output
1163from smartmontools smartctl utility:</b>
1164
1165<ul>
1166 <li><a href="examples/MAXTOR-0.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM</li>
1167 <li><a href="examples/MAXTOR-1.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM (has failing SMART status - reallocated sector count)</li>
1168 <li><a href="examples/MAXTOR-2.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM (has had failing SMART test in the past.  Look at the Seek Error Rate)</li>
1169 <li><a href="examples/MAXTOR-7.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM (has failing SMART status, some failed self-tests)</li>
1170 <li><a href="examples/MAXTOR-8.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM (has failing SMART status - calibration retry count)</li>
1171 <li><a href="examples/MAXTOR-9.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM (has failing SMART status - calibration retry count)</li>
1172 <li><a href="examples/MAXTOR-10.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM (failing self-tests. Note Current_Pending_Sector raw value and Uncorrectable (UNC) read errors)</li>
1173 <li><a href="examples/MAXTOR-3.txt">MAXTOR 6L080J4</a> 80 GB 7200 RPM</li>
1174 <li><a href="examples/MAXTOR-4.txt">MAXTOR 6L080J4</a> 80 GB 7200 RPM</li>
1175 <li><a href="examples/Maxtor-5.txt">Maxtor 98196H8</a> 80 GB 5400 RPM</li>
1176 <li><a href="examples/MAXTOR-6.txt">Maxtor 4R080J0</a> Note: Attribute 9 (lifetime) stored in minutes!</li>
1177 <li><a href="examples/IC35L120AVVA07-0-0.txt">IBM IC35L120AVVA07 (GXP 120 series)</a> 120 GB 7200 RPM (note 3 temperatures)</li>
1178 <li><a href="examples/IC35L120AVVA07-0-1.txt">IBM IC35L120AVVA07 (GXP 120 series)</a> 120 GB 7200 RPM (note 3 temperatures)</li>
1179 <li><a href="examples/IC35L120AVV207-0.txt">IBM IC35L120AVV207 (GXP 180 series)</a> 120 GB 7200 RPM (note 3 temperatures)</li>
1180 <li><a href="examples/IC35L120AVV207-1.txt">IBM IC35L120AVV207 (GXP 180 series)</a> (failing SMART status and self-tests)</li>
1181 <li><a href="examples/HITACHI_DK23BA-20-0.txt">HITACHI_DK23BA-20</a> Hitachi 20 GB Laptop Disk</li>
1182 <li><a href="examples/HITACHI_DK23AA-12B.txt">HITACHI_DK23AA-12B</a> Really sick failing Hitachi Laptop Disk</li>
1183 <li><a href="examples/TOSHIBA-0.txt">TOSHIBA MK2018GAS</a> Toshiba 20 GB Laptop Disk</li>
1184 <li><a href="examples/TOSHIBA-MK6021GAS.txt">TOSHIBA MK6021GAS</a> Toshiba 60 GB Laptop Disk (note 3 temperatures)</li>
1185 <li><a href="examples/FUJITSU1.txt">Fujitsu MHR2040AT</a> Fujitsu Laptop Disk (has failing SMART status - write error count)</li>
1186 <li><a href="examples/FUJITSU_MHR2020AT.txt">Fujitsu MHR2020AT</a> Fujitsu Laptop Disk (has failing SMART status and self-tests)</li>
1187 <li><a href="examples/WD2500JB.txt">Western Digital WD2500JB</a> Western Digital Disk (failing SMART status and self-tests)</li>
1188</ul>
1189
1190<hr size="2" />
1191
1192Maintained by: <a href="mailto:smartmontools-support&#64;lists.sourceforge.net">Bruce Allen</a><br />
1193Copyright (C) 2002-5 Bruce Allen<br />
1194Last updated: <tt>$Date: 2006/05/19 16:50:36 $</tt><br />
1195CVS tag: <tt>$Id: index.html,v 1.199 2006/05/19 16:50:36 chrfranke Exp $</tt>
1196
1197<hr size="2" />
1198
1199<div align="center">Hosted by</div>
1200
1201<div align="center"><a href="http://sourceforge.net/"><img style="border:0;width=:88px;height:31px"
1202   src="http://sourceforge.net/sflogo.php?group_id=64297&amp;type=5" alt="SourceForge.net" /></a></div>
1203
1204<br />
1205
1206<div align="center"><a href="http://validator.w3.org/check/referer"><img style="border:0;width=:88px;height:31px"
1207   src="http://www.w3.org/Icons/valid-xhtml10.png" alt="Valid XHTML 1.0!" /></a></div>
1208
1209<br />
1210
1211<div align="center"><a href="http://validator.w3.org/check?uri=http%3A%2F%2Fsmartmontools.sourceforge.net">
1212Validate XHTML 1.0 Transitional.</a></div>
1213
1214<br />
1215
1216<div align="center"><a href="http://validator.w3.org/checklink?uri=http%3A%2F%2Fsmartmontools.sourceforge.net&amp;hide_type=all&amp;depth=&amp;check=Check">Check/Validate all links on this page.</a></div>
1217
1218</body>
1219</html>
Note: See TracBrowser for help on using the browser.