Changes between Version 1 and Version 2 of FAQ


Ignore:
Timestamp:
09/14/2009 10:27:11 AM (10 years ago)
Author:
Gabriele Pohl
Comment:

Transform HTML to Wiki-Syntax

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v1 v2  
    4949For example, in the message:[[BR]]
    5050{{{
    51  Device: /dev/hda, SMART Attribute: 194 Temperature_Celsius changed from 94 to 93
     51 Device: /dev/hda, SMART Attribute: 194
     52 Temperature_Celsius changed from 94 to 93
    5253}}}
    5354the value given is the ''Normalized'' not the ''Raw'' Attribute value (the
     
    5657the information is printed with the ''Raw'' values as well, for example:
    5758{{{
    58  Device: /dev/hda, SMART Attribute: 194 Temperature_Celsius changed from 94 [Raw 22] to 93 [Raw 23]
     59 Device: /dev/hda, SMART Attribute: 194
     60 Temperature_Celsius changed from 94 [Raw 22] to 93 [Raw 23]
    5961}}}
    6062Here the Raw values are the actual disk temperatures in Celsius.  The
     
    9092----
    9193
    92 
    93 == Configuration ==
    94 
    95 == Protocols, Devices and Controllers ==
    96 
    97 == Smartmontools Database ==
    98 
    99 == Selftests ==
    100 
    101 == Operating System ==
    102 
    103 == Firmware Issues ==
    104 
    105 == Distribution ==
    106 
    107 {{{
    108 #!html
    109 
    110 <!-- Selftests time stamp don't correspond to power-on time -->
    111 <h3><a name="time-stamps-WD"></a>The time stamps in the self-test log of my Western Digital (WD) disk
    112 don't correspond to the power-on time when the test was run.</h3>
    113 
    114 <p>
     94=== The time stamps in the self-test log don't correspond to the power-on time, when test was run on my Western Digital (WD) disk ===
     95
    11596The self-test log timestamps in many WD disks roll back to zero every
    116971092 hours (65536 minutes).  This problem is due to a WD firmware bug.
     
    118999. However when the power-on lifetime is calculated for self-test log
    119100entries, the lifetime in minutes is put into a 16-bit register then
    120 divided by 60.  The 16-bit register overflows and wraps around every
    121 1092 hours.</p>
    122 
    123 <p>For WD drives that exhibit this firmware bug, the relationship between
    124 Attribute 9's raw value (H) and the time-stamps in the self-test log (h) are given by:<br />
    125 Let H = power on hours as shown by Attribute 9 (correct)<br />
    126 Let M = 60*H (power on minutes, correct)<br />
    127 Let m = M mod 65536 (incorrect value of power on minutes)<br />
    128 Let h = m/60 (incorrect value of power on hours, shown in self-test log)</p>
    129 <hr />
    130 
    131 <!-- Normalized values larger than current values -->
    132 <h3><a name="worst-larger-than-current"></a>The (normalized) WORST Attribute values of my Western Digital
    133 (WD) disk are <strong>larger</strong> than the (normalized) CURRENT Attribute values</h3>
    134 <p>Western Digital firmware initializes SMART Attributes 10, 11, and
     101divided by 60.  The 16-bit register overflows and wraps around every 1092 hours.
     102
     103For WD drives that exhibit this firmware bug, the relationship between
     104Attribute 9's raw value (H) and the time-stamps in the self-test log (h) are given by:
     105{{{
     106 Let H = power on hours as shown by Attribute 9 (correct)
     107 Let M = 60*H (power on minutes, correct)
     108 Let m = M mod 65536 (incorrect value of power on minutes)
     109 Let h = m/60 (incorrect value of power on hours, shown in self-test log)
     110}}}
     111
     112----
     113
     114=== The (normalized) WORST Attribute values of my Western Digital (WD) disk are larger than the (normalized) CURRENT Attribute values ===
     115
     116Western Digital firmware initializes SMART Attributes 10, 11, and
    135117199 after either 120 spin-ups or 8 power-on hours.  Until that time,
    136 they have the uninitialized value 253.</p>
    137 <hr />
    138 
    139 <!-- Attributes not recognized -->
    140 <h3><a name="attributes-not-recognized"></a>What Attributes does smartmontools not yet recognize?</h3>
    141 <p>From Maxtor disks (99), (100), and (101).  These are not used by
     118they have the uninitialized value 253.
     119
     120----
     121
     122=== What Attributes does smartmontools not yet recognize? ===
     123From Maxtor disks (99), (100), and (101).  These are not used by
    142124Maxtor in SMART revision 5.  They will be used in SMART revision 6,
    143 but the engineering group has not yet decided what to monitor with these Attributes.</p>
    144 <hr />
     125but the engineering group has not yet decided what to monitor with these Attributes.
     126
     127----
     128
     129
     130== Configuration ==
     131
     132----
     133
     134=== My Fedora Core Linux system displays the startup message: 'smartd [FAILED]' ===
     135
     136Fedora Core is distributed with a {{{smartd}}} configuration file
     137{{{/etc/smartd.conf}}} that monitors the first IDE disk /dev/hda.  If this
     138device does not exist (or lacks SMART capability) you will get the
     139error message above.  Look in SYSLOG (/var/log/messages) for
     140additional details about what is going wrong.
     141
     142The solution: If your system has only SCSI disks, or has IDE disk(s)
     143on a non-primary controller, just edit {{{/etc/smartd.conf}}} to reflect the
     144correct location of the drive(s).  Please also read the {{{smartd.conf}}}
     145man page for additional information.
     146
     147----
     148
     149== Protocols, Devices and Controllers ==
     150
     151== Smartmontools Database ==
     152
     153== Selftests ==
     154
     155== Operating System ==
     156
     157== Firmware Issues ==
     158
     159== Distribution ==
     160
     161{{{
     162#!html
     163
     164
    145165
    146166<!-- Operating system requirements -->
     
    513533<hr />
    514534
    515 <h3><a name="fedora-failed"></a>My Fedora Core Linux system displays the startup message: smartd [FAILED]</h3>
    516 
    517 <p>Fedora Core is distributed with a <tt>smartd</tt> configuration file
    518 
    519 <tt>/etc/smartd.conf</tt> that monitors the first IDE disk /dev/hda.  If this
    520 device does not exist (or lacks SMART capability) you will get the
    521 error message above.  Look in SYSLOG (/var/log/messages) for
    522 additional details about what is going wrong.</p>
    523 
    524 <p>The solution: If your system has only SCSI disks, or has IDE disk(s)
    525 on a non-primary controller, just edit <tt>/etc/smartd.conf</tt> to reflect the
    526 correct location of the drive(s).  Please also read the <tt>smartd.conf</tt>
    527 man page for additional information.</p>
    528 <hr />
    529 
    530535<h3><a name="temp-seagate"></a>Attribute 194 (Temperature Celsius) behaves strangely on my Seagate disk</h3>
    531536