Changes between Version 1 and Version 2 of FAQ

Timestamp:

Sep 14, 2009, 12:27:11 PM (15 years ago)

Author:

Gabriele Pohl

Comment:

Transform HTML to Wiki-Syntax

FAQ

@@ -49 +49 @@
 For example, in the message:[[BR]]
 {{{
- Device: /dev/hda, SMART Attribute: 194 Temperature_Celsius changed from 94 to 93
+ Device: /dev/hda, SMART Attribute: 194 
+ Temperature_Celsius changed from 94 to 93
 }}}
 the value given is the ''Normalized'' not the ''Raw'' Attribute value (the
@@ -56 +57 @@
 the information is printed with the ''Raw'' values as well, for example:
 {{{
- Device: /dev/hda, SMART Attribute: 194 Temperature_Celsius changed from 94 [Raw 22] to 93 [Raw 23]
+ Device: /dev/hda, SMART Attribute: 194 
+ Temperature_Celsius changed from 94 [Raw 22] to 93 [Raw 23]
 }}}
 Here the Raw values are the actual disk temperatures in Celsius.  The
@@ -90 +92 @@
 ----
 
-
-== Configuration ==
-
-== Protocols, Devices and Controllers ==
-
-== Smartmontools Database ==
-
-== Selftests ==
-
-== Operating System ==
-
-== Firmware Issues ==
-
-== Distribution ==
-
-{{{
-#!html
-
-<!-- Selftests time stamp don't correspond to power-on time -->
-<h3><a name="time-stamps-WD"></a>The time stamps in the self-test log of my Western Digital (WD) disk
-don't correspond to the power-on time when the test was run.</h3>
-
-<p>
+=== 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 ===
+
 The self-test log timestamps in many WD disks roll back to zero every
 1092 hours (65536 minutes).  This problem is due to a WD firmware bug.
@@ -118 +99 @@
 9. However when the power-on lifetime is calculated for self-test log
 entries, the lifetime in minutes is put into a 16-bit register then
-divided by 60.  The 16-bit register overflows and wraps around every
-1092 hours.</p>
-
-<p>For WD drives that exhibit this firmware bug, the relationship between
-Attribute 9's raw value (H) and the time-stamps in the self-test log (h) are given by:<br />
-Let H = power on hours as shown by Attribute 9 (correct)<br />
-Let M = 60*H (power on minutes, correct)<br />
-Let m = M mod 65536 (incorrect value of power on minutes)<br />
-Let h = m/60 (incorrect value of power on hours, shown in self-test log)</p>
-<hr />
-
-<!-- Normalized values larger than current values -->
-<h3><a name="worst-larger-than-current"></a>The (normalized) WORST Attribute values of my Western Digital
-(WD) disk are <strong>larger</strong> than the (normalized) CURRENT Attribute values</h3>
-<p>Western Digital firmware initializes SMART Attributes 10, 11, and
+divided by 60.  The 16-bit register overflows and wraps around every 1092 hours.
+
+For WD drives that exhibit this firmware bug, the relationship between
+Attribute 9's raw value (H) and the time-stamps in the self-test log (h) are given by:
+{{{
+ Let H = power on hours as shown by Attribute 9 (correct)
+ Let M = 60*H (power on minutes, correct)
+ Let m = M mod 65536 (incorrect value of power on minutes)
+ Let h = m/60 (incorrect value of power on hours, shown in self-test log)
+}}}
+
+----
+
+=== The (normalized) WORST Attribute values of my Western Digital (WD) disk are larger than the (normalized) CURRENT Attribute values ===
+
+Western Digital firmware initializes SMART Attributes 10, 11, and
 199 after either 120 spin-ups or 8 power-on hours.  Until that time,
-they have the uninitialized value 253.</p>
-<hr />
-
-<!-- Attributes not recognized -->
-<h3><a name="attributes-not-recognized"></a>What Attributes does smartmontools not yet recognize?</h3>
-<p>From Maxtor disks (99), (100), and (101).  These are not used by
+they have the uninitialized value 253.
+
+----
+
+=== What Attributes does smartmontools not yet recognize? ===
+From Maxtor disks (99), (100), and (101).  These are not used by
 Maxtor in SMART revision 5.  They will be used in SMART revision 6,
-but the engineering group has not yet decided what to monitor with these Attributes.</p>
-<hr />
+but the engineering group has not yet decided what to monitor with these Attributes.
+
+----
+
+
+== Configuration ==
+
+----
+
+=== My Fedora Core Linux system displays the startup message: 'smartd [FAILED]' ===
+
+Fedora Core is distributed with a {{{smartd}}} configuration file
+{{{/etc/smartd.conf}}} that monitors the first IDE disk /dev/hda.  If this
+device does not exist (or lacks SMART capability) you will get the
+error message above.  Look in SYSLOG (/var/log/messages) for
+additional details about what is going wrong.
+
+The solution: If your system has only SCSI disks, or has IDE disk(s)
+on a non-primary controller, just edit {{{/etc/smartd.conf}}} to reflect the
+correct location of the drive(s).  Please also read the {{{smartd.conf}}}
+man page for additional information.
+
+----
+
+== Protocols, Devices and Controllers ==
+
+== Smartmontools Database ==
+
+== Selftests ==
+
+== Operating System ==
+
+== Firmware Issues ==
+
+== Distribution ==
+
+{{{
+#!html
+
+
 
 <!-- Operating system requirements -->
@@ -513 +533 @@
 <hr />
 
-<h3><a name="fedora-failed"></a>My Fedora Core Linux system displays the startup message: smartd [FAILED]</h3>
-
-<p>Fedora Core is distributed with a <tt>smartd</tt> configuration file
-
-<tt>/etc/smartd.conf</tt> that monitors the first IDE disk /dev/hda.  If this
-device does not exist (or lacks SMART capability) you will get the
-error message above.  Look in SYSLOG (/var/log/messages) for
-additional details about what is going wrong.</p>
-
-<p>The solution: If your system has only SCSI disks, or has IDE disk(s)
-on a non-primary controller, just edit <tt>/etc/smartd.conf</tt> to reflect the
-correct location of the drive(s).  Please also read the <tt>smartd.conf</tt>
-man page for additional information.</p>
-<hr />
-
 <h3><a name="temp-seagate"></a>Attribute 194 (Temperature Celsius) behaves strangely on my Seagate disk</h3>