diff --git a/CVSROOT/checkoutlist b/CVSROOT/checkoutlist
deleted file mode 100644
index b04b3501f5efd94313942eb7439457bc82f5a2f5..0000000000000000000000000000000000000000
--- a/CVSROOT/checkoutlist
+++ /dev/null
@@ -1,13 +0,0 @@
-# The "checkoutlist" file is used to support additional version controlled
-# administrative files in $CVSROOT/CVSROOT, such as template files.
-#
-# The first entry on a line is a filename which will be checked out from
-# the corresponding RCS file in the $CVSROOT/CVSROOT directory.
-# The remainder of the line is an error message to use if the file cannot
-# be checked out.
-#
-# File format:
-#
-#	[<whitespace>]<filename><whitespace><error message><end-of-line>
-#
-# comment lines begin with '#'
diff --git a/CVSROOT/commitinfo b/CVSROOT/commitinfo
deleted file mode 100644
index b19e7b7a63e8e90cdb49c43f02035646c4a76e0a..0000000000000000000000000000000000000000
--- a/CVSROOT/commitinfo
+++ /dev/null
@@ -1,15 +0,0 @@
-# The "commitinfo" file is used to control pre-commit checks.
-# The filter on the right is invoked with the repository and a list 
-# of files to check.  A non-zero exit of the filter program will 
-# cause the commit to be aborted.
-#
-# The first entry on a line is a regular expression which is tested
-# against the directory that the change is being committed to, relative
-# to the $CVSROOT.  For the first match that is found, then the remainder
-# of the line is the name of the filter to run.
-#
-# If the repository name does not match any of the regular expressions in this
-# file, the "DEFAULT" line is used, if it is specified.
-#
-# If the name "ALL" appears as a regular expression it is always used
-# in addition to the first matching regex or "DEFAULT".
diff --git a/CVSROOT/config b/CVSROOT/config
deleted file mode 100644
index ff43ec005ab332bc2aa7e1378754180e75a4b049..0000000000000000000000000000000000000000
--- a/CVSROOT/config
+++ /dev/null
@@ -1,14 +0,0 @@
-# Set this to "no" if pserver shouldn't check system users/passwords
-#SystemAuth=no
-
-# Put CVS lock files in this directory rather than directly in the repository.
-#LockDir=/var/lock/cvs
-
-# Set `TopLevelAdmin' to `yes' to create a CVS directory at the top
-# level of the new working directory when using the `cvs checkout'
-# command.
-#TopLevelAdmin=no
-
-# Set `LogHistory' to `all' or `TOFEWGCMAR' to log all transactions to the
-# history file, or a subset as needed (ie `TMAR' logs all write operations)
-#LogHistory=TOFEWGCMAR
diff --git a/CVSROOT/cvswrappers b/CVSROOT/cvswrappers
deleted file mode 100644
index 0accaf1b1532448d633d8a183cd8e3a5dd3b4a75..0000000000000000000000000000000000000000
--- a/CVSROOT/cvswrappers
+++ /dev/null
@@ -1,23 +0,0 @@
-# This file affects handling of files based on their names.
-#
-# The -t/-f options allow one to treat directories of files
-# as a single file, or to transform a file in other ways on
-# its way in and out of CVS.
-#
-# The -m option specifies whether CVS attempts to merge files.
-#
-# The -k option specifies keyword expansion (e.g. -kb for binary).
-#
-# Format of wrapper file ($CVSROOT/CVSROOT/cvswrappers or .cvswrappers)
-#
-#  wildcard	[option value][option value]...
-#
-#  where option is one of
-#  -f		from cvs filter		value: path to filter
-#  -t		to cvs filter		value: path to filter
-#  -m		update methodology	value: MERGE or COPY
-#  -k		expansion mode		value: b, o, kkv, &c
-#
-#  and value is a single-quote delimited value.
-# For example:
-#*.gif -k 'b'
diff --git a/CVSROOT/editinfo b/CVSROOT/editinfo
deleted file mode 100644
index d78886c1522b6eae3470c13da218c3d8e197cf71..0000000000000000000000000000000000000000
--- a/CVSROOT/editinfo
+++ /dev/null
@@ -1,21 +0,0 @@
-# The "editinfo" file is used to allow verification of logging
-# information.  It works best when a template (as specified in the
-# rcsinfo file) is provided for the logging procedure.  Given a
-# template with locations for, a bug-id number, a list of people who
-# reviewed the code before it can be checked in, and an external
-# process to catalog the differences that were code reviewed, the
-# following test can be applied to the code:
-#
-#   Making sure that the entered bug-id number is correct.
-#   Validating that the code that was reviewed is indeed the code being
-#       checked in (using the bug-id number or a seperate review
-#       number to identify this particular code set.).
-#
-# If any of the above test failed, then the commit would be aborted.
-#
-# Actions such as mailing a copy of the report to each reviewer are
-# better handled by an entry in the loginfo file.
-#
-# One thing that should be noted is the the ALL keyword is not
-# supported.  There can be only one entry that matches a given
-# repository.
diff --git a/CVSROOT/loginfo b/CVSROOT/loginfo
deleted file mode 100644
index 20957ed843e3834a67a2a71a54b202355d7a23a3..0000000000000000000000000000000000000000
--- a/CVSROOT/loginfo
+++ /dev/null
@@ -1,29 +0,0 @@
-# The "loginfo" file controls where "cvs commit" log information
-# is sent.  The first entry on a line is a regular expression which must match
-# the directory that the change is being made to, relative to the
-# $CVSROOT.  If a match is found, then the remainder of the line is a filter
-# program that should expect log information on its standard input.
-#
-# If the repository name does not match any of the regular expressions in this
-# file, the "DEFAULT" line is used, if it is specified.
-#
-# If the name ALL appears as a regular expression it is always used
-# in addition to the first matching regex or DEFAULT.
-#
-# You may specify a format string as part of the
-# filter.  The string is composed of a `%' followed
-# by a single format character, or followed by a set of format
-# characters surrounded by `{' and `}' as separators.  The format
-# characters are:
-#
-#   s = file name
-#   V = old version number (pre-checkin)
-#   v = new version number (post-checkin)
-#
-# For example:
-#DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog
-# or
-#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
-^sm5$ /cvsroot/sitedocs/CVSROOT/cvstools/syncmail -u %{sVv} smartmontools-cvs@lists.sourceforge.net
-^sm5/[_a-zA-Z0-9]*$ /cvsroot/sitedocs/CVSROOT/cvstools/syncmail -u %{sVv} smartmontools-cvs@lists.sourceforge.net
-^www$ /cvsroot/sitedocs/CVSROOT/cvstools/syncmail -u %{sVv} smartmontools-cvs@lists.sourceforge.net
diff --git a/CVSROOT/modules b/CVSROOT/modules
deleted file mode 100644
index cb9e9efc94b342879a5fff24b425473fc11edd01..0000000000000000000000000000000000000000
--- a/CVSROOT/modules
+++ /dev/null
@@ -1,26 +0,0 @@
-# Three different line formats are valid:
-#	key	-a    aliases...
-#	key [options] directory
-#	key [options] directory files...
-#
-# Where "options" are composed of:
-#	-i prog		Run "prog" on "cvs commit" from top-level of module.
-#	-o prog		Run "prog" on "cvs checkout" of module.
-#	-e prog		Run "prog" on "cvs export" of module.
-#	-t prog		Run "prog" on "cvs rtag" of module.
-#	-u prog		Run "prog" on "cvs update" of module.
-#	-d dir		Place module in directory "dir" instead of module name.
-#	-l		Top-level directory only -- do not recurse.
-#
-# NOTE:  If you change any of the "Run" options above, you'll have to
-# release and re-checkout any working directories of these modules.
-#
-# And "directory" is a path to a directory relative to $CVSROOT.
-#
-# The "-a" option specifies an alias.  An alias is interpreted as if
-# everything on the right of the "-a" had been typed on the command line.
-#
-# You can encode a module within a module by using the special '&'
-# character to interpose another module into the current module.  This
-# can be useful for creating a module that consists of many directories
-# spread out over the entire source repository.
diff --git a/CVSROOT/notify b/CVSROOT/notify
deleted file mode 100644
index 34f0bc288808e56e499d0852a9bfc9a3214b02d9..0000000000000000000000000000000000000000
--- a/CVSROOT/notify
+++ /dev/null
@@ -1,12 +0,0 @@
-# The "notify" file controls where notifications from watches set by
-# "cvs watch add" or "cvs edit" are sent.  The first entry on a line is
-# a regular expression which is tested against the directory that the
-# change is being made to, relative to the $CVSROOT.  If it matches,
-# then the remainder of the line is a filter program that should contain
-# one occurrence of %s for the user to notify, and information on its
-# standard input.
-#
-# "ALL" or "DEFAULT" can be used in place of the regular expression.
-#
-# For example:
-#ALL mail %s -s "CVS notification"
diff --git a/CVSROOT/rcsinfo b/CVSROOT/rcsinfo
deleted file mode 100644
index 49e59f4d0df9b432c5b99c0b806378a77c9cd870..0000000000000000000000000000000000000000
--- a/CVSROOT/rcsinfo
+++ /dev/null
@@ -1,13 +0,0 @@
-# The "rcsinfo" file is used to control templates with which the editor
-# is invoked on commit and import.
-#
-# The first entry on a line is a regular expression which is tested
-# against the directory that the change is being made to, relative to the
-# $CVSROOT.  For the first match that is found, then the remainder of the
-# line is the name of the file that contains the template.
-#
-# If the repository name does not match any of the regular expressions in this
-# file, the "DEFAULT" line is used, if it is specified.
-#
-# If the name "ALL" appears as a regular expression it is always used
-# in addition to the first matching regex or "DEFAULT".
diff --git a/CVSROOT/taginfo b/CVSROOT/taginfo
deleted file mode 100644
index 274a46dd5b61069f1cea62395178b09aa3120248..0000000000000000000000000000000000000000
--- a/CVSROOT/taginfo
+++ /dev/null
@@ -1,20 +0,0 @@
-# The "taginfo" file is used to control pre-tag checks.
-# The filter on the right is invoked with the following arguments:
-#
-# $1 -- tagname
-# $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d
-# $3 -- repository
-# $4->  file revision [file revision ...]
-#
-# A non-zero exit of the filter program will cause the tag to be aborted.
-#
-# The first entry on a line is a regular expression which is tested
-# against the directory that the change is being committed to, relative
-# to the $CVSROOT.  For the first match that is found, then the remainder
-# of the line is the name of the filter to run.
-#
-# If the repository name does not match any of the regular expressions in this
-# file, the "DEFAULT" line is used, if it is specified.
-#
-# If the name "ALL" appears as a regular expression it is always used
-# in addition to the first matching regex or "DEFAULT".
diff --git a/CVSROOT/verifymsg b/CVSROOT/verifymsg
deleted file mode 100644
index 86f747ce222390e6aa7a488074e372030d57a479..0000000000000000000000000000000000000000
--- a/CVSROOT/verifymsg
+++ /dev/null
@@ -1,21 +0,0 @@
-# The "verifymsg" file is used to allow verification of logging
-# information.  It works best when a template (as specified in the
-# rcsinfo file) is provided for the logging procedure.  Given a
-# template with locations for, a bug-id number, a list of people who
-# reviewed the code before it can be checked in, and an external
-# process to catalog the differences that were code reviewed, the
-# following test can be applied to the code:
-#
-#   Making sure that the entered bug-id number is correct.
-#   Validating that the code that was reviewed is indeed the code being
-#       checked in (using the bug-id number or a seperate review
-#       number to identify this particular code set.).
-#
-# If any of the above test failed, then the commit would be aborted.
-#
-# Actions such as mailing a copy of the report to each reviewer are
-# better handled by an entry in the loginfo file.
-#
-# One thing that should be noted is the the ALL keyword is not
-# supported.  There can be only one entry that matches a given
-# repository.
diff --git a/www/3w-xxxx.txt b/www/3w-xxxx.txt
deleted file mode 100644
index 5dde49c574c8ad84e69d89797ceeea17115f68e6..0000000000000000000000000000000000000000
--- a/www/3w-xxxx.txt
+++ /dev/null
@@ -1,157 +0,0 @@
----------------------------------------------------------------------------
-# November 27, 2003
-#
-# This patch is now against the official 3ware version 1.02.00.036 3w-xxxx.c driver
-# dated Wed Jul 16 20:30:28 2003. Instructions for use:
-# 
-# [1] download the 1.02.00.036 3w-xxxx.c driver from 
-#     http://www.3ware.com/support/download.asp
-#
-# [2] Unpack it:
-#       tar zxvf rh7x_8x.tgz (or su7x_8x.tgz for SuSE)
-#
-# [3] Unpack the source code, and move to the right directory:
-#       cd src/2.4
-#       tar zxvf 3w-xxxx.tgz
-#       cd driver
-#
-# [4] Copy THIS FILE (what you are reading!) into that
-#     directory and name it 3w-xxxx.txt
-#
-# [5] Patch the driver:
-#       patch < 3w-xxxx.txt
-#     You should get the response 'patching file 3w-xxxx.c'.
-#
-# [6] Build the driver with the command:
-#       make
-#     This will create the driver: a file named 3w-xxxx.o
-#
-# [7] Load the driver (you must be root to do this):
-#       /sbin/insmod ./3w-xxxx.o
-#     [Note: if '/sbin/lsmod' shows that the driver is loaded already,
-#     then unmount any file systems that use it, then unload the driver
-#     with '/sbin/rmmod 3w-xxxx' first!]
-#
-# [8] Copy the driver into place in the kernel tree:
-#       cp ./3w-xxxx.o /lib/modules/`uname -r`/kernel/drivers/scsi
-#     That's it!
-#
-# August 14, 2003
-#
-# Adam Radford has incorporated a change that now allows the 3w-xxxx
-# driver to return the Cylinder Low/High values.  These are needed to
-# get the SMART health status.  This patch incorporates those changes
-# as well.
-#
-# August 12, 2003
-#
-# 3ware has incorporated a more general version of this fix into their latest
-# 3w-xxxx driver release. Rather than using this patch, you can upgrade your 
-# 3w-xxxx driver to version 1.02.00.037 or greater.  Or you can use this patch.
-#
-# August 8, 2003
-# PATCH FOR 3WARE 3w-xxxx DRIVER
-# Bruce Allen ballen at gravity.phys.uwm.edu
-# CVS ID of this file: $Id: 3w-xxxx.txt,v 1.5 2003/11/28 17:58:50 ballen4705 Exp $
-# 
-# To apply this patch, save this entire file to 3w-xxxx.txt in a
-# directory containing the original unpatched 3w-xxxx.c file. Then
-# given the command:
-#                     patch < 3w-xxxx.txt
-# That's it!
-#
-# TECHNICAL EXPLANATION OF THE PATCH FOLLOWS.  SKIP IT IF YOU DON'T CARE.
-#
-# The 3w-xxxx SCSI RAID driver for 3ware Escalade controller cards has a bug
-# in the "passthru" ioctl() which prevents two SMART commands from being
-# passed to the ATA devices behind the controller. The commands are:
-# 
-#  SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE 
-#  (Command Register=0xB0/Feature Register=0xD2)
-# 
-#  SMART ENABLE/DISABLE AUTOMATIC OFF-LINE
-#  (Command Register=0xB0/Feature Register=0xDB)
-# 
-# [Note: the second of these commands is listed as "Obsolete" in the ATA
-# specifications.  It was originally defined in SFF-8035i.  Most vendors
-# (IBM/Hitachi, Maxtor, Samsung, WD, among others) still implement it for
-# backwards compatibility.]
-# 
-# The problem arises because in both cases (stupidly!) the ENABLE subcommand
-# is indicated with a nonzero value of the Sector Count Register.  For the
-# AUTOSAVE command one uses Sector Count Register=0xF1 and for the AUTOMATIC
-# OFF-LINE command one uses Sector Count Register=0xF8.
-# 
-# This provokes the following error messages from the 3w-xxxx driver:
-#   3w-xxxx: tw_ioctl(): Passthru size (123392) too big.
-#   3w-xxxx: tw_ioctl(): Passthru size (126976) too big.
-# and the driver doesn't pass the ATA command on.  This is because the
-# passthru part of the 3w-xxxx driver assumes that the value in the Sector
-# Count Register is the number of 512-byte blocks to transfer, and these
-# values exceed the internal buffer sizes.
-# 
-# In fact both of these are non-data commands, and so this is trivial to
-# fix.  I am attaching an 8-line patch for this purpose.  It looks for these
-# particular commands and then treats them as non-data commands. It has been
-# tested on both a 6800 and a 7500 controller, and should be endian-order
-# and 32/64-bit clean.
-# 
-# [Note: the normal linux ide drivers also assume that the Sector Count
-# Register is the number of 512-byte sectors to transfer to user space.  
-# But in that case the user can simply allocate a userland buffer large
-# enough to hold the 0xf1*0x200 or 0xf8*0x200 bytes, and then ignore the
-# contents.]
-#
-# -----------------------------------------------------------------------
-
---- 3w-xxxx.c.orig	Wed Jul 16 20:30:28 2003
-+++ 3w-xxxx.c	Thu Nov 27 11:20:25 2003
-@@ -173,6 +173,9 @@
-    1.02.00.035 - Improve tw_allocate_memory() memory allocation.
-                  Fix tw_chrdev_ioctl() to sleep correctly.
-    1.02.00.036 - Increase character ioctl timeout to 60 seconds.
-+   
-+   This version 1.02.00.036 3w-xxxx.c driver has been patched for full smartmontools support.
-+   
- */
- 
- #include <linux/module.h>
-@@ -1930,12 +1933,15 @@
- 			}
- 
- 			passthru = (TW_Passthru *)tw_dev->command_packet_virtual_address[request_id];
--			passthru->sg_list[0].length = passthru->sector_count*512;
--			if (passthru->sg_list[0].length > TW_MAX_PASSTHRU_BYTES) {
--				printk(KERN_WARNING "3w-xxxx: tw_ioctl(): Passthru size (%d) too big.\n", passthru->sg_list[0].length);
--				return 1;
-+			/* Don't load sg_list for non-data ATA cmds */
-+			if ((passthru->param != 0) && (passthru->param != 0x8)) {
-+				passthru->sg_list[0].length = passthru->sector_count*512;
-+				if (passthru->sg_list[0].length > TW_MAX_PASSTHRU_BYTES) {
-+					printk(KERN_WARNING "3w-xxxx: tw_ioctl(): Passthru size (%d) too big.\n", passthru->sg_list[0].length);
-+					return 1;
-+				}
-+				passthru->sg_list[0].address = tw_dev->alignment_physical_address[request_id];
- 			}
--			passthru->sg_list[0].address = tw_dev->alignment_physical_address[request_id];
- 			tw_post_command_packet(tw_dev, request_id);
- 			return 0;
- 		case TW_CMD_PACKET:
-@@ -2185,8 +2191,15 @@
- 	ioctl = (TW_Ioctl *)buff;
- 	switch (ioctl->opcode) {
- 		case TW_ATA_PASSTHRU:
--			passthru = (TW_Passthru *)ioctl->data;
--			memcpy(buff, tw_dev->alignment_virtual_address[request_id], passthru->sector_count * 512);
-+		        passthru = (TW_Passthru *)ioctl->data;
-+			/* Don't return data for non-data ATA cmds */
-+			if ((passthru->param != 0) && (passthru->param != 0x8))
-+				memcpy(buff, tw_dev->alignment_virtual_address[request_id], passthru->sector_count * 512);
-+			else {
-+			/* For non-data cmds, return cmd pkt */
-+				if (tw_dev->srb[request_id]->request_bufflen >= sizeof(TW_Command))
-+					memcpy(buff, tw_dev->command_packet_virtual_address[request_id], sizeof(TW_Command));
-+			}
- 			break;
- 		case TW_CMD_PACKET_WITH_DATA:
- 			dprintk(KERN_WARNING "3w-xxxx: tw_ioctl_complete(): caught TW_CMD_PACKET_WITH_DATA.\n");
diff --git a/www/BadBlockHowTo.txt b/www/BadBlockHowTo.txt
deleted file mode 100644
index f59086d1d80605a3d6575a25f0b1bc4a2566f4ed..0000000000000000000000000000000000000000
--- a/www/BadBlockHowTo.txt
+++ /dev/null
@@ -1,505 +0,0 @@
-THIS DOCUMENT SHOWS HOW TO IDENTIFY THE FILE ASSOCIATED WITH AN
-UNREADABLE DISK SECTOR, AND HOW TO FORCE THAT SECTOR TO REALLOCATE.
-
-Assumptions: Linux OS, ext2 or ext3 file system.
-
-Bruce Allen <smartmontools-support@lists.sourceforge.net>
-
-Thanks to Sergey Vlasov, Theodore Ts'o, Michael Bendzick, and others
-for explaining this to me. I would like to add text showing how to do
-this for other file systems, in particular ReiserFS, XFS, and JFS:
-please email me if you can provide this information.
-
-NOTE: Starting with GNU coreutils release 5.3.0, dd on Linux includes
-options 'iflag=direct' and 'oflag=direct'.  Using these with the dd commands
-below should be helpful, because adding these flags should avoid any interaction
-with the block buffering IO layer in Linux and permit direct reads/writes
-from the raw device.  Use 'dd --help' to see if your version of dd supports
-these options. If not, build the latest code from
-fttp://alpha.gnu.org/gnu/coreutils.
-
-In this example, the disk is failing self-tests at Logical Block
-Address LBA = 0x016561e9 = 23421417.  The LBA counts sectors in units
-of 512 bytes, and starts at zero.
-
------------------------------------------------------------------------------------------------
-root]# smartctl -l selftest /dev/hda:
-
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed: read failure       90%       217         0x016561e9
------------------------------------------------------------------------------------------------
-
-Note that other signs that there is a bad sector on the disk can be
-found in the non-zero value of the Current Pending Sector count:
------------------------------------------------------------------------------------------------
-root]# smartctl -A /dev/hda
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       1
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       1
------------------------------------------------------------------------------------------------
-
-First Step: We need to locate the partition on which this sector of
-the disk lives:
------------------------------------------------------------------------------------------------
-root]# fdisk -lu /dev/hda
-
-Disk /dev/hda: 123.5 GB, 123522416640 bytes
-255 heads, 63 sectors/track, 15017 cylinders, total 241254720 sectors
-Units = sectors of 1 * 512 = 512 bytes
-
-   Device Boot    Start       End    Blocks   Id  System
-/dev/hda1   *        63   4209029   2104483+  83  Linux
-/dev/hda2       4209030   5269319    530145   82  Linux swap
-/dev/hda3       5269320 238227884 116479282+  83  Linux
-/dev/hda4     238227885 241248104   1510110   83  Linux
------------------------------------------------------------------------------------------------
-
-The partition /dev/hda3 starts at LBA 5269320 and extends past the
-'problem' LBA.  The 'problem' LBA is offset 23421417 - 5269320 =
-18152097 sectors into the partition /dev/hda3.
-
-To verify the type of the file system and the mount point, look in
-/etc/fstab:
------------------------------------------------------------------------------------------------
-root]# grep hda3 /etc/fstab
-/dev/hda3 /data ext2 defaults 1 2
------------------------------------------------------------------------------------------------
-You can see that this is an ext2 file system, mounted at /data.
-
-Second Step: we need to find the blocksize of the file system
-(normally 4096 bytes for ext2):
------------------------------------------------------------------------------------------------
-root]# tune2fs -l /dev/hda3 | grep Block
-Block count:              29119820
-Block size:               4096
------------------------------------------------------------------------------------------------
-In this case the block size is 4096 bytes.
-
-Third Step: we need to determine which File System Block contains this
-LBA.  The formula is:
-  b = (int)((L-S)*512/B)
-where:
-b = File System block number
-B = File system block size in bytes
-L = LBA of bad sector
-S = Starting sector of partition as shown by fdisk -lu
-and (int) denotes the integer part.
-
-In our example, L=23421417, S=5269320, and B=4096.  Hence the
-'problem' LBA is in block number
-   b = (int)18152097*512/4096 = (int)2269012.125
-so b=2269012.
-
-Note: the fractional part of 0.125 indicates that this problem LBA is
-actually the second of the eight sectors that make up this file system
-block.
-
-Fourth Step: we use debugfs to locate the inode stored in this block,
-and the file that contains that inode:
------------------------------------------------------------------------------------------------
-root]# debugfs
-debugfs 1.32 (09-Nov-2002)
-debugfs:  open /dev/hda3
-debugfs:  icheck 2269012
-Block	Inode number
-2269012	41032
-debugfs:  ncheck 41032
-Inode	Pathname
-41032	/S1/R/H/714197568-714203359/H-R-714202192-16.gwf
------------------------------------------------------------------------------------------------
-
-In this example, you can see that the problematic file (with the mount
-point included in the path) is:
-/data/S1/R/H/714197568-714203359/H-R-714202192-16.gwf
-
-
-To force the disk to reallocate this bad block we'll write zeros to
-the bad block, and sync the disk:
------------------------------------------------------------------------------------------------
-root]# dd if=/dev/zero of=/dev/hda3 bs=4096 count=1 seek=2269012
-root]# sync
------------------------------------------------------------------------------------------------
-
-NOTE: THIS LAST STEP HAS PERMANENTLY AND IRRETREVIABLY DESTROYED SOME
-OF THE DATA THAT WAS IN THIS FILE.  DON'T DO THIS UNLESS YOU DON'T
-NEED THE FILE OR YOU CAN REPLACE IT WITH A FRESH OR CORRECT VERSION.
-
-
-Now everything is back to normal: the sector has been reallocated.
-Compare the output just below to similar output near the top of this
-article:
------------------------------------------------------------------------------------------------
-root]# smartctl -A /dev/hda
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       1
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       1
------------------------------------------------------------------------------------------------
-
-Note: for some disks it may be necessary to update the SMART Attribute values by using
-smartctl -t offline /dev/hda
-
-The disk now passes its self-tests again:
-
------------------------------------------------------------------------------------------------
-root]# smartctl -t long /dev/hda  [wait until test completes, then]
-root]# smartctl -l selftest /dev/hda
-
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed without error       00%       239         -
-# 2  Extended offline    Completed: read failure       90%       217         0x016561e9
-# 3  Extended offline    Completed: read failure       90%       212         0x016561e9
-# 4  Extended offline    Completed: read failure       90%       181         0x016561e9
-# 5  Extended offline    Completed without error       00%        14         -
-# 6  Extended offline    Completed without error       00%         4         -
------------------------------------------------------------------------------------------------
-
-and no longer shows any offline uncorrectable sectors:
-
------------------------------------------------------------------------------------------------
-root]# smartctl -A /dev/hda
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       1
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
------------------------------------------------------------------------------------------------
-
-
-
-A SECOND EXAMPLE
-
-On this drive, the first sign of trouble was this email from smartd:
-
-    To: ballen
-    Subject: SMART error (selftest) detected on host: medusa-slave166.medusa.phys.uwm.edu
-
-    This email was generated by the smartd daemon running on host:
-    medusa-slave166.medusa.phys.uwm.edu in the domain: master001-nis
-
-    The following warning/error was logged by the smartd daemon:
-    Device: /dev/hda, Self-Test Log error count increased from 0 to 1
-
-    
-Running smartctl -a /dev/hda confirmed the problem:
-    
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed: read failure       80%       682         0x021d9f44
-
-Note that the failing LBA reported is 0x021d9f44 (base 16) = 35495748 (base 10)
-    
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       3
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       3
-
-and one can see above that there are 3 sectors on the list of pending
-sectors that the disk can't read but would like to reallocate.
-
-The device also shows errors in the SMART error log:
-
-Error 212 occurred at disk power-on lifetime: 690 hours
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 12 46 9f 1d e2  Error: UNC 18 sectors at LBA = 0x021d9f46 = 35495750
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  25 00 12 46 9f 1d e0 00 2485545.000  READ DMA EXT
-
-Signs of trouble at this LBA may also be found in SYSLOG:
-
-[root]# grep LBA /var/log/messages | awk '{print $12}' | sort | uniq
- LBAsect=35495748
- LBAsect=35495750
-
-So I decide to do a quick check to see how many bad sectors there
-really are. Using the bash shell I check 70 sectors around the trouble
-area:
-    
-[root]# export i=35495730
-[root]# while [ $i -lt 35495800 ]
-        > do echo $i
-        > dd if=/dev/hda of=/dev/null bs=512 count=1 skip=$i
-        > let i+=1
-        > done
- 
-<SNIP>   
-
-35495734
-1+0 records in
-1+0 records out
-35495735
-dd: reading `/dev/hda': Input/output error
-0+0 records in
-0+0 records out
-
-<SNIP>
-
-35495751
-dd: reading `/dev/hda': Input/output error
-0+0 records in
-0+0 records out
-35495752
-1+0 records in
-1+0 records out
-
-<SNIP>
-
-which shows that the seventeen sectors 35495735-35495751 (inclusive)
-are not readable.
-
-Next, we identify the files at those locations.  The partitioning
-information on this disk is identical to the first example above, and
-as in that case the problem sectors are on the third partition
-/dev/hda3.  So we have:
-     L=35495735 to 35495751
-     S=5269320
-     B=4096
-so that b=3778301 to 3778303 are the three bad blocks in the file
-system.
-
-[root]# debugfs
-debugfs 1.32 (09-Nov-2002)
-debugfs:  open /dev/hda3
-debugfs:  icheck 3778301
-Block   Inode number
-3778301 45192
-debugfs:  icheck 3778302
-Block   Inode number
-3778302 45192
-debugfs:  icheck 3778303
-Block   Inode number
-3778303 45192
-debugfs:  ncheck 45192
-Inode   Pathname
-45192   /S1/R/H/714979488-714985279/H-R-714979984-16.gwf
-debugfs:  quit
-
-And finally, just to confirm that this is really the damaged file:
-
-[root]# md5sum /data/S1/R/H/714979488-714985279/H-R-714979984-16.gwf
-md5sum: /data/S1/R/H/714979488-714985279/H-R-714979984-16.gwf: Input/output error
-
-Finally we force the disk to reallocate the three bad blocks:
-[root]# dd if=/dev/zero of=/dev/hda3 bs=4096 count=3 seek=3778301
-[root]# sync
-
-We could also probably use:
-[root]# dd if=/dev/zero of=/dev/hda bs=512 count=17 seek=35495735
-
-At this point we now have:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
-
-which is encouraging, since the pending sectors count is now zero.
-Note that the drive reallocation count has not yet increased: the
-drive may now have confidence in these sectors and have decided not to
-reallocate them..
-
-A device self test: 
-  [root#] smartctl -t long /dev/hda
-(then wait about an hour) shows no unreadable sectors or errors:
-
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed without error       00%       692         -
-# 2  Extended offline    Completed: read failure       80%       682         0x021d9f44
-
-[USEFUL HINTS ADDED BY OTHERS]
-
----------------------------------------------------------------------------
-
-From: Kay Diederichs
-                                                                                                                              
-I read your badblocks-howto at
-http://smartmontools.sourceforge.net/BadBlockHowTo.txt and greatly
-benefitted from it. One thing that's (maybe) missing is that often the
-"smartctl -t long" scan finds a bad sector which is _not_ assigned to
-any file. In that case it does not help to run debugfs, or rather
-debugfs reports the fact that no file owns that sector. Furthermore,
-it is somewhat laborious to come up with the correct numbers for
-debugfs, and debugfs is slow ...
-                                                                                                                              
-So what I suggest in the case of presence of
-Current_Pending_Sector/Offline_Uncorrectable errors is to create a
-huge file on that filesystem.
-  dd if=/dev/zero of=/some/mount/point bs=4k
-creates the file. Leave it running until the partition/filesystem is
-full. This will make the disk reallocate those sectors which do not
-belong to a file. Check the "smartctl -a" output after that and make
-sure that the sectors are reallocated. If any remain, use the debugfs
-method.  Of course the usual caveats apply - back it up first, and so
-on.
-                                                                                                                              
----------------------------------------------------------------------------
-
-From: Frederic BOITEUX
-
-HOW TO LOCATE AND REPAIR BAD BLOCKS ON AN LVM VOLUME
-
-* Smartd reports an error in a short test�:
--------------------------------------------
-
-# smartctl -a /dev/hdb
-...
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Short offline       Completed: read failure       90%        66         37383668
-
-So the disk has a bad block located in LBA block 37383668
-
-
-* In which physical partition is the bad block�?
-------------------------------------------------
-
-# sfdisk -lu /dev/hdb
-
-Disk /dev/hdb: 9729 cylinders, 255 heads, 63 sectors/track
-Units = sectors of 512 bytes, counting from 0
-
-   Device Boot    Start       End   #sectors  Id  System
-/dev/hdb1            63    996029     995967  82  Linux swap / Solaris
-/dev/hdb2   *    996030   1188809     192780  83  Linux
-/dev/hdb3       1188810 156296384  155107575  8e  Linux LVM
-/dev/hdb4             0         -          0   0  Empty
-
-It's in the /dev/hdb3 partition, a LVM2 partition.
-From the LVM2 partition beginning, the bad block has an offset of
-(37383668 - 1188810) = 36194858
-
-We have to find in which LVM2 logical partition the block belongs to.
-
-
-* In which logical partition is the bad block�?
------------------------------------------------
-
-*IMPORTANT*�: LVM2 can use different schemes dividing its physical
- partitions to logical ones�: linear, striped, contiguous or
- not... The following example assumes that allocation is linear�!
-
-
-The physical partition used by LVM2 is divided in PE (Physical Extent)
-units of the same size, starting at pe_start' 512 bytes blocks from
-the beginning of the physical partition.
-
-The 'pvdisplay' command gives the size of the PE (in KB) of the
-LVM partition�:
-#  part=/dev/hdb3�; pvdisplay -c $part | awk -F: '{print $8}'
-4096
-
-To get its size in LBA block size (512 bytes or 0.5 KB), we multiply this
-number by 2�: 4096 * 2 = 8192 blocks for each PE.
-
-
-To find the offset from the beginning of the physical partition is a
-bit more difficult�: if you have a recent LVM2 version, try�:
-# pvs -o+pe_start $part
-
-Either, you can look in /etc/lvm/backup�:
-# grep pe_start $(grep -l $part /etc/lvm/backup/*)
-                        pe_start = 384
-
-
-Then, we search in which PE is the badblock, calculating the PE rank
-in which the faulty block of the partition is�:
-physical partition's bad block number / sizeof(PE) =
-36194858 / 8192 = 4418.3176
-
-So we have to find in which LVM2 logical partition is used the PE
-number 4418 (count starts from 0)�:
-# lvdisplay --maps |egrep 'Physical|LV Name|Type'
-  LV Name                /dev/WDC80Go/racine
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    0 to 127
-  LV Name                /dev/WDC80Go/usr
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    128 to 1407
-  LV Name                /dev/WDC80Go/var
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    1408 to 1663
-  LV Name                /dev/WDC80Go/tmp
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    1664 to 1791
-  LV Name                /dev/WDC80Go/home
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    1792 to 3071
-  LV Name                /dev/WDC80Go/ext1
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    3072 to 10751
-  LV Name                /dev/WDC80Go/ext2
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    10752 to 18932
-
-So the PE #4418 is in the /dev/WDC80Go/ext1 LVM logical partition.
-
-
-* Size of logical block of filesystem on /dev/WDC80Go/ext1�:
-------------------------------------------------------------
-
-It's a ext3 fs, so I get it like this�:
-# dumpe2fs /dev/WDC80Go/ext1 | grep 'Block size'
-dumpe2fs 1.37 (21-Mar-2005)
-Block size:               4096
-
-
-* bad block number for the filesystem�:
----------------------------------------
-
-The logical partition begins on PE 3072�:
- (# PE's start of partition * sizeof(PE)) + parttion offset[pe_start] =
- (3072 * 8192) + 384 = 25166208
-512b block of the physical partition, so the bad block number for the
-filesystem� is�:
-(36194858 - 25166208) / (sizeof(fs block) / 512)
-= 11028650 / (4096 / 512)  = 1378581.25
-
-
-* Test of the fs bad block�:
-
-dd if=/dev/WDC80Go/ext1 of=block1378581 bs=4096 count=1 skip=1378581
-
-If this dd command succeeds, without any error message in console or
-syslog, then the block number calculation is probably wrong�! *Don't*
-go further, re-check it and if you don't find the error, please
-renunce�!
-
-
-* Search / correction follows the same scheme as for simple
-  partitions�:
-
-- find possible impacted files with debugfs (icheck <fs block nb>,
-  then ncheck <icheck nb>).
-
-- reallocate bad block writing zeros in it, *using the fs block size*�:
-
-dd if=/dev/zero of=/dev/WDC80Go/ext1 count=1 bs=4096 seek=1378581
-
-Et voil�!
-
----------------------------------------------------------------------------
-
-
-
-
-This document is version $Id: BadBlockHowTo.txt,v 1.9 2006/06/12 02:16:50 ballen4705 Exp $
-It is Copyright Bruce Allen (2004-6) and distributed under GPL2.
-
-
diff --git a/www/BadBlockSCSIHowTo.txt b/www/BadBlockSCSIHowTo.txt
deleted file mode 100644
index a146d0e689912de6e007026b16b6df87456626cf..0000000000000000000000000000000000000000
--- a/www/BadBlockSCSIHowTo.txt
+++ /dev/null
@@ -1,169 +0,0 @@
-Introduction
-============
-This document supplies some extra information, mainly associated with
-SCSI disks, to the http://smartmontools.sourceforge.net/BadBlockHowTo.txt
-document which concentrates on ATA disks and recovery at the file
-system level.
-
-As the name of the link suggests, the BadBlockHowTo.txt discusses what
-can be done when smartmontools reports a bad block. The approach
-taken is to use the facilities within the ext2 and ext3 file systems
-in Linux to remap around the damaged section of the disk. While this
-approach will work with SCSI disks as well, it does have some
-disadvantages.
-
-SCSI disks have their own logical to physical mapping allowing
-a damaged sector (usually 512 bytes long) to be remapped irrespective
-of the operating system, file system or software RAID being used.
-Also if the disk has been "ejected" from a RAID, after repairing
-its bad block(s) (or simply reformatting it) the disk could be
-used in other roles.
-
-Details
-=======
-The terms "block" and "sector" are used interchangeably, although
-"block" tends to get used in higher level or more abstract contexts
-such as a "logical block".
-
-When a SCSI disk is formatted, defective sectors identified during
-the manufacturing process (the so called "primary" list: PLIST),
-those found during the format itself (the "certification" list: CLIST),
-those given explicitly to the format command (the DLIST) and optionally
-the previous "grown" list (GLIST) are not used in the logical block
-map. The number (and low level addresses) of the unmapped sectors can be
-found with the READ DEFECT DATA SCSI command.
-
-SCSI disks tend to be divided into zones which have spare sectors and
-perhaps spare tracks, to support the logical block address mapping
-process. The idea is that if a logical block is remapped, the heads do not
-have to move a long way to access the replacement sector. Note that spare
-sectors are a scarce resource.
-
-Once a SCSI disk format has completed successfully, other problems
-may appear over time. These fall into two categories:
-  - recoverable: the Error Correction Codes (ECC) detect a problem
-    but it is "small" enough to be corrected. Optionally other
-    strategies such as retrying the access may retriev the data.
-  - unrecoverable: try as it may, the disk logic and ECC algorithms
-    cannot recover the data. This is often reported as a "medium
-    error".
-Other things can go wrong, typically associated with the transport and
-they will be reported using a term other than "medium error". For example
-a disk may decide a read operation was successful but a computer's host
-bus adapter (HBA) checking the incoming data detects a CRC error due to
-a bad cable or termination.
-
-Depending on the disk vendor, recoverable errors can be ignored. After all,
-some disks have up to 68 bytes of ECC above the payload size of 512 bytes
-so why use up spare sectors which are limited in number (see note A below)?
-If the disk does decide to re-allocate (reassign) a sector, then whether it
-tries or reports an error immediately depends on the settings of the ARRE
-and AWRE bits in the read-write error recovery mode page. Usually these bits
-are set enabling automatic (read or write) re-allocation. [It is possible
-that disks inside a hardware RAID have those bits cleared (disabled) and the
-RAID controller does things manually or flags the disk for replacement.]
-The automatic re-allocation may also fail if the zone (or disk) has run out
-of spare sectors.
-
-Another point about RAIDs, and applications that require a high data rate,
-is that the controller logic may not want a disk to spend too long trying
-to recover an error.
-
-Unrecoverable errors will cause a "medium error" sense key, perhaps with
-some useful additional sense information. If the extended background self
-test includes a full disk read scan, one would expect the self test log to
-list the bad block, as shown in the BadBlockHowTo.txt document. Recent SCSI
-disks with a periodic background scan should also list unrecoverable read
-errors (and  recoverable errors as well). The advantage of the background
-scan is that it runs to completion while self tests will often terminate at
-the first serious error.
-
-SCSI disks expect unrecoverable errors to be fixed manually using the
-REASSIGN SCSI command since loss of data is involved. It is possible that an
-operating system or a file system could issue the REASSIGN SCSI command
-itself but the author is unaware of any examples. The REASSIGN SCSI command
-will reassign one or more blocks, attempting to (partially ?) recover the
-data (a forlorn hope at this stage), fetch an unused spare sector from the
-current zone while adding the damaged old sector to the GLIST (hence the
-name "grown" list). The contents of the GLIST may not be that interesting
-but smartctl prints out the number of entries in the grown list and if that
-number grows quickly, the disk may be approaching the end of its useful life.
-
-Here is an alternate brute force technique to consider: if the data on the
-SCSI or ATA disk has all been backed up (e.g. is held on the other disks in
-a RAID 5 enclosure), then simply reformatting the disk may be the least
-fiddly approach.
-
-What to do
-==========
-Given a "bad block", it still may be useful to look at fdisk (if the disk
-has multiple partitions) to find out which partition is involved, then use
-debugfs (or a similar tool for the file system in question) to find out
-which, if any, file or other part of the file system may have been damaged.
-This is discussed in the BadBlockHowTo.txt document.
-
-Then a program that can execute the REASSIGN SCSI command is required. In
-Linux (2.4 and 2.6 series), FreeBSD and Tru64 (osf) the author's sg_reassign
-in the sg3_utils package can be used. Also found in that package is
-sg_verify which can be used to check that a block is readable.
-
-Assuming logical block address 0x123456 has been reported by smartmontools
-as bad block, then:
-  # sg_verify --lba=0x123456 /dev/sda
-
-should also report a problem. To check the number of elements in the
-GLIST before the block reassignment, try:
-  # sg_reassign --grown /dev/sda
-
-To actually reassign that address try:
-  # sg_reassign --address=0x123456 /dev/sda
-
-If that succeeded then checking the GLIST length again should indicate
-that it has grown by one element. If the disk was unable to recover
-any data, then the "new" block at lba 0x123456 has vendor specific
-data in it. The sg_reassign utility can also do bulk reassigns, see
-'man sg_reassign' for more information.
-
-The dd command could be used to read the contents of the "new" block:
-  # dd if=/dev/sda iflag=direct skip=0x123456 of=blk.img bs=512 count=1
-
-and a hex editor used to view and potentially change the 'blk.img' file.
-An altered 'blk.img' file (or /dev/zero) could be written back with:
-  # dd if=blk.img of=/dev/sda seek=0x123456 oflag=direct bs=512 count=1
-
-Notes: the 0x123456 is an arbitrary hexadecimal logical block address.
-Recent versions of dd (e.g. those that support 'iflag=') support
-hexadecimal addresses. Utilities in recent versions of the sg3_utils
-package also accept the trailing 'h' notation for hexadecimal.
-Alternatively decimal numbers could be used; most window managers have a
-handy calculator that will do hex to decimal conversions. More work may
-be needed at the file system level, especially if the reassigned block
-held critical fs information such as a superblock or a directory.
-
-Even if a full backup of the disk is available, or the disk has been
-"ejected" from a RAID, it may still be worthwhile to reassign the bad
-block(s) that caused the problem (or simply format the disk (see sg_format
-in the sg3_utils package)) and re-use the disk later (not unlike the
-way a replacement disk from a manufacturer might be used).
-
-Conclusion
-==========
-This document contains some suggestions of what to do when smartmontools
-reports a "bad block" on a SCSI disk. These suggestions are more general
-in nature and lower level than those discussed in the BadBlockHowTo.txt
-document. As always, there is no substitute for regular backups, even
-high number RAIDs (e.g. 60) won't help when the user accidentally deletes
-a directory.
-
-
-Note A: Detecting and fixing an error with ECC "on the fly" and not going
-        the further step and reassigning the block in question may explain
-        why some disks have large numbers in their read error counter log.
-        Various worried users have reported large numbers in the "errors
-        corrected without substantial delay" counter field which is in the
-        "Errors corrected by ECC fast" column in the 'smartctl -l error'
-        output.
-
-
-Douglas Gilbert
-2006/9/17
diff --git a/www/FAQ.xml b/www/FAQ.xml
deleted file mode 100644
index d46201b3c2802f63c5b4fcf591e70b4758639ca0..0000000000000000000000000000000000000000
--- a/www/FAQ.xml
+++ /dev/null
@@ -1,543 +0,0 @@
-<?xml version='1.0' encoding='ISO-8859-1'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
-	"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" >
-
-<!--
-Layout borrowed from Doug's smartmontools_scsi.xml.  The following text
-is also from his file.
-
-This is DocBook XML that can be rendered into a single HTML page with a
-command like 'xmlto html-nochunks <this_file_name>'.  It can also be
-rendered into multi-page HTML (drop the "-nochunks") or pdf, ps, txt,
-etc.
--->
-
-<article id="index">
- <articleinfo>
-   <title>FAQ - Frequently Asked Questions</title>
-   <author>
-    <firstname>smartmontools</firstname>
-    <surname>developers</surname>
-    <affiliation>
-     <address>
-      <email>smartmontools-support@lists.sourceforge.net</email>
-     </address>
-    </affiliation>
-   </author>
-  <authorinitials>sd</authorinitials>
-  <pubdate>2003-09-24</pubdate>
-
-  <revhistory>
-     <revision>
-       <revnumber>1.0</revnumber>
-       <date>2003-10-22</date>
-       <authorinitials>sd</authorinitials>
-       <revremark>
-             Moved from index.html to XML
-       </revremark>
-     </revision>
-  </revhistory>
-
-  <copyright>
-   <year>2003</year>
-   <holder>Bruce Allen</holder>
-  </copyright>
-
-  <legalnotice>
-   <para>
-      Permission is granted to copy, distribute and/or modify this
-      document under the terms of the GNU Free Documentation License,
-      Version 1.1 or any later version published by the Free Software
-      Foundation; with no Invariant Sections, with no Front-Cover Texts,
-      and with no Back-Cover Texts.
-   </para>
-   <para>
-    For an online copy of the license see
-    <ulink url="http://www.fsf.org/copyleft/fdl.html">
-    <literal>http://www.fsf.org/copyleft/fdl.html</literal></ulink> .
-   </para>
-
-  </legalnotice>
-
-  <abstract>
-  <para>
-   FAQ - Frequently Asked Questions
-  </para>
-  </abstract>
- </articleinfo>
-
-<!--
-<toc></toc>
--->
-
-
-<sect1 id="a">
-
-<title>What do I do if I have problems, or need support?  Suppose I want
-to become a developer, or suggest some new extensions?</title>
-
-<para>First, search the support mailing list archives to see if your
-question has been answered.  Instructions are in the following
-paragraph.  If you don't find an answer there, then please send an
-e-mail to the smartmontools-support mailing list.  Instructions are
-available at <ulink url="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">
-<literal>http://lists.sourceforge.net/mailman/listinfo/smartmontools-support</literal></ulink>
-. The list is moderated but you're not required to subscribe to it in
-order to post your question.</para>
-
-<para>To search the archives, first go to <ulink url="http://sourceforge.net/mailarchive/forum.php?forum=smartmontools-support">
-<literal>http://sourceforge.net/mailarchive/forum.php?forum=smartmontools-support</literal></ulink>
-. In the top left corner you will see a search box: use <emphasis
-role="bold">Mailing List</emphasis> as the type of search.  This tool
-works very well.</para>
-
-<para>Note that from time to time SourceForge has mailing problems and
-you'll get a message telling you that <emphasis role="italic">Either
-your mailing list name was misspelled or your mailing list has not been
-archived yet.  If this list has just been created, please retry in 2-4
-hours</emphasis>.  If this happens, you'll have to try again
-later.</para>
-
-</sect1>
-
-<sect1 id="b">
-
-<title>What are the future plans for smartmontools?</title>
-
-<para>My plan is that smartmontools-5.x will support ATA/ATAPI-5 disks. 
-Eventually, we'll do smartmontools-6.x to support ATA/ATAPI-6 disks,
-smartmontools-7.x for the ATA/ATAPI-7 standard, and so on.  The "x" will
-denote revision level, as bugs get found and fixed, and as enhancements
-get added.  If it's possible to maintain backwards compatibility, that
-would be nice, but I don't know if it will be possible or
-practical.</para>
-
-</sect1>
-
-<sect1 id="c">
-
-<title>Why are you doing this?</title>
-
-<para>My research group at U. Wisconsin - Milwaukee runs a beowulf
-cluster -  <ulink url="http://www.lsc-group.phys.uwm.edu/beowulf/medusa/">
-<literal>http://www.lsc-group.phys.uwm.edu/beowulf/medusa/</literal></ulink>
--  with 600 ATA-5 and -6 disks (300 IBM and 300 Maxtor).  We have more
-than 50 TB of data stored on the system.  I also help out with a cluster
--  <ulink url="http://pandora.aei.mpg.de/merlin/">
-<literal>http://pandora.aei.mpg.de/merlin/</literal></ulink> -  at the
-Albert Einstein Institute that has another 300 IBM ATA-6 disks (36 TB
-total).  It's nice to have advanced warning when a disk is going to
-fail.</para>
-
-</sect1>
-
-<sect1 id="d">
-
-<title>I see some strange output from smartctl.  What does it
-mean?</title>
-
-<para>The raw S.M.A.R.T. attributes (temperature, power-on lifetime, and
-so on) are stored in vendor-specific structures.  Sometime these are
-strange.  Hitachi disks (at least some of them) store power-on lifetime
-in minutes, rather than hours (see next question below).  IBM disks (at
-least some of them) have three temperatures stored in the raw structure,
-not just one.  And so on.  If you find strange output, or unknown
-attributes, please send an e-mail to the mailing list and we'll help you
-try and figure it out.</para>
-
-</sect1>
-
-<sect1 id="e">
-
-<title>What Kernel Version is needed? (Linux)</title>
-
-<para>Kernel versions 2.4.0 or later should work.  We recommend the
-latest 2.4 kernel.</para>
-
-<para>Vanilla kernel.org 2.2.X kernels do not support the
-HDIO_DRIVE_TASK ioctl(), which is needed for the ATA drive to execute
-the ATA SMART RETURN STATUS command.  So these kernels will not
-work.</para>
-
-<para>Vendor-supplied 2.2.X kernels, and vanilla 2.2.X kernels patched
-with Andre Hedrick's IDE patches -  <ulink url="http://www.funet.fi/pub/linux/kernel/people/hedrick/ide-2.2.20/">
-<literal>http://www.funet.fi/pub/linux/kernel/people/hedrick/ide-2.2.20/</literal></ulink>
-(also available from your local kernel.org mirror, not updated for
-2.2.21 or later, and probably still containing a few bugs) may support
-the needed ioctl().</para>
-
-<para>If the configuration option CONFIG_IDE_TASK_IOCTL exists in your
-2.2.X kernel source code tree, then your 2.2.X kernel will probably
-support smartmontools.  Note that this kernel configuration option does
-<emphasis role="italic">not</emphasis> need to be enabled.  Its presence
-merely indicates that the required HDIO_DRIVE_TASK ioctl() is
-supported.</para>
-
-</sect1>
-
-<sect1 id="f">
-
-<title>What attributes does smartmontools not yet recognize?</title>
-
-<para>From Maxtor disks (99), (100), (101)</para>
-
-<para>If you can attach names/meanings to these attributes, please send
-a note to the mailing list.  If you have access to other SMART utilities
-(especially manufacturer-specific ones, see below) and can send us
-comparison output from smartctl and the other utility, that's especially
-useful.</para>
-
-</sect1>
-
-<sect1 id="g">
-
-<title>My Maxtor/Hitachi/Fujitsu disk is only a few days old, yet
-smartctl reports its age (Attribute 9) as thousands of hours!</title>
-
-<para>On some recent disks, Maxtor has started to use Attribute 9 to
-store the lifetime in minutes rather than hours.  In this case, use the
--m option (smartctl versions 5.0.X) or the --vendorattribute=9,minutes
-(smartctl 5.1.X) option to correctly display hours and minutes.</para>
-
-<para>Some models of Fujitsu disks are known to use Attribute 9 for
-lifetime in seconds.  In that case, use the --vendorattribute=9,seconds
-option to correctly display hours, minutes and seconds.</para>
-
-</sect1>
-
-<sect1 id="h">
-
-<title>The power-on timer (Attribute 9 raw value) on my Maxtor disk acts
-strange.</title>
-
-<para>There are three related problems with Maxtor's SMART
-firmware:</para>
-
-<para><emphasis role="bold">1 - </emphasis>On some disks from 2001/2002,
-the raw value of Attribute 9 (Power On Time) is <emphasis
-role="italic">supposed</emphasis> to be minutes. But it advances at an
-unpredictable rate, always more slowly than one count per minute.  One
-(unconfirmed) theory is that when the disk is in idle mode, the counter
-stops advancing.  This is only supposed to happen in standby
-mode.</para>
-
-<para><emphasis role="bold">2 - </emphasis> In Maxtor disks that use the
-raw value of Attribute 9 as a minutes counter, only two bytes (of the
-six available) are used to store the raw value.  So it resets to zero
-once every 65536=2^16 minutes, or about once every 1092 hours.  This is
-fixed in all Maxtor disks manufactured after July 2003, where the raw
-value was extended to four bytes.</para>
-
-<para><emphasis role="bold">3 - </emphasis> In Maxtor disks that use the
-raw value of Attribute 9 as a minutes counter, the hour time-stamps in
-the self-test and ATA error logs are calculated by right shifting 6
-bits.  This is equivalent to dividing by 64 rather than by 60.  As a
-result, the hour time-stamps in these logs advance 7% more slowly than
-they should.  Thus, if you do self-tests once per week at the same time,
-instead of the time-stamps being 168 hours apart, they are 157 hours
-apart.  This is also fixed in all Maxtor disks manufactured after July
-2003.</para>
-
-</sect1>
-
-<sect1 id="i">
-
-<title>Where can I find manufacturer-specific disk-testing
-utilities?</title>
-
-<para>A good listing of such utilities can be found at <ulink url="http://www.benchmarkhq.ru/english.html?/be_hdd2.html">
-<literal>http://www.benchmarkhq.ru/english.html?/be_hdd2.html</literal></ulink>
-. Unfortunately most of these are for MS operating systems, but most can
-be run from an MS-DOS boot disk.  Note: if you do run one of these
-utilities, and it identifies the meanings of any SMART Attributes that
-are not known to smartmontools, please report them to the mailing
-list.</para>
-
-<para>These utilities have an important role to fill.  If your disk has
-bad sectors (for example, as revealed by running self-tests with
-smartmontools) and the disk is not able to recover the data from those
-sectors, then the disk will <emphasis role="italic">not</emphasis>
-automatically reallocate those damaged sectors from its set of spare
-sectors, because forcing the reallocation to take place may entail some
-loss of data.  Because the commands that force such reallocation are
-<emphasis role="italic">Vendor Specific</emphasis>, most manufactuers
-provide a utility for this purpose.  It may cause data loss but can
-repair damaged sectors (at least, until it runs out of replacement
-sectors).</para>
-
-</sect1>
-
-<sect1 id="j">
-
-<title>When I run <emphasis role="tt">smartd</emphasis>,
-the SYSLOG <emphasis role="tt">/var/log/messages</emphasis> contains
-messages like this:</title>
-
-<programlisting>
-smartd: Reading Device /dev/sdv
-modprobe: modprobe: Can't locate module block-major-65
-</programlisting>
-
-<para>This is because when <emphasis role="tt">smartd</emphasis> starts,
-it looks for all ATA and SCSI devices to monitor (matching the pattern
-<emphasis role="tt">/dev/hd[a-z]</emphasis> or <emphasis
-role="tt">/dev/sd[a-z]</emphasis>).  The log messages appear because
-your system doesn't have most of these devices.</para>
-
-<para>Recent releases of smartd can use a configuration file <emphasis
-role="tt">smartd.conf</emphasis> to specify which devices to include or
-exclude from start-up search.</para>
-
-</sect1>
-
-<sect1 id="k">
-
-<title>What's the story on IBM SMART disks?</title>
-
-<para>Apparently some of the older SMART firmware on IBM disks can
-interfere with the regular operation of the disk.   If you have this
-problem, a firmware upgrade that fixes the problem is avaialable at
-<ulink url="http://www.geocities.com/dtla_update/">
-<literal>http://www.geocities.com/dtla_update/</literal></ulink>
-.</para>
-
-</sect1>
-
-<sect1 id="l">
-
-<title>How can I check that the package hasn't been tampered
-with?</title>
-
-<para>Since the <emphasis role="tt">smartmontools</emphasis> utilities
-run as root, you might be concerned about something harmful being
-embedded within them. Starting with release 5.19 of <emphasis
-role="tt">smartmontools</emphasis>, the .rpm files and tarball have been
-GPG signed.  (The tarball's fingerprint is given in the SoureForge
-Release Notes.) Please verify these using the GPG Signing Key available
-at <ulink url="http://smartmontools.sourceforge.net/SmartmontoolsSigningKey.txt">
-<literal>http://smartmontools.sourceforge.net/SmartmontoolsSigningKey.txt</literal></ulink>
-.</para>
-
-</sect1>
-
-<sect1 id="m">
-
-<title>Is there a bootable standalone CD or floppy that contains
-smartmontools?</title>
-
-<para>If you have a system that is showing signs of disk trouble (for
-example, it's unbootable and the console is full of disk error messages)
-it can be handy to have a version of smartmontools that can be run off
-of a bootable CD or floppy to examine the disk's SMART data and run
-self-tests.  This is also useful if you want to run Captive Self-Tests
-(the <emphasis role="bold"><emphasis role="tt">-C</emphasis></emphasis>
-option of <emphasis role="bold"><emphasis
-role="tt">smartctl</emphasis></emphasis> ) on disks that can not easily
-be unmounted, such as those hosting the Operating System files.  Or you
-can use this to run <emphasis role="tt">smartctl</emphasis> on computers
-that don't use Linux as the day-to-day Operating System.</para>
-
-<para>At present I am only aware of three such bootable disks:</para>
-
-<itemizedlist>
-<listitem>
-<para>LNX-BBC Bootable CD - <ulink url="http://www.lnx-bbc.org/">
-<literal>http://www.lnx-bbc.org/</literal></ulink></para>
-</listitem>
-
-<listitem>
-<para>Stresslinux Bootable CD - <ulink url="http://www.stresslinux.org/">
-<literal>http://www.stresslinux.org/</literal></ulink></para>
-</listitem>
-
-<listitem>
-<para>RIP (Recovery Is Possible) Bootable CD/Floppy - <ulink url="http://www.tux.org/pub/people/kent-robotti/looplinux/rip/">
-<literal>http://www.tux.org/pub/people/kent-robotti/looplinux/rip/</literal></ulink></para>
-</listitem>
-</itemizedlist>
-
-<para> Please let us know if there are others, and we'll add them to
-this list.</para>
-
-</sect1>
-
-<sect1 id="n">
-
-<title>Can I monitor ATA disks behind SCSI RAID controllers?</title>
-
-<para>From release 5.1-16, smartmontools supports 3ware SCSI RAID
-controllers that use ATA disks internally.  To pass commands through the
-3ware controller, use the smartmontools <emphasis role="bold">-d
-3ware,N</emphasis> option or Directive.</para>
-
-<para>In smartmontools release 5.1-16, the SMART HEALTH STATUS
-(smartmontools <emphasis role="bold">-H</emphasis>) is not returned
-correctly for 3ware devices.  In this release, the ENABLE AUTOMATIC
-OFFLINE and ENABLE ATTRIBUTE AUTOSAVE commands (smartmontools <emphasis
-role="bold">-o on</emphasis> and <emphasis role="bold">-S on</emphasis>)
-are <emphasis role="italic">disabled</emphasis> for 3ware devices,
-because at the time 5.1-16 was released, the 3w-xxxx driver could not
-pass these commands through to the ATA disks.</para>
-
-<para>Later smartmontools CVS code and releases <emphasis
-role="italic">do</emphasis> correctly support <emphasis
-role="italic">all</emphasis> of these commands.  You may:</para>
-
-<itemizedlist>
-<listitem>
-<para>Use version <emphasis role="bold">1.02.00.037</emphasis> or
-greater of the 3w-xxxx driver, or</para>
-</listitem>
-
-<listitem>
-<para>Patch earlier 3ware 3w-xxxx drivers with <ulink url="http://smartmontools.sourceforge.net/3w-xxxx.txt">
-<literal>http://smartmontools.sourceforge.net/3w-xxxx.txt</literal></ulink>
-so that these commands reach the disks, or</para>
-</listitem>
-
-<listitem>
-<para>Use an <emphasis role="bold">unpatched</emphasis> earlier 3w-xxxx
-driver (which won't pass these commands to the disks but will instead
-print harmless warning messages to SYSLOG).</para>
-</listitem>
-</itemizedlist>
-
-<para>Since smartmontools 3ware support is new, please report positive
-or negative experiences to the mailing list, particularly for 64-bit
-and/or big-endian architectures.</para></sect1>
-
-<sect1 id="o">
-
-<title>SCSI disks and tapes (TapeAlert)</title>
-
-<para>smartmontools for SCSI disks and tapes (including medium changers)
-is discussed at <ulink url="http://smartmontools.sourceforge.net/smartmontools_scsi.html">
-<literal>http://smartmontools.sourceforge.net/smartmontools_scsi.html</literal></ulink>
-.</para>
-
-</sect1>
-
-<sect1 id="p">
-
-<title>FireWire, USB, and SATA disks/systems</title>
-
-<para>As for USB and FireWire (ieee1394) disks and tape drives, the news
-isn't good.  They appear to Linux as SCSI devices but their
-implementations do not usually support those SCSI commands needed by
-smartmontools.  The ieee1394 consortium recently certified the first
-external enclosure (containing a ATA disk and a protocol bridge) as
-being compliant to the relevant standards.  Such devices have already
-been on the market for about 3  years and they tend to only support the
-bare minimum of commands needed for device operation (i.e. S.M.A.R.T.
-support is an unsupported extra).</para>
-
-<para>I'd be very grateful to find someone who could help me test the
-smartmontools code on serial ATA (SATA) disks.  They should appear as
-normal ATA disks in Linux.</para>
-
-</sect1>
-
-<sect1 id="q">
-
-<title>How does smartmontools differ from smartsuite?</title>
-
-<para>The smartsuite code was originally developed as a Senior Thesis by
-Michael Cornwell at the Concurrent Systems Laboratory (now part of the
-Storage Systems Research Center - <ulink url="http://ssrc.soe.ucsc.edu/">
-<literal>http://ssrc.soe.ucsc.edu/</literal></ulink>), Jack Baskin
-School of Engineering, University of California, Santa Cruz.  You can
-find some information about the original smartsuite project here:</para>
-
-<itemizedlist>
-<listitem>
-<para>Press Release 1 - <ulink url="http://www.ucsc.edu/news_events/press_releases/archive/99-00/09-99/smart_software.htm">
-<literal>http://www.ucsc.edu/news_events/press_releases/archive/99-00/09-99/smart_software.htm</literal></ulink></para>
-</listitem>
-
-<listitem>
-<para>Press Release 2 - <ulink url="http://www.santa-cruz.com/archive/1999/September/22/local/stories/5local.htm">
-<literal>http://www.santa-cruz.com/archive/1999/September/22/local/stories/5local.htm</literal></ulink></para>
-</listitem>
-
-<listitem>
-<para>Press Release 3 - <ulink url="http://www.ucsc.edu/currents/99-00/09-27/smart.html">
-<literal>http://www.ucsc.edu/currents/99-00/09-27/smart.html</literal></ulink></para>
-</listitem>
-</itemizedlist>
-
-<para>smartmontools was derived directly from smartsuite.  It differs
-from smartsuite in that it supports the ATA/ATAPI-5 standard.  So for
-example <emphasis role="tt">smartctl</emphasis> from smartsuite has no
-facility for printing the SMART self-test logs, and doesn't print
-timestamp information in the most usable way.</para>
-
-<para>The <emphasis role="tt">smartctl</emphasis> utility in
-smartmontools has added functionality for this (<emphasis role="tt">-q,
--l selftest,-S, -T, -v and -m</emphasis> options), updated
-documentation, and also fixes small technical bugs in smartsuite.  [One
-example: smartsuite does not actually use the ATA SMART RETURN STATUS
-command to find out the health status of a disk.  It instead tries to
-infer this from the SMART Attribute values.]  See <ulink url="http://smartmontools.cvs.sourceforge.net/viewcvs.py/smartmontools/sm5/CHANGELOG?rev=HEAD&amp;content-type=text/plain">
-<literal>http://smartmontools.cvs.sourceforge.net/viewcvs.py/smartmontools/sm5/CHANGELOG?rev=HEAD&amp;content-type=text/plain</literal></ulink> for a summary of what's been done.</para>
-
-<para>The <emphasis role="tt">smartd</emphasis> utility differs from the
-smartsuite <emphasis role="tt">smartd</emphasis> in major ways.  First,
-it prints somewhat more informative error messages to the syslog. 
-Second, on startup it looks for a configuration file <emphasis
-role="tt">smartd.conf</emphasis>, and if <emphasis
-role="tt">smartd</emphasis> finds this file, it monitors the list of
-devices therein, rather than querying all IDE and SCSI devices on your
-system.  (If the configuration file does not exist, then it does query
-all IDE and SCSI devices.)  Also, it's a well-behaved daemon and doesn't
-leave open file descriptors and other detrius behind.</para>
-
-<para>In addition, the <emphasis role="tt">smartmontools</emphasis>
-version of <emphasis role="tt">smartd</emphasis> can be instructed (via
-Directives in the configuration file) to monitor for changes in a number
-of different disk properties: the SMART status, failure or prefailure
-attributes going below threshold, new errors appearing in the ATA Error
-Log or the SMART Self-Test Log, and so on. <emphasis
-role="tt">smartd</emphasis> can also send an e-mail warning or run a
-user-specified executable if it detects a problem with the disk.</para>
-
-<para>The other principle difference is that smartmontools is an
-OpenSource development project, meaning that we keep the files in CVS,
-and that  other developers who wish to contribute can commit changes to
-the archive.  If you would like to contribute, please write to the
-mailing-list.</para>
-
-<para>But the bottom line is that the code in smartmontools is derived
-directly from smartsuite and is similar.  The smartsuite package can be
-found at <ulink url="http://sourceforge.net/projects/smartsuite/">
-<literal>http://sourceforge.net/projects/smartsuite/</literal></ulink>
-.</para></sect1>
-
-<sect1 id="r">
-
-<title>Does it work on Windows?</title>
-
-<para>Currently not, but we consider Cygwin - <ulink url="http://www.cygwin.com/">
-<literal>http://www.cygwin.com/</literal></ulink> -  the way to go,
-where CVS compiles almost out of the box but still lacks any specific
-code to make it work.  Write to the mailing list if you're interested in
-porting it.  Someone already sent some S.M.A.R.T. code for Windows,
-which may be of use.  Porting to other platforms may be easier as well
-now that any Linux specific code (like linux/hdreg.h) has been removed,
-and more will be done soon in that direction.</para>
-
-<para>A Cygwin port would probably only require and additional DLL,
-cygwin1.dll, to run on plain Windows.</para></sect1>
-
-<sect1 id="s">
-
-<title>Why has the versioning scheme changed?</title>
-
-<para>With the move to GNU Autoconf and GNU Automake it changed from
-5.X-Y (where X and Y are one or more numbers) to 5.Y.  This had to be
-done because the -Y extension is used by distributions to almost always
-denote a new build of the same version. So, the first version with that
-change will be 5.19 and not 5.1-19.</para>
-
-</sect1>
-
-</article>
diff --git a/www/Makefile b/www/Makefile
deleted file mode 100644
index 485f573726d613850d6a69f65627bf342b78d8c6..0000000000000000000000000000000000000000
--- a/www/Makefile
+++ /dev/null
@@ -1,22 +0,0 @@
-# Manufactures HTML file from XML file. Note: do NOT edit the HTML
-# file, only the XML file.
-
-all: smartmontools_scsi.html badblockhowto.html
-
-smartmontools_scsi.html: smartmontools_scsi.xml 
-	xmlto html-nochunks smartmontools_scsi.xml
-
-badblockhowto.html: badblockhowto.xml 
-	xmlto html-nochunks badblockhowto.xml
-
-upload: smartmontools_scsi.html index.html
-	scp smartmontools_scsi.html ballen4705@smartmontools.sourceforge.net:/home/groups/s/sm/smartmontools/htdocs
-	scp badblockhowto.html ballen4705@smartmontools.sourceforge.net:/home/groups/s/sm/smartmontools/htdocs
-	scp 3w-xxxx.txt ballen4705@smartmontools.sourceforge.net:/home/groups/s/sm/smartmontools/htdocs
-	scp index.html ballen4705@smartmontools.sourceforge.net:/home/groups/s/sm/smartmontools/htdocs
-	scp examples/*.html ballen4705@smartmontools.sourceforge.net:/home/groups/s/sm/smartmontools/htdocs/examples
-	scp examples/*.txt ballen4705@smartmontools.sourceforge.net:/home/groups/s/sm/smartmontools/htdocs/examples
-	scp BadBlockHowTo.txt ballen4705@smartmontools.sourceforge.net:/home/groups/s/sm/smartmontools/htdocs
-
-clean:
-	rm smartmontools_scsi.html badblockhowto.html
diff --git a/www/SmartmontoolsSigningKey.txt b/www/SmartmontoolsSigningKey.txt
deleted file mode 100644
index 0ac19356f748d2b5f81b33962e588e8af28fb16d..0000000000000000000000000000000000000000
--- a/www/SmartmontoolsSigningKey.txt
+++ /dev/null
@@ -1,27 +0,0 @@
------BEGIN PGP PUBLIC KEY BLOCK-----
-Version: GnuPG v1.0.7 (GNU/Linux)
-
-mQGiBD9XAXIRBACgLEphBmhUKWE1mRKzjkq/8vZHtJsVUiFivcbxaSLa9jBbJoZV
-sQk5fdcleVE6CcuodMetVE6Gl8uM4W4iymp0i35lwefdgmUzJYmza1ZD7Uk0x4zv
-tKi9xZ9Hc+yrf4SHRwLTZxuUyLf9TURwGXfLd2bxP1USYJVL4vOYoiBwBwCgq/w3
-EyO5PhlGp5rfE+WIoyy9GHcEAIYP3ctigHu6tnSobIGA77BFOv+v7DbXRjbKhEz1
-s4lPGQQP5h2t4VFRiy9RlD4GlEXD51cRFMmtFk4cBbOuONQbNOJFQQ/9JpVBU6/O
-CZrVMUqDnQMd2mdUU8pxM7cguaw5cPFxqqX5dkW1JikGrlG1QsH5UxuYhdadO+al
-1fTnA/9RMRscXd6aAdN66pZ9mGoqIxVUO6N+icXO7DP+ArIt7gu4GLgvvARlgMiS
-neRV4g7mvLm41kBDEv5gug+h2ha5ZI+P51oSRYs8yA5fVtl0GA2YRA2QercALv6C
-CtAvnFXWFqSeyW1ESdd2zFKBjhXlBVkmujOyKDS6LXRpZjwJXrRWU21hcnRtb250
-b29scyBTaWduaW5nIEtleSAodGhyb3VnaCAyMDA0KSA8c21hcnRtb250b29scy1z
-dXBwb3J0QGxpc3RzLnNvdXJjZWZvcmdlLm5ldD6IZAQTEQIAJAUCP1cBcgIbAwUJ
-AnjQAAYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRAjPh86m7GaIlTQAJ9IsqaxHbqX
-BSd+xfJwUAZyKWqyLwCgoa2rMvHAHa/Pvpt4E0i0xF9NW3yITAQTEQIADAUCP1cB
-+QWDAnjPeQAKCRARGZEEN/UVgWa7AJ95rEDeEw9G3uqAZO7L9u650QPX6wCgoHJ9
-Hq/akQJZhOgSKyrgVEyAc8S5AQ0EP1cBeBAEAMLXV8RwVFDs5EvfkQNwasoKNS+N
-PvvhO/weED188XklZ3QTiToEp2b4JFaoUkTk1l2f9JxagDPaVHR6XU8H740x25LZ
-gC6XObKMBxqJ9CrBLGcMt/bCugquDu18KFlL3Y1rq9uBxq9JS6CJthUzeaaFdFQS
-V7tF2+3hBz/Okqo7AAMFA/9l0YcKnTKDy8jdOtNjky1NEbaF1LjyRc4laT6N4O6q
-Xg2oGD6MgS7zSK/ORcT3B0T5kpTo6gnKLTYDxEAvpNjrOjlwn08Jtm3xrQZLId/W
-RAo+Qqn5Or+sugZZpQPHrGGB9TTc0AL3MfCbK4mlssVhS0SAq35E/osCLQcor7Sx
-sohPBBgRAgAPBQI/VwF4AhsMBQkCeNAAAAoJECM+HzqbsZoi4WUAn2IQhEtHY/48
-4rljbro8yUwYlrXzAJ44VfTwmjLlI9aoYdRW/cTtZ0tPgw==
-=f2kQ
------END PGP PUBLIC KEY BLOCK-----
diff --git a/www/SmartmontoolsSigningKey_2005.txt b/www/SmartmontoolsSigningKey_2005.txt
deleted file mode 100644
index 82e20be2f4a9d09b3112588550505fbc24824b2b..0000000000000000000000000000000000000000
--- a/www/SmartmontoolsSigningKey_2005.txt
+++ /dev/null
@@ -1,27 +0,0 @@
------BEGIN PGP PUBLIC KEY BLOCK-----
-Version: GnuPG v1.2.3 (GNU/Linux)
- 
-mQGiBEJl08ARBAC8HLnkjodFpCGWxIquBNqVNLbcJIi+4KuhD0o7Jn2njif31ZMu
-useJAoKmlYD7wEShJemkTfdj76QEtv3DGAKXo3ylI50FzZwR8SflHvdM7D3ewk29
-hDGM7QqvezwG7nToz1IqmT6t6LUtp7FtqeLlJs+Ly9jzGIDlB1H3LIFsJwCgtkAY
-VCv6cLuGnc2TE+elAi98KqUEAIORBntWHPtGb4uMXo0gAJzsu0m66OWosCNwT6Hb
-EQZQc3fiW80Ph1tr9MHh24nyA4PaciKygrXt3GvIxlGocRB1YIk/BeDiGckMNn3L
-/3R1KFPPbhCsuGcjOZ8hcwn/rVtSAYYptnotEftwdJc1iDtXogRXGs0RINqfL/NL
-855SBACBUHQcQTHkj3nmciyh2gVBbbHC/NVDVbTxPLLH5MbKYd9cm/xAL+AztIsE
-MgICJtSkYqg2QIN8VPRFMILdBa8DNYT03bVhlERf09AB9PrB9507QrEMFIoQjYF6
-41R74xj++3VNtbLSn2HFcY7E7hWmW9arYGka24jbrwCZnPqyvbRWU21hcnRtb250
-b29scyBTaWduaW5nIEtleSAodGhyb3VnaCAyMDA2KSA8c21hcnRtb250b29scy1z
-dXBwb3J0QGxpc3RzLnNvdXJjZWZvcmdlLm5ldD6IZAQTEQIAJAUCQmXTwAIbAwUJ
-Az6RAAYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRAildgUhBq66DfgAJ9Ad+ywl9EA
-TxbZarsWWb20AgsFJgCfRUjmcUMOoM2o6PJqxcn2rauOjrCITAQTEQIADAUCQmXU
-FgWDAz6QqgAKCRARGZEEN/UVgeFJAJoDVs8e1QCs6WMljf0hXp5FEr/xIgCfUnbX
-NKDft/y8GcktEJZVJrQ/Bcq5AQ0EQmXTwxAEAKtS+tILqIraz2vIpkI468o0ou+m
-XsPg0Vjv1FX4iIotg9iqOaURITBJW1uyOWzwgIKQr9IV3KDjiViK/OeebGk++fA6
-F23k7UAePInOXp0f01xHwr2dkhoV07AFCjFrarsK5/aXz01lgg9vpgxuQ6Z78ci8
-MkX+NmcCxo+3Ilk/AAMFBACpXVsbcf4xxQd7IXc7bcwkAdnmB8NsTEm1L3fwk3Em
-nW1UcQWzov2iJIBWOIbZDfRgTQC47cSIpE42ez6t8QFaG7zROBEHqBw4q1HA7sPT
-3DU8mOMvU5hbitTE8N3J9vMxcCyzqKfSfYDnLsMNldV/QAJGhyX4LmTamx5p5Ks/
-+YhPBBgRAgAPBQJCZdPDAhsMBQkDPpEAAAoJECKV2BSEGrroVn8AnAhM11Nj07Jo
-di8zFUMf0A962Yg7AJ4ptOiGVlWiLhJiSIfSWROPwweAlQ==
-=5DeE
------END PGP PUBLIC KEY BLOCK-----
diff --git a/www/badblockhowto.xml b/www/badblockhowto.xml
deleted file mode 100644
index f02958909a94011ad9a2d08ee6e4c95938ed3ff5..0000000000000000000000000000000000000000
--- a/www/badblockhowto.xml
+++ /dev/null
@@ -1,991 +0,0 @@
-<?xml version='1.0' encoding='ISO-8859-1'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
-        "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" >
-
-<!--
-This is DocBook XML that can be rendered into a single HTML page with a
-command like 'xmlto html-nochunks <this_file_name>'. It can
-also be rendered into multi-page HTML (drop the "-nochunks") or pdf,
-ps, txt, etc.
--->
-
-<article id="index">
- <articleinfo>
-   <title>Bad block HOWTO for smartmontools</title>
-   <author>
-    <firstname>Bruce</firstname>
-    <surname>Allen</surname>
-    <affiliation>
-     <address>
-      <email>smartmontools-support@lists.sourceforge.net</email>
-     </address>
-    </affiliation>
-   </author>
-   <authorinitials>ba</authorinitials>
-   <author>
-    <firstname>Douglas</firstname>
-    <surname>Gilbert</surname>
-    <affiliation>
-     <address>
-      <email>smartmontools-support@lists.sourceforge.net</email>
-     </address>
-    </affiliation>
-   </author>
-   <authorinitials>dpg</authorinitials>
-  <pubdate>2006-11-14</pubdate>
-
-  <revhistory>
-     <revision>
-       <revnumber>1.0</revnumber>
-       <date>2006-11-14</date>
-       <authorinitials>dpg</authorinitials>
-       <revremark>
-             merge BadBlockHowTo.txt and BadBlockSCSIHowTo.txt
-       </revremark>
-     </revision>
-  </revhistory>
-
-  <copyright>
-   <year>2004</year>
-   <year>2005</year>
-   <year>2006</year>
-   <holder>Bruce Allen</holder>
-  </copyright>
-
-  <legalnotice>
-   <para>
-      Permission is granted to copy, distribute and/or modify this document
-      under the terms of the GNU Free Documentation License, Version 1.1
-      or any later version published by the Free Software Foundation;
-      with no Invariant Sections, with no Front-Cover Texts, and with
-      no Back-Cover Texts.
-   </para>
-   <para>
-    For an online copy of the license see
-    <ulink url="http://www.fsf.org/copyleft/fdl.html">
-    <literal>www.fsf.org/copyleft/fdl.html</literal></ulink>.
-   </para>
-
-  </legalnotice>
-
-  <abstract>
-  <para>
-    This article describes what actions might be taken when smartmontools
-    detects a bad block on a disk. It demonstrates how to identify the file
-    associated with an unreadable disk sector, and how to force that sector
-    to reallocate.
-  </para>
-  </abstract>
- </articleinfo>
-
-<!--
-<toc></toc>
--->
-
-
-  <sect1 id="intro">
-      <title>Introduction</title>
-<para>
-Handling bad blocks is a difficult problem as it often involves
-decisions about losing information. Modern storage devices tend
-to handle the simple cases automatically, for example by writing
-a disk sector that was read with difficulty to another area on
-the media. Even though such a remapping can be done by a disk
-drive transparently, there is still a lingering worry about media
-deterioration and the disk running out of spare sectors to remap.
-</para>
-<para>
-Can smartmontools help? As the <acronym>SMART</acronym> acronym suggests,
-the <command>smartctl</command> command and the <command>smartd</command>
-daemon concentrate on monitoring and analysis. So apart from changing some
-reporting settings, smartmontools will not modify the raw data in a
-device. Also smartmontools only works with physical devices, it does
-not know about partitions and file systems. So other tools are needed.
-The job of smartmontools is to alert the user that something is wrong
-and user intervention may be required.
-</para>
-<para>
-One approach is to work out the mapping between the logical block
-address used by a storage device and a file or some other component of a
-file system using that device. Note that there may not be such a mapping
-reflecting that a bad block has been found at a location not currently
-used by the file system. A user may want to do this analysis to localize
-and minimize the replacement file(s) that are retrieved from some
-backup store. This approach requires knowledge of the file system
-involved and this document uses the Linux ext2 and ext3 file systems for
-examples. Also the type of content may come into play. For example if
-an area storing video has a corrupted sector, it may be easiest to
-accept that a frame or two might be corrupted and instruct the disk
-not to retry as that may have the visual effect of changing a momentary
-blank into a 1 second pause.
-</para>
-<para>
-Another approach is to ignore the upper level consequences (e.g. corrupting
-a file or worse damage to a file system) and use the facilities offered by
-a storage device to repair the damage. The SCSI disk command set is used
-elaborate this approach.
-</para>
-</sect1>
-
-  <sect1 id="rfile">
-      <title>Repairs in a file system</title>
-<para>
-This section contains examples of what to do at the file system level
-when smartmontools reports a bad block. These examples assume the Linux
-operating system and either the ext2 or ext3 file system. The various
-Linux commands shown have man pages and the reader is encouraged to examine
-these. Of note is the <command>dd</command> command which is often used in
-repair work
-<footnote><para>
-Starting with GNU coreutils release 5.3.0, the <command>dd</command>
-command in Linux includes the options 'iflag=direct' and 'oflag=direct'.
-Using these with the <command>dd</command> commands should be helpful,
-because adding these flags should avoid any interaction
-with the block buffering IO layer in Linux and permit direct reads/writes
-from the raw device.  Use <command>dd --help</command> to see if your
-version of dd supports these options. If not, the latest code for dd
-can be found at <ulink url="http://alpha.gnu.org/gnu/coreutils">
-<literal>alpha.gnu.org/gnu/coreutils</literal></ulink>.
-</para></footnote>
-and has a unique command line syntax.
-</para>
-<para>
-The author would like to thank Sergey Vlasov, Theodore Ts'o,
-Michael Bendzick, and others for explaining this approach. The author would
-like to add text showing how to do this for other file systems, in
-particular ReiserFS, XFS, and JFS: please email if you can provide this
-information.
-</para>
-
-  <sect2 id="example1">
-      <title>First example</title>
-<para>
-In this example, the disk is failing self-tests at Logical Block
-Address LBA = 0x016561e9 = 23421417.  The LBA counts sectors in units
-of 512 bytes, and starts at zero.
-</para>
-<para>
-<programlisting>
-root]# smartctl -l selftest /dev/hda:
-
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed: read failure       90%       217         0x016561e9
-</programlisting>
-Note that other signs that there is a bad sector on the disk can be
-found in the non-zero value of the Current Pending Sector count:
-<programlisting>
-root]# smartctl -A /dev/hda
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       1
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       1
-</programlisting>
-</para>
-<para>
-First Step: We need to locate the partition on which this sector of
-the disk lives:
-<programlisting>
-root]# fdisk -lu /dev/hda
-
-Disk /dev/hda: 123.5 GB, 123522416640 bytes
-255 heads, 63 sectors/track, 15017 cylinders, total 241254720 sectors
-Units = sectors of 1 * 512 = 512 bytes
-
-   Device Boot    Start       End    Blocks   Id  System
-/dev/hda1   *        63   4209029   2104483+  83  Linux
-/dev/hda2       4209030   5269319    530145   82  Linux swap
-/dev/hda3       5269320 238227884 116479282+  83  Linux
-/dev/hda4     238227885 241248104   1510110   83  Linux
-</programlisting>
-
-The partition /dev/hda3 starts at LBA 5269320 and extends past the
-'problem' LBA.  The 'problem' LBA is offset 23421417 - 5269320 =
-18152097 sectors into the partition /dev/hda3.
-</para>
-<para>
-To verify the type of the file system and the mount point, look in
-/etc/fstab:
-<programlisting>
-root]# grep hda3 /etc/fstab
-/dev/hda3 /data ext2 defaults 1 2
-</programlisting>
-You can see that this is an ext2 file system, mounted at /data.
-</para>
-<para>
-Second Step: we need to find the blocksize of the file system
-(normally 4096 bytes for ext2):
-<programlisting>
-root]# tune2fs -l /dev/hda3 | grep Block
-Block count:              29119820
-Block size:               4096
-</programlisting>
-In this case the block size is 4096 bytes.
-
-Third Step: we need to determine which File System Block contains this
-LBA.  The formula is:
-<programlisting>
-  b = (int)((L-S)*512/B)
-where:
-b = File System block number
-B = File system block size in bytes
-L = LBA of bad sector
-S = Starting sector of partition as shown by fdisk -lu
-and (int) denotes the integer part.
-</programlisting>
-
-In our example, L=23421417, S=5269320, and B=4096.  Hence the
-'problem' LBA is in block number
-<programlisting>
-   b = (int)18152097*512/4096 = (int)2269012.125
-so b=2269012.
-</programlisting>
-</para>
-<para>
-Note: the fractional part of 0.125 indicates that this problem LBA is
-actually the second of the eight sectors that make up this file system
-block.
-</para>
-<para>
-Fourth Step: we use debugfs to locate the inode stored in this block,
-and the file that contains that inode:
-<programlisting>
-root]# debugfs
-debugfs 1.32 (09-Nov-2002)
-debugfs:  open /dev/hda3
-debugfs:  icheck 2269012
-Block   Inode number
-2269012 41032
-debugfs:  ncheck 41032
-Inode   Pathname
-41032   /S1/R/H/714197568-714203359/H-R-714202192-16.gwf
-</programlisting>
-
-In this example, you can see that the problematic file (with the mount
-point included in the path) is:
-/data/S1/R/H/714197568-714203359/H-R-714202192-16.gwf
-</para>
-<para>
-To force the disk to reallocate this bad block we'll write zeros to
-the bad block, and sync the disk:
-<programlisting>
-root]# dd if=/dev/zero of=/dev/hda3 bs=4096 count=1 seek=2269012
-root]# sync
-</programlisting>
-</para>
-<para>
-<emphasis>NOTE:</emphasis> This last step has <emphasis>permanently
-</emphasis> and irretrievably <emphasis>destroyed</emphasis> some of
-the data that was in this file.  Don't do this unless you don't need
-the file or you can replace it with a fresh or correct version.
-</para>
-<para>
-Now everything is back to normal: the sector has been reallocated.
-Compare the output just below to similar output near the top of this
-article:
-<programlisting>
-root]# smartctl -A /dev/hda
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       1
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       1
-</programlisting>
-
-Note: for some disks it may be necessary to update the SMART Attribute values by using
-<command>smartctl -t offline /dev/hda</command>
-</para>
-<para>
-The disk now passes its self-tests again:
-
-<programlisting>
-root]# smartctl -t long /dev/hda  [wait until test completes, then]
-root]# smartctl -l selftest /dev/hda
-
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed without error       00%       239         -
-# 2  Extended offline    Completed: read failure       90%       217         0x016561e9
-# 3  Extended offline    Completed: read failure       90%       212         0x016561e9
-# 4  Extended offline    Completed: read failure       90%       181         0x016561e9
-# 5  Extended offline    Completed without error       00%        14         -
-# 6  Extended offline    Completed without error       00%         4         -
-</programlisting>
-</para>
-<para>
-and no longer shows any offline uncorrectable sectors:
-
-<programlisting>
-root]# smartctl -A /dev/hda
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       1
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
-</programlisting>
-</para>
-</sect2>
-
-
-  <sect2 id="example2">
-      <title>Second Example</title>
-<para>
-On this drive, the first sign of trouble was this email from smartd:
-<programlisting>
-    To: ballen
-    Subject: SMART error (selftest) detected on host: medusa-slave166.medusa.phys.uwm.edu
-
-    This email was generated by the smartd daemon running on host:
-    medusa-slave166.medusa.phys.uwm.edu in the domain: master001-nis
-
-    The following warning/error was logged by the smartd daemon:
-    Device: /dev/hda, Self-Test Log error count increased from 0 to 1
-</programlisting>
-</para>
-<para>
-Running <command>smartctl -a /dev/hda</command> confirmed the problem:
-    
-<programlisting>
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed: read failure       80%       682         0x021d9f44
-
-Note that the failing LBA reported is 0x021d9f44 (base 16) = 35495748 (base 10)
-    
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       3
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       3
-</programlisting>
-</para>
-<para>
-and one can see above that there are 3 sectors on the list of pending
-sectors that the disk can't read but would like to reallocate.
-</para>
-<para>
-The device also shows errors in the SMART error log:
-<programlisting>
-Error 212 occurred at disk power-on lifetime: 690 hours
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 12 46 9f 1d e2  Error: UNC 18 sectors at LBA = 0x021d9f46 = 35495750
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  25 00 12 46 9f 1d e0 00 2485545.000  READ DMA EXT
-</programlisting>
-</para>
-<para>
-Signs of trouble at this LBA may also be found in SYSLOG:
-<programlisting>
-[root]# grep LBA /var/log/messages | awk '{print $12}' | sort | uniq
- LBAsect=35495748
- LBAsect=35495750
-</programlisting>
-</para>
-<para>
-So I decide to do a quick check to see how many bad sectors there
-really are. Using the bash shell I check 70 sectors around the trouble
-area:
-<programlisting>
-[root]# export i=35495730
-[root]# while [ $i -lt 35495800 ]
-        > do echo $i
-        > dd if=/dev/hda of=/dev/null bs=512 count=1 skip=$i
-        > let i+=1
-        > done
- 
-&lt;SNIP&gt;   
-
-35495734
-1+0 records in
-1+0 records out
-35495735
-dd: reading `/dev/hda': Input/output error
-0+0 records in
-0+0 records out
-
-&lt;SNIP&gt;
-
-35495751
-dd: reading `/dev/hda': Input/output error
-0+0 records in
-0+0 records out
-35495752
-1+0 records in
-1+0 records out
-
-&lt;SNIP&gt;
-</programlisting>
-</para>
-<para>
-which shows that the seventeen sectors 35495735-35495751 (inclusive)
-are not readable.
-</para>
-<para>
-Next, we identify the files at those locations.  The partitioning
-information on this disk is identical to the first example above, and
-as in that case the problem sectors are on the third partition
-/dev/hda3.  So we have:
-<programlisting>
-     L=35495735 to 35495751
-     S=5269320
-     B=4096
-</programlisting>
-so that b=3778301 to 3778303 are the three bad blocks in the file
-system.
-
-<programlisting>
-[root]# debugfs
-debugfs 1.32 (09-Nov-2002)
-debugfs:  open /dev/hda3
-debugfs:  icheck 3778301
-Block   Inode number
-3778301 45192
-debugfs:  icheck 3778302
-Block   Inode number
-3778302 45192
-debugfs:  icheck 3778303
-Block   Inode number
-3778303 45192
-debugfs:  ncheck 45192
-Inode   Pathname
-45192   /S1/R/H/714979488-714985279/H-R-714979984-16.gwf
-debugfs:  quit
-</programlisting>
-</para>
-<para>
-And finally, just to confirm that this is really the damaged file:
-</para>
-<para>
-<programlisting>
-[root]# md5sum /data/S1/R/H/714979488-714985279/H-R-714979984-16.gwf
-md5sum: /data/S1/R/H/714979488-714985279/H-R-714979984-16.gwf: Input/output error
-</programlisting>
-</para>
-<para>
-Finally we force the disk to reallocate the three bad blocks:
-<programlisting>
-[root]# dd if=/dev/zero of=/dev/hda3 bs=4096 count=3 seek=3778301
-[root]# sync
-</programlisting>
-</para>
-<para>
-We could also probably use:
-<programlisting>
-[root]# dd if=/dev/zero of=/dev/hda bs=512 count=17 seek=35495735
-</programlisting>
-</para>
-<para>
-At this point we now have:
-<programlisting>
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
-</programlisting>
-</para>
-<para>
-which is encouraging, since the pending sectors count is now zero.
-Note that the drive reallocation count has not yet increased: the
-drive may now have confidence in these sectors and have decided not to
-reallocate them..
-</para>
-<para>
-A device self test: 
-<programlisting>
-  [root#] smartctl -t long /dev/hda
-(then wait about an hour) shows no unreadable sectors or errors:
-
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed without error       00%       692         -
-# 2  Extended offline    Completed: read failure       80%       682         0x021d9f44
-</programlisting>
-</para>
-</sect2>
-
-  <sect2 id="unmapped">
-      <title>Unassigned sectors</title>
-<para>
-This section was written by Kay Diederichs.
-</para>
-<para>
-I read your badblocks-howto at and greatly
-benefited from it. One thing that's (maybe) missing is that often the
-<command>smartctl -t long</command> scan finds a bad sector which is
-<emphasis> not</emphasis> assigned to
-any file. In that case it does not help to run debugfs, or rather
-debugfs reports the fact that no file owns that sector. Furthermore,
-it is somewhat laborious to come up with the correct numbers for
-debugfs, and debugfs is slow ...
-</para>
-<para>
-So what I suggest in the case of presence of
-Current_Pending_Sector/Offline_Uncorrectable errors is to create a
-huge file on that file system.
-<programlisting>
-  dd if=/dev/zero of=/some/mount/point bs=4k
-</programlisting>
-creates the file. Leave it running until the partition/file system is
-full. This will make the disk reallocate those sectors which do not
-belong to a file. Check the <command>smartctl -a</command> output after
-that and make
-sure that the sectors are reallocated. If any remain, use the debugfs
-method.  Of course the usual caveats apply - back it up first, and so
-on.
-</para>
-</sect2>
-
-  <sect2 id="lvm">
-      <title>LVM repairs</title>
-<para>
-This section was written by Frederic BOITEUX. It was titled: "HOW TO
-LOCATE AND REPAIR BAD BLOCKS ON AN LVM VOLUME".
-</para>
-<para>
-Smartd reports an error in a short test�:
-<programlisting>
-# smartctl -a /dev/hdb
-...
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Short offline       Completed: read failure       90%        66         37383668
-</programlisting>
-So the disk has a bad block located in LBA block 37383668
-</para>
-<para>
-In which physical partition is the bad block�?
-<programlisting>
-# sfdisk -lu /dev/hdb
-
-Disk /dev/hdb: 9729 cylinders, 255 heads, 63 sectors/track
-Units = sectors of 512 bytes, counting from 0
-
-   Device Boot    Start       End   #sectors  Id  System
-/dev/hdb1            63    996029     995967  82  Linux swap / Solaris
-/dev/hdb2   *    996030   1188809     192780  83  Linux
-/dev/hdb3       1188810 156296384  155107575  8e  Linux LVM
-/dev/hdb4             0         -          0   0  Empty
-</programlisting>
-
-It's in the /dev/hdb3 partition, a LVM2 partition.
-From the LVM2 partition beginning, the bad block has an offset of
-<programlisting>
-(37383668 - 1188810) = 36194858
-</programlisting>
-</para>
-<para>
-We have to find in which LVM2 logical partition the block belongs to.
-</para>
-<para>
-In which logical partition is the bad block�?
-</para>
-<para>
-<emphasis>IMPORTANT</emphasis>�: LVM2 can use different schemes dividing
-its physical partitions to logical ones�: linear, striped, contiguous or
- not... The following example assumes that allocation is linear�!
-</para>
-<para>
-The physical partition used by LVM2 is divided in PE (Physical Extent)
-units of the same size, starting at pe_start' 512 bytes blocks from
-the beginning of the physical partition.
-</para>
-<para>
-The 'pvdisplay' command gives the size of the PE (in KB) of the
-LVM partition�:
-<programlisting>
-#  part=/dev/hdb3�; pvdisplay -c $part | awk -F: '{print $8}'
-4096
-</programlisting>
-</para>
-<para>
-To get its size in LBA block size (512 bytes or 0.5 KB), we multiply this
-number by 2�: 4096 * 2 = 8192 blocks for each PE.
-</para>
-<para>
-To find the offset from the beginning of the physical partition is a
-bit more difficult�: if you have a recent LVM2 version, try�:
-<programlisting>
-# pvs -o+pe_start $part
-</programlisting>
-</para>
-<para>
-Either, you can look in /etc/lvm/backup�:
-<programlisting>
-# grep pe_start $(grep -l $part /etc/lvm/backup/*)
-                        pe_start = 384
-</programlisting>
-</para>
-<para>
-Then, we search in which PE is the badblock, calculating the PE rank
-in which the faulty block of the partition is�:
-physical partition's bad block number / sizeof(PE) =
-<programlisting>
-36194858 / 8192 = 4418.3176
-</programlisting>
-</para>
-<para>
-So we have to find in which LVM2 logical partition is used the PE
-number 4418 (count starts from 0)�:
-<programlisting>
-# lvdisplay --maps |egrep 'Physical|LV Name|Type'
-  LV Name                /dev/WDC80Go/racine
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    0 to 127
-  LV Name                /dev/WDC80Go/usr
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    128 to 1407
-  LV Name                /dev/WDC80Go/var
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    1408 to 1663
-  LV Name                /dev/WDC80Go/tmp
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    1664 to 1791
-  LV Name                /dev/WDC80Go/home
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    1792 to 3071
-  LV Name                /dev/WDC80Go/ext1
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    3072 to 10751
-  LV Name                /dev/WDC80Go/ext2
-    Type                linear
-    Physical volume     /dev/hdb3
-    Physical extents    10752 to 18932
-</programlisting>
-</para>
-<para>
-So the PE #4418 is in the <filename>/dev/WDC80Go/ext1</filename>
-LVM logical partition.
-</para>
-<para>
-Size of logical block of filesystem on <filename>/dev/WDC80Go/ext1
-</filename>�:
-</para>
-<para>
-It's a ext3 fs, so I get it like this�:
-<programlisting>
-# dumpe2fs /dev/WDC80Go/ext1 | grep 'Block size'
-dumpe2fs 1.37 (21-Mar-2005)
-Block size:               4096
-</programlisting>
-</para>
-<para>
-bad block number for the filesystem�:
-</para>
-<para>
-The logical partition begins on PE 3072�:
-<programlisting>
- (# PE's start of partition * sizeof(PE)) + parttion offset[pe_start] =
- (3072 * 8192) + 384 = 25166208
-</programlisting>
-512b block of the physical partition, so the bad block number for the
-filesystem� is�:
-<programlisting>
-(36194858 - 25166208) / (sizeof(fs block) / 512)
-= 11028650 / (4096 / 512)  = 1378581.25
-</programlisting>
-</para>
-<para>
-Test of the fs bad block�:
-<programlisting>
-dd if=/dev/WDC80Go/ext1 of=block1378581 bs=4096 count=1 skip=1378581
-</programlisting>
-</para>
-<para>
-If this dd command succeeds, without any error message in console or
-syslog, then the block number calculation is probably wrong�! *Don't*
-go further, re-check it and if you don't find the error, please
-renunce�!
-</para>
-<para>
-Search / correction follows the same scheme as for simple
-partitions�:
-<itemizedlist>
-<listitem><para>
-find possible impacted files with debugfs (icheck &lt;fs block nb&gt;,
-then ncheck &lt;icheck nb&gt;).
-</para></listitem>
-<listitem><para>
-reallocate bad block writing zeros in it, *using the fs block size*�:
-</para></listitem>
-</itemizedlist>
-</para>
-<para>
-<programlisting>
-dd if=/dev/zero of=/dev/WDC80Go/ext1 count=1 bs=4096 seek=1378581
-</programlisting>
-</para>
-<para>
-Et voil�!
-</para>
-</sect2>
-
-</sect1>
-
-  <sect1 id="sdisk">
-      <title>Repairs at the disk level</title>
-<para>
-This section ignores the upper level impact of a bad block and just
-repairs the underlying sector so that defective sectors will not cause
-problems in the future. The SCSI disk command set and associated disk
-architecture are assumed.
-</para>
-<para>
-SCSI disks have their own logical to physical mapping allowing
-a damaged sector (usually carrying 512 bytes of data) to be
-remapped irrespective of the operating system, file system or software
-RAID being used.
-</para>
-
-  <sect2 id="sdetails">
-      <title>Details</title>
-<para>
-The terms <emphasis>block</emphasis> and <emphasis>sector</emphasis> are
-used interchangeably, although block tends to get used in higher level or
-more abstract contexts such as a <emphasis>logical block</emphasis>.
-</para>
-<para>
-When a SCSI disk is formatted, defective sectors identified during
-the manufacturing process (the so called primary list: PLIST),
-those found during the format itself (the certification list: CLIST),
-those given explicitly to the format command (the DLIST) and optionally
-the previous grown list (GLIST) are not used in the logical block
-map. The number (and low level addresses) of the unmapped sectors can be
-found with the READ DEFECT DATA SCSI command.
-</para>
-<para>
-SCSI disks tend to be divided into zones which have spare sectors and
-perhaps spare tracks, to support the logical block address mapping
-process. The idea is that if a logical block is remapped, the heads do not
-have to move a long way to access the replacement sector. Note that spare
-sectors are a scarce resource.
-</para>
-<para>
-Once a SCSI disk format has completed successfully, other problems
-may appear over time. These fall into two categories:
-<itemizedlist>
-<listitem><para>
-recoverable: the Error Correction Codes (ECC) detect a problem
-but it is small enough to be corrected. Optionally other strategies
-such as retrying the access may retrieve the data.
-</para></listitem>
-<listitem><para>
-unrecoverable: try as it may, the disk logic and ECC algorithms
-cannot recover the data. This is often reported as a
-<emphasis>medium error</emphasis>.
-</para></listitem>
-</itemizedlist>
-</para>
-<para>
-Other things can go wrong, typically associated with the transport and
-they will be reported using a term other than
-<emphasis>medium error</emphasis>. For example a disk may decide a read
-operation was successful but a computer's host bus adapter (HBA) checking
-the incoming data detects a CRC error due to a bad cable or termination.
-</para>
-<para>
-Depending on the disk vendor, recoverable errors can be ignored. After all,
-some disks have up to 68 bytes of ECC above the payload size of 512 bytes
-so why use up spare sectors which are limited in number
-<footnote><para>
-Detecting and fixing an error with ECC "on the fly" and not going the further
-step and reassigning the block in question may explain why some disks have
-large numbers in their read error counter log. Various worried users have
-reported large numbers in the "errors corrected without substantial delay"
-counter field which is in the "Errors corrected by ECC fast" column in
-the <command>smartctl -l error</command> output.
-</para></footnote>
-?
-If the disk can recover the data and does decide to re-allocate (reassign)
-a sector, then first it checks the settings of the ARRE and AWRE bits in the
-read-write error recovery mode page. Usually these bits are set
-<footnote><para>
-Often disks inside a hardware RAID have the ARRE and AWRE bits
-cleared (disabled) so the RAID controller can do things manually or flag
-the disk for replacement.
-</para></footnote>
-enabling automatic (read or write) re-allocation. The automatic
-re-allocation may also fail if the zone (or disk) has run out of spare
-sectors.
-</para>
-<para>
-Another consideration with RAIDs, and applications that require a high
-data rate without pauses, is that the controller logic may not want a
-disk to spend too long trying to recover an error.
-</para>
-<para>
-Unrecoverable errors will cause a <emphasis>medium error</emphasis> sense
-key, perhaps with some useful additional sense information. If the extended
-background self test includes a full disk read scan, one would expect the
-self test log to list the bad block, as shown in the <xref linkend="rfile"/>.
-Recent SCSI disks with a periodic background scan should also list
-unrecoverable read errors (and some recoverable errors as well). The
-advantage of the background scan is that it runs to completion while self
-tests will often terminate at the first serious error.
-</para>
-<para>
-SCSI disks expect unrecoverable errors to be fixed manually using the
-REASSIGN BLOCKS SCSI command since loss of data is involved. It is possible
-that an operating system or a file system could issue the REASSIGN BLOCKS
-command itself but the author is unaware of any examples. The REASSIGN BLOCKS
-command will reassign one or more blocks, attempting to (partially ?) recover
-the data (a forlorn hope at this stage), fetch an unused spare sector from the
-current zone while adding the damaged old sector to the GLIST (hence the
-name "grown" list). The contents of the GLIST may not be that interesting
-but <command>smartctl</command> prints out the number of entries in the grown
-list and if that number grows quickly, the disk may be approaching the end
-of its useful life.
-</para>
-<para>
-Here is an alternate brute force technique to consider: if the data on the
-SCSI or ATA disk has all been backed up (e.g. is held on the other disks in
-a RAID 5 enclosure), then simply reformatting the disk may be the least
-cumbersome approach.
-</para>
-</sect2>
-
-  <sect2 id="sexample">
-      <title>Example</title>
-<para>
-Given a "bad block", it still may be useful to look at the
-<command>fdisk</command> command (if the disk has multiple partitions)
-to find out which partition is involved, then use
-<command>debugfs</command> (or a similar tool for the file system in
-question) to find out which, if any, file or other part of the file system
-may have been damaged. This is discussed in the <xref linkend="rfile"/>.
-</para>
-<para>
-Then a program that can execute the REASSIGN BLOCKS SCSI command is
-required. In Linux (2.4 and 2.6 series), FreeBSD, Tru64(OSF) and Windows
-the author's <command>sg_reassign</command> utility in the sg3_utils
-package can be used. Also found in that package is
-<command>sg_verify</command> which can be used to check that a block is
-readable.
-</para>
-<para>
-Assume that logical block address 1193046 (which is 123456 in hex) is
-corrupt
-<footnote><para>
-In this case the corruption was manufactured by using the WRITE LONG
-SCSI command. See <command>sg_write_long</command> in sg3_utils.
-</para></footnote>
-on the disk at <filename>/dev/sdb</filename>. A long selftest command like
-<command>smartctl -t long /dev/sdb</command> may result in log results
-like this:
-<programlisting>
-# smartctl -l selftest /dev/sdb
-smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-
-SMART Self-test log
-Num  Test              Status            segment  LifeTime  LBA_first_err [SK ASC ASQ]
-     Description                         number   (hours)
-# 1  Background long   Failed in segment      -     354           1193046 [0x3 0x11 0x0]
-# 2  Background short  Completed              -     323                 - [-   -    -]
-# 3  Background short  Completed              -     194                 - [-   -    -]
-</programlisting>
-</para>
-<para>
-The <command>sg_verify</command> utility can be used to confirm that there
-is a problem at that address:
-<programlisting>
-# sg_verify --lba=1193046 /dev/sdb
-verify (10):  Fixed format, current;  Sense key: Medium Error
- Additional sense: Unrecovered read error
-  Info fld=0x123456 [1193046]
-  Field replaceable unit code: 228
-  Actual retry count: 0x008b
-medium or hardware error, reported lba=0x123456
-</programlisting>
-</para>
-<para>
-Now the GLIST length is checked before the block reassignment:
-<programlisting>
-# sg_reassign --grown /dev/sdb
->> Elements in grown defect list: 0
-</programlisting>
-</para>
-<para>
-And now for the actual reassignment followed by another check of the GLIST
-length:
-<programlisting>
-# sg_reassign --address=1193046 /dev/sdb
-
-# sg_reassign --grown /dev/sdb
->> Elements in grown defect list: 1
-</programlisting>
-</para>
-<para>
-The GLIST length has grown by one as expected. If the disk was unable to
-recover any data, then the "new" block at lba 0x123456 has vendor specific
-data in it. The <command>sg_reassign</command> utility can also do bulk
-reassigns, see <command>man sg_reassign</command> for more information.
-</para>
-<para>
-The <command>dd</command> command could be used to read the contents of
-the "new" block:
-<programlisting>
-# dd if=/dev/sdb iflag=direct skip=1193046 of=blk.img bs=512 count=1
-</programlisting>
-</para>
-<para>
-and a hex editor
-<footnote><para>
-Most window managers have a handy calculator that will do hex to
-decimal conversions. More work may be needed at the file system level,
-</para></footnote>
-used to view and potentially change the
-<filename>blk.img</filename> file. An altered <filename>blk.img</filename>
-file (or <filename>/dev/zero</filename>) could be written back with:
-<programlisting>
-# dd if=blk.img of=/dev/sdb seek=1193046 oflag=direct bs=512 count=1
-</programlisting>
-</para>
-<para>
-More work may be needed at the file system level, especially if the
-reassigned block held critical file system information such as
-a superblock or a directory.
-</para>
-<para>
-Even if a full backup of the disk is available, or the disk has been
-"ejected" from a RAID, it may still be worthwhile to reassign the bad
-block(s) that caused the problem (or simply format the disk (see
-<command>sg_format</command> in the sg3_utils package)) and re-use the
-disk later (not unlike the way a replacement disk from a manufacturer
-might be used).
-</para>
-<para>
-CVS $Id: badblockhowto.xml,v 1.1 2006/11/16 02:19:58 dpgilbert Exp $
-</para>
-</sect2>
-</sect1>
-
-<!--
-<appendix id="appendix">
-      <title>annex a</title>
-<sect1 id="what">
-      <title>what</title>
-<para>
-dummy
-</para>
-
-<para>
-CVS $Id: badblockhowto.xml,v 1.1 2006/11/16 02:19:58 dpgilbert Exp $
-</para>
-</sect1>
-</appendix>
-
--->
-
-</article>
diff --git a/www/cvs-script b/www/cvs-script
deleted file mode 100755
index 52cbaea9b36a4f7048b65a3ea20700e378de7c47..0000000000000000000000000000000000000000
--- a/www/cvs-script
+++ /dev/null
@@ -1,6 +0,0 @@
-#!/bin/bash
-# execute this script in the current shell, using for example
-# . cvs_script
-unset CVS_SERVER
-export CVS_RSH=ssh
-export CVSROOT=:ext:ballen4705@smartmontools.cvs.sourceforge.net:/cvsroot/smartmontools
diff --git a/www/examples/FUJITSU1.txt b/www/examples/FUJITSU1.txt
deleted file mode 100644
index b10abf7a3b232514e1133510003645544d3ad932..0000000000000000000000000000000000000000
--- a/www/examples/FUJITSU1.txt
+++ /dev/null
@@ -1,80 +0,0 @@
-[root/]# smartctl -v 9,seconds -v 200,writeerrorcount /dev/hda
-
-smartctl version 5.1-18 Copyright (C) 2002-3 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     FUJITSU MHR2040AT
-Serial Number:    NJ41T291391J
-Firmware Version: 40BA
-Device is:        Not in smartctl database [for details use: -P showall]
-ATA Version is:   6
-ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 1
-Local Time is:    Thu Sep  4 22:18:48 2003 CEST
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: FAILED!
-Drive failure expected in less than 24 hours. SAVE ALL DATA.
-See vendor-specific Attribute list for failed Attributes.
-
-General SMART Values:
-Off-line data collection status: (0x00)	Offline data collection activity was
-					never started.
-					Auto Off-line Data Collection: Disabled.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 ( 468) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-					No Conveyance Self-test supported.
-					No Selective Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-					No General Purpose Logging support.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine
-recommended polling time: 	 (  60) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000f   100   100   046    Pre-fail  Always       -       52685626284
-  2 Throughput_Performance  0x0005   100   100   020    Pre-fail  Offline      -       0
-  3 Spin_Up_Time            0x0003   093   093   025    Pre-fail  Always       -       24065
-  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       160
-  5 Reallocated_Sector_Ct   0x0033   099   099   024    Pre-fail  Always       -       31
-  7 Seek_Error_Rate         0x000f   100   100   047    Pre-fail  Always       -       131071
-  8 Seek_Time_Performance   0x0005   100   100   019    Pre-fail  Offline      -       0
-  9 Power_On_Seconds        0x0032   092   092   000    Old_age   Always       -       1335h+10m+34s
- 10 Spin_Retry_Count        0x0013   100   100   020    Pre-fail  Always       -       0
- 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       150
-192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       7
-193 Load_Cycle_Count        0x0032   074   074   000    Old_age   Always       -       95890
-194 Temperature_Celsius     0x0022   090   100   000    Old_age   Always       -       57
-195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       10141348
-196 Reallocated_Event_Count 0x0032   099   099   000    Old_age   Always       -       30
-197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
-198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
-199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
-200 Write_Error_Count       0x000f   036   033   060    Pre-fail  Always   FAILING_NOW 2883583
-203 Run_Out_Cancel          0x0002   091   091   000    Old_age   Always       -       2589872160305
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log structure revision number 1
-No self-tests have been logged
-
-
diff --git a/www/examples/FUJITSU_MHR2020AT.txt b/www/examples/FUJITSU_MHR2020AT.txt
deleted file mode 100644
index 4f8dc82b9c5b6858e849cf8e682dbe855fdb0c53..0000000000000000000000000000000000000000
--- a/www/examples/FUJITSU_MHR2020AT.txt
+++ /dev/null
@@ -1,158 +0,0 @@
-smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     FUJITSU MHR2020AT
-Serial Number:    NJ13T2215TUH
-Firmware Version: 30B8
-Device is:        Not in smartctl database [for details use: -P showall]
-ATA Version is:   6
-ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 1
-Local Time is:    Sun Aug 15 13:21:33 2004 MEST
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: FAILED!
-Drive failure expected in less than 24 hours. SAVE ALL DATA.
-See vendor-specific Attribute list for failed Attributes.
-
-General SMART Values:
-Offline data collection status:  (0x00)	Offline data collection activity
-					was never started.
-					Auto Offline Data Collection: Disabled.
-Self-test execution status:      ( 105)	The previous self-test completed having
-					the servo (and/or seek) element of the 
-					test failed.
-Total time to complete Offline 
-data collection: 		 ( 234) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Auto Offline data collection on/off support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-					No Conveyance Self-test supported.
-					No Selective Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-					No General Purpose Logging support.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine
-recommended polling time: 	 (  30) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000f   007   001   046    Pre-fail  Always   FAILING_NOW 154618843423
-  2 Throughput_Performance  0x0005   100   100   020    Pre-fail  Offline      -       145
-  3 Spin_Up_Time            0x0003   094   083   025    Pre-fail  Always       -       24321
-  4 Start_Stop_Count        0x0032   097   097   000    Old_age   Always       -       1887
-  5 Reallocated_Sector_Ct   0x0033   099   099   024    Pre-fail  Always       -       1
-  7 Seek_Error_Rate         0x000f   100   100   047    Pre-fail  Always       -       458751
-  8 Seek_Time_Performance   0x0005   100   100   019    Pre-fail  Offline      -       0
-  9 Power_On_Seconds        0x0032   088   088   000    Old_age   Always       -       1819h+16m+52s
- 10 Spin_Retry_Count        0x0013   100   100   020    Pre-fail  Always       -       0
- 12 Power_Cycle_Count       0x0032   091   091   000    Old_age   Always       -       1467
-192 Power-Off_Retract_Count 0x0032   099   099   000    Old_age   Always       -       44
-193 Load_Cycle_Count        0x0032   086   086   000    Old_age   Always       -       49810
-194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       32
-195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       1221
-196 Reallocated_Event_Count 0x0032   099   099   000    Old_age   Always       -       1
-197 Current_Pending_Sector  0x0012   001   001   000    Old_age   Always       -       10
-198 Offline_Uncorrectable   0x0010   092   092   000    Old_age   Offline      -       17
-199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
-200 Multi_Zone_Error_Rate   0x000f   100   100   060    Pre-fail  Always       -       393215
-203 Run_Out_Cancel          0x0002   100   100   000    Old_age   Always       -       429515210380
-
-SMART Error Log Version: 1
-ATA Error Count: 6861 (device log contains only the most recent five errors)
-	CR = Command Register [HEX]
-	FR = Features Register [HEX]
-	SC = Sector Count Register [HEX]
-	SN = Sector Number Register [HEX]
-	CL = Cylinder Low Register [HEX]
-	CH = Cylinder High Register [HEX]
-	DH = Device/Head Register [HEX]
-	DC = Device Command Register [HEX]
-	ER = Error register [HEX]
-	ST = Status register [HEX]
-Powered_Up_Time is measured from power on, and printed as
-DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
-SS=sec, and sss=millisec. It "wraps" after 49.710 days.
-
-Error 6861 occurred at disk power-on lifetime: 1818 hours (75 days + 18 hours)
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 59 8b 7d 16 51 f0  Error: UNC 139 sectors at LBA = 0x0051167d = 5314173
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-  -- -- -- -- -- -- -- --  ----------------  --------------------
-  25 00 90 78 16 51 f0 00      08:22:32.857  READ DMA EXT
-
-Error 6860 occurred at disk power-on lifetime: 1818 hours (75 days + 18 hours)
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 59 8b 7d 16 51 f0  Error: UNC 139 sectors at LBA = 0x0051167d = 5314173
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-  -- -- -- -- -- -- -- --  ----------------  --------------------
-  25 00 98 70 16 51 f0 00      08:22:27.700  READ DMA EXT
-
-Error 6859 occurred at disk power-on lifetime: 1818 hours (75 days + 18 hours)
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 59 8b 7d 16 51 f0  Error: UNC 139 sectors at LBA = 0x0051167d = 5314173
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-  -- -- -- -- -- -- -- --  ----------------  --------------------
-  25 00 a0 68 16 51 f0 00      08:22:22.558  READ DMA EXT
-
-Error 6858 occurred at disk power-on lifetime: 1818 hours (75 days + 18 hours)
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 59 8b 7d 16 51 f0  Error: UNC 139 sectors at LBA = 0x0051167d = 5314173
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-  -- -- -- -- -- -- -- --  ----------------  --------------------
-  25 00 a8 60 16 51 f0 00      08:22:17.458  READ DMA EXT
-
-Error 6857 occurred at disk power-on lifetime: 1818 hours (75 days + 18 hours)
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 59 8b 7d 16 51 f0  Error: UNC 139 sectors at LBA = 0x0051167d = 5314173
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-  -- -- -- -- -- -- -- --  ----------------  --------------------
-  25 00 b0 58 16 51 f0 00      08:22:12.558  READ DMA EXT
-
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Short offline       Completed: servo/seek failure 90%      1819         -
-# 2  Extended offline    Completed: servo/seek failure 90%      1816         -
-
-Device does not support Selective Self Tests/Logging
diff --git a/www/examples/HITACHI_DK23AA-12B.txt b/www/examples/HITACHI_DK23AA-12B.txt
deleted file mode 100644
index 6f9b62e60cff0d5751ceceeae48873b665319356..0000000000000000000000000000000000000000
--- a/www/examples/HITACHI_DK23AA-12B.txt
+++ /dev/null
@@ -1,173 +0,0 @@
-smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     HITACHI_DK23AA-12B
-Serial Number:    xxxxxx
-Firmware Version: 00XDA0B6
-Device is:        Not in smartctl database [for details use: -P showall]
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-Local Time is:    Sat Apr 24 17:19:58 2004 EST
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: FAILED!
-Drive failure expected in less than 24 hours. SAVE ALL DATA.
-See vendor-specific Attribute list for failed Attributes.
-
-General SMART Values:
-Offline data collection status:  (0x00)	Offline data collection activity was
-					never started.
-					Auto Offline Data Collection: Disabled.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete Offline 
-data collection: 		 (1110) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Auto Offline data collection on/off support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-					No Conveyance Self-test supported.
-					No Selective Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-					No General Purpose Logging support.
-Short self-test routine 
-recommended polling time: 	 (   1) minutes.
-Extended self-test routine
-recommended polling time: 	 (  19) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000d   099   099   050    Pre-fail  Offline      -       68719476757
-  4 Start_Stop_Count        0x0032   097   097   050    Old_age   Always       -       3259
-  5 Reallocated_Sector_Ct   0x0033   001   001   010    Pre-fail  Always   FAILING_NOW 1876
-  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       760
-  9 Power_On_Hours          0x0032   090   090   060    Old_age   Always       -       21783
- 10 Spin_Retry_Count        0x0013   100   100   050    Pre-fail  Always       -       0
-196 Reallocated_Event_Count 0x0032   001   001   001    Old_age   Always   FAILING_NOW 254
-197 Current_Pending_Sector  0x0032   097   093   001    Old_age   Always       -       3
-198 Offline_Uncorrectable   0x0010   100   100   001    Old_age   Offline      -       0
-199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
-221 G-Sense_Error_Rate      0x000a   100   100   050    Old_age   Always       -       42
-223 Load_Retry_Count        0x0012   100   100   050    Old_age   Always       -       149
-225 Load_Cycle_Count        0x0032   050   050   050    Old_age   Always   FAILING_NOW 5110222858734
-250 Read_Error_Retry_Rate   0x000a   090   001   050    Old_age   Always   In_the_past 103
-
-SMART Error Log Version: 1
-ATA Error Count: 1151 (device log contains only the most recent five errors)
-	CR = Command Register [HEX]
-	FR = Features Register [HEX]
-	SC = Sector Count Register [HEX]
-	SN = Sector Number Register [HEX]
-	CL = Cylinder Low Register [HEX]
-	CH = Cylinder High Register [HEX]
-	DH = Device/Head Register [HEX]
-	DC = Device Command Register [HEX]
-	ER = Error register [HEX]
-	ST = Status register [HEX]
-Timestamp = decimal seconds since the previous disk power-on.
-Note: timestamp "wraps" after 2^32 msec = 49.710 days.
-
-Error 1151 occurred at disk power-on lifetime: 5445 hours
-  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  01 51 01 01 4f c2 e0  Error: obs
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  b0 d5 01 01 4f c2 e0 00   46273.155  SMART READ LOG
-  b0 d1 01 01 4f c2 e0 00   46273.138  SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
-  b0 d0 01 00 4f c2 e0 00   46273.009  SMART READ DATA
-  b0 da 00 00 4f c2 a0 00   46272.881  SMART RETURN STATUS
-  b0 da 00 00 4f c2 e0 00   46272.760  SMART RETURN STATUS
-
-Error 1150 occurred at disk power-on lifetime: 5354 hours
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  01 51 01 56 36 54 e1  Error: AMNF 1 sectors at LBA = 0x01543656 = 22296150
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  c8 00 80 d7 35 54 e1 00    1517.332  READ DMA
-  c8 00 80 57 35 54 e1 00    1517.329  READ DMA
-  ca 00 08 67 1d cb e0 00    1516.014  WRITE DMA
-  ca 00 30 37 1d cb e0 00    1515.992  WRITE DMA
-  ca 00 10 2f e0 ca e0 00    1515.874  WRITE DMA
-
-Error 1149 occurred at disk power-on lifetime: 5352 hours
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  01 51 0c bb c5 57 e1  Error: AMNF 12 sectors at LBA = 0x0157c5bb = 22529467
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  c8 00 20 a7 c5 57 e1 00     380.146  READ DMA
-  10 00 3f 00 00 00 e0 00     380.146  RECALIBRATE [OBS-4]
-  c8 00 20 a7 c5 57 e1 00     377.932  READ DMA
-  c8 00 20 a7 c5 57 e1 00     373.729  READ DMA
-  c8 00 80 6f 41 5f e1 00     371.776  READ DMA
-
-Error 1148 occurred at disk power-on lifetime: 5352 hours
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  01 51 0c bb c5 57 e1  Error: AMNF 12 sectors at LBA = 0x0157c5bb = 22529467
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  c8 00 20 a7 c5 57 e1 00     377.932  READ DMA
-  c8 00 20 a7 c5 57 e1 00     373.729  READ DMA
-  c8 00 80 6f 41 5f e1 00     371.776  READ DMA
-  c8 00 80 ef 40 5f e1 00     371.742  READ DMA
-  ca 00 08 57 1f cb e0 00     371.291  WRITE DMA
-
-Error 1147 occurred at disk power-on lifetime: 5352 hours
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  01 51 0c bb c5 57 e1  Error: AMNF 12 sectors at LBA = 0x0157c5bb = 22529467
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  c8 00 20 a7 c5 57 e1 00     373.729  READ DMA
-  c8 00 80 6f 41 5f e1 00     371.776  READ DMA
-  c8 00 80 ef 40 5f e1 00     371.742  READ DMA
-  ca 00 08 57 1f cb e0 00     371.291  WRITE DMA
-  ca 00 10 47 1f cb e0 00     371.262  WRITE DMA
-
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Short offline       Completed without error       00%      5445         -
-# 2  Short offline       Completed without error       00%      5445         -
-# 3  Short offline       Aborted by host               90%      5445         -
-# 4  Short offline       Completed without error       00%      5445         -
-# 5  Short offline       Completed without error       00%      5445         -
-
diff --git a/www/examples/HITACHI_DK23BA-20-0.txt b/www/examples/HITACHI_DK23BA-20-0.txt
deleted file mode 100644
index 13e9cb0122e0c6e4e072ddfc91efba9d9a4a3d19..0000000000000000000000000000000000000000
--- a/www/examples/HITACHI_DK23BA-20-0.txt
+++ /dev/null
@@ -1,163 +0,0 @@
-[root@ballen www]# /usr/sbin/smartctl -am /dev/hda
-
-smartctl version 5.0-25 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     HITACHI_DK23BA-20                       
-Serial Number:    12H7M8
-Firmware Version: 00E0A0D2
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-See vendor-specific Attribute list for marginal Attributes.
-
-General SMART Values:
-Off-line data collection status: (0x00)	Offline data collection activity was
-					never started.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 (1530) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  26) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000d   100   083   050    Pre-fail     -       677
-  3 Spin_Up_Time            0x0007   100   100   050    Pre-fail     -       0
-  4 Start_Stop_Count        0x0032   100   100   050    Old_age      -       249
-  5 Reallocated_Sector_Ct   0x0033   099   099   010    Pre-fail     -       30
-  7 Seek_Error_Rate         0x000f   100   100   050    Pre-fail     -       319
-  9 Power_On_Hours          0x0032   099   099   060    Old_age      -       701 h + 42 m
- 10 Spin_Retry_Count        0x0013   100   100   050    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   050    Old_age      -       249
-192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age      -       15
-195 Hardware_ECC_Recovered  0x001a   100   001   050    Old_age  In_the_past 559
-196 Reallocated_Event_Count 0x0032   097   097   001    Old_age      -       30
-197 Current_Pending_Sector  0x0032   095   095   001    Old_age      -       5
-198 Offline_Uncorrectable   0x0010   095   095   001    Old_age      -       31
-199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age      -       0
-221 G-Sense_Error_Rate      0x000a   100   100   050    Old_age      -       0
-223 Load_Retry_Count        0x0012   100   100   050    Old_age      -       0
-225 Load_Cycle_Count        0x0032   095   095   050    Old_age      -       18446744072753281791
-230 Unknown_Attribute       0x0032   100   100   060    Old_age      -       18484
-250 Unknown_Attribute       0x000a   100   070   050    Old_age      -       601
-
-SMART Error Log Version: 1
-ATA Error Count: 9 (device log contains only the most recent five errors)
-	DCR = Device Control Register
-	FR  = Features Register
-	SC  = Sector Count Register
-	SN  = Sector Number Register
-	CL  = Cylinder Low Register
-	CH  = Cylinder High Register
-	D/H = Device/Head Register
-	CR  = Content written to Command Register
-	ER  = Error register
-	STA = Status register
-Timestamp is seconds since the previous disk power-on.
-Note: timestamp "wraps" after 2^32 msec = 49.710 days.
-
-Error 1 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: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   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%       691         
-# 2  Extended off-line   Completed: read failure       40%       661         0x002c1985
-# 3  Extended off-line   Completed: read failure       40%       661         0x002c1985
-# 4  Short off-line      Completed                     00%       660         
-# 5  Extended off-line   Completed: read failure       40%       658         0x002c1985
-# 6  Short off-line      Completed                     00%       658         
-# 7  Short off-line      Completed                     00%       658         
-# 8  Extended off-line   Completed: read failure       40%       658         0x002c1985
-# 9  Extended off-line   Completed: read failure       40%       657         0x002c1985
-#10  Short off-line      Completed                     00%       647         
-#11  Short off-line      Completed                     00%       587         
-#12  Short off-line      Completed                     00%       583         
-#13  Short off-line      Completed                     00%       551         
-#14  Short captive       Interrupted (host reset)      40%       551         
-#15  Short off-line      Completed                     00%       551         
-#16  Extended off-line   Completed: read failure       40%       550         0x002c1985
-#17  Extended off-line   Aborted by host               50%       550         
-#18  Short off-line      Completed                     00%       550         
-#19  Short off-line      Completed                     00%       537         
-#20  Extended off-line   Completed: read failure       40%       536         0x002c1985
-#21  Short off-line      Completed                     00%       536         
diff --git a/www/examples/IC35L120AVV207-0.txt b/www/examples/IC35L120AVV207-0.txt
deleted file mode 100644
index 4e43e8c2d0976622c07e0e0cddc4507716f5cca6..0000000000000000000000000000000000000000
--- a/www/examples/IC35L120AVV207-0.txt
+++ /dev/null
@@ -1,67 +0,0 @@
-# smartctl -a /dev/hda
-smartctl version 5.0-45 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     IC35L120AVV207-0                        
-Serial Number:    VNVD02G4G4BDEG
-Firmware Version: V24OA63A
-ATA Version is:   6
-ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 3a
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Off-line data collection status: (0x00)	Offline data collection activity was
-					never started.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 (2855) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   1) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  48) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000b   100   100   060    Pre-fail     -       0
-  2 Throughput_Performance  0x0005   100   100   050    Pre-fail     -       0
-  3 Spin_Up_Time            0x0007   102   102   024    Pre-fail     -       16974103
-  4 Start_Stop_Count        0x0012   100   100   000    Old_age      -       14
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail     -       0
-  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail     -       0
-  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail     -       0
-  9 Power_On_Hours          0x0012   100   100   000    Old_age      -       242
- 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   000    Old_age      -       14
-192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age      -       24
-193 Load_Cycle_Count        0x0012   100   100   050    Old_age      -       24
-194 Temperature_Celsius     0x0002   203   203   000    Old_age      -       27 (Lifetime Min/Max 20/37)
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age      -       0
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age      -       0
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age      -       0
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed                     00%        54         
diff --git a/www/examples/IC35L120AVV207-1.txt b/www/examples/IC35L120AVV207-1.txt
deleted file mode 100644
index 48a69910371771d2fdf0b10b19e3ce0ea3d4aff6..0000000000000000000000000000000000000000
--- a/www/examples/IC35L120AVV207-1.txt
+++ /dev/null
@@ -1,191 +0,0 @@
-smartctl version 5.31 Copyright (C) 2002-4 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     IC35L120AVV207-1
-Serial Number:    VNVD09G4H3HPMT
-Firmware Version: V24OA66A
-Device is:        In smartctl database [for details use: -P show]
-ATA Version is:   6
-ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 3a
-Local Time is:    Tue Jun 15 23:38:56 2004 CDT
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: FAILED!
-Drive failure expected in less than 24 hours. SAVE ALL DATA.
-See vendor-specific Attribute list for failed Attributes.
-
-General SMART Values:
-Offline data collection status:  (0x84)	Offline data collection activity
-					was suspended by an interrupting command from host.
-					Auto Offline Data Collection: Enabled.
-Self-test execution status:      ( 121)	The previous self-test completed having
-					the read element of the test failed.
-Total time to complete Offline 
-data collection: 		 (2855) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Auto Offline data collection on/off support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-					No Conveyance Self-test supported.
-					No Selective Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-					General Purpose Logging supported.
-Short self-test routine 
-recommended polling time: 	 (   1) minutes.
-Extended self-test routine
-recommended polling time: 	 (  48) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000b   089   089   060    Pre-fail  Always       -       1703986
-  2 Throughput_Performance  0x0005   015   015   050    Pre-fail  Offline  FAILING_NOW 5518
-  3 Spin_Up_Time            0x0007   100   100   024    Pre-fail  Always       -       278
-  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       9
-  5 Reallocated_Sector_Ct   0x0033   091   091   005    Pre-fail  Always       -       277
-  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
-  8 Seek_Time_Performance   0x0005   123   123   020    Pre-fail  Offline      -       37
-  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       2759
- 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
- 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       9
-192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       45
-193 Load_Cycle_Count        0x0012   100   100   050    Old_age   Always       -       45
-194 Temperature_Celsius     0x0002   166   166   000    Old_age   Always       -       33 (Lifetime Min/Max 23/44)
-196 Reallocated_Event_Count 0x0032   092   092   000    Old_age   Always       -       319
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       49
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       20
-199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
-
-SMART Error Log Version: 1
-ATA Error Count: 161 (device log contains only the most recent five errors)
-	CR = Command Register [HEX]
-	FR = Features Register [HEX]
-	SC = Sector Count Register [HEX]
-	SN = Sector Number Register [HEX]
-	CL = Cylinder Low Register [HEX]
-	CH = Cylinder High Register [HEX]
-	DH = Device/Head Register [HEX]
-	DC = Device Command Register [HEX]
-	ER = Error register [HEX]
-	ST = Status register [HEX]
-Powered_Up_Time is measured from power on, and printed as
-DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
-SS=sec, and sss=millisec. It "wraps" after 49.710 days.
-
-Error 161 occurred at disk power-on lifetime: 2752 hours (114 days + 16 hours)
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 46 c2 a7 02 e0  Error: UNC 70 sectors at LBA = 0x0002a7c2 = 174018
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-  -- -- -- -- -- -- -- --  ----------------  --------------------
-  25 00 46 c2 a7 02 e0 00  23d+03:19:20.800  READ DMA EXT
-  25 00 48 c0 a7 02 e0 00  23d+03:19:16.000  READ DMA EXT
-  25 00 1c a4 a7 02 e0 00  23d+03:19:15.200  READ DMA EXT
-  25 00 1e a2 a7 02 e0 00  23d+03:19:10.400  READ DMA EXT
-  25 00 20 a0 a7 02 e0 00  23d+03:19:02.200  READ DMA EXT
-
-Error 160 occurred at disk power-on lifetime: 2752 hours (114 days + 16 hours)
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 47 c1 a7 02 e0  Error: UNC 71 sectors at LBA = 0x0002a7c1 = 174017
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-  -- -- -- -- -- -- -- --  ----------------  --------------------
-  25 00 48 c0 a7 02 e0 00  23d+03:19:16.000  READ DMA EXT
-  25 00 1c a4 a7 02 e0 00  23d+03:19:15.200  READ DMA EXT
-  25 00 1e a2 a7 02 e0 00  23d+03:19:10.400  READ DMA EXT
-  25 00 20 a0 a7 02 e0 00  23d+03:19:02.200  READ DMA EXT
-  25 00 22 9e a7 02 e0 00  23d+03:18:57.400  READ DMA EXT
-
-Error 159 occurred at disk power-on lifetime: 2752 hours (114 days + 16 hours)
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 02 be a7 02 e0  Error: UNC 2 sectors at LBA = 0x0002a7be = 174014
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-  -- -- -- -- -- -- -- --  ----------------  --------------------
-  25 00 1e a2 a7 02 e0 00  23d+03:19:10.400  READ DMA EXT
-  25 00 20 a0 a7 02 e0 00  23d+03:19:02.200  READ DMA EXT
-  25 00 22 9e a7 02 e0 00  23d+03:18:57.400  READ DMA EXT
-  25 00 24 9c a7 02 e0 00  23d+03:18:52.400  READ DMA EXT
-  25 00 26 9a a7 02 e0 00  23d+03:18:40.200  READ DMA EXT
-
-Error 158 occurred at disk power-on lifetime: 2752 hours (114 days + 16 hours)
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 02 be a7 02 e0  Error: UNC 2 sectors at LBA = 0x0002a7be = 174014
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-  -- -- -- -- -- -- -- --  ----------------  --------------------
-  25 00 20 a0 a7 02 e0 00  23d+03:19:02.200  READ DMA EXT
-  25 00 22 9e a7 02 e0 00  23d+03:18:57.400  READ DMA EXT
-  25 00 24 9c a7 02 e0 00  23d+03:18:52.400  READ DMA EXT
-  25 00 26 9a a7 02 e0 00  23d+03:18:40.200  READ DMA EXT
-  25 00 28 98 a7 02 e0 00  23d+03:18:32.100  READ DMA EXT
-
-Error 157 occurred at disk power-on lifetime: 2752 hours (114 days + 16 hours)
-  When the command that caused the error occurred, the device was active or idle.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 03 bd a7 02 e0  Error: UNC 3 sectors at LBA = 0x0002a7bd = 174013
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
-  -- -- -- -- -- -- -- --  ----------------  --------------------
-  25 00 22 9e a7 02 e0 00  23d+03:18:57.400  READ DMA EXT
-  25 00 24 9c a7 02 e0 00  23d+03:18:52.400  READ DMA EXT
-  25 00 26 9a a7 02 e0 00  23d+03:18:40.200  READ DMA EXT
-  25 00 28 98 a7 02 e0 00  23d+03:18:32.100  READ DMA EXT
-  25 00 2a 96 a7 02 e0 00  23d+03:18:26.400  READ DMA EXT
-
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed: read failure       90%      2692         173893
-# 2  Short offline       Completed: read failure       10%      2654         173911
-# 3  Extended offline    Completed: read failure       90%      2524         174132
-# 4  Extended offline    Completed without error       00%      2358         -
-# 5  Extended offline    Completed without error       00%      2192         -
-# 6  Extended offline    Completed without error       00%      2023         -
-# 7  Extended offline    Completed without error       00%      1857         -
-# 8  Extended offline    Completed without error       00%      1689         -
-# 9  Extended offline    Completed without error       00%      1521         -
-#10  Extended offline    Completed without error       00%      1355         -
-#11  Extended offline    Completed without error       00%      1187         -
-#12  Extended offline    Completed without error       00%      1020         -
-#13  Extended offline    Completed without error       00%       854         -
-#14  Extended offline    Completed without error       00%       685         -
-#15  Extended offline    Completed without error       00%       517         -
-#16  Extended offline    Completed without error       00%       349         -
-#17  Extended offline    Completed without error       00%       181         -
-#18  Extended offline    Completed without error       00%        13         -
-#19  Extended offline    Completed without error       00%         4         -
-
-Device does not support Selective Self Tests/Logging
diff --git a/www/examples/IC35L120AVVA07-0-0.txt b/www/examples/IC35L120AVVA07-0-0.txt
deleted file mode 100644
index 57926ccfba480e32daeec54bd0011e23ffdfc5e3..0000000000000000000000000000000000000000
--- a/www/examples/IC35L120AVVA07-0-0.txt
+++ /dev/null
@@ -1,69 +0,0 @@
-smartctl version 5.0-24 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     IC35L120AVVA07-0                        
-Serial Number:    VNC605A6GG8W8A
-Firmware Version: VA6OA52A
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Off-line data collection status: (0x00)	Offline data collection activity was
-					never started.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 (3399) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   1) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  57) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000b   100   100   060    Pre-fail     -       0
-  2 Throughput_Performance  0x0005   147   147   050    Pre-fail     -       266
-  3 Spin_Up_Time            0x0007   093   093   024    Pre-fail     -       23593335
-  4 Start_Stop_Count        0x0012   100   100   000    Old_age      -       13
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail     -       0
-  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail     -       0
-  8 Seek_Time_Performance   0x0005   138   138   020    Pre-fail     -       30
-  9 Power_On_Hours          0x0012   100   100   000    Old_age      -       554
- 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   000    Old_age      -       13
-192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age      -       36
-193 Load_Cycle_Count        0x0012   100   100   050    Old_age      -       36
-194 Temperature_Centigrade  0x0002   183   183   000    Old_age      -       30 (Lifetime Min/Max 23/39)
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age      -       0
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age      -       0
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age      -       0
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed                     00%       492         
-# 2  Short off-line      Completed                     00%       296         
-# 3  Extended off-line   Completed                     00%       169         
-# 4  Short off-line      Completed                     00%       168         
diff --git a/www/examples/IC35L120AVVA07-0-1.txt b/www/examples/IC35L120AVVA07-0-1.txt
deleted file mode 100644
index 992a620cec64e49651e672bbf8da46d9f6a57e77..0000000000000000000000000000000000000000
--- a/www/examples/IC35L120AVVA07-0-1.txt
+++ /dev/null
@@ -1,67 +0,0 @@
-smartctl version 5.0-24 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     IC35L120AVVA07-0                        
-Serial Number:    VNC605A6GEWZDA
-Firmware Version: VA6OA52A
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Off-line data collection status: (0x00)	Offline data collection activity was
-					never started.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 (3399) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   1) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  57) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000b   100   100   060    Pre-fail     -       0
-  2 Throughput_Performance  0x0005   100   100   050    Pre-fail     -       0
-  3 Spin_Up_Time            0x0007   098   098   024    Pre-fail     -       22348126
-  4 Start_Stop_Count        0x0012   100   100   000    Old_age      -       13
-  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail     -       0
-  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail     -       0
-  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail     -       0
-  9 Power_On_Hours          0x0012   100   100   000    Old_age      -       554
- 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   000    Old_age      -       13
-192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age      -       36
-193 Load_Cycle_Count        0x0012   100   100   050    Old_age      -       36
-194 Temperature_Centigrade  0x0002   189   189   000    Old_age      -       29 (Lifetime Min/Max 23/36)
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age      -       0
-197 Current_Pending_Sector  0x0022   100   100   000    Old_age      -       0
-198 Offline_Uncorrectable   0x0008   100   100   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age      -       0
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed                     00%       492         
-# 2  Extended off-line   Completed                     00%       169         
diff --git a/www/examples/MAXTOR-0.txt b/www/examples/MAXTOR-0.txt
deleted file mode 100644
index 13e0eb28e95d5c7d703ac975814277c44d1c525c..0000000000000000000000000000000000000000
--- a/www/examples/MAXTOR-0.txt
+++ /dev/null
@@ -1,139 +0,0 @@
-smartctl version 5.0-24 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     MAXTOR 4K080H4                          
-Serial Number:    674205306226        
-Firmware Version: A08.1500
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Off-line data collection status: (0x02)	Offline data collection activity 
-					completed without error.
-Self-test execution status:      ( 112)	The previous self-test completed having
-					the read element of the test failed.
-Total time to complete off-line 
-data collection: 		 (  44) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  50) minutes.
-
-SMART Attributes Data Structure revision number: 11
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x0029   100   253   020    Pre-fail     -       0
-  3 Spin_Up_Time            0x0027   077   077   020    Pre-fail     -       2909
-  4 Start_Stop_Count        0x0032   100   100   008    Old_age      -       29
-  5 Reallocated_Sector_Ct   0x0033   100   100   020    Pre-fail     -       1
-  7 Seek_Error_Rate         0x000b   100   100   023    Pre-fail     -       0
-  9 Power_On_Hours          0x0012   097   097   001    Old_age      -       1992
- 10 Spin_Retry_Count        0x0026   100   100   000    Old_age      -       0
- 11 Calibration_Retry_Count 0x0013   100   100   020    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   008    Old_age      -       29
- 13 Read_Soft_Error_Rate    0x000b   100   100   023    Pre-fail     -       0
-194 Temperature_Centigrade  0x0022   093   090   042    Old_age      -       19
-195 Hardware_ECC_Recovered  0x001a   100   006   000    Old_age      -       7683906
-196 Reallocated_Event_Count 0x0010   099   099   020    Old_age      -       1
-197 Current_Pending_Sector  0x0032   100   100   020    Old_age      -       1
-198 Offline_Uncorrectable   0x0010   100   100   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x001a   198   198   000    Old_age      -       2
-
-SMART Error Log Version: 1
-ATA Error Count: 11 (device log contains only the most recent five errors)
-	DCR = Device Control Register
-	FR  = Features Register
-	SC  = Sector Count Register
-	SN  = Sector Number Register
-	CL  = Cylinder Low Register
-	CH  = Cylinder High Register
-	D/H = Device/Head Register
-	CR  = Content written to Command Register
-	ER  = Error register
-	STA = Status register
-Timestamp is seconds since the previous disk power-on.
-Note: timestamp "wraps" after 2^32 msec = 49.710 days.
-
-Error 1 occurred at disk power-on lifetime: 1029 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:40 SC:02 SN:41 CL:2d CH:70 D/H:e8 ST:d1
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 70   08   02   41   2d   70    e8   c4     90.713
- 70   08   04   3f   2d   70    e8   c4     86.648
- 70   08   06   3d   2d   70    e8   c4     82.584
- 70   08   08   3b   2d   70    e8   c4     78.342
- 28   08   04   8b   2c   28    e8   c5     78.341
-
-Error 2 occurred at disk power-on lifetime: 1029 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:40 SC:04 SN:3f CL:2d CH:70 D/H:e8 ST:d1
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 70   08   04   3f   2d   70    e8   c4     86.648
- 70   08   06   3d   2d   70    e8   c4     82.584
- 70   08   08   3b   2d   70    e8   c4     78.342
- 28   08   04   8b   2c   28    e8   c5     78.341
- 28   08   08   4b   2c   28    e8   c5     78.339
-
-Error 3 occurred at disk power-on lifetime: 1029 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:40 SC:06 SN:3d CL:2d CH:70 D/H:e8 ST:d1
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 70   08   06   3d   2d   70    e8   c4     82.584
- 70   08   08   3b   2d   70    e8   c4     78.342
- 28   08   04   8b   2c   28    e8   c5     78.341
- 28   08   08   4b   2c   28    e8   c5     78.339
- 28   08   08   0b   2c   28    e8   c5     78.338
-
-Error 4 occurred at disk power-on lifetime: 1029 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:40 SC:08 SN:3b CL:2d CH:70 D/H:e8 ST:d1
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 70   08   08   3b   2d   70    e8   c4     78.342
- 28   08   04   8b   2c   28    e8   c5     78.341
- 28   08   08   4b   2c   28    e8   c5     78.339
- 28   08   08   0b   2c   28    e8   c5     78.338
- 28   08   08   cb   2b   28    e8   c5     78.337
-
-Error 5 occurred at disk power-on lifetime: 1029 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:40 SC:66 SN:41 CL:2d CH:70 D/H:e8 ST:d1
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 70   08   66   41   2d   70    e8   c4     69.020
- 70   08   68   3f   2d   70    e8   c4     64.956
- 70   08   6a   3d   2d   70    e8   c4     60.891
- 70   08   6c   3b   2d   70    e8   c4     56.826
- 70   08   fe   a9   2c   70    e8   c4     52.713
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed: read failure       90%      1965         0x08702f11
-# 2  Short off-line      Completed                     00%      1800         
-# 3  Short off-line      Completed                     00%      1778         
-# 4  Short off-line      Completed                     00%      1777         
diff --git a/www/examples/MAXTOR-1.txt b/www/examples/MAXTOR-1.txt
deleted file mode 100644
index b1ed8ace35f6f00813087682bb8b1d9177b3ad2f..0000000000000000000000000000000000000000
--- a/www/examples/MAXTOR-1.txt
+++ /dev/null
@@ -1,143 +0,0 @@
-smartctl version 5.0-24 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     MAXTOR 4K080H4                          
-Serial Number:    674119123435        
-Firmware Version: A08.1500
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: FAILED!
-Drive failure expected in less than 24 hours. SAVE ALL DATA.
-See vendor-specific Attribute list for failed Attributes.
-
-General SMART Values:
-Off-line data collection status: (0x04)	Offline data collection activity was 
-					suspended by an interrupting command from host.
-Self-test execution status:      (  89)	The previous self-test completed having
-					the electrical element of the test
-					failed.
-Total time to complete off-line 
-data collection: 		 (2536) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  50) minutes.
-
-SMART Attributes Data Structure revision number: 11
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x0029   100   253   020    Pre-fail     -       0
-  3 Spin_Up_Time            0x0027   074   074   020    Pre-fail     -       3294
-  4 Start_Stop_Count        0x0032   100   100   008    Old_age      -       32
-  5 Reallocated_Sector_Ct   0x0033   001   001   020    Pre-fail FAILING_NOW 499
-  7 Seek_Error_Rate         0x000b   100   001   023    Pre-fail In_the_past 0
-  9 Power_On_Hours          0x0012   086   086   001    Old_age      -       9812
- 10 Spin_Retry_Count        0x0026   100   100   000    Old_age      -       0
- 11 Calibration_Retry_Count 0x0013   100   100   020    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   008    Old_age      -       32
- 13 Read_Soft_Error_Rate    0x000b   100   001   023    Pre-fail In_the_past 0
-194 Temperature_Centigrade  0x0022   091   086   042    Old_age      -       24
-195 Hardware_ECC_Recovered  0x001a   006   004   000    Old_age      -       417912090
-196 Reallocated_Event_Count 0x0010   100   100   020    Old_age      -       0
-197 Current_Pending_Sector  0x0032   033   032   020    Old_age      -       338
-198 Offline_Uncorrectable   0x0010   100   100   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x001a   200   200   000    Old_age      -       0
-
-SMART Error Log Version: 1
-ATA Error Count: 20255 (device log contains only the most recent five errors)
-	DCR = Device Control Register
-	FR  = Features Register
-	SC  = Sector Count Register
-	SN  = Sector Number Register
-	CL  = Cylinder Low Register
-	CH  = Cylinder High Register
-	D/H = Device/Head Register
-	CR  = Content written to Command Register
-	ER  = Error register
-	STA = Status register
-Timestamp is seconds since the previous disk power-on.
-Note: timestamp "wraps" after 2^32 msec = 49.710 days.
-
-Error 1 occurred at disk power-on lifetime: 9574 hours
-When the command that caused the error occurred, the device was in a vendor specific or reserved state.
-After command completion occurred, registers were:
-ER:40 SC:60 SN:b8 CL:c6 CH:02 D/H:e5 ST:d1
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 02   05   60   b8   c6   02    e5   c4     474.857
- 02   05   f8   20   c6   02    e5   c4     470.748
- 02   05   08   18   c6   02    e5   c4     470.746
- 00   00   f8   20   c5   02    e5   c4     470.732
- 00   00   08   18   c5   02    e5   c4     470.730
-
-Error 2 occurred at disk power-on lifetime: 9574 hours
-When the command that caused the error occurred, the device was in a vendor specific or reserved state.
-After command completion occurred, registers were:
-ER:40 SC:68 SN:b0 CL:c6 CH:02 D/H:e5 ST:d1
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 02   05   f8   20   c6   02    e5   c4     470.748
- 02   05   08   18   c6   02    e5   c4     470.746
- 00   00   f8   20   c5   02    e5   c4     470.732
- 00   00   08   18   c5   02    e5   c4     470.730
- 02   05   f8   20   c4   02    e5   c4     470.717
-
-Error 3 occurred at disk power-on lifetime: 9574 hours
-When the command that caused the error occurred, the device was in a vendor specific or reserved state.
-After command completion occurred, registers were:
-ER:40 SC:08 SN:c0 CL:3e CH:0e D/H:e5 ST:d1
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 0e   05   08   c0   3e   0e    e5   c4     181.677
- d0   04   08   b0   67   d0    e4   c5     181.651
- 0e   05   08   a0   45   0e    e5   c4     181.646
- 0e   05   80   20   43   0e    e5   c4     181.635
- 0e   05   80   20   41   0e    e5   c4     181.622
-
-Error 4 occurred at disk power-on lifetime: 9574 hours
-When the command that caused the error occurred, the device was in a vendor specific or reserved state.
-After command completion occurred, registers were:
-ER:40 SC:60 SN:c0 CL:3e CH:0e D/H:e5 ST:d1
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 0e   05   80   a0   3e   0e    e5   c4     172.530
- 0e   05   80   20   3d   0e    e5   c4     172.335
- 0e   05   80   20   3c   0e    e5   c4     164.744
- 0e   05   10   10   3b   0e    e5   c4     164.736
- 0e   05   f8   18   3a   0e    e5   c4     157.202
-
-Error 5 occurred at disk power-on lifetime: 9574 hours
-When the command that caused the error occurred, the device was in a vendor specific or reserved state.
-After command completion occurred, registers were:
-ER:40 SC:c0 SN:18 CL:04 CH:d3 D/H:e4 ST:d1
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- d3   04   c0   18   04   d3    e4   c4     502.837
- d3   04   f8   e0   03   d3    e4   c4     498.739
- d3   04   f8   e8   02   d3    e4   c4     498.716
- 55   01   c8   90   70   55    e1   c4     498.705
- 55   01   38   48   70   55    e1   c4     498.680
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Short off-line      Completed: electrical failure 90%      9786         
-# 2  Extended captive    Completed: servo/seek failure 90%      9676         0x04b7ed3d
-# 3  Extended captive    Completed                     00%      9575         
-# 4  Extended off-line   Completed                     00%      9432         
-# 5  Extended off-line   Completed                     00%      9415         
diff --git a/www/examples/MAXTOR-10.txt b/www/examples/MAXTOR-10.txt
deleted file mode 100644
index adb8beb9e75050ae872432eac6085f2878023613..0000000000000000000000000000000000000000
--- a/www/examples/MAXTOR-10.txt
+++ /dev/null
@@ -1,188 +0,0 @@
-smartctl version 5.22 Copyright (C) 2002-3 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     MAXTOR 4K080H4
-Serial Number:    674119014987
-Firmware Version: A08.1500
-Device is:        In smartctl database [for details use: -P show]
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-Local Time is:    Mon Oct 27 14:30:17 2003 CST
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Offline data collection status:  (0x80)	Offline data collection activity was
-					never started.
-					Auto Offline Data Collection: Enabled.
-Self-test execution status:      ( 112)	The previous self-test completed having
-					the read element of the test failed.
-Total time to complete Offline 
-data collection: 		 (  44) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Auto Offline data collection on/off support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-					No Conveyance Self-test supported.
-					No Selective Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-					No General Purpose Logging support.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine
-recommended polling time: 	 (  50) minutes.
-
-SMART Attributes Data Structure revision number: 11
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x0029   100   253   020    Pre-fail  Offline      -       0
-  3 Spin_Up_Time            0x0027   075   074   020    Pre-fail  Always       -       3135
-  4 Start_Stop_Count        0x0032   100   100   008    Old_age   Always       -       54
-  5 Reallocated_Sector_Ct   0x0033   098   097   020    Pre-fail  Always       -       14
-  7 Seek_Error_Rate         0x000b   100   100   023    Pre-fail  Always       -       0
-  9 Power_On_Hours          0x0012   072   072   001    Old_age   Always       -       18875
- 10 Spin_Retry_Count        0x0026   100   100   000    Old_age   Always       -       0
- 11 Calibration_Retry_Count 0x0013   100   100   020    Pre-fail  Always       -       0
- 12 Power_Cycle_Count       0x0032   100   100   008    Old_age   Always       -       53
- 13 Read_Soft_Error_Rate    0x000b   100   085   023    Pre-fail  Always       -       0
-194 Temperature_Celsius     0x0022   093   088   042    Old_age   Always       -       20
-195 Hardware_ECC_Recovered  0x001a   028   002   000    Old_age   Always       -       1472864733
-196 Reallocated_Event_Count 0x0010   100   099   020    Old_age   Offline      -       0
-197 Current_Pending_Sector  0x0032   100   100   020    Old_age   Always       -       2
-198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
-199 UDMA_CRC_Error_Count    0x001a   200   200   000    Old_age   Always       -       0
-
-SMART Error Log Version: 1
-ATA Error Count: 28 (device log contains only the most recent five errors)
-	CR = Command Register [HEX]
-	FR = Features Register [HEX]
-	SC = Sector Count Register [HEX]
-	SN = Sector Number Register [HEX]
-	CL = Cylinder Low Register [HEX]
-	CH = Cylinder High Register [HEX]
-	DH = Device/Head Register [HEX]
-	DC = Device Command Register [HEX]
-	ER = Error register [HEX]
-	ST = Status register [HEX]
-Timestamp = decimal seconds since the previous disk power-on.
-Note: timestamp "wraps" after 2^32 msec = 49.710 days.
-
-Error 28 occurred at disk power-on lifetime: 18785 hours
-  When the command that caused the error occurred, the device was in an unknown state.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 d1 38 ce 8f 40 e0  Error: UNC
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  c8 00 38 ce 8f 40 e0 40     315.769  READ DMA
-  c8 00 40 c6 8f 40 e0 40     311.634  READ DMA
-  b0 00 01 01 4f c2 e0 1f     284.485  [Reserved SMART command]
-  b0 00 01 06 4f c2 e0 34     284.470  [Reserved SMART command]
-  b0 00 01 00 4f c2 e0 34     284.399  [Reserved SMART command]
-
-Error 27 occurred at disk power-on lifetime: 18785 hours
-  When the command that caused the error occurred, the device was in an unknown state.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 59 38 ce 8f 40 e0  Error: UNC
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  c8 00 40 c6 8f 40 e0 40     311.634  READ DMA
-  b0 00 01 01 4f c2 e0 1f     284.485  [Reserved SMART command]
-  b0 00 01 06 4f c2 e0 34     284.470  [Reserved SMART command]
-  b0 00 01 00 4f c2 e0 34     284.399  [Reserved SMART command]
-  b0 00 00 00 4f c2 00 34     284.328  [Reserved SMART command]
-
-Error 26 occurred at disk power-on lifetime: 18744 hours
-  When the command that caused the error occurred, the device was in an unknown state.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 d1 08 bf 00 30 e0  Error: UNC
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  c8 00 08 bf 00 30 e0 30     134.258  READ DMA
-  c8 00 08 cf 3d 34 e0 34     134.247  READ DMA
-  c8 00 08 af 00 34 e0 34     134.215  READ DMA
-  c8 00 28 6f 3e 28 e0 28     134.213  READ DMA
-  c8 00 08 67 3e 28 e0 28     134.201  READ DMA
-
-Error 25 occurred at disk power-on lifetime: 18619 hours
-  When the command that caused the error occurred, the device was in an unknown state.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 59 07 89 67 10 e3  Error: UNC
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  c8 03 08 88 67 10 e3 10      54.493  READ DMA
-  c8 03 08 88 69 08 e3 08      54.483  READ DMA
-  c8 03 08 88 67 08 e3 08      54.471  READ DMA
-  c8 02 08 88 69 ec e2 ec      54.464  READ DMA
-  c8 02 08 88 67 ec e2 ec      54.439  READ DMA
-
-Error 24 occurred at disk power-on lifetime: 18619 hours
-  When the command that caused the error occurred, the device was in an unknown state.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 59 06 8a 67 0c e2  Error: UNC
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  c8 02 08 88 67 0c e2 0c      49.281  READ DMA
-  c8 02 08 88 69 08 e2 08      49.270  READ DMA
-  c8 02 08 88 69 04 e2 04      49.259  READ DMA
-  c8 02 08 88 69 00 e2 00      49.257  READ DMA
-  c8 02 08 50 5c 00 e2 00      49.254  READ DMA
-
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed: read failure       80%     18841         0x001f807f
-# 2  Extended offline    Completed: read failure       80%     18673         0x020c678a
-# 3  Extended offline    Completed: read failure       80%     18505         0x020c678a
-# 4  Extended offline    Completed: read failure       80%     18338         0x020c678a
-# 5  Extended offline    Completed: read failure       90%     18229         0x00408f96
-# 6  Extended offline    Completed: read failure       80%     18171         0x02386789
-# 7  Extended offline    Completed without error       00%     18051         -
-# 8  Short offline       Completed without error       00%     18051         -
-# 9  Extended offline    Completed without error       00%     18003         -
-#10  Extended offline    Completed without error       00%     17836         -
-#11  Extended offline    Completed without error       00%     17668         -
-#12  Extended offline    Completed without error       00%     17501         -
-#13  Extended offline    Completed without error       00%     17334         -
-#14  Extended offline    Completed without error       00%     17166         -
-#15  Extended offline    Completed without error       00%     16999         -
-#16  Extended offline    Completed without error       00%     16831         -
-#17  Extended offline    Completed without error       00%     16664         -
-#18  Extended offline    Completed without error       00%     16603         -
-#19  Extended offline    Completed without error       00%     16497         -
-#20  Extended offline    Completed without error       00%     16329         -
-#21  Extended offline    Completed without error       00%     16163         -
-
diff --git a/www/examples/MAXTOR-2.txt b/www/examples/MAXTOR-2.txt
deleted file mode 100644
index 9ff60ffcb3927d55bfa1c40ff5b803b9cc9ced87..0000000000000000000000000000000000000000
--- a/www/examples/MAXTOR-2.txt
+++ /dev/null
@@ -1,79 +0,0 @@
-smartctl version 5.0-24 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     MAXTOR 4K080H4                          
-Serial Number:    674119113862        
-Firmware Version: A08.1500
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-See vendor-specific Attribute list for marginal Attributes.
-
-General SMART Values:
-Off-line data collection status: (0x05)	Offline data collection activity was 
-					aborted by an interrupting command from host.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 (  44) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  50) minutes.
-
-SMART Attributes Data Structure revision number: 11
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x0029   100   253   020    Pre-fail     -       0
-  3 Spin_Up_Time            0x0027   075   075   020    Pre-fail     -       3249
-  4 Start_Stop_Count        0x0032   100   100   008    Old_age      -       31
-  5 Reallocated_Sector_Ct   0x0033   100   100   020    Pre-fail     -       0
-  7 Seek_Error_Rate         0x000b   100   001   023    Pre-fail In_the_past 0
-  9 Power_On_Hours          0x0012   086   086   001    Old_age      -       9754
- 10 Spin_Retry_Count        0x0026   100   100   000    Old_age      -       0
- 11 Calibration_Retry_Count 0x0013   100   100   020    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   008    Old_age      -       31
- 13 Read_Soft_Error_Rate    0x000b   100   100   023    Pre-fail     -       0
-194 Temperature_Centigrade  0x0022   035   032   042    Old_age  FAILING_NOW 168
-195 Hardware_ECC_Recovered  0x001a   100   002   000    Old_age      -       880099716
-196 Reallocated_Event_Count 0x0010   100   100   020    Old_age      -       0
-197 Current_Pending_Sector  0x0032   100   100   020    Old_age      -       0
-198 Offline_Uncorrectable   0x0010   100   253   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x001a   200   200   000    Old_age      -       0
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Short off-line      Completed                     00%      9691         
-# 2  Short captive       Completed                     00%      9691         
-# 3  Extended captive    Completed                     00%      9618         
-# 4  Extended captive    Interrupted (host reset)      90%      9563         
-# 5  Short captive       Completed                     00%      9563         
-# 6  Short off-line      Completed                     00%      9563         
-# 7  Short captive       Completed                     00%      9545         
-# 8  Extended off-line   Completed                     00%      9541         
-# 9  Short captive       Completed                     00%      9541         
-#10  Extended off-line   Completed                     00%      9537         
-#11  Extended off-line   Completed                     00%      9536         
-#12  Extended off-line   Interrupted (host reset)      90%      9534         
-#13  Extended off-line   Completed                     00%      9517         
-#14  Extended off-line   Completed                     00%      9484         
diff --git a/www/examples/MAXTOR-3.txt b/www/examples/MAXTOR-3.txt
deleted file mode 100644
index 26df69e5977a8b4e46958290ac79b663d7246e4e..0000000000000000000000000000000000000000
--- a/www/examples/MAXTOR-3.txt
+++ /dev/null
@@ -1,67 +0,0 @@
-smartctl version 5.0-24 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     MAXTOR 6L080J4                          
-Serial Number:    664201100034        
-Firmware Version: A93.0500
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Off-line data collection status: (0x00)	Offline data collection activity was
-					never started.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 (  35) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  40) minutes.
-
-SMART Attributes Data Structure revision number: 11
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x0029   100   253   020    Pre-fail     -       0
-  3 Spin_Up_Time            0x0027   069   066   020    Pre-fail     -       3984
-  4 Start_Stop_Count        0x0032   100   100   008    Old_age      -       110
-  5 Reallocated_Sector_Ct   0x0033   100   100   020    Pre-fail     -       0
-  7 Seek_Error_Rate         0x000b   100   100   023    Pre-fail     -       0
-  9 Power_On_Hours          0x0012   099   099   001    Old_age      -       1294
- 10 Spin_Retry_Count        0x0026   100   100   000    Old_age      -       0
- 11 Calibration_Retry_Count 0x0013   100   100   020    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   008    Old_age      -       110
- 13 Read_Soft_Error_Rate    0x000b   100   100   023    Pre-fail     -       0
-194 Temperature_Centigrade  0x0022   092   087   042    Old_age      -       22
-195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age      -       1163
-196 Reallocated_Event_Count 0x0010   100   100   020    Old_age      -       0
-197 Current_Pending_Sector  0x0032   100   100   020    Old_age      -       0
-198 Offline_Uncorrectable   0x0010   100   253   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x001a   200   200   000    Old_age      -       0
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed                     00%      1038         
-# 2  Extended off-line   Aborted by host               00%       786         
-# 3  Extended off-line   Aborted by host               00%       786         
diff --git a/www/examples/MAXTOR-4.txt b/www/examples/MAXTOR-4.txt
deleted file mode 100644
index 65ae2850d953448898079f827870b697f26dc07d..0000000000000000000000000000000000000000
--- a/www/examples/MAXTOR-4.txt
+++ /dev/null
@@ -1,65 +0,0 @@
-smartctl version 5.0-24 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     MAXTOR 6L080J4                          
-Serial Number:    664205757172        
-Firmware Version: A93.0500
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Off-line data collection status: (0x04)	Offline data collection activity was 
-					suspended by an interrupting command from host.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 (  35) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  40) minutes.
-
-SMART Attributes Data Structure revision number: 11
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x0029   100   253   020    Pre-fail     -       0
-  3 Spin_Up_Time            0x0027   065   064   020    Pre-fail     -       4481
-  4 Start_Stop_Count        0x0032   100   100   008    Old_age      -       81
-  5 Reallocated_Sector_Ct   0x0033   100   100   020    Pre-fail     -       0
-  7 Seek_Error_Rate         0x000b   100   100   023    Pre-fail     -       0
-  9 Power_On_Hours          0x0012   098   098   001    Old_age      -       1767
- 10 Spin_Retry_Count        0x0026   100   100   000    Old_age      -       0
- 11 Calibration_Retry_Count 0x0013   100   100   020    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   008    Old_age      -       81
- 13 Read_Soft_Error_Rate    0x000b   100   100   023    Pre-fail     -       0
-194 Temperature_Centigrade  0x0022   091   084   042    Old_age      -       24
-195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age      -       52795
-196 Reallocated_Event_Count 0x0010   100   100   020    Old_age      -       0
-197 Current_Pending_Sector  0x0032   100   100   020    Old_age      -       0
-198 Offline_Uncorrectable   0x0010   100   253   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x001a   200   200   000    Old_age      -       0
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed                     00%      1283         
diff --git a/www/examples/MAXTOR-6.txt b/www/examples/MAXTOR-6.txt
deleted file mode 100644
index fe37f6541cc9b0f487578982b94f6a4931f984fd..0000000000000000000000000000000000000000
--- a/www/examples/MAXTOR-6.txt
+++ /dev/null
@@ -1,156 +0,0 @@
-# /usr/sbin/smartctl -a -m /dev/hda
-smartctl version 5.0-49 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     Maxtor 4R080J0                          
-Serial Number:    R20BZ3LE            
-Firmware Version: RAMB1TU0
-ATA Version is:   7
-ATA Standard is:  Unrecognized. Minor revision code: 0x1e
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Off-line data collection status: (0x82)	Offline data collection activity 
-					completed without error.
-Self-test execution status:      (  33)	The self-test routine was interrupted
-					by the host with a hard or soft reset.
-Total time to complete off-line 
-data collection: 		 ( 241) seconds.
-Offline data collection
-capabilities: 			 (0x5b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  41) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  3 Spin_Up_Time            0x0027   252   252   063    Pre-fail     -       1621
-  4 Start_Stop_Count        0x0032   253   253   000    Old_age      -       18
-  5 Reallocated_Sector_Ct   0x0033   253   253   063    Pre-fail     -       0
-  6 Read_Channel_Margin     0x0001   253   253   100    Pre-fail     -       0
-  7 Seek_Error_Rate         0x000a   253   252   000    Old_age      -       0
-  8 Seek_Time_Performance   0x0027   252   244   187    Pre-fail     -       41642
-  9 Power_On_Hours          0x0032   253   253   000    Old_age      -       27 h + 13 m
- 10 Spin_Retry_Count        0x002b   252   252   157    Pre-fail     -       0
- 11 Calibration_Retry_Count 0x002b   253   252   223    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   253   253   000    Old_age      -       24
-192 Power-Off_Retract_Count 0x0032   253   253   000    Old_age      -       0
-193 Load_Cycle_Count        0x0032   253   253   000    Old_age      -       0
-194 Temperature_Celsius     0x0032   253   253   000    Old_age      -       29
-195 Hardware_ECC_Recovered  0x000a   253   252   000    Old_age      -       31004
-196 Reallocated_Event_Count 0x0008   253   253   000    Old_age      -       0
-197 Current_Pending_Sector  0x0008   253   253   000    Old_age      -       0
-198 Offline_Uncorrectable   0x0008   253   253   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x0008   199   199   000    Old_age      -       0
-200 Multi_Zone_Error_Rate   0x000a   253   252   000    Old_age      -       0
-201 Unknown_Attribute       0x000a   253   252   000    Old_age      -       3
-202 Unknown_Attribute       0x000a   253   252   000    Old_age      -       0
-203 Unknown_Attribute       0x000b   253   252   180    Pre-fail     -       2
-204 Unknown_Attribute       0x000a   253   252   000    Old_age      -       0
-205 Unknown_Attribute       0x000a   253   252   000    Old_age      -       0
-207 Unknown_Attribute       0x002a   252   252   000    Old_age      -       0
-208 Unknown_Attribute       0x002a   252   252   000    Old_age      -       0
-209 Unknown_Attribute       0x0024   079   063   000    Old_age      -       0
- 99 Unknown_Attribute       0x0004   253   253   000    Old_age      -       0
-100 Unknown_Attribute       0x0004   253   253   000    Old_age      -       0
-101 Unknown_Attribute       0x0004   253   253   000    Old_age      -       0
-
-SMART Error Log Version: 1
-ATA Error Count: 5
-	DCR = Device Control Register
-	FR  = Features Register
-	SC  = Sector Count Register
-	SN  = Sector Number Register
-	CL  = Cylinder Low Register
-	CH  = Cylinder High Register
-	D/H = Device/Head Register
-	CR  = Content written to Command Register
-	ER  = Error register
-	STA = Status register
-Timestamp is seconds since the previous disk power-on.
-Note: timestamp "wraps" after 2^32 msec = 49.710 days.
-
-Error 5 occurred at disk power-on lifetime: 4 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:04 SC:00 SN:00 CL:f4 CH:2c D/H:00 ST:01
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 0e   d4   00   82   4f   c2    f0   b0     8907.296
- 08   d4   00   82   4f   c2    f0   b0     6260.832
- 08   d1   01   01   4f   c2    f0   b0     6260.800
- 08   d0   01   00   4f   c2    f0   b0     6260.768
- 08   da   00   00   4f   c2    10   b0     6260.736
-
-Error 4 occurred at disk power-on lifetime: 1 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:04 SC:00 SN:00 CL:f4 CH:2c D/H:00 ST:01
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 0e   d4   00   82   4f   c2    f0   b0     1944.192
- 08   d4   00   82   4f   c2    f0   b0     1824.240
- 08   d1   01   01   4f   c2    f0   b0     1824.224
- 08   d0   01   00   4f   c2    f0   b0     1824.160
- 08   00   08   3f   00   00    f0   ca     1810.400
-
-Error 3 occurred at disk power-on lifetime: 1 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:04 SC:00 SN:00 CL:f4 CH:2c D/H:00 ST:01
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 0e   d4   00   82   4f   c2    f0   b0     1456.432
- 08   d4   00   82   4f   c2    f0   b0     1379.456
- 08   d1   01   01   4f   c2    f0   b0     1379.440
- 08   d0   01   00   4f   c2    f0   b0     1379.376
- 08   00   08   f7   01   54    f0   ca     1378.544
-
-Error 2 occurred at disk power-on lifetime: 0 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:04 SC:00 SN:00 CL:f4 CH:2c D/H:00 ST:51
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 08   d4   00   82   4f   c2    f0   b0     908.320
- 08   d1   01   01   4f   c2    f0   b0     908.320
- 08   d0   01   00   4f   c2    f0   b0     908.272
- 08   d4   00   7f   4f   c2    f0   b0     905.696
- 08   d1   01   01   4f   c2    f0   b0     905.664
-
-Error 1 occurred at disk power-on lifetime: 0 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:04 SC:50 SN:40 CL:97 CH:03 D/H:10 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   fe   00   00   00   00    10   ef     137.184
- 00   3d   00   00   00   00    10   c3     137.136
- 00   e4   00   00   00   00    10   c3     137.088
- 00   3d   00   00   00   00    10   c3     137.088
- 00   00   00   00   5e   20    10   70     137.040
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended captive    Interrupted (host reset)      10%         4         
-# 2  Short off-line      Completed                     00%         2         
-# 3  Short captive       Completed                     00%         2         
-# 4  Extended captive    Interrupted (host reset)      40%         1         
-# 5  Extended captive    Interrupted (host reset)      70%         1         
-# 6  Extended captive    Interrupted (host reset)      40%         0         
diff --git a/www/examples/MAXTOR-7.txt b/www/examples/MAXTOR-7.txt
deleted file mode 100644
index 1d3fa00491946ea74388b37962bdac003ee8c829..0000000000000000000000000000000000000000
--- a/www/examples/MAXTOR-7.txt
+++ /dev/null
@@ -1,157 +0,0 @@
-smartctl version 5.1-4 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     MAXTOR 4K080H4                          
-Serial Number:    674119114160        
-Firmware Version: A08.1500
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-Local Time is:    Tue May 13 08:59:49 2003 CDT
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: FAILED!
-Drive failure expected in less than 24 hours. SAVE ALL DATA.
-See vendor-specific Attribute list for failed Attributes.
-
-General SMART Values:
-Off-line data collection status: (0x82) Offline data collection activity 
-                                        completed without error.
-Self-test execution status:      ( 112) The previous self-test completed having
-                                        the read element of the test failed.
-Total time to complete off-line 
-data collection:                 (  44) seconds.
-Offline data collection
-capabilities:                    (0x1b) SMART execute Offline immediate.
-                                        Automatic timer ON/OFF support.
-                                        Suspend Offline collection upon new
-                                        command.
-                                        Offline surface scan supported.
-                                        Self-test supported.
-SMART capabilities:            (0x0003) Saves SMART data before entering
-                                        power-saving mode.
-                                        Supports SMART auto save timer.
-Error logging capability:        (0x01) Error logging supported.
-Short self-test routine 
-recommended polling time:        (   2) minutes.
-Extended self-test routine 
-recommended polling time:        (  50) minutes.
-
-SMART Attributes Data Structure revision number: 11
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x0029   100   253   020    Pre-fail     -       0
-  3 Spin_Up_Time            0x0027   075   075   020    Pre-fail     -       3214
-  4 Start_Stop_Count        0x0032   100   100   008    Old_age      -       58
-  5 Reallocated_Sector_Ct   0x0033   098   098   020    Pre-fail     -       12
-  7 Seek_Error_Rate         0x000b   001   001   023    Pre-fail FAILING_NOW 13
-  9 Power_On_Hours          0x0012   078   078   001    Old_age      -       14851
- 10 Spin_Retry_Count        0x0026   100   100   000    Old_age      -       0
- 11 Calibration_Retry_Count 0x0013   100   090   020    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   008    Old_age      -       58
- 13 Read_Soft_Error_Rate    0x000b   100   085   023    Pre-fail     -       0
-194 Temperature_Celsius     0x0022   091   087   042    Old_age      -       24
-195 Hardware_ECC_Recovered  0x001a   004   003   000    Old_age      -       513691822
-196 Reallocated_Event_Count 0x0010   099   099   020    Old_age      -       1
-197 Current_Pending_Sector  0x0032   098   098   020    Old_age      -       12
-198 Offline_Uncorrectable   0x0010   100   100   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x001a   200   200   000    Old_age      -       0
-
-SMART Error Log Version: 1
-ATA Error Count: 25 (device log contains only the most recent five errors)
-        DCR = Device Control Register
-        FR  = Features Register
-        SC  = Sector Count Register
-        SN  = Sector Number Register
-        CL  = Cylinder Low Register
-        CH  = Cylinder High Register
-        D/H = Device/Head Register
-        CR  = Content written to Command Register
-        ER  = Error register
-        STA = Status register
-Timestamp is seconds since the previous disk power-on.
-Note: timestamp "wraps" after 2^32 msec = 49.710 days.
-
-Error 25 occurred at disk power-on lifetime: 14799 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:40 SC:04 SN:53 CL:1d CH:0c D/H:e0 ST:59
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 0c   00   08   4f   1d   0c    e0   c8     0.523
- 0c   00   08   47   1d   0c    e0   c8     510.677
- 04   00   08   6f   04   04    e0   ca     510.675
- 04   00   08   4f   1c   04    e0   ca     510.674
- 04   00   08   6f   04   04    e0   ca     510.674
-
-Error 24 occurred at disk power-on lifetime: 14799 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:40 SC:03 SN:44 CL:1d CH:0c D/H:e0 ST:59
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 0c   00   08   3f   1d   0c    e0   c8     495.294
- 0c   00   08   37   1d   0c    e0   c8     491.239
- 0c   00   08   2f   1d   0c    e0   c8     488.433
- 14   00   08   17   04   14    e0   ca     488.432
- 0c   00   08   b7   00   0c    e0   ca     488.432
-
-Error 23 occurred at disk power-on lifetime: 14799 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:40 SC:06 SN:21 CL:18 CH:0c D/H:e0 ST:59
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 0c   00   08   1f   18   0c    e0   c8     392.659
- 00   00   08   17   18   0c    e0   c8     392.654
- 0c   00   08   0f   18   0c    e0   c8     392.624
- 00   00   08   07   18   0c    e0   c8     392.620
- 00   00   08   ff   17   0c    e0   c8     392.615
-
-Error 22 occurred at disk power-on lifetime: 14799 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:40 SC:05 SN:b2 CL:16 CH:0c D/H:e0 ST:59
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 0c   00   08   af   16   0c    e0   c8     385.889
- 04   00   08   6f   04   04    e0   ca     385.886
- 04   00   08   4f   1c   04    e0   ca     385.886
- 04   00   08   6f   04   04    e0   ca     385.886
- 04   00   08   4f   1c   04    e0   ca     385.885
-
-Error 21 occurred at disk power-on lifetime: 14799 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:40 SC:06 SN:a9 CL:16 CH:0c D/H:e0 ST:59
-Sequence of commands leading to the command that caused the error were:
-DCR   FR   SC   SN   CL   CH   D/H   CR   Timestamp
- 0c   00   08   a7   16   0c    e0   c8     381.795
- 04   00   08   6f   04   04    e0   ca     381.793
- 04   00   08   4f   1c   04    e0   ca     381.793
- 04   00   08   6f   04   04    e0   ca     381.792
- 04   00   08   4f   1c   04    e0   ca     381.792
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed: read failure       90%     14757         0x000409bb
-# 2  Extended off-line   Completed: read failure       90%     14755         0x000bf956
-# 3  Extended off-line   Completed                     00%     14305         -
-# 4  Extended off-line   Completed                     00%     14100         -
-# 5  Extended off-line   Completed                     00%     13721         -
-# 6  Extended off-line   Completed                     00%     13636         -
-# 7  Extended off-line   Completed                     00%     13233         -
-# 8  Extended off-line   Completed                     00%     13078         -
-# 9  Extended off-line   Completed                     00%     12093         -
-#10  Extended off-line   Completed                     00%     11926         -
-#11  Extended off-line   Completed                     00%     11428         -
-#12  Extended off-line   Completed                     00%     11030         -
-#13  Extended off-line   Completed                     00%     10888         -
-#14  Extended off-line   Completed                     00%     10728         -
-#15  Extended off-line   Completed                     00%     10435         -
-#16  Extended off-line   Completed                     00%     10267         -
-#17  Extended off-line   Completed                     00%     10098         -
-#18  Extended off-line   Completed                     00%      9930         -
-#19  Extended off-line   Completed                     00%      9599         -
diff --git a/www/examples/MAXTOR-8.txt b/www/examples/MAXTOR-8.txt
deleted file mode 100644
index 3ae4d87735563a46d403293ec5ce00b26d6bb3d0..0000000000000000000000000000000000000000
--- a/www/examples/MAXTOR-8.txt
+++ /dev/null
@@ -1,82 +0,0 @@
-smartctl version 5.1-14 Copyright (C) 2002-3 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     MAXTOR 4K080H4
-Serial Number:    674119116076
-Firmware Version: A08.1500
-Device is:        In smartctl database [for details use: -P show]
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-Local Time is:    Tue Jun 17 14:46:37 2003 CDT
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: FAILED!
-Drive failure expected in less than 24 hours. SAVE ALL DATA.
-See vendor-specific Attribute list for failed Attributes.
-
-General SMART Values:
-Off-line data collection status: (0x82)	Offline data collection activity was
-					completed without error.
-					Auto Off-line Data Collection: Enabled.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 (  44) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-					No Conveyance Self-test supported.
-					No Selective Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-					No General Purpose Logging support.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  50) minutes.
-
-SMART Attributes Data Structure revision number: 11
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x0029   100   253   020    Pre-fail  Offline      -       0
-  3 Spin_Up_Time            0x0027   075   075   020    Pre-fail  Always       -       3249
-  4 Start_Stop_Count        0x0032   100   100   008    Old_age   Always       -       45
-  5 Reallocated_Sector_Ct   0x0033   100   100   020    Pre-fail  Always       -       0
-  7 Seek_Error_Rate         0x000b   100   001   023    Pre-fail  Always   In_the_past 0
-  9 Power_On_Hours          0x0012   082   082   001    Old_age   Always       -       12223
- 10 Spin_Retry_Count        0x0026   100   100   000    Old_age   Always       -       0
- 11 Calibration_Retry_Count 0x0013   020   020   020    Pre-fail  Always   FAILING_NOW 8
- 12 Power_Cycle_Count       0x0032   100   100   008    Old_age   Always       -       45
- 13 Read_Soft_Error_Rate    0x000b   100   100   023    Pre-fail  Always       -       0
-194 Temperature_Celsius     0x0022   094   088   042    Old_age   Always       -       17
-195 Hardware_ECC_Recovered  0x001a   100   007   000    Old_age   Always       -       494134044
-196 Reallocated_Event_Count 0x0010   100   100   020    Old_age   Offline      -       0
-197 Current_Pending_Sector  0x0032   100   100   020    Old_age   Always       -       0
-198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
-199 UDMA_CRC_Error_Count    0x001a   200   200   000    Old_age   Always       -       0
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed                     00%     11610         -
-# 2  Extended off-line   Completed                     00%     11213         -
-# 3  Extended off-line   Completed                     00%     11072         -
-# 4  Extended off-line   Completed                     00%     10911         -
-# 5  Extended off-line   Completed                     00%     10618         -
-# 6  Extended off-line   Completed                     00%     10450         -
-# 7  Extended off-line   Completed                     00%     10282         -
-# 8  Extended off-line   Completed                     00%     10114         -
-# 9  Extended off-line   Completed                     00%      9783         -
-
diff --git a/www/examples/MAXTOR-9.txt b/www/examples/MAXTOR-9.txt
deleted file mode 100644
index 6a692423d766812c05a4c6f298bda322d780a655..0000000000000000000000000000000000000000
--- a/www/examples/MAXTOR-9.txt
+++ /dev/null
@@ -1,94 +0,0 @@
-smartctl version 5.1-14 Copyright (C) 2002-3 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     MAXTOR 4K080H4
-Serial Number:    674119123112
-Firmware Version: A08.1500
-Device is:        In smartctl database [for details use: -P show]
-ATA Version is:   5
-ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 1
-Local Time is:    Tue Aug 19 02:06:11 2003 CDT
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: FAILED!
-Drive failure expected in less than 24 hours. SAVE ALL DATA.
-See vendor-specific Attribute list for failed Attributes.
-
-General SMART Values:
-Off-line data collection status: (0x80)	Offline data collection activity was
-					never started.
-					Auto Off-line Data Collection: Enabled.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 (  44) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-					No Conveyance Self-test supported.
-					No Selective Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-					No General Purpose Logging support.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  50) minutes.
-
-SMART Attributes Data Structure revision number: 11
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x0029   100   253   020    Pre-fail  Offline      -       0
-  3 Spin_Up_Time            0x0027   075   074   020    Pre-fail  Always       -       3186
-  4 Start_Stop_Count        0x0032   100   100   008    Old_age   Always       -       68
-  5 Reallocated_Sector_Ct   0x0033   100   100   020    Pre-fail  Always       -       0
-  7 Seek_Error_Rate         0x000b   100   100   023    Pre-fail  Always       -       0
-  9 Power_On_Hours          0x0012   074   074   001    Old_age   Always       -       17202
- 10 Spin_Retry_Count        0x0026   100   100   000    Old_age   Always       -       0
- 11 Calibration_Retry_Count 0x0013   010   010   020    Pre-fail  Always   FAILING_NOW 9
- 12 Power_Cycle_Count       0x0032   100   100   008    Old_age   Always       -       68
- 13 Read_Soft_Error_Rate    0x000b   100   100   023    Pre-fail  Always       -       0
-194 Temperature_Celsius     0x0022   092   087   042    Old_age   Always       -       22
-195 Hardware_ECC_Recovered  0x001a   018   003   000    Old_age   Always       -       1082933060
-196 Reallocated_Event_Count 0x0010   100   100   020    Old_age   Offline      -       0
-197 Current_Pending_Sector  0x0032   100   100   020    Old_age   Always       -       0
-198 Offline_Uncorrectable   0x0010   100   253   000    Old_age   Offline      -       0
-199 UDMA_CRC_Error_Count    0x001a   200   200   000    Old_age   Always       -       0
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed                     00%     17157         -
-# 2  Extended off-line   Completed                     00%     16990         -
-# 3  Extended off-line   Completed                     00%     16823         -
-# 4  Extended off-line   Completed                     00%     16657         -
-# 5  Extended off-line   Completed                     00%     16598         -
-# 6  Extended off-line   Completed                     00%     16490         -
-# 7  Extended off-line   Completed                     00%     16323         -
-# 8  Extended off-line   Completed                     00%     16157         -
-# 9  Extended off-line   Completed                     00%     15991         -
-#10  Extended off-line   Completed                     00%     15696         -
-#11  Extended off-line   Completed                     00%     15614         -
-#12  Extended off-line   Completed                     00%     15241         -
-#13  Extended off-line   Completed                     00%     15026         -
-#14  Extended off-line   Completed                     00%     14785         -
-#15  Extended off-line   Completed                     00%     14334         -
-#16  Extended off-line   Completed                     00%     14129         -
-#17  Extended off-line   Completed                     00%     13750         -
-#18  Extended off-line   Completed                     00%     13665         -
-#19  Extended off-line   Completed                     00%     13262         -
-#20  Extended off-line   Completed                     00%     13108         -
-#21  Extended off-line   Completed                     00%     12125         -
-
diff --git a/www/examples/Maxtor-5.txt b/www/examples/Maxtor-5.txt
deleted file mode 100644
index 3bb171eb6fd032d5ad56dea9925c85bec295c545..0000000000000000000000000000000000000000
--- a/www/examples/Maxtor-5.txt
+++ /dev/null
@@ -1,127 +0,0 @@
-smartctl version 5.0-36 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     Maxtor 98196H8                          
-Serial Number:    V80HV6NC            
-Firmware Version: ZAH814Y0
-ATA Version is:   6
-ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 0
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Off-line data collection status: (0x00)	Offline data collection activity was
-					never started.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 (  30) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  60) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000a   253   252   000    Old_age      -       26
-  3 Spin_Up_Time            0x0027   208   206   063    Pre-fail     -       11285
-  4 Start_Stop_Count        0x0032   253   253   000    Old_age      -       62
-  5 Reallocated_Sector_Ct   0x0033   253   253   063    Pre-fail     -       0
-  6 Read_Channel_Margin     0x0001   253   253   100    Pre-fail     -       0
-  7 Seek_Error_Rate         0x000a   253   252   000    Old_age      -       0
-  8 Seek_Time_Performance   0x0027   249   244   187    Pre-fail     -       50271
-  9 Power_On_Hours          0x0032   236   236   000    Old_age      -       32671
- 10 Spin_Retry_Count        0x002b   253   252   223    Pre-fail     -       0
- 11 Calibration_Retry_Count 0x002b   253   252   223    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   253   253   000    Old_age      -       67
-196 Reallocated_Event_Count 0x0008   253   253   000    Old_age      -       0
-197 Current_Pending_Sector  0x0008   253   253   000    Old_age      -       0
-198 Offline_Uncorrectable   0x0008   253   253   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x0008   199   199   000    Old_age      -       0
-200 Unknown_Attribute       0x000a   253   252   000    Old_age      -       0
-201 Unknown_Attribute       0x000a   253   252   000    Old_age      -       1
-202 Unknown_Attribute       0x000a   253   252   000    Old_age      -       0
-203 Unknown_Attribute       0x000b   253   252   180    Pre-fail     -       2
-204 Unknown_Attribute       0x000a   253   252   000    Old_age      -       0
-205 Unknown_Attribute       0x000a   253   252   000    Old_age      -       0
-207 Unknown_Attribute       0x002a   253   252   000    Old_age      -       0
-208 Unknown_Attribute       0x002a   253   252   000    Old_age      -       0
-209 Unknown_Attribute       0x0024   253   253   000    Old_age      -       0
- 96 Unknown_Attribute       0x0004   253   253   000    Old_age      -       0
- 97 Unknown_Attribute       0x0004   253   253   000    Old_age      -       0
- 98 Unknown_Attribute       0x0004   253   253   000    Old_age      -       0
- 99 Unknown_Attribute       0x0004   253   253   000    Old_age      -       0
-100 Unknown_Attribute       0x0004   253   253   000    Old_age      -       0
-101 Unknown_Attribute       0x0004   253   253   000    Old_age      -       0
-
-SMART Error Log Version: 1
-ATA Error Count: 3
-	DCR = Device Control Register
-	FR  = Features Register
-	SC  = Sector Count Register
-	SN  = Sector Number Register
-	CL  = Cylinder Low Register
-	CH  = Cylinder High Register
-	D/H = Device/Head Register
-	CR  = Content written to Command Register
-	ER  = Error register
-	STA = Status register
-Timestamp is seconds since the previous disk power-on.
-Note: timestamp "wraps" after 2^32 msec = 49.710 days.
-
-Error 1 occurred at disk power-on lifetime: 0 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:04 SC:40 SN:42 CL:97 CH:23 D/H:00 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   fe   00   00   00   00    00   ef     137.440
- 00   d9   00   00   4f   c2    00   b0     137.328
- 00   da   00   00   4f   c2    00   b0     137.232
- 00   d8   00   00   4f   c2    00   b0     137.152
- 00   db   00   00   4f   c2    00   b0     136.976
-
-Error 2 occurred at disk power-on lifetime: 0 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:04 SC:40 SN:40 CL:97 CH:23 D/H:00 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   fe   00   00   00   00    00   ef     342.432
- 00   e4   00   00   00   00    00   c3     342.368
- 00   d0   00   00   0a   00    00   c3     342.368
- 00   fe   00   00   00   00    00   ef     342.304
- 00   3d   00   00   00   00    00   c3     342.256
-
-Error 3 occurred at disk power-on lifetime: 0 hours
-When the command that caused the error occurred, the device was in an unknown state.
-After command completion occurred, registers were:
-ER:04 SC:40 SN:40 CL:97 CH:03 D/H:00 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   fe   00   00   00   00    00   ef     342.304
- 00   3d   00   00   00   00    00   c3     342.256
- 00   e4   00   00   00   00    00   c3     342.192
- 00   3d   00   00   00   00    00   c3     342.192
- 00   00   01   01   00   00    00   ec     342.144
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Short off-line      Completed                     00%      5255         
diff --git a/www/examples/TOSHIBA-0.txt b/www/examples/TOSHIBA-0.txt
deleted file mode 100644
index 965e55d99af8af42a5d6592c3159dd9fbb70312a..0000000000000000000000000000000000000000
--- a/www/examples/TOSHIBA-0.txt
+++ /dev/null
@@ -1,73 +0,0 @@
-smartctl version 5.0-31 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     TOSHIBA MK2018GAS                       
-Serial Number:    X22F7553T           
-Firmware Version: Q2.03 D 
-ATA Version is:   5
-ATA Standard is:  Unrecognized. Minor revision code: 0x00
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Off-line data collection status: (0x00)	Offline data collection activity was
-					never started.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 ( 212) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  23) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail     -       0
-  2 Throughput_Performance  0x0005   100   100   050    Pre-fail     -       0
-  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail     -       910
-  4 Start_Stop_Count        0x0032   100   100   000    Old_age      -       18
-  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail     -       0
-  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail     -       0
-  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail     -       0
-  9 Power_On_Hours          0x0032   100   100   000    Old_age      -       9
- 10 Spin_Retry_Count        0x0033   100   100   030    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   000    Old_age      -       18
-192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age      -       6
-193 Load_Cycle_Count        0x0032   100   100   000    Old_age      -       437
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age      -       0
-197 Current_Pending_Sector  0x0032   100   100   000    Old_age      -       0
-198 Offline_Uncorrectable   0x0030   100   100   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age      -       0
-220 Disk_Shift              0x0002   100   100   000    Old_age      -       4250
-222 Loaded_Hours            0x0032   100   100   000    Old_age      -       4
-223 Load_Retry_Count        0x0032   100   100   000    Old_age      -       0
-224 Load_Friction           0x0022   100   100   000    Old_age      -       0
-226 Load-in_Time            0x0026   100   100   000    Old_age      -       590
-240 Unknown_Attribute       0x0001   100   100   001    Pre-fail     -       0
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed                     00%         4         
-# 2  Short captive       Completed                     00%         0         
-# 3  Short off-line      Completed                     00%         0         
diff --git a/www/examples/TOSHIBA-MK6021GAS.txt b/www/examples/TOSHIBA-MK6021GAS.txt
deleted file mode 100644
index 776cb3dcee4f794a875c763556a27b001893c597..0000000000000000000000000000000000000000
--- a/www/examples/TOSHIBA-MK6021GAS.txt
+++ /dev/null
@@ -1,74 +0,0 @@
-smartctl version 5.1-7 Copyright (C) 2002 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     TOSHIBA MK6021GAS                       
-Serial Number:    Y2MJ1530T           
-Firmware Version: GA023A  
-ATA Version is:   5
-ATA Standard is:  Unrecognized. Minor revision code: 0x00
-Local Time is:    Mon Feb 17 09:37:27 2003 CST
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: PASSED
-
-General SMART Values:
-Off-line data collection status: (0x00)	Offline data collection activity was
-					never started.
-Self-test execution status:      (   0)	The previous self-test routine completed
-					without error or no self-test has ever 
-					been run.
-Total time to complete off-line 
-data collection: 		 ( 587) seconds.
-Offline data collection
-capabilities: 			 (0x1b) SMART execute Offline immediate.
-					Automatic timer ON/OFF support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine 
-recommended polling time: 	 (  65) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE     WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail     -       0
-  2 Throughput_Performance  0x0005   100   100   050    Pre-fail     -       0
-  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail     -       1267
-  4 Start_Stop_Count        0x0032   100   100   000    Old_age      -       18
-  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail     -       0
-  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail     -       0
-  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail     -       0
-  9 Power_On_Hours          0x0032   100   100   000    Old_age      -       39
- 10 Spin_Retry_Count        0x0033   100   100   030    Pre-fail     -       0
- 12 Power_Cycle_Count       0x0032   100   100   000    Old_age      -       16
-192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age      -       1
-193 Load_Cycle_Count        0x0032   100   100   000    Old_age      -       460
-194 Temperature_Celsius     0x0022   100   100   000    Old_age      -       40 (Lifetime Min/Max 17/51)
-196 Reallocated_Event_Count 0x0032   100   100   000    Old_age      -       0
-197 Current_Pending_Sector  0x0032   100   100   000    Old_age      -       0
-198 Offline_Uncorrectable   0x0030   100   100   000    Old_age      -       0
-199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age      -       0
-220 Disk_Shift              0x0002   100   100   000    Old_age      -       8332
-222 Loaded_Hours            0x0032   100   100   000    Old_age      -       30
-223 Load_Retry_Count        0x0032   100   100   000    Old_age      -       0
-224 Load_Friction           0x0022   100   100   000    Old_age      -       0
-226 Load-in_Time            0x0026   100   100   000    Old_age      -       159
-240 Head flying hours       0x0001   100   100   001    Pre-fail     -       0
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log, version number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended off-line   Completed                     00%         4         -
-
diff --git a/www/examples/WD2500JB.txt b/www/examples/WD2500JB.txt
deleted file mode 100644
index 04e963a8b2bbeff348eb643fcb2e4748c210356f..0000000000000000000000000000000000000000
--- a/www/examples/WD2500JB.txt
+++ /dev/null
@@ -1,192 +0,0 @@
-smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Device Model:     WDC WD2500JB-32EVA0
-Serial Number:    WD-WMAEH1156826
-Firmware Version: 15.05R15
-Device is:        In smartctl database [for details use: -P show]
-ATA Version is:   6
-ATA Standard is:  Exact ATA specification draft version not indicated
-Local Time is:    Fri Jun 25 08:14:16 2004 CDT
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: FAILED!
-Drive failure expected in less than 24 hours. SAVE ALL DATA.
-See vendor-specific Attribute list for failed Attributes.
-
-General SMART Values:
-Offline data collection status:  (0x84)	Offline data collection activity was
-					suspended by an interrupting command from host.
-					Auto Offline Data Collection: Enabled.
-Self-test execution status:      (  73)	The previous self-test completed having
-					a test element that failed and the test
-					element that failed is not known.
-Total time to complete Offline 
-data collection: 		 (7608) seconds.
-Offline data collection
-capabilities: 			 (0x7b) SMART execute Offline immediate.
-					Auto Offline data collection on/off support.
-					Suspend Offline collection upon new
-					command.
-					Offline surface scan supported.
-					Self-test supported.
-					Conveyance Self-test supported.
-					Selective Self-test supported.
-SMART capabilities:            (0x0003)	Saves SMART data before entering
-					power-saving mode.
-					Supports SMART auto save timer.
-Error logging capability:        (0x01)	Error logging supported.
-					No General Purpose Logging support.
-Short self-test routine 
-recommended polling time: 	 (   2) minutes.
-Extended self-test routine
-recommended polling time: 	 (  95) minutes.
-Conveyance self-test routine
-recommended polling time: 	 (   5) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     0x000b   001   001   051    Pre-fail  Always   FAILING_NOW 2777
-  3 Spin_Up_Time            0x0007   125   120   021    Pre-fail  Always       -       4283
-  4 Start_Stop_Count        0x0032   100   100   040    Old_age   Always       -       133
-  5 Reallocated_Sector_Ct   0x0033   199   199   140    Pre-fail  Always       -       1
-  7 Seek_Error_Rate         0x000b   200   200   051    Pre-fail  Always       -       0
-  9 Power_On_Hours          0x0032   092   092   000    Old_age   Always       -       6545
- 10 Spin_Retry_Count        0x0013   100   100   051    Pre-fail  Always       -       0
- 11 Calibration_Retry_Count 0x0013   100   100   051    Pre-fail  Always       -       0
- 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       133
-194 Temperature_Celsius     0x0022   128   253   000    Old_age   Always       -       22
-196 Reallocated_Event_Count 0x0032   199   199   000    Old_age   Always       -       1
-197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       13
-198 Offline_Uncorrectable   0x0012   200   200   000    Old_age   Always       -       0
-199 UDMA_CRC_Error_Count    0x000a   200   253   000    Old_age   Always       -       1
-200 Multi_Zone_Error_Rate   0x0009   200   155   051    Pre-fail  Offline      -       0
-
-SMART Error Log Version: 1
-ATA Error Count: 50 (device log contains only the most recent five errors)
-	CR = Command Register [HEX]
-	FR = Features Register [HEX]
-	SC = Sector Count Register [HEX]
-	SN = Sector Number Register [HEX]
-	CL = Cylinder Low Register [HEX]
-	CH = Cylinder High Register [HEX]
-	DH = Device/Head Register [HEX]
-	DC = Device Command Register [HEX]
-	ER = Error register [HEX]
-	ST = Status register [HEX]
-Timestamp = decimal seconds since the previous disk power-on.
-Note: timestamp "wraps" after 2^32 msec = 49.710 days.
-
-Error 50 occurred at disk power-on lifetime: 1082 hours
-  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 07 82 a9 ee e0  Error: 
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  00 00 25 00 00 07 00 00 2825901.100  NOP [Abort queued commands]
-  03 00 82 00 00 5f 67 00 2825901.100  CFA REQUEST EXTENDED ERROR CODE
-  00 00 25 00 00 01 00 00 2825901.100  NOP [Abort queued commands]
-  00 00 25 00 00 08 00 00 2825901.100  NOP [Abort queued commands]
-  12 00 ee 00 00 5f a9 00 2825901.100  RECALIBRATE [RET-4]
-
-Error 49 occurred at disk power-on lifetime: 1082 hours
-  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 07 82 a9 ee e0  Error: 
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  00 00 25 00 00 07 00 00 2825899.350  NOP [Abort queued commands]
-  12 00 ee 00 00 7f a9 00 2825899.350  RECALIBRATE [RET-4]
-  00 00 25 00 00 08 00 00 2825899.350  NOP [Abort queued commands]
-  00 00 25 00 00 08 00 00 2825899.350  NOP [Abort queued commands]
-  12 00 ee 00 00 5f a9 00 2825899.350  RECALIBRATE [RET-4]
-
-Error 48 occurred at disk power-on lifetime: 1082 hours
-  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 08 17 a9 ee e0  Error: 
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  00 00 25 00 00 08 00 00 2825880.900  NOP [Abort queued commands]
-  00 00 d6 00 00 77 ad 00 2825880.900  NOP [Abort queued commands]
-  00 00 25 00 00 08 00 00 2825880.900  NOP [Abort queued commands]
-  00 00 d0 00 00 5f 5c 00 2825880.900  NOP [Abort queued commands]
-  00 00 35 00 00 08 00 00 2825880.900  NOP [Abort queued commands]
-
-Error 47 occurred at disk power-on lifetime: 1082 hours
-  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 08 17 a9 ee e0  Error: 
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  00 00 25 00 00 08 00 00 2825879.000  NOP [Abort queued commands]
-  00 00 d6 00 00 77 ad 00 2825879.000  NOP [Abort queued commands]
-  00 00 35 00 00 08 00 00 2825879.000  NOP [Abort queued commands]
-  00 00 35 00 00 08 00 00 2825879.000  NOP [Abort queued commands]
-  06 00 8a 00 00 4f 3b 00 2825879.000  [RESERVED]
-
-Error 46 occurred at disk power-on lifetime: 1082 hours
-  When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
-
-  After command completion occurred, registers were:
-  ER ST SC SN CL CH DH
-  -- -- -- -- -- -- --
-  40 51 08 c5 a8 ee e0  Error: 
-
-  Commands leading to the command that caused the error were:
-  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
-  -- -- -- -- -- -- -- --   ---------  --------------------
-  00 00 25 00 00 08 00 00 2825875.250  NOP [Abort queued commands]
-  00 00 25 00 00 08 00 00 2825875.250  NOP [Abort queued commands]
-  06 00 ba 00 00 f7 66 00 2825875.250  [RESERVED]
-  00 00 35 00 00 10 00 00 2825875.250  NOP [Abort queued commands]
-  06 00 ba 00 00 1f 66 00 2825875.250  [RESERVED]
-
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Short offline       Completed: unknown failure    90%      1077         0xfff00000
-# 2  Short offline       Completed without error       00%      1053         -
-# 3  Short offline       Completed without error       00%      1030         -
-# 4  Short offline       Completed without error       00%      1007         -
-# 5  Short offline       Completed without error       00%       983         -
-# 6  Extended offline    Completed without error       00%       961         -
-# 7  Short offline       Completed without error       00%       938         -
-# 8  Short offline       Completed without error       00%       914         -
-# 9  Short offline       Completed without error       00%       891         -
-#10  Short offline       Completed without error       00%       868         -
-#11  Short offline       Completed without error       00%       844         -
-#12  Short offline       Completed without error       00%       821         -
-#13  Extended offline    Completed without error       00%       799         -
-#14  Short offline       Completed without error       00%       775         -
-#15  Short offline       Completed without error       00%       752         -
-#16  Short offline       Completed without error       00%       728         -
-#17  Short offline       Completed without error       00%       705         -
-#18  Short offline       Completed without error       00%       682         -
-#19  Short offline       Completed without error       00%       659         -
-#20  Extended offline    Completed without error       00%       637         -
-#21  Short offline       Completed without error       00%       613         -
-
diff --git a/www/examples/WD800JD.txt b/www/examples/WD800JD.txt
deleted file mode 100644
index 1c69e5f980f03c9217e799c74370fdd635ad720d..0000000000000000000000000000000000000000
--- a/www/examples/WD800JD.txt
+++ /dev/null
@@ -1,115 +0,0 @@
-[root@nemo-slave0560 ~]# /net/m0001/root/ballen/sm5/smartctl  -a -d sat   /dev/sda
-smartctl version 5.37 [x86_64-unknown-linux-gnu] Copyright (C) 2002-6 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-=== START OF INFORMATION SECTION ===
-Model Family:     Western Digital Caviar SE (Serial ATA) family
-Device Model:     WDC WD800JD-08LSA0
-Serial Number:    WD-WMAM9H167762
-Firmware Version: 07.01D07
-User Capacity:    80,032,038,912 bytes
-Device is:        In smartctl database [for details use: -P show]
-ATA Version is:   7
-ATA Standard is:  Exact ATA specification draft version not indicated
-Local Time is:    Tue Jun 13 07:39:15 2006 CDT
-SMART support is: Available - device has SMART capability.
-SMART support is: Enabled
-
-=== START OF READ SMART DATA SECTION ===
-SMART overall-health self-assessment test result: FAILED!
-Drive failure expected in less than 24 hours. SAVE ALL DATA.
-See vendor-specific Attribute list for failed Attributes.
-
-General SMART Values:
-Offline data collection status:  (0x84) Offline data collection activity
-                                        was suspended by an interrupting command from host.
-                                        Auto Offline Data Collection: Enabled.
-Self-test execution status:      (  73) The previous self-test completed having
-                                        a test element that failed and the test
-                                        element that failed is not known.
-Total time to complete Offline 
-data collection:                 (2580) seconds.
-Offline data collection
-capabilities:                    (0x7b) SMART execute Offline immediate.
-                                        Auto Offline data collection on/off support.
-                                        Suspend Offline collection upon new
-                                        command.
-                                        Offline surface scan supported.
-                                        Self-test supported.
-                                        Conveyance Self-test supported.
-                                        Selective Self-test supported.
-SMART capabilities:            (0x0003) Saves SMART data before entering
-                                        power-saving mode.
-                                        Supports SMART auto save timer.
-Error logging capability:        (0x01) Error logging supported.
-                                        General Purpose Logging supported.
-Short self-test routine 
-recommended polling time:        (   2) minutes.
-Extended self-test routine
-recommended polling time:        (  34) minutes.
-Conveyance self-test routine
-recommended polling time:        (   5) minutes.
-
-SMART Attributes Data Structure revision number: 16
-Vendor Specific SMART Attributes with Thresholds:
-ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
-  1 Raw_Read_Error_Rate     POSR--   200   200   051    Pre-fail  Always       -       0
-  3 Spin_Up_Time            PO----   164   164   021    Pre-fail  Always       -       2775
-  4 Start_Stop_Count        -O--CM   100   100   000    Old_age   Always       -       20
-  5 Reallocated_Sector_Ct   PO--CM   129   129   140    Pre-fail  Always   FAILING_NOW 562
-  7 Seek_Error_Rate         POSR--   200   187   051    Pre-fail  Always       -       0
-  9 Power_On_Hours          -O--CM   099   099   000    Old_age   Always       -       1211
- 10 Spin_Retry_Count        PO--C-   100   253   051    Pre-fail  Always       -       0
- 11 Calibration_Retry_Count -O--C-   100   253   051    Old_age   Always       -       0
- 12 Power_Cycle_Count       -O--CM   100   100   000    Old_age   Always       -       20
-190 Temperature_Celsius     -O---M   082   037   045    Old_age   Always   In_the_past 18
-194 Temperature_Celsius     -O---M   125   080   000    Old_age   Always       -       18
-196 Reallocated_Event_Count -O--CM   148   148   000    Old_age   Always       -       52
-197 Current_Pending_Sector  -O--C-   200   200   000    Old_age   Always       -       0
-198 Offline_Uncorrectable   ----C-   200   200   000    Old_age   Offline      -       0
-199 UDMA_CRC_Error_Count    -OSRCM   200   200   000    Old_age   Always       -       0
-200 Multi_Zone_Error_Rate   P--R--   200   200   051    Pre-fail  Offline      -       0
-                            ||||||_ M self-preserving
-                            |||||__ C event count
-                            ||||___ R error rate
-                            |||____ S speed/performance
-                            ||_____ O updated online
-                            |______ P prefailure warning
-
-SMART Error Log Version: 1
-No Errors Logged
-
-SMART Self-test log structure revision number 1
-Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
-# 1  Extended offline    Completed: unknown failure    90%      1207         -
-# 2  Extended offline    Completed: unknown failure    90%      1187         -
-# 3  Extended offline    Completed: unknown failure    90%      1163         -
-# 4  Extended offline    Completed: unknown failure    90%      1139         -
-# 5  Extended offline    Completed: unknown failure    90%      1115         -
-# 6  Extended offline    Completed: unknown failure    90%      1091         -
-# 7  Extended offline    Completed: unknown failure    90%      1067         -
-# 8  Extended offline    Completed: unknown failure    90%      1043         -
-# 9  Extended offline    Completed: unknown failure    90%      1022         -
-#10  Extended offline    Completed: unknown failure    90%       998         -
-#11  Extended offline    Completed: unknown failure    90%       974         -
-#12  Extended offline    Completed without error       00%       943         -
-#13  Extended offline    Completed without error       00%       919         -
-#14  Extended offline    Completed without error       00%       895         -
-#15  Extended offline    Completed without error       00%       875         -
-#16  Extended offline    Completed without error       00%       857         -
-#17  Extended offline    Completed without error       00%       833         -
-#18  Extended offline    Completed without error       00%       809         -
-#19  Extended offline    Completed without error       00%       785         -
-#20  Extended offline    Completed without error       00%       761         -
-#21  Extended offline    Completed without error       00%       737         -
-
-SMART Selective self-test log data structure revision number 1
- SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
-    1        0        0  Not_testing
-    2        0        0  Not_testing
-    3        0        0  Not_testing
-    4        0        0  Not_testing
-    5        0        0  Not_testing
-Selective self-test flags (0x0):
-  After scanning selected spans, do NOT read-scan remainder of disk.
-If Selective self-test is pending on power-up, resume after 0 minute delay.
diff --git a/www/examples/atapi_cdrw_smt_a.html b/www/examples/atapi_cdrw_smt_a.html
deleted file mode 100644
index 3e6cea3184ec067f6462097c24d5d00c78abf359..0000000000000000000000000000000000000000
--- a/www/examples/atapi_cdrw_smt_a.html
+++ /dev/null
@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <meta http-equiv="content-type"
- content="text/html; charset=ISO-8859-1">
-  <title>atapi_cdrw_smt_a</title>
-</head>
-<body>
-<span style="font-family: monospace;">smartctl version 5.1-12 Copyright
-(C) 2002-3 Bruce Allen</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Home page is
-http://smartmontools.sourceforge.net/</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Device: ATAPI&nbsp;&nbsp;&nbsp;
-CD-RW 48X16&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Version: A.RZ</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Device type: CD/DVD</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Local Time is: Thu May 15
-17:24:44 2003 EST</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Device does not support SMART</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Device does not support Error
-Counter logging</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Device does not support Self Test
-logging</span>
-</body>
-</html>
diff --git a/www/examples/ativ_36_smt_a.html b/www/examples/ativ_36_smt_a.html
deleted file mode 100644
index c5dc6b2b326e1020fdd4e59f7aac524fb2b4c796..0000000000000000000000000000000000000000
--- a/www/examples/ativ_36_smt_a.html
+++ /dev/null
@@ -1,61 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <meta http-equiv="content-type"
- content="text/html; charset=ISO-8859-1">
-  <title>Atlas IV 36 WLS smartmontools output</title>
-</head>
-<body>
-<span style="font-family: monospace;">Device: QUANTUM&nbsp; ATLAS IV 36
-WLS&nbsp; Version: 0A0A </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Serial number: 363930037828 </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Local Time is: Sat May&nbsp; 3
-21:20:08 2003 EST </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Device supports SMART and is
-Disabled </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Temperature Warning Enabled </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">SMART Sense: Ok! </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Current Drive
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp; 35 C </span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Error counter log: </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Errors Corrected&nbsp;&nbsp;&nbsp; Total&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Total&nbsp;&nbsp; Correction&nbsp;&nbsp;&nbsp;&nbsp;
-Gigabytes&nbsp;&nbsp;&nbsp; Total </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-delay:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [rereads/&nbsp;&nbsp;&nbsp;
-errors&nbsp;&nbsp; algorithm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-processed&nbsp;&nbsp;&nbsp; uncorrected </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-minor | major&nbsp; rewrites]&nbsp; corrected&nbsp;
-invocations&nbsp;&nbsp; [10^9 bytes]&nbsp; errors </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">read:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-65535&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-4.295&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">write:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-4.295&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 </span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Non-medium error
-count:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 13</span>
-</body>
-</html>
diff --git a/www/examples/bnch_DLT1.html b/www/examples/bnch_DLT1.html
deleted file mode 100644
index efa6a371318df3b037a982309b3805b82d334752..0000000000000000000000000000000000000000
--- a/www/examples/bnch_DLT1.html
+++ /dev/null
@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <meta http-equiv="content-type"
- content="text/html; charset=ISO-8859-1">
-  <title>benchmark tape systems DLT1</title>
-</head>
-<body>
-<span style="font-family: monospace;">smartctl version 5.1-11 Copyright
-(C) 2002-3 Bruce Allen </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Home page is </span><a
- class="moz-txt-link-freetext"
- href="http://smartmontools.sourceforge.net/"
- style="font-family: monospace;">http://smartmontools.sourceforge.net/</a><span
- style="font-family: monospace;"> </span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Device: BNCHMARK
-DLT1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Version: 391B </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Serial number: 0000052369<br>
-Device type: tape</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Local Time is: Sun May&nbsp; 4
-11:53:27 2003 EST </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">device is NOT READY (media
-absent, spun down, etc) </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">TapeAlert Supported </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">TapeAlert: Ok! </span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Error counter log: </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Errors Corrected&nbsp;&nbsp;&nbsp; Total&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Total&nbsp;&nbsp; Correction&nbsp;&nbsp;&nbsp;&nbsp;
-Gigabytes&nbsp;&nbsp;&nbsp; Total </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-delay:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [rereads/&nbsp;&nbsp;&nbsp;
-errors&nbsp;&nbsp; algorithm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-processed&nbsp;&nbsp;&nbsp; uncorrected </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-minor | major&nbsp; rewrites]&nbsp; corrected&nbsp;
-invocations&nbsp;&nbsp; [10^9 bytes]&nbsp; errors </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">read:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0.000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">write:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-5.920&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Warning: device does not support
-Self Test Logging</span>
-</body>
-</html>
diff --git a/www/examples/bnch_robot.html b/www/examples/bnch_robot.html
deleted file mode 100644
index 5069b96191292ddc95c1c81cc18c20c685b3d7d5..0000000000000000000000000000000000000000
--- a/www/examples/bnch_robot.html
+++ /dev/null
@@ -1,64 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <meta http-equiv="content-type"
- content="text/html; charset=ISO-8859-1">
-  <title>Benchmark tape systems robot</title>
-</head>
-<body>
-<span style="font-family: monospace;">smartctl version 5.1-11 Copyright
-(C) 2002-3 Bruce Allen </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Home page is </span><a
- class="moz-txt-link-freetext"
- href="http://smartmontools.sourceforge.net/"
- style="font-family: monospace;">http://smartmontools.sourceforge.net/</a><span
- style="font-family: monospace;"> </span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Device:
-STK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-L20&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Version: 0207 </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Serial number: LLC02207812<br>
-Device type: medium changer</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Local Time is: Sun May&nbsp; 4
-11:54:39 2003 EST </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Temperature Warning Disabled or
-Not Supported </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">TapeAlert Supported </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">TapeAlert Errors (C=Critical,
-W=Warning, I=Informational): </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">[0x02] W: There is a problem with
-the library mechanism. If problem persists, </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;call the library supplier
-help line. </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">[0x0d] W: There is a potential
-problem with the drive ejecting cartridges or </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;with the library mechanism
-picking a cartridge from a slot. </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;1. No action needs to be
-taken at this time. </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;2. If the problem persists,
-call the library supplier help line. </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">[0x0e] W: There is a potential
-problem with the library mechanism placing a </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;cartridge into a slot. </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;1. No action needs to be
-taken at this time. </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;2. If the problem persists,
-call the library supplier help line. </span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">No Error counter log to report </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Warning: device does not support
-Self Test Logging</span>
-</body>
-</html>
diff --git a/www/examples/ddrs_39130_smt_a.html b/www/examples/ddrs_39130_smt_a.html
deleted file mode 100644
index e920d71a1f8def59fe8d5930e2431dcfb3109511..0000000000000000000000000000000000000000
--- a/www/examples/ddrs_39130_smt_a.html
+++ /dev/null
@@ -1,82 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <meta http-equiv="content-type"
- content="text/html; charset=ISO-8859-1">
-  <title>ddrs_39130_smt_a.html</title>
-</head>
-<body>
-<span style="font-family: monospace;">smartctl version 5.1-12 Copyright
-(C) 2002-3 Bruce Allen</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Home page is
-http://smartmontools.sourceforge.net/</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&nbsp;</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Device:
-IBM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-DDRS-39130D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Version: DC1B</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Serial number: QE702689</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Device type: disk</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Local Time is: Thu May 15
-16:51:27 2003 EST</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Device supports SMART and is
-Enabled</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Temperature Warning Disabled or
-Not Supported</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">SMART Health Status: OK</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&nbsp;</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Error counter log:</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Errors Corrected&nbsp;&nbsp;&nbsp; Total&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Total&nbsp;&nbsp; Correction&nbsp;&nbsp;&nbsp;&nbsp;
-Gigabytes&nbsp;&nbsp;&nbsp; Total</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-delay:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [rereads/&nbsp;&nbsp;&nbsp;
-errors&nbsp;&nbsp; algorithm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-processed&nbsp;&nbsp;&nbsp; uncorrected</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-minor | major&nbsp; rewrites]&nbsp; corrected&nbsp;
-invocations&nbsp;&nbsp; [10^9 bytes]&nbsp; errors</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">read:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-4.295&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">write:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-4.295&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">verify:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0.072&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&nbsp;</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Non-medium error
-count:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Device does not support Self Test
-logging</span>
-</body>
-</html>
diff --git a/www/examples/hp_c5713a_smt_a.html b/www/examples/hp_c5713a_smt_a.html
deleted file mode 100644
index 4c4beea98338e0e74f5eb441caec307f1bb102e2..0000000000000000000000000000000000000000
--- a/www/examples/hp_c5713a_smt_a.html
+++ /dev/null
@@ -1,13 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <meta http-equiv="content-type"
- content="text/html; charset=ISO-8859-1">
-  <title>HP DDS-4 drive smartmontools output</title>
-</head>
-<body>
-<pre wrap="">smartctl version 5.1-11 Copyright (C) 2002-3 Bruce Allen<br>Home page is <a
- class="moz-txt-link-freetext"
- href="http://smartmontools.sourceforge.net/">http://smartmontools.sourceforge.net/</a><br><br>Device: HP       C5713A           Version: H910<br>Local Time is: Thu May  1 23:26:38 2003 EEST<br>Temperature Warning Disabled or Not Supported<br>TapeAlert Supported<br>TapeAlert: Ok!<br><br>Error counter log:<br>          Errors Corrected    Total      Total   Correction     Gigabytes    Total<br>              delay:       [rereads/    errors   algorithm      processed    uncorrected<br>            minor | major  rewrites]  corrected  invocations   [10^9 bytes]  errors<br>read:          0        0         0         2          0          0.000           0<br>write:         0        0         0         0          0          0.000           0<br>Warning: device does not support Self Test Logging</pre>
-</body>
-</html>
diff --git a/www/examples/mam3184_smt_a.html b/www/examples/mam3184_smt_a.html
deleted file mode 100644
index b2896462e43f6c797e65f83180f7db7b6debc1d4..0000000000000000000000000000000000000000
--- a/www/examples/mam3184_smt_a.html
+++ /dev/null
@@ -1,170 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <title>mam3184_smt_a.html</title>
-  <meta http-equiv="content-type"
- content="text/html; charset=ISO-8859-1">
-</head>
-<body>
-<span style="font-family: monospace;">smartctl version 5.1-12 Copyright
-(C) 2002-3 Bruce Allen</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Home page is
-http://smartmontools.sourceforge.net/</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Device: FUJITSU&nbsp;
-MAM3184MP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Version: 0106</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Serial number: UKS0P2300CK0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Device type: disk</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Local Time is: Thu May 15
-15:35:10 2003 EST</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Device supports SMART and is
-Enabled</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Temperature Warning Enabled</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">SMART Health Status: OK</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Current Drive
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp; 42 C</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Drive Trip
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 65 C</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Manufactured in week 10 of year
-2002</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Current start stop
-count:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 280 times</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Recommended start stop
-count:&nbsp; 10000 times</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Error counter log:</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Errors Corrected&nbsp;&nbsp;&nbsp; Total&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Total&nbsp;&nbsp; Correction&nbsp;&nbsp;&nbsp;&nbsp;
-Gigabytes&nbsp;&nbsp;&nbsp; Total</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-delay:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [rereads/&nbsp;&nbsp;&nbsp;
-errors&nbsp;&nbsp; algorithm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-processed&nbsp;&nbsp;&nbsp; uncorrected</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-minor | major&nbsp; rewrites]&nbsp; corrected&nbsp;
-invocations&nbsp;&nbsp; [10^9 bytes]&nbsp; errors</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">read:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-510.626&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">write:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-13&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-769.950&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Non-medium error
-count:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 855</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">SMART Self-test log</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Num&nbsp;
-Test&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-segment&nbsp; LifeTime&nbsp; LBA_first_err [SK ASC ASQ]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;
-Description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-number&nbsp;&nbsp; (hours)</span><br style="font-family: monospace;">
-<span style="font-family: monospace;"># 1&nbsp; Background
-long&nbsp;&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;
-980&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 2&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;
-788&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 3&nbsp; Background
-long&nbsp;&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;
-768&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 4&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;
-665&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 5&nbsp; Background
-long&nbsp;&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;
-635&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 6&nbsp; Foreground
-long&nbsp;&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;
-635&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 7&nbsp; Foreground
-long&nbsp;&nbsp; Interrupted (bus reset ?)&nbsp;&nbsp; -&nbsp;&nbsp;
-634&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 8&nbsp; Foreground
-long&nbsp;&nbsp; Interrupted (bus reset ?)&nbsp;&nbsp; -&nbsp;&nbsp;
-634&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 9&nbsp; Foreground
-long&nbsp;&nbsp; Interrupted (bus reset ?)&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">#10&nbsp; Foreground short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">#11&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Long (extended) Self Test
-duration: 837 seconds [13.9 minutes]</span><br>
-<tt><br>
-</tt>
-</body>
-</html>
diff --git a/www/examples/mam3184_smt_health.html b/www/examples/mam3184_smt_health.html
deleted file mode 100644
index 37a41fb18685bd2b8a5c35ece46f9b56664d442a..0000000000000000000000000000000000000000
--- a/www/examples/mam3184_smt_health.html
+++ /dev/null
@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <title>mam3184_smt_health.html</title>
-  <meta http-equiv="content-type"
- content="text/html; charset=ISO-8859-1">
-</head>
-<body>
-<span style="font-family: monospace;">smartctl version 5.1-12 Copyright
-(C) 2002-3 Bruce Allen</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Home page is
-http://smartmontools.sourceforge.net/</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">SMART Health Status: FAILURE
-PREDICTION THRESHOLD EXCEEDED (FALSE) [asc=5d,ascq=ff]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Current Drive
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp; 42 C</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Drive Trip
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 65 C</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Manufactured in week 10 of year
-2002</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Current start stop
-count:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 280 times</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Recommended start stop
-count:&nbsp; 10000 times</span><br>
-<tt><br>
-</tt>
-</body>
-</html>
diff --git a/www/examples/map3735_smt_a.html b/www/examples/map3735_smt_a.html
deleted file mode 100644
index 928904f1bd0e06b1a78b85815f93ae34c24bff38..0000000000000000000000000000000000000000
--- a/www/examples/map3735_smt_a.html
+++ /dev/null
@@ -1,86 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <meta http-equiv="content-type"
- content="text/html; charset=ISO-8859-1">
-  <title>Fujitsu MAP 3735 smartmontools output</title>
-</head>
-<body>
-<span style="font-family: monospace;">smartctl version 5.1-10 Copyright
-(C) 2002-3 Bruce Allen </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Home page is </span><a
- class="moz-txt-link-freetext"
- href="http://smartmontools.sourceforge.net/"
- style="font-family: monospace;">http://smartmontools.sourceforge.net/</a><span
- style="font-family: monospace;"> </span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Device: FUJITSU&nbsp;
-MAP3735NP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Version: 0105 </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Serial number: UPG0P2A00491 </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Local Time is: Sat May&nbsp; 3
-21:22:09 2003 EST </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Device supports SMART and is
-Disabled </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Temperature Warning Disabled or
-Not Supported </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">SMART Sense: Ok! </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Current Drive
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp; 39 C </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Drive Trip
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 65 C </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Manufactured in week 40 of year
-2002 </span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Current start stop
-count:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 14 times </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Recommended start stop
-count:&nbsp; 10000 times </span><br style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Error counter log: </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Errors Corrected&nbsp;&nbsp;&nbsp; Total&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Total&nbsp;&nbsp; Correction&nbsp;&nbsp;&nbsp;&nbsp;
-Gigabytes&nbsp;&nbsp;&nbsp; Total </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-delay:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [rereads/&nbsp;&nbsp;&nbsp;
-errors&nbsp;&nbsp; algorithm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-processed&nbsp;&nbsp;&nbsp; uncorrected </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-minor | major&nbsp; rewrites]&nbsp; corrected&nbsp;
-invocations&nbsp;&nbsp; [10^9 bytes]&nbsp; errors </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">read:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-810.959&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">write:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-72.300&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 </span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Non-medium error
-count:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 27 </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">No self-tests have been logged </span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Long (extended) Self Test
-duration: 2872 seconds [47.9 minutes]</span>
-</body>
-</html>
diff --git a/www/examples/st318451_smt_a.html b/www/examples/st318451_smt_a.html
deleted file mode 100644
index fcbadaa880c2b67ad2e9431b3080bd83bb194176..0000000000000000000000000000000000000000
--- a/www/examples/st318451_smt_a.html
+++ /dev/null
@@ -1,185 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <title>st318451_smt_a</title>
-  <meta http-equiv="content-type"
- content="text/html; charset=ISO-8859-1">
-</head>
-<body>
-<span style="font-family: monospace;">smartctl version 5.1-12 Copyright
-(C) 2002-3 Bruce Allen</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Home page is
-http://smartmontools.sourceforge.net/</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Device: SEAGATE&nbsp;
-ST318451LW&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Version: 0003</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Serial number:
-3CC01TTG000071033QEA</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Device type: disk</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Local Time is: Thu May 15
-17:12:14 2003 EST</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Device supports SMART and is
-Enabled</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Temperature Warning Enabled</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">SMART Health Status: OK</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Current Drive
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp; 34 C</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Drive Trip
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 65 C</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Error counter log:</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Errors Corrected&nbsp;&nbsp;&nbsp; Total&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Total&nbsp;&nbsp; Correction&nbsp;&nbsp;&nbsp;&nbsp;
-Gigabytes&nbsp;&nbsp;&nbsp; Total</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-delay:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [rereads/&nbsp;&nbsp;&nbsp;
-errors&nbsp;&nbsp; algorithm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-processed&nbsp;&nbsp;&nbsp; uncorrected</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-minor | major&nbsp; rewrites]&nbsp; corrected&nbsp;
-invocations&nbsp;&nbsp; [10^9 bytes]&nbsp; errors</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">read:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-21&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-21&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-21&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-100.431&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">write:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0.016&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">verify:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0.010&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Non-medium error
-count:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">SMART Self-test log</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Num&nbsp;
-Test&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-segment&nbsp; LifeTime&nbsp; LBA_first_err [SK ASC ASQ]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;
-Description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-number&nbsp;&nbsp; (hours)</span><br style="font-family: monospace;">
-<span style="font-family: monospace;"># 1&nbsp; Background
-long&nbsp;&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;
-11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 2&nbsp; Background
-long&nbsp;&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;
-11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 3&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;
-11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 4&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;
-10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 5&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 6&nbsp; Background
-long&nbsp;&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 7&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 8&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;"># 9&nbsp; Background
-long&nbsp;&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">#10&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">#11&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">#12&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">#13&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Long (extended) Self Test
-duration: 587 seconds [9.8 minutes]</span><br>
-<tt><br>
-</tt>
-</body>
-</html>
diff --git a/www/examples/st336754_smt_a.html b/www/examples/st336754_smt_a.html
deleted file mode 100644
index aaea65b2e71abc3af21ae7cecd0f404e8f55aafd..0000000000000000000000000000000000000000
--- a/www/examples/st336754_smt_a.html
+++ /dev/null
@@ -1,130 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="content-type">
-  <title>st336754_smt_a</title>
-</head>
-<body>
-<span style="font-family: monospace;"># smartctl -a /dev/sdb</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">smartctl version 5.37
-[i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Home page is
-http://smartmontools.sourceforge.net/</span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Device: SEAGATE&nbsp;
-ST336754SS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Version: 0003</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Serial number:</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Device type: disk</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Transport protocol: SAS</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Local Time is: Sun Oct 22
-21:01:48 2006 EDT</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Device supports SMART and is
-Enabled</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">Temperature Warning Enabled</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">SMART Health Status: OK</span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Current Drive
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp; 44 C</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Drive Trip
-Temperature:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 68 C</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Elements in grown defect list: 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Vendor (Seagate) cache information</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp; Blocks sent to initiator =
-198739843</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp; Blocks received from
-initiator = 0</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp; Blocks read from cache and
-sent to initiator = 13554175</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp; Number of read and write
-commands whose size &lt;= segment size = 1943196</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp; Number of read and write
-commands whose size &gt; segment size = 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Vendor (Seagate/Hitachi) factory
-information</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp; number of hours powered up
-= 634.37</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp; number of minutes until
-next internal SMART test = 62</span><br style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Error counter log:</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Errors Corrected
-by&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Total&nbsp;&nbsp; Correction&nbsp;&nbsp;&nbsp;&nbsp;
-Gigabytes&nbsp;&nbsp;&nbsp; Total</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-ECC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-rereads/&nbsp;&nbsp;&nbsp; errors&nbsp;&nbsp;
-algorithm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; processed&nbsp;&nbsp;&nbsp;
-uncorrected</span><br style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-fast | delayed&nbsp;&nbsp; rewrites&nbsp; corrected&nbsp;
-invocations&nbsp;&nbsp; [10^9 bytes]&nbsp; errors</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">read:&nbsp;&nbsp;&nbsp;&nbsp;
-350782&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;
-350782&nbsp;&nbsp;&nbsp;&nbsp;
-350782&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-141.464&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">write:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0.012&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">verify:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-568&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-568&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-568&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-0.063&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Non-medium error
-count:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0</span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">SMART Self-test log</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">Num&nbsp;
-Test&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Status&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-segment&nbsp; LifeTime&nbsp; LBA_first_err [SK ASC ASQ]</span><br
- style="font-family: monospace;">
-<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;
-Description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-number&nbsp;&nbsp; (hours)</span><br style="font-family: monospace;">
-<span style="font-family: monospace;"># 1&nbsp; Background short&nbsp;
-Completed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp;&nbsp;&nbsp;&nbsp;
-634&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-- [-&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; -]</span><br
- style="font-family: monospace;">
-<br style="font-family: monospace;">
-<span style="font-family: monospace;">Long (extended) Self Test
-duration: 603 seconds [10.1 minutes]</span>
-</body>
-</html>
diff --git a/www/index.html b/www/index.html
deleted file mode 100644
index 2489a3deb2ad3b256422b044923b347ab0d979b4..0000000000000000000000000000000000000000
--- a/www/index.html
+++ /dev/null
@@ -1,1289 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
- <title>smartmontools Home Page (last updated $Date: 2006/11/04 20:04:26 $)</title>
- <link rev="made" href="mailto:smartmontools-support&#64;sourceforge.net" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
- <meta name="description" content="smartmontools Home Page" />
- <meta name="keywords" content="S.M.A.R.T., SMART, FreeBSD, Linux, NetBSD, Solaris, Windows, disk, monitor, monitoring" />
-</head>
-<body>
-
-<!-- $Id: index.html,v 1.208 2006/11/04 20:04:26 chrfranke Exp $ -->
-
-<div align="center">
-  <img src="smart_logo.gif" border="0" width="105" height="59" alt="SMART LOGO" />
-  <br />
-  <h1><font color="#3333ff">smartmontools Home Page</font></h1>
-</div>
-
-<p>Welcome! This is the home page for the smartmontools package.</p>
-
-<font color="#ff0000">
-<b>NEWS:</b>
-</font>
-<ul>
-<li><font color="#ff0000">Smartmontools 5.36 (stable) was released 2006-04-16, see
-<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/NEWS?revision=RELEASE_5_36&amp;view=markup">
-NEWS</a> and
-<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/CHANGELOG?revision=RELEASE_5_36&amp;view=markup">
-CHANGELOG</a> for details.
-</font></li>
-<li><font color="#ff0000">SourceForge CVS architecture has changed 2006-05-12, please read
-notes <a href="#CVSInstall">below</a> if you install smartmontools from CVS.</font></li>
-<li><font color="#ff0000">A Windows installer version of smartmontools 5.36 was released
-2006-06-06, see <a href="#WindowsInstall">below</a>.</font></li>
-<li><font color="#ff0000">New RAID controller support (CCISS and HighPoint on Linux,
-3ware on Windows) was added, see <a href="#FAQ-RAID">below</a>.</font></li>
-</ul>
-<font color="#ff0000">
-Please report problems (or success!) with the new release to the
-<a href="http://lists.sourceforge.net/lists/listinfo/smartmontools-support">
-smartmontools-support mailing list</a>.
-</font>
-
-
-<p>The smartmontools package contains two utility programs
-(<font color="#3333ff"><b>smartctl</b></font> and
-<font color="#3333ff"><b>smartd</b></font>) to control and monitor storage
-systems using the Self-Monitoring, Analysis and Reporting Technology
-System (SMART) built into most modern ATA and SCSI hard
-disks.&#160; In many cases, these utilities will provide advanced warning
-of disk degradation and failure.</p> 
-
-<p>Smartmontools is originally derived from the Linux <a
-href="http://sourceforge.net/projects/smartsuite/">smartsuite
-package</a>, and includes support for ATA/ATAPI-3 to -7 disks and SCSI
-disk and tape devices.  It should run on any modern Darwin (Mac OSX),
-Linux, FreeBSD, NetBSD, OpenBSD, Solaris, OS/2, eComStation or <a
-href="#windows">Windows</a> system. Alternatively, it can also be run
-from one of the <a href="#bootable">bootable CDs or floppies containing
-smartmontools</a>.</p>
-
-<p>For printing convenience, everything except for the <a
-href="#sampleoutput">example output</a> is on a single page.</p>
-
-<hr size="2" />
-
-<ul>
-<li><a href="http://www.linuxjournal.com/article.php?sid=6983">
-Monitoring Hard Disks with SMART (Linux Journal, January 2004, page 74)</a></li>
-<li><a href="#howtodownload">How to download and install
-smartmontools</a></li>
-<li><a href="#PROBLEMS">Serious Problem Reports (system lockup, etc.)</a></li>
-<li><a href="#FAQ">Frequently Asked Questions</a></li>
-<li><a href="#scsi">SCSI disks and tapes (TapeAlert)</a></li>
-<li><a href="#testinghelp">FireWire, USB, and SATA disks/tapes</a></li>
-<li><a href="#differfromsmartsuite">How does smartmontools differ from
-smartsuite?</a></li>
-<li><a href="#references">Useful references on SMART and ATA/ATAPI-5,
--6, and -7</a></li>
-<li><a href="#sampleoutput">Example output from smartmontools</a>
-<b>smartctl</b> utility</li>
-<li><a href="http://smartmontools.cvs.sourceforge.net/smartmontools/">CVS
-repository</a> and <a href="http://sourceforge.net/projects/smartmontools/">SourceForge's
-Project Page</a></li>
-<li>Mailing List <a href="http://lists.sourceforge.net/lists/listinfo/smartmontools-support">Information</a>
-and <a href="http://sourceforge.net/mailarchive/forum.php?forum=smartmontools-support">Archives</a>
-(Archive has <b>Search Box</b> in top left corner). <a href="#altmail">Alternative</a> (and usually up to date) archives.</li>
-<li><a name="man"></a>
-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>
-</ul>
-
-<hr size="2" />
-
-<b><a name="howtodownload"></a>How to download and install
-smartmontools</b>
-
-<p>There are different ways to get and install
-smartmontools.&#160; You can use any of the procedures below
-(the fourth is for Debian Linux only).&#160; Just after "Method 6" below are
-some instructions for trying out smartmontools once you have completed
-the installation. The 
-<b><a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/INSTALL?view=markup">
-INSTALL</a></b> file contains additional information.
-</p>
-<b>First Method (Redhat/Fedora Linux) - Install from the RPM file</b>
-<ul>
-<li>Download the latest binary RPM file (<tt>*.rpm</tt>) from <a href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>.&#160;
-Don't get the SRPM file (<tt>*.src.rpm</tt>).<br/> SuSE users: use one of the SuSE-specific RPM files.</li>
-<li>Install it using RPM.&#160; <i>You must be root to do this</i>:
-<pre>su root (enter root password)
-rpm -ivh smartmontools-5.32.i386.rpm</pre>
-For most users, this is all that is needed.</li>
-<li>If you receive an error message, you have probably previously
-installed the <tt>smartsuite</tt> package, or RedHat's
-<tt>kernel-utils</tt> package, which provide older versions of the
-<tt>smartd</tt> and <tt>smartctl</tt> utilities.&#160; In this case you
-should use the <tt>--nodeps</tt> or <tt>--force</tt> arguments of rpm to
-replace these two utilities:
-<pre>rpm -ivh --nodeps --force smartmontools-5.32.i386.rpm</pre></li>
-<li>If you want to remove the package (<tt>rpm -e smartmontools</tt>)
-and your system does not have <tt>chkconfig</tt> installed, you may need
-to use:
-<pre>rpm -e --noscripts smartmontools</pre></li>
-</ul>
-
-<b>Second Method (Linux/Solaris/FreeBSD/NetBSD/OpenBSD/Cygwin) - Install from the source tarball</b>
-<ul>
-<li>Download the latest source tarball from <a
-href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>.
-Note: you probably want the most recent stable release. Stable releases have
-even-numbered extensions, and unstable experimental releases have
-odd-numbered extensions.</li>
-<li>Uncompress the tarball:
-<pre>tar zxvf smartmontools-5.32.tar.gz</pre></li>
-<li>The previous step created a directory called <tt>smartmontools-5.32</tt>
-containing the code.&#160; Go to that directory, build, and install:
-<pre>cd smartmontools-5.32
-./configure
-make
-make install
-</pre></li>
-<li> Note that the <tt>./configure</tt> step above is not possible for releases &lt;=5.1-18, you 
-have to edit the Makefile by hand to change installation paths. For releases &gt;=5.19, <tt>./configure</tt>
-can take optional arguments. These optional arguments are fully explained in the
-<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/INSTALL?view=markup">INSTALL</a>
-file. The most important one is <tt>--prefix</tt> to change the default installation directories.<p>
-<i>Please note that the default installation location changed in versions &gt;=5.31.</i>
-If you don't pass any arguments to <tt>./configure</tt> all files will reside under
-<b>/usr/local</b> to not interfere with files from your distribution. For more detailed
-information please also refer to the 
-<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/INSTALL?view=markup">INSTALL</a>
-document.
-</p>
-</li>
-<li>To compile from another directory (avoids overwriting virgin files from the smartmontools package)
-replace <tt>./configure [options]</tt> by:
-<pre>
-mkdir objdir
-cd objdir
-../configure [options]
-</pre></li>
-<li>To install to another destination (useful for testing and to avoid overwriting an existing smartmontools installation)
-replace <tt>make install</tt> by:
-<pre>
-make DESTDIR=/home/myself/smartmontools-test install
-</pre>
-Use a full path: <tt>~/smartmontools-test</tt> won't work.
-</li>
-<li>Unless the destination directory is your home directory (or a location that you have write permission)
-only root can do <tt>make install</tt></li>
-</ul>
-
-<b><a name="CVSInstall"></a>
-Third Method (Darwin/FreeBSD/Linux/NetBSD/OpenBSD/Solaris/Cygwin) - Install from the CVS repository</b>
-<ul>
-<li><p><font color="#ff0000">Due to the new the SourceForge CVS
-architecture, the hostname for CVS access has changed from
-<tt>cvs.sourceforge.net</tt> to <tt>smartmontools.cvs.sourceforge.net</tt>.
-To update a copy of smartmontools checked out before 2006-05-12, change all
-the <tt>*/CVS/Root</tt> files accordingly.
-</font></p></li>
-
-<li><p>One of the really cool things about CVS is that you can get
-<i>any</i> version of the code you want, from the first release up the
-the most current development version.&#160; And it's trivial, because
-each release is <u>tagged</u> with a name like
-<tt>RELEASE_5_1_18</tt>.&#160; You can see what the different names are
-by looking at the <a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/">
-CVS repository</a>.&#160; You'll see the tag names in the little scroll
-window where it says "Show only files with tag".&#160; All you need to
-do to get the latest development code is
-(but note that the development code may be unstable, and that the
-documentation and code may be inconsistent):</p>
-
-<pre>cvs -d:pserver:anonymous@smartmontools.cvs.sourceforge.net:/cvsroot/smartmontools login (when prompted for a password, just press Enter)
-cvs -d:pserver:anonymous@smartmontools.cvs.sourceforge.net:/cvsroot/smartmontools co sm5</pre></li>
-
-<li>To instead get the 5.1-16 release:
-
-<pre>cvs -d:pserver:anonymous@smartmontools.cvs.sourceforge.net:/cvsroot/smartmontools co -r RELEASE_5_1_16 sm5</pre></li>
-
-<li><p>This will create a subdirectory called <tt>sm5/</tt> containing the
-code.&#160; Go to that directory, build, and install:</p>
-<pre>cd sm5
-./autogen.sh
-./configure
-make
-make install
-</pre>
-
-<ul>
-<li>See notes under <b>Second method - install from source tarball</b> for different options to <tt>./configure</tt>
-and other useful remarks.</li>
-<li>Skip <tt>./autogen.sh</tt> and <tt>./configure</tt> for tagged releases
-&lt;= 5.1-18 (RELEASE_5_X_Y, where X = 0 or 1 and Y = 0 to 18).</li>
-<li>If you get the current sources (<tt>cvs co</tt> with no arguments or do <tt>cvs up
--A</tt>) then you <i>will</i>  need those two additional steps.</li>
-</ul></li>
-
-<li>To update your sources to the 5.1-18 release:
-<pre>cd sm5
-cvs up -r RELEASE_5_1_18</pre></li>
-
-<li>To update any tagged release to the latest development code:
-
-<pre>cd sm5
-cvs up -A</pre></li>
-</ul>
-
-<b>Fourth Method (Debian Linux) - Install the Debian package</b>
-<ul>
-<li>
-The latest version of the smartmontools package in <i>.deb</i> format is
-available at the  <a href="http://packages.debian.org/unstable/utils/smartmontools.html">Debian smartmontools
-package page</a>.
-This package is for the (unreleased) <a href="http://www.debian.org/releases/">unstable</a>
-distribution.</li>
-<li>If you're running Debian <a
-href="http://www.debian.org/releases/stable/">stable</a> please download a
-backport to stable <a
-href="http://www.backports.org/debian/pool/main/s/smartmontools/">here</a>.
-These packages are provided by <a
-href="http://www.backports.org">www.backports.org</a>.</li>
-<li>
-You can then install the package using:
-<pre>
-dpkg -i smartmontools_5.36-1_i386.deb
-</pre>
-If you prefer to fetch the packages using apt, please read the instructions at
-<a href="http://www.backports.org/dokuwiki/doku.php?id=instructions">backports.org</a>.
-</li>
-</ul>
-
-<b><a name="CygwinInstall"></a>
-Fifth Method (Windows with <a href="http://www.cygwin.com/">Cygwin</a>
-installed) - Install the Cygwin package
-</b>
-<ul>
-<li>Starting with CVS snapshot 2005-11-15, smartmontools is part of
-the <a href="http://cygwin.com/packages/">Cygwin distribution</a>.
-A list of available smartmontools packages and their contents is
-<a href="http://cygwin.com/packages/smartmontools/">here</a>.
-</li>
-<li><p>To update your installation, click on the "Install or update now!"
-link on the <a href="http://cygwin.com/">Cygwin web page</a>.
-This downloads <tt>setup.exe</tt> to your system.
-Then, run setup and answer all of the questions.
-Select smartmontools package in the "Utils" category.</p>
-</li>
-<li><p>The optional source package (<tt>smartmontools-*-src.tar.bz2</tt>)
-can be used to build both the Cygwin and the Windows binary packages
-on Cygwin.
-Refer to the file <tt>/usr/share/doc/Cygwin/smartmontools-*.README</tt>
-for details.</p>
-</li>
-</ul>
-
-<b><a name="WindowsInstall"></a>
-Sixth Method (Windows) - Install the Windows package
-</b>
-<ul>
-<li>Download and run the latest smartmontools
-<a href="http://nsis.sourceforge.net/Main_Page">NSIS</a>-installer
-(<tt>*.win32-setup.exe</tt>) from
-<a href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>.
-<ul>
-<li>The default install type "Full" creates start menu shortcuts
-including an uninstaller, and adds the install directory to the PATH variable.
-</li>
-<li>Select install type "Extract files only" to disable these extra
-components.
-</li>
-<li><font color="#ff0000">
-Virus scanners occasionally produce false positive virus reports for
-NSIS-installers, see the
-<a href="http://nsis.sourceforge.net/NSIS_False_Positives">NSIS False Positives page</a>.
-If this is the case for the smartmontools installer, please send a report to the
-<a href="mailto:smartmontools-support&#64;lists.sourceforge.net">smartmontools-support
-mailing list</a>.
-</font></li>
-</ul>
-</li>
-<li><p>Or download and unzip the latest smartmontools Windows archive
-(<tt>*.win32.zip</tt>) from
-<a href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>.
-</p></li>
-<li><p>More recent (and probably unstable) Windows test releases build from CVS
-snapshots are available <a href="http://smartmontools-win32.dyndns.org/smartmontools/">here</a>.
-</p></li>
-</ul>
-
-
-<b>After installing it using Method 1, 2, 3, 4 or 5 above, you can read the
-man pages, and try out the commands:</b>
-
-<pre>
-man smartd.conf
-man smartctl
-man smartd
-/usr/sbin/smartctl -s on -o on -S on /dev/hda (only root can do this)
-/usr/sbin/smartctl -a /dev/hda (only root can do this)</pre>
-
-<p>Note that the default location for the manual pages are
-<tt>/usr/share/man/man5</tt> and <tt>/usr/share/man/man8</tt>.&#160; If
-"<tt>man</tt>" doesn't find them, then you may need to add
-<tt>/usr/share/man</tt> to your <tt>MANPATH</tt> environment
-variable.</p>
-
-<p>The Windows package (see Method 6 above) provides preformatted man pages
-in <tt>*.html</tt> and <tt>*.txt</tt> format.</p>
-
-<hr size="2" />
-
-<a name="PROBLEMS"></a><b>Serious Problem Reports</b>
-<p>If a serious problem gets reported to us, it gets added to the
-<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/WARNINGS?view=markup">
-WARNINGS</a> file in smartmontools. So far there are only a few problem systems listed.</p>
-
-<hr size="2" />
-
-<a name="FAQ"></a><b>Frequently Asked Questions</b>
-
-<p>If your question is not here, please <a href="mailto:smartmontools-support&#64;lists.sourceforge.net">email
-me</a>.</p>
-
-<ul>
-<li><b>Is the smartmontools File Download/Mail List/Mail Archive/CVS server broken?</b>
-
-<p>SourceForge is a free service, which supports a very large number of
-users and projects. Please check the <a
-href="http://sourceforge.net/docman/display_doc.php?docid=2352&amp;group_id=1">
-SourceForge Site Status Page</a> to see the maintenance schedule and to
-learn if SourceForge is experiencing unscheduled system outages or other
-problems.</p>
-
-<p>
-<a name="altmail"></a>Alternative mailing-list archives are provided by
-<a href="http://gmane.org/find.php?list=smartmontools">Gmane</a> and MARC (<a
-href="http://marc.theaimsgroup.com/?l=smartmontools-support">smartmontools-support</a>
-and <a
-href="http://marc.theaimsgroup.com/?l=smartmontools-database">smartmontools-database</a>).</p>
-
-</li>
-
-<li><b>What do I do if I have problems, or need support?&#160; Suppose
-I want to become a developer, or suggest some new extensions?</b>
-
-<p>First, search the support mailing list archives to see if your
-question has been answered. Instructions are in the following
-paragraph.  If you don't find an answer there, then please send an
-email to the <a
-href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">smartmontools-support
-mailing list</a>.  This is a moderated forum: you are not
-required to subscribe to the list in order to post your question.
-</p>
-
-<p>To search the email archives, first go to the <a
-href="http://sourceforge.net/mailarchive/forum.php?forum=smartmontools-support">
-mailing list archive</a>.  In the top left corner you will see a
-search box: use <b>Mailing List</b> as the type of search. This tool
-works very well.</p>
-
-<p>Note that from time to time SourceForge has mailing list problems
-and you'll get a message telling you that <i>Either your mailing list
-name was misspelled or your mailing list has not been archived yet. If
-this list has just been created, please retry in 2-4 hours</i>.  If
-this happens, you'll have to try again later.  Or use <a
-href="#altmail">alternative</a> (and usually up to date) email
-archives.
-</p>
-
-</li>
-
-<li><b>What are the future plans for smartmontools?</b>
-
-<p>My plan is that smartmontools-5.x will support ATA/ATAPI-5
-disks.&#160; 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.&#160; The "x" will denote revision level, as bugs get found and
-fixed, and as enhancements get added.&#160; If it's possible to maintain
-backwards compatibility, that would be nice, but I don't know if it will
-be possible or practical.</p></li>
-
-<li><b>Why are you doing this?</b>
-
-<p>My research group at U. Wisconsin - Milwaukee runs a <a
-href="http://www.lsc-group.phys.uwm.edu/beowulf/medusa/">beowulf
-cluster</a> with 600 ATA-5 and -6 disks (300 IBM and 300
-Maxtor).&#160; We have more than 50 TB of data stored on the
-system.&#160; I also help out with a <a
-href="http://pandora.aei.mpg.de/merlin/"> cluster</a> at the Albert
-Einstein Institute that has 540 IBM ATA-6 disks (65 TB
-total). It's nice to have advanced warning when a disk is going to
-fail.</p></li>
-
-<li><b>Where can I find distribution-specific bug reports?</b>
-<p>
-The smartmontools package supports a number of different operating
-systems. Some of those operating systems are also distributed by
-multiple sources, and some of these maintain a database of bug
-reports.  Here are links:
-</p>
-
-<ul>
-<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>
-<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>
-<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>
-<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>
-<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>
-<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>
-</ul>
-<p>
-If you can provide additional distribution or OS-specific bug-database links, please send an email to smartmontools-support.
-</p></li>
-
-<li><b>I see some strange output from smartctl.  What does it mean?</b>
-
-<p>The raw SMART attributes (temperature, power-on lifetime, and so
-on) are stored in vendor-specific structures.&#160; Sometime these are
-strange.&#160; Hitachi disks (at least some of them) store power-on
-lifetime in minutes, rather than hours (see next question below).&#160; IBM disks (at least some
-of them) have three temperatures stored in the raw structure, not just
-one.&#160; And so on.&#160; If you find strange output, or unknown
-attributes, please send an email to <a href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support"> 
-smartmontools-support</a> and we'll help you try and figure it
-out.</p></li>
-
-
-<li><b>Why is my disk temperature s reported by smartd as 150 Celsius?</b>
-<p>
-It's not.  Please read the end of the <b>smartd</b> man page (NOTES).
-For example, in the message: <br/>
-<b>'Device: /dev/hda, SMART Attribute: 194 Temperature_Celsius changed from 94 to 93'</b><br/>
-the value given is the 'Normalized' not the 'Raw' Attribute value (the
-disk temperature in this case is about 22 Celsius).  The
-<b>'-R'</b> and <b>'-r'</b> Directives modify this behavior, so that
-the information is printed with the Raw values as well, for example:
-<br/>
-<b>'Device: /dev/hda, SMART Attribute: 194 Temperature_Celsius changed from 94 [Raw 22] to 93 [Raw 23]'</b><br/>
-Here the Raw values are the actual disk temperatures in Celsius.  The
-way in which the Raw values are printed, and the names under which the
-Attributes are reported, is governed by the various
-<b>'-v Num,Description'</b> Directives described in the <b>smartd</b>
-man page. Please see the <b>smartctl</b> manual page for further
-explanation of the differences between Normalized and Raw Attribute
-values.
-</p>
-</li>
-
-<li><b>What are the operating system requirements?</b>
-<p>
-Please see the first section of the
-<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/INSTALL?view=markup">
-INSTALL</a> file.
-</p>
-</li>
-
-<li><b>What Attributes does smartmontools not yet recognize?</b>
-
-<p>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>
-</li>
-
-<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>
-
-<p>On recent disks, Maxtor has started to use Attribute 9 to
-store the power-on disk lifetime in minutes rather than hours.  In this case, use
-the:<br/>
-<tt>-v 9,minutes</tt><br/>
-option to correctly display hours and minutes.
-</p>
-<p>Some models of Fujitsu disks use Attribute 9 to store
-the power-on disk lifetime in seconds. In that case, use the:<br/>
-<tt>-v 9,seconds</tt><br/>
-option to correctly display hours, minutes and seconds.</p>
-</li>
-
-<li><b>The power-on timer (Attribute 9 raw value) on my Maxtor disk acts strange.</b>
-
-<p>There are three related problems with Maxtor's SMART firmware:
-</p>
-
-<p>
-<b>1 - </b> On some Maxtor disks, the raw value of Attribute 9 (Power
-On Time) is <i>supposed</i> to be minutes. But it advances at an
-unpredictable rate, always more slowly than one count per minute.
-This is because when the disk is in idle mode, the counter stops
-advancing.  This is only supposed to happen in standby mode.  This
-will be corrected in Maxtor product lines released after October 2004.
-</p>
-
-<p>
-<b>2 - </b> In Maxtor disks that use the raw value of Attribute 9 as a
-minutes counter, only two bytes (of the six available) are used to
-store the raw value.  So it resets to zero once every 65536=2^16
-minutes, or about once every 1092 hours. This is fixed in all Maxtor
-disks manufactured after July 2003, where the raw value was extended
-to four bytes.
-</p>
-
-<p>
-<b>3 - </b> In Maxtor disks that use the raw value of Attribute 9 as a
-minutes counter, the hour time-stamps in the self-test and ATA error
-logs are calculated by right shifting 6 bits.  This is equivalent to
-dividing by 64 rather than by 60.  As a result, the hour time stamps
-in these logs advance 7% more slowly than they should.  Thus, if you
-do self-tests once per week at the same time, instead of the
-time-stamps being 168 hours apart, they are 157 hours apart.  This is
-also fixed in all Maxtor disks manufactured after July 2003.
-</p>
-</li>
-
-<li><b>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</b>
-
-<p>
-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.
-The power-on lifetime in hours is correctly stored in Attribute
-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>
-</li>
-
-<li><b>The (normalized) WORST Attribute values of my Western Digital
-(WD) disk are <u>larger</u> than the (normalized) CURRENT Attribute
-values</b>
-<p>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>
-</li>
-
-<li><b>Where can I find manufacturer-specific disk-testing
-utilities?</b>
-
-<p>A good listing of such utilities can be found <a
-href="http://www.benchmarkhq.ru/english.html?/be_hdd2.html">here</a>.
-Unfortunately most of these are for MS operating systems, but most can
-be run from an MS-DOS boot disk or from the UBCD (Ultimate Boot CD,
-see <a href="#bootable">below</a>).
-</p>
-
-<p>Note: if you do run one of these utilities, and it identifies the
-meanings of any SMART Attributes that are not known to smartmontools,
-please report them to the mailing list above.
-</p>
-
-<p>These utilities have an important role to fill.  If your disk has
-bad sectors (for example, as revealed by running self-tests with
-smartmontools) and the disk is not able to recover the data from those
-sectors, then the disk will <i>not</i> automatically reallocate those
-damaged sectors from its set of spare sectors, because
-forcing the reallocation to take place may entail some loss of data.
-Because the commands that force such reallocation are
-<i>Vendor Specific</i>, most manufactuers provide a utility for this
-purpose. It may cause data loss but can repair damaged sectors (at
-least, until it runs out of replacement sectors).
-</p>
-</li>
-
-<li><b>When I run <tt>smartd</tt>, the SYSLOG <tt>/var/log/messages</tt>
-contains messages like this:</b>
-<pre>smartd: Reading Device /dev/sdv
-modprobe: modprobe: Can't locate module block-major-65</pre>
-
-<p>This is because when <tt>smartd</tt> starts, if there is no
-configuration file, it looks for all ATA and SCSI devices to monitor
-(matching the pattern <tt>/dev/hd[a-t]</tt> or
-<tt>/dev/sd[a-z]</tt>).&#160; The log messages appear because your
-system doesn't have most of these devices.</p>
-
-<p>The solution is simple: use the <tt>smartd</tt> configuration file
-<tt>/etc/smartd.conf</tt> to specify which devices to monitor.</p></li>
-
-<li><b>What's the story on IBM SMART disks?</b>
-
-<p>Apparently some of the older SMART firmware on IBM disks can 
-interfere with the regular operation of the disk.&#160; If you have this
-problem, here are some links:<br/>
-<a href="http://www.geocities.com/dtla_update/">Geocities Site</a>,
-<a href="http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-42215">IBM Site #1</a>,
-<a href="http://www-1.ibm.com/support/docview.wss?uid=psg1MIGR-42215">IBM Site #2</a><br/>
-to an IBM Firmware Upgrade that fixes the problem.
-</p></li>
-
-<li><b>How can I check that the package hasn't been tampered with?</b>
-
-<p>Since the <tt>smartmontools</tt> utilities run as root, you might
-be concerned about something harmful being embedded within
-them. Starting with release 5.19 of <tt>smartmontools</tt>, the .rpm
-files and tarball have been GPG signed. The tarball's fingerprint is
-given in a file on the release page with a name like
-<tt>smartmontools-5.32.tar.gz.asc</tt>.  Please verify these using
-the 
-<a href="SmartmontoolsSigningKey_2005.txt">Smartmontools GPG Signing Key (current)</a>
-<a href="SmartmontoolsSigningKey.txt">Smartmontools GPG Signing Key (before 2005)</a>
-</p></li>
-
-<li><b>Is there a bootable standalone CD or floppy that contains smartmontools?</b>
-
-<p>If you have a system that is showing signs of disk trouble (for
-example, it's unbootable and the console is full of disk error
-messages) it can be handy to have a version of smartmontools that can
-be run off of a bootable CD or floppy to examine the disk's SMART data and run
-self-tests.  This is also useful if you want to run Captive Self-Tests
-(the <b><tt>-<font size="+2">C</font></tt></b> option of
-<b><tt>smartctl</tt></b> ) on disks that can not easily be unmounted,
-such as those hosting the Operating System files. Or you can use
-this to run <tt>smartctl</tt> on computers that don't use Linux as the
-day-to-day operating system.</p>
-
-<p><a name="bootable"></a>Here is a list of such bootable CDs:</p>
-<ul>
-<li><a href="http://www.lnx-bbc.org/">LNX-BBC Bootable CD</a> </li>
-<li><a href="http://www.stresslinux.org/">Stresslinux Bootable CD</a></li>
-<li><a href="http://www.tux.org/pub/people/kent-robotti/looplinux/rip/">RIP (Recovery Is Possible) Bootable CD</a></li>
-<li><a href="http://www.sysresccd.org/Main_Page">SystemRescueCd</a></li>
-<li><a href="http://www.gpstudio.com/stux/">STUX Bootable CD</a></li>
-<li><a href="http://www.knopper.net/knoppix/index-en.html">Knoppix Bootable CD</a>
-(Version 3.6 contains smartmontools 5.32, older versions contain
-<a href="#differfromsmartsuite">smartsuite</a>)</li>
-<li><a href="http://www.grml.org/">Grml Bootable CD</a>
-(Knoppix and Debian based CD without KDE and OpenOffice but about 800
-<a href="http://www.grml.org/features/list.html">packages</a> added)</li>
-<li><a href="http://smartlinux.sourceforge.net/">S.M.A.R.T. Linux</a>
-(a bootable FLOPPY containing smartmontools!)</li>
-<li><a href="http://ubcd.sourceforge.net/">Ultimate Boot CD</a>
-(The "Full" version of UBCD 3.0 contains
-<a href="http://www.inside-security.de/insert_en.html">INSERT</a> with smartmontools 5.32
-<a href="http://ubcd.sourceforge.net/insert/start.html#TOCChanges">added</a>)</li>
-<li><a href="http://www.911cd.net/forums/lofiversion/index.php/t13459.html">Smartctl Plugin</a>
-for <a href="http://www.nu2.nu/pebuilder/">BartPE bootable live windows CD</a></li>
-</ul>
-<p>
-Please let me know if there are others, and I will add them to this
-list.
-</p>
-</li>
-
-<li><a name="FAQ-RAID"></a><b>Can I monitor disks behind RAID controllers?</b>
-
-<p>
-RAID controllers typically simulate a (logical) disk for each array of
-(physical) disks to the OS.
-Access to SMART functionality relies on ATA or SCSI pass through I/O controls
-providing direct access to each physical disk.
-But the standard I/O controls available are usually not designed to make this
-distinction between logical and physical disks.
-Therefore, smartmontools has to use vendor specific I/O controls.
-Support for disks behind RAID controllers is highly dependent on both platform
-and controller type.
-</p>
-<ul>
-<li><p>
-3ware RAID controllers are supported on Linux since smartmontools release 5.1-18.
-Support for char devices /dev/tw* was added in release 5.33. 
-</p></li>
-<li><p>
-3ware support on FreeBSD is available since release 5.33, multiple controller and
-char device support was added in release 5.36.
-</p></li>
-<li><p><font color="#ff0000">
-3ware 9000 support for Windows was added 2006-09-27, the corresponding 3ware
-driver 9.4.0 was released 2006-11-01.
-</font></p></li>
-<li><p><font color="#ff0000">
-HighPoint RocketRAID support for Linux was added 2006-08-25.
-</font></p></li>
-<li><p><font color="#ff0000">
-CCISS (Compaq Smart Array Controller) support for Linux was added 2006-10-09.
-</font></p></li>
-</ul>
-<p>
-The recent additions will appear in upcoming release 5.37.
-</p>
-<p>
-See<b>
-<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/INSTALL?view=markup">INSTALL</a>
-</b>file for information about kernel and driver requirements on your platform,
-and the <a href="#man">man pages</a> for controller specific smartmontools options or
-directives (<tt>-d 3ware,N</tt>, <tt>-d cciss,N</tt>, <tt>-d hpt,L/M/N</tt>).
-</p>
-
-</li>
-
-<li><a name="windows"></a><b>Does it work on Windows?</b>
-
-<p>Yes, finally it does. A windows port of smartctl 5.26 by
-<a href="http://sourceforge.net/users/chrfranke/">Christian Franke</a>
-was first checked in 2004/02/23 on CVS branch
-<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/?pathrev=RELEASE_5_26_WIN32_BRANCH">
-RELEASE_5_26_WIN32_BRANCH</a> and has been merged to the CVS trunk later.</p>
-
-<p>The <a href="http://www.cygwin.com/">Cygwin</a> environment can be
-used to built both Cygwin and Windows (using <a href="http://www.mingw.org/">MinGW</a>)
-versions of smartctl and smartd.
-Installation instructions for binary distributions can be found
-<a href="#CygwinInstall">here</a> and <a href="#WindowsInstall">here</a>.</p>
-
-</li>
-
-<li><b>Why did the release version scheme change?</b>
-
-<p>It was non-standard.  So with the move to GNU Autoconf and GNU
-Automake it changed from 5.X-Y (where X and Y are one or more digits)
-to 5.Y. Starting with the first release, and moving forward in time, the releases are
-numbered as follows:<br/>
-<tt>
-5.0-1,&nbsp;
-5.0-2,&nbsp;
-...,&nbsp;
-5.0-45,&nbsp;
-5.1-1,&nbsp;
-...,&nbsp;
-5.1-18,&nbsp;
-5.19,&nbsp;
-5.20,&nbsp;
-...
-</tt>
-</p>
-</li>
-
-<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>
-<p>
- If your drive is not in the database, then the
- <i>names</i> of the Attributes (displayed in the <tt>ATTRIBUTE_NAME</tt> column of
- <tt>smartctl -A /dev/hd?</tt>) and the <i>format</i> of the the raw Attribute
- values shown in the <tt>RAW_VALUE</tt> column may be incorrect.  This
- is mostly cosmetic: the essential drive health monitoring/testing
- functionality of <b>smartmontools</b> does <i>not</i> depend upon the
- database.
-</p>
-
-<p>
-<b>
- If your drive is not in the database, pleaes check <a
- href="http://sourceforge.net/project/showfiles.php?group_id=64297">here</a>
- to be sure that you are using the latest smartmontools release.  Each
- new release has additional drives added to the database.  Please do
- not submit a new drive for the database without checking to see if it
- is already in the database of the current smartmontools release
- version.
-</b>
-</p>
-
-<p>
-<b> If your drive is not in the database of the current release,</b>
- to have it added to the database, first use the command:<br/>
- <tt>smartctl -t short /dev/hd?</tt><br/> to run a short self-test on
- the drive, and wait a few minutes for the test to complete.  Then
- email the entire output from:<br/> <tt>smartctl -a /dev/hd?</tt><br/>
- to <a
- href="https://lists.sourceforge.net/lists/listinfo/smartmontools-database">smartmontools-database</a>
- as a plain-text ASCII email attachment (file type: ".txt").  The timestamp
- in the self-test log will help us to determine whether Attribute 9 is
- being used to store the lifetime in hours, minutes, or seconds.
-</p>
-<p>
-If you need to use any of the vendor-specific display options
- (<tt>-v</tt> options) with the drive, or if any of the Attributes are
- behaving strangely, please include that information as well.
-</p>
-</li>
-
-<li><b>My ATA drive is failing its self-tests, but its SMART health status is 'PASS'. What's going on?</b>
-
-<p>
-If your ATA drive supports self-tests, you should run them on a
-regular basis, for example one per week:
-<br/><tt>smartctl -t long /dev/hd?</tt><br/>
-After the test has completed, you should examine the results with:
-<br/><tt>smartctl -l selftest /dev/hd?</tt><br/>
-</p>
-
-<p>
-If the drive fails a self-test, but still has 'PASS' SMART health
-status, this usually means that there is a corrupted sector on the
-disk, which can not be read.  If the disk were able to read that
-sector of data, even once, then the disk firmware would mark the
-sector as 'bad' and then allocate a spare sectors to replace it.  But
-if the disk can't read the sector even once, then it won't reallocate
-the sector, in hopes of being able, at some time in the future, to
-read the data from it.  See <a
-href="http://smartmontools.sourceforge.net/BadBlockHowTo.txt">BadBlockHowTo</a>
-for instructions about how to force this sector to reallocate (Linux
-only).
-</p>
-<p>
-The disk still has passing health status because the firmware has not
-found other signs of trouble, such as a failing servo.
-</p>
-<p>
-Such disks can often be repaired by using the disk manufaturer's 'disk
-evaluation and repair' utility.  Beware: this may force reallocation
-of the lost sector and thus corrupt or destroy any file system on the
-disk. See <a
-href="http://smartmontools.sourceforge.net/BadBlockHowTo.txt">BadBlockHowTo</a>
-for generic Linux instructions.
-</p>
-
-</li>
-
-<li><b>smartd is warning that my ATA disk has unreadable or uncorrectable or pending sectors. What's going on?</b>
-
-<p>
-Disk drives store data in blocks (sectors) of 512 bytes.  Each 512
-bytes has additional bytes appended to it (usually 40 to 60) which are
-used internally by the disk firmware for error checking/detection and
-correction.  These are called ECC bytes.
-</p>
-<p>
-Sometimes the data in a sector gets corrupted.  This can happen
-because a speck of dust scratched the disk, or because the disk was
-powered down while writing data to that sector, or for other reasons.
-Usually the ECC bytes can be used to correct the corrupted data.
-However if the ECC bytes are inconsistent or can't be used to correct
-the bad data, then the 512 bytes of data are lost.  Such a sector is
-called unreadable or uncorrectable.
-</p>
-<p>
-If your disk has an unreadable sector, this means that some of your
-data can't be retrieved.  You can force the disk to replace the
-unreadable sector with a spare good sector, but only at the price of
-losing the 512 bytes of data forever.
-</p>
-<p>
-Disks with uncorrectable sectors can often be repaired by using the
-disk manufaturer's 'disk evaluation and repair' utility (see previous
-FAQ entry).  Beware: this may force reallocation of the lost sector
-and thus corrupt or destroy any file system on the disk. See <a
-href="http://smartmontools.sourceforge.net/BadBlockHowTo.txt">BadBlockHowTo</a>
-for generic Linux instructions.
-</p>
-<p>
-Normally when an uncorrectable sector is found, the disk puts this
-onto a 'pending sector list' to indicate that it should be replaced
-with a spare good sector.  However this replacement won't take place
-until either the disk can read the data on the bad sector, or is
-commanded to write new data to that bad sector.
-</p>
-
-</li>
-
-
-<li><b>My computer's BIOS has a SMART enable/disable setting.  What
-does it do, and how should I set it?</b>
-<p>
-Some type of BIOS can check the SMART health status of a disk at
-bootup: the equivalent of '<tt>smartctl -H /dev/hd?</tt>'.  This one-time check on
-bootup is done if the BIOS SMART setting is set to 'ENABLE', and is
-not done if the setting is set to 'DISABLE'.
-</p>
-
-<p>
-If this one-time check is done, and the disk's health status is found
-to be 'FAIL', then typically the BIOS will display an error message
-and refuse to boot the machine.
-</p>
-
-<p>
-For the proper functioning of smartmontools, either BIOS setting may
-be used.
-</p>
-</li>
-
-
-<li><b>My Fedora Core Linux system displays the startup message: smartd [FAILED]</b>
-<p>
-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.
-</p>
-<p>
-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.
-</p>
-</li>
-
-<li><b>Attribute 194 (Temperature Celsius) behaves strangely on my Seagate disk</b>
-<p>
-Some Seagate disks store the current temperature Celsius in both the
-RAW and NORMALIZED Attribute 194 values, and the maximum lifetime
-temperature in Celsius in the WORST value.  Since cooler is better,
-this means that in this case, <i>lower</i> NORMALIZED Attribute values
-are farther from failure, and that over time the WORST Attribute
-values get <i>larger</i>, not <i>smaller</i> (as with other
-Attributes).
-</p>
-</li>
-
-<li><b>What's this smartctl message mean?: Warning: ATA error count 9 inconsistent with error log pointer 5</b>
-<p>
-The ATA error log is stored in a circular buffer, and the ATA
-specifications are unambiguous about how the entries should be
-ordered.  This warning message means that the disk's firmware does not
-strictly obey the ATA specification regarding the ordering of the
-error log entries in the circular buffer.  Smartmontools will correct
-for this oversight, so this warning message can be safely ignored by
-users.  (On the other hand, firmware engineers: please read the ATA
-specs more closely then fix your code!).
-</p>
-</li>
-
-<li><a name="FAQ-win-ata-as-scsi"></a><b>On Windows, smartctl aborts
-with the message "...SMART_GET_VERSION failed". What is going wrong?</b>
-<p>
-A failing
-<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/Storage_r/hh/Storage_r/k307_2a8bcdd5-f85d-4228-b59c-bba2cc3211ee.xml.asp">
-SMART_GET_VERSION</a> call means that the device driver does not
-implement the I/O controls (see <a href="#FAQ-win-ioctl">below</a>)
-to access ATA SMART functionality.
-</p>
-<p>
-Some Windows drivers for (S)ATA controllers are implemented as SCSI
-class drivers. This is usually the case for drivers which support RAID.
-Unfortunately, such drivers do not support the ATA specific SMART I/O
-controls.
-</p>
-</li>
-
-<li><a name="FAQ-win-ioctl"></a><b>On Windows, smartctl prints the
-message: "...Log Read failed: Function not implemented". What is
-going wrong?</b>
-<p>
-This means that the device driver does not support the command
-SMART READ LOG.
-<u>The message does not indicate a hard disk problem!</u>
-It does also not mean that the disk itself does not support SMART
-logs. It may still be possible to read the logs with a Linux version
-of smartmontools run from some <a href="#bootable">bootable CD</a>.
-</p>
-<p>
-To access ATA SMART functionality on Windows, smartmontools uses the
-I/O control calls
-<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/Storage_r/hh/Storage_r/k307_8c974d08-3752-4442-82a5-cc13835ba482.xml.asp">
-SMART_RCV_DRIVE_DATA</a> and
-<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/Storage_r/hh/Storage_r/k307_2b043284-934c-4440-a4a4-6078f1bc845d.xml.asp">
-SMART_SEND_DRIVE_CMD</a>.
-These calls were available since Win95 OSR2.
-An example program from Microsoft can be found
-<a href="http://download.microsoft.com/download/winddk/sample3/9x/W9X/EN-US/SmartApp.exe">
-here</a> (the related KB article 208048 is no longer available).
-</p>
-<p>
-Starting with NT4, these calls do more restrictive parameter checks.
-In particular, the command codes for SMART READ LOG and ABORT SELF-TEST
-are not accepted. To perform these functions, smartmontools uses the
-undocumented functions SCSIOP_ATA_PASSTHROUGH (NT4) or
-IOCTL_IDE_PASS_THROUGH (2000/XP) instead.
-An example program using these calls can be found
-<a href="ftp://ftp.heise.de/pub/ct/listings/0207-218.zip">here</a>,
-a related newsgroup thread is
-<a href="http://groups.google.com/group/microsoft.public.development.device.drivers/browse_frm/thread/e9763262823e11d1">
-here</a>.
-</p>
-Unfortunately, these undocumented functions are not implemented in
-most vendor specific ATA device drivers. Smartctl prints a
-"Function not implemented" message in this case.
-<p>
-A new I/O control call
-<a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/Storage_r/hh/Storage_r/k307_e93738e1-b773-452b-8776-854f9c616967.xml.asp">
-IOCTL_ATA_PASS_THROUGH</a> is available since Win2003 and XP SP2.
-It should be supported by most new drivers. Experimental code using
-this call was added 2006-04-27 and will appear in smartmontools
-release 5.37.
-</p>
-</li>
-</ul>
-
-<hr size="2" /><a name="scsi"></a><b>SCSI disks and tapes
-(TapeAlert)</b>
-<p>Smartmontools for SCSI disks and tapes (including medium changers) is
-discussed on a separate <a href="smartmontools_scsi.html">page</a>.
-</p>
-
-<hr size="2" /><a name="testinghelp"></a><b>FireWire, USB, and SATA 
-disks/systems</b>
-<p>As for USB and FireWire (ieee1394) disks and tape drives, the news
-is not good. They appear to Linux as SCSI devices but their
-implementations do not usually support those SCSI commands needed by
-smartmontools. The ieee1394 consortium recently certified the <span
- style="font-style: italic;">first</span> external enclosure (containing
-a ATA disk and a protocol bridge) as being compliant to the relevant
-standards. Such devices have already been on the market for about 3 
-years and they tend to only support the bare minimum of commands
-needed for device operation (i.e. SMART support is an unsupported
-extra).<br />
-</p>
-<p>Smartmontools should work correctly with SATA drives under both
-Linux 2.4 and 2.6 kernels, <i>if</i> you use the standard IDE drivers
-in <tt>drivers/ide</tt>. If you use the new <tt>libata</tt> drivers,
-it won't work correctly because <tt>libata</tt> doesn't yet support
-the needed ATA-passthrough ioctl() calls.  Jeff Garzik, the
-<tt>libata</tt> developer, says that this support will be added to
-libata in the future.  When this happens, we'll add support to
-smartmontools for a new SATA/libata device type <tt>'-d sata'</tt>.
-Typically, to force an SATA disk to run using the standard
-(non-libata) drivers, you must use the BIOS to select "legacy mode"
-for the controller.  If the IDE driver doesn't support your particular
-SATA controller, or the controller doesn't have a legacy interface,
-then only libata can be used.  Unless the hard disk controller on the
-system motherboard is Intel, VIA or nVidia, standard IDE drivers may
-not work
-</p>
-<p>Note: an unofficial <a
-href="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">
-patch to libata</a> that allows smartmontools to be used
-with the standard '-d ata' device type was posted to the linux
-kernel mailing list at the end of August 2004. The patch is included in the
-<a href="http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/">libata-dev
-patchset</a> that can be applied to a recent Linux kernel (>= 2.6.9). With a
-SATA disk driven by a libata driver, smartmontools can now be used by specifying both the
-device type 'ata' and the SCSI device corresponding to this disk, for example,
-<tt>smartctl -i -d ata /dev/sda</tt>.
-The patch is still under development and it is probably best to make sure that
-the disk is idle before trying smartmontools.
-</p>
-
-
-<hr size="2" /><a name="differfromsmartsuite"></a><b>How does
-smartmontools differ from smartsuite?</b>
-
-<p>The smartsuite code was originally developed as a Senior Thesis by
-Michael Cornwell at the Concurrent Systems Laboratory (now part of the
-<a href="http://ssrc.soe.ucsc.edu/">Storage Systems Research
-Center</a>), Jack Baskin School of Engineering, University of
-California, Santa Cruz.
-You can find some information about the original smartsuite project here:
-<a href="http://www.ucsc.edu/news_events/press_releases/archive/99-00/09-99/smart_software.htm">Press Release 1</a>, 
-<a href="http://www.santa-cruz.com/archive/1999/September/22/local/stories/5local.htm">Press Release 2</a>, 
-<a href="http://www.ucsc.edu/currents/99-00/09-27/smart.html">Press Release 3</a>.
-</p>
-
-<p>
-According to <a href="http://csl.cse.ucsc.edu/">SSRC</a>
-smartsuite is no longer maintained; the last release was in 2001.
-</p>
-
-<p>Smartmontools was derived directly from smartsuite.&#160; It differs
-from smartsuite in that it supports the ATA/ATAPI-5 standard.&#160; So
-for example <tt>smartctl</tt> from smartsuite has no facility for
-printing the SMART self-test logs, and doesn't print timestamp
-information in the most usable way.&#160; The <tt>smartctl</tt> utility
-in smartmontools has added functionality for this (<tt>-q, -l selftest,-S,
--T, -v and -m</tt> options), updated documentation, and also fixes small
-technical bugs in smartsuite. [One example: smartsuite does not actually use the
-ATA SMART RETURN STATUS command to find out the health status of a disk.  It instead tries to infer this from the
-SMART Attribute values.]&#160; See the 
-<a href="http://smartmontools.cvs.sourceforge.net/smartmontools/sm5/CHANGELOG?view=markup">CHANGELOG</a>
-file in CVS for a summary of what's been done.&#160; The <tt>smartd</tt>
-utility differs from the smartsuite <tt>smartd</tt> in major ways.&#160;
-First, it prints somewhat more informative error messages to the syslog.
-&#160; 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.&#160; (If the configuration file does not
-exist, then it does query all IDE and SCSI devices.)&#160; Also, it's
-a well-behaved daemon and doesn't leave open file descriptors and other
-detrius behind.&#160; In addition, the <tt>smartmontools</tt> version of
-<tt>smartd</tt> can be instructed (via Directives in the configuration
-file) to monitor for changes in a number of different disk properties:
-the SMART status, failure or prefailure attributes going below
-threshold, new errors appearing in the ATA Error Log or the SMART
-Self-Test Log, and so on. <tt>smartd</tt> can also send an email warning or run a
-user-specified executable if it detects a problem with the disk.
-</p>
-
-<p>The other principle difference is that smartmontools is an
-OpenSource development project, meaning that we keep the files in CVS,
-and that other developers who wish to contribute can commit changes to
-the archive. If you would like to contribute, please write to to <a
-href="http://lists.sourceforge.net/mailman/listinfo/smartmontools-support">smartmontools-support</a>.</p>
-
-<p>But the bottom line is that the code in smartmontools is derived
-directly from smartsuite and is similar.&#160; The smartsuite package
-can be found <a href="http://sourceforge.net/projects/smartsuite/">here</a>.</p>
-
-<hr size="2" /><a name="references"></a><b><big>Useful references on
-SMART and the  ATA/ATAPI standards</big></b>
-
-<p><big>If you are having trouble understanding the output of smartctl
-or smartd, please first read the manual pages installed on your
-system:</big></p>
-
-<pre>
-man 8 smartctl
-man 8 smartd
-man 5 smartd.conf
-</pre>
-
-<p>
-Here are on-line versions of the smartmontools man pages:<br/> <a
-href="man/smartctl.8.html">smartctl manual page</a><br/> <a
-href="man/smartd.8.html">smartd manual page</a><br/> <a
-href="man/smartd.conf.5.html">smartd.conf manual page</a><br/> Note
-that these are the manual pages for the <b><i>current version</i></b>
-of smartmontools in the developers CVS repository; they might not
-correspond to the (possibly older) version of smartmontools installed
-on <i>your</i> system.  So the manual pages installed on your system
-should be regarded as definitive for your installation.</p>
-
-<p><big>If you'd like to know more about SMART, then the following
-references may be helpful:</big></p>
-
-<ul>
-<li><a href="http://www.linuxjournal.com/article.php?sid=6983">Monitoring Hard Disks with SMART (Linux Journal, Jan 2004)</a></li>
-<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>
-<li><a href="http://www.linux-user.de/ausgabe/2004/10/056-smartmontools/">Vorbeugen statt Crash (Deutsch)</a>
-from <a href="http://www.linux-user.de/ausgabe/2004/10">LinuxUser 2004/10</a></li>
-<li><a href="http://www.linux-magazine.com/issue/49/Monitoring_Hard_Disks_with_smartmontools.pdf">Crash Prevention
-(English version of above)</a> from <a href="http://www.linux-magazine.com/issue/49">Linux Magazine Dec 2004</a></li>
-<li><a href="http://www.wikipedia.org/">Wikipedia</a> articles about SMART:
-<a href="http://en.wikipedia.org/wiki/Self-Monitoring%2C_Analysis_and_Reporting_Technology">English</a>,
-<a href="http://de.wikipedia.org/wiki/Self-Monitoring%2C_Analysis_and_Reporting_Technology">Deutsch</a>,
-<a href="http://es.wikipedia.org/wiki/SMART">Espa&#241;ol</a>,
-<a href="http://fr.wikipedia.org/wiki/Self-Monitoring%2C_Analysis_and_Reporting_Technology">Fran&#231;ais</a>,
-<a href="http://it.wikipedia.org/wiki/Self-Monitoring%2C_Analysis_and_Reporting_Technology">Italiano</a>,
-<a href="http://ja.wikipedia.org/wiki/Self-Monitoring%2C_Analysis_and_Reporting_Technology">Japanese</a>,
-<a href="http://nl.wikipedia.org/wiki/S.M.A.R.T.">Nederlands</a>,
-<a href="http://pl.wikipedia.org/wiki/S.M.A.R.T._%28informatyka%29">Polski</a>,
-<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>,
-<a href="http://sk.wikipedia.org/wiki/S.M.A.R.T">Sloven&#269;ina</a>
-</li>
- <li>The <a href="http://www.t13.org/project/d1321r3-ATA-ATAPI-5.pdf"> ATAPI/ATA-5
-Revision 3 specification</a> (start with Section 8.41)</li>
- <li>The <a href="http://www.t13.org/docs2002/d1410r3b.pdf"> ATAPI/ATA-6
-Revision 3b specification</a></li>
- <li>The  ATAPI/ATA-7 specification (Draft 4b) 
-  <a href="http://www.t13.org/docs2004/d1532v1r4b-ATA-ATAPI-7.pdf">Volume 1 (has SMART documentation)</a>,
-  <a href="http://www.t13.org/docs2004/d1532v2r4b-ATA-ATAPI-7.pdf">Volume 2</a>,
-  <a href="http://www.t13.org/docs2004/d1532v3r4b-ATA-ATAPI-7.pdf">Volume 3</a></li>
- <li>The <a href="http://www.t13.org/docs2005/D1699r1f-ATA8-ACS.pdf">ATAPI/ATA-8 Command Set
-specification (Draft 1f)</a></li>
- <li><a href="http://www.t13.org/#FTP_site">Other revisions
-of the ATAPI/ATA Specs</a></li>
-<li>SCSI References:
-<ul>
- <li>The <a href="http://www.t10.org">homepage of the T10 project</a>.</li>
- <li>The <a href="ftp://ftp.t10.org/t10/drafts/s2/">SCSI-2 draft</a> by the T10 project.</li>
- <li>See also other subdirectories <a href="ftp://ftp.t10.org/t10/drafts/">here</a>.</li>
-</ul>
-</li>
-<li>
-  The original SMART specification is SFF-8035i from the <a href="http://www.sffcommittee.com/ns/">
-  Small Form Factors (SFF) Committee</a>.&#160; 
-  <ul>
-    <li>
-      Here is the SFF <a href="ftp://ftp.seagate.com/sff/INF-8035.TXT"> "link"</a>
-     (they have "expired" the document).
-    </li>
-    <li>
-      Version 1.0 of <a href="ftp://ftp3.ds.pg.gda.pl/people/macro/S.M.A.R.T./SFF-8035i.pdf">
-      SFF-8035i "Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.)". </a>
-    </li>
-    <li>
-      Revision 2.0 of <a href="ftp://ftp3.ds.pg.gda.pl/people/macro/S.M.A.R.T./8035R2_0.PDF">
-      SFF-8035i "Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.)". </a>
-    </li>
-    <li>
-      Revision 1.4 of <a href="ftp://ftp3.ds.pg.gda.pl/people/macro/S.M.A.R.T./8055.PDF">
-      SFF-8055i "S.M.A.R.T. Applications Guide for the ATA and SCSI Interfaces" </a>
-    </li>
-  </ul>
-</li>
-<li>From the <a href="http://cmrr.ucsd.edu/smart/">UCSD SMART Project</a>:
-<ul> 
- <li><a href="http://cmrr.ucsd.edu/smart/tech_papr/HamerlySmartPaper.pdf">Bayesian
-Approaches to Failure Prediction for Disk Drives</a></li>
-  <li><a href="http://cmrr.ucsd.edu/smart/tech_papr/SmtPapTransReliFinalWeb.pdf">Improved
-Disk-Drive Failure Warnings</a></li>
- </ul>
- </li>
- <li>From the Seagate Corporation:
- <ul>
-<!--  <li><a href="http://www.seagate.com/newsinfo/docs/disc/drive_reliability.pdf" target="_blank">
-Estimating Drive Reliability in Desktop Computers and Consumer Electronics Systems</a></li> -->
-  <li><a href="http://www.seagate.com/docs/pdf/whitepaper/enhanced_smart.pdf" target="_blank">Enhanced SMART - Get SMART For Reliability</a></li>
-  <li><a href="http://www.seagate.com/docs/pdf/whitepaper/smart_u8.pdf" target="_blank">Playing it SMART</a></li>
-  <li><a href="http://www.seagate.com/docs/pdf/whitepaper/Enhanced_DST_Tech_Paper.pdf" target="_blank">Enhanced Drive Self-Test</a></li>
- </ul>
- </li>
- <li><u>Specifying Reliability in the Disk Drive Industry: No More
-MTBF's</u>, Jon G. Elerath (IBM Storage Systems Division) in
-<i>Proceedings of the IEEE 2000 Annual Reliability and Maintainability
-Symposium, pg 194, 0-7803-5848-1/00/$10.00.</i></li>
- <li><a href="http://smartlinux.sourceforge.net/smart/">Zbigniew Chlondowski's SMART Information Site.</a>
-This includes a useful list of <a href="http://smartlinux.sourceforge.net/smart/attributes.php">Attributes
-and their meanings.</a>
-</li>
-</ul>
-
-<hr size="2" /><a name="sampleoutput"></a><b>Example output
-from smartmontools smartctl utility:</b>
-
-<ul>
- <li><a href="examples/MAXTOR-0.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM</li>
- <li><a href="examples/MAXTOR-1.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM (has failing SMART status - reallocated sector count)</li>
- <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>
- <li><a href="examples/MAXTOR-7.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM (has failing SMART status, some failed self-tests)</li>
- <li><a href="examples/MAXTOR-8.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM (has failing SMART status - calibration retry count)</li>
- <li><a href="examples/MAXTOR-9.txt">MAXTOR 4K080H4</a> 80 GB 5400 RPM (has failing SMART status - calibration retry count)</li>
- <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>
- <li><a href="examples/MAXTOR-3.txt">MAXTOR 6L080J4</a> 80 GB 7200 RPM</li>
- <li><a href="examples/MAXTOR-4.txt">MAXTOR 6L080J4</a> 80 GB 7200 RPM</li>
- <li><a href="examples/Maxtor-5.txt">Maxtor 98196H8</a> 80 GB 5400 RPM</li>
- <li><a href="examples/MAXTOR-6.txt">Maxtor 4R080J0</a> Note: Attribute 9 (lifetime) stored in minutes!</li>
- <li><a href="examples/IC35L120AVVA07-0-0.txt">IBM IC35L120AVVA07 (GXP 120 series)</a> 120 GB 7200 RPM (note 3 temperatures)</li>
- <li><a href="examples/IC35L120AVVA07-0-1.txt">IBM IC35L120AVVA07 (GXP 120 series)</a> 120 GB 7200 RPM (note 3 temperatures)</li>
- <li><a href="examples/IC35L120AVV207-0.txt">IBM IC35L120AVV207 (GXP 180 series)</a> 120 GB 7200 RPM (note 3 temperatures)</li>
- <li><a href="examples/IC35L120AVV207-1.txt">IBM IC35L120AVV207 (GXP 180 series)</a> (failing SMART status and self-tests)</li>
- <li><a href="examples/HITACHI_DK23BA-20-0.txt">HITACHI_DK23BA-20</a> Hitachi 20 GB Laptop Disk</li>
- <li><a href="examples/HITACHI_DK23AA-12B.txt">HITACHI_DK23AA-12B</a> Really sick failing Hitachi Laptop Disk</li>
- <li><a href="examples/TOSHIBA-0.txt">TOSHIBA MK2018GAS</a> Toshiba 20 GB Laptop Disk</li>
- <li><a href="examples/TOSHIBA-MK6021GAS.txt">TOSHIBA MK6021GAS</a> Toshiba 60 GB Laptop Disk (note 3 temperatures)</li>
- <li><a href="examples/FUJITSU1.txt">Fujitsu MHR2040AT</a> Fujitsu Laptop Disk (has failing SMART status - write error count)</li>
- <li><a href="examples/FUJITSU_MHR2020AT.txt">Fujitsu MHR2020AT</a> Fujitsu Laptop Disk (has failing SMART status and self-tests)</li>
- <li><a href="examples/WD2500JB.txt">Western Digital WD2500JB</a> Western Digital Disk (failing SMART status and self-tests)</li>
- <li><a href="examples/WD800JD.txt">Western Digital WD800JD</a> Western Digital Disk (failing SMART status - too may reallocated sectors, and self-tests)</li>
-</ul>
-
-<hr size="2" />
-
-Maintained by: <a href="mailto:smartmontools-support&#64;lists.sourceforge.net">Bruce Allen</a><br />
-Copyright (C) 2002-5 Bruce Allen<br />
-Last updated: <tt>$Date: 2006/11/04 20:04:26 $</tt><br />
-CVS tag: <tt>$Id: index.html,v 1.208 2006/11/04 20:04:26 chrfranke Exp $</tt>
-
-<hr size="2" />
-
-<div align="center">Hosted by</div>
-
-<div align="center"><a href="http://sourceforge.net/"><img style="border:0;width=:88px;height:31px"
-   src="http://sourceforge.net/sflogo.php?group_id=64297&amp;type=5" alt="SourceForge.net" /></a></div>
-
-<br />
-
-<div align="center"><a href="http://validator.w3.org/check/referer"><img style="border:0;width=:88px;height:31px"
-   src="http://www.w3.org/Icons/valid-xhtml10.png" alt="Valid XHTML 1.0!" /></a></div>
-
-<br />
-
-<div align="center"><a href="http://validator.w3.org/check?uri=http%3A%2F%2Fsmartmontools.sourceforge.net">
-Validate XHTML 1.0 Transitional.</a></div>
-
-<br />
-
-<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>
-
-</body>
-</html>
diff --git a/www/script b/www/script
deleted file mode 100755
index fa7cd8c224367b6aba467f81fc960da4efc80375..0000000000000000000000000000000000000000
--- a/www/script
+++ /dev/null
@@ -1,24 +0,0 @@
-#! /bin/bash
-
-# This is a script to wrap smartctl output into http:// displayable form
-# It requires a filename as input, and produces an file with a .html extension as output
-
-if [ $# -ne 1 ] ; then
-	echo This script requires one a file as input
-	exit 1
-fi
-
-model=`grep "Device Model"  $1  | awk '{print $3}' `
-
-# see if file name in use
-let i=0
-while [ -f $model-$i.html ] ; do
-	let i+=1
-done
-
-filename=$model-$i
-echo -e "<pre><tt>\n"    > $filename.html
-cat $1                  >> $filename.html
-echo -e "</tt></pre>\n" >> $filename.html
-
-echo created file $filename.html
diff --git a/www/smart_logo.gif b/www/smart_logo.gif
deleted file mode 100644
index 16a179c824bb4205d117f371eec0500eaf4d4c50..0000000000000000000000000000000000000000
Binary files a/www/smart_logo.gif and /dev/null differ
diff --git a/www/smartmontools_scsi.xml b/www/smartmontools_scsi.xml
deleted file mode 100644
index 0ab71ce6f363e69c2b66f415990ee8d2d76c43da..0000000000000000000000000000000000000000
--- a/www/smartmontools_scsi.xml
+++ /dev/null
@@ -1,1511 +0,0 @@
-<?xml version='1.0' encoding='ISO-8859-1'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
-	"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" >
-
-<!--
-This is DocBook XML that can be rendered into a single HTML page with a
-command like 'xmlto html-nochunks <this_file_name>'. It can
-also be rendered into multi-page HTML (drop the "-nochunks") or pdf,
-ps, txt, etc.
--->
-
-<article id="index">
- <articleinfo>
-   <title>Smartmontools for SCSI devices</title>
-   <author>
-    <firstname>Douglas</firstname>
-    <surname>Gilbert</surname>
-    <affiliation>
-     <address>
-      <email>dgilbert at interlog dot com</email>
-     </address>
-    </affiliation>
-   </author>
-  <authorinitials>dpg</authorinitials>
-  <pubdate>2006-11-21</pubdate>
-
-  <revhistory>
-     <revision>
-       <revnumber>1.6</revnumber>
-       <date>2006-11-21</date>
-       <authorinitials>dpg</authorinitials>
-       <revremark>
-             auto '-d sat', background scan, windows device names
-       </revremark>
-     </revision>
-     <revision>
-       <revnumber>1.5</revnumber>
-       <date>2006-06-24</date>
-       <authorinitials>dpg</authorinitials>
-       <revremark>
-             device type 'sat'
-       </revremark>
-     </revision>
-     <revision>
-       <revnumber>1.4</revnumber>
-       <date>2006-05-08</date>
-       <authorinitials>dpg</authorinitials>
-       <revremark>
-             5.38 update, SATA, SAS
-       </revremark>
-     </revision>
-     <revision>
-       <revnumber>1.3</revnumber>
-       <date>2004-09-25</date>
-       <authorinitials>dpg</authorinitials>
-       <revremark>
-             error counter descriptions, error events log page
-       </revremark>
-     </revision>
-     <revision>
-       <revnumber>1.2</revnumber>
-       <date>2004-05-27</date>
-       <authorinitials>dpg</authorinitials>
-       <revremark>
-             reorganise, details in appendix, version 5.31
-       </revremark>
-     </revision>
-     <revision>
-       <revnumber>1.1</revnumber>
-       <date>2003-10-13</date>
-       <authorinitials>dpg</authorinitials>
-       <revremark>
-             freebsd, timestamp
-       </revremark>
-     </revision>
-     <revision>
-       <revnumber>1.0</revnumber>
-       <date>2003-05-26</date>
-       <authorinitials>dpg</authorinitials>
-       <revremark>
-             first cut
-       </revremark>
-     </revision>
-  </revhistory>
-
-  <copyright>
-   <year>2003</year>
-   <year>2004</year>
-   <year>2005</year>
-   <year>2006</year>
-   <holder>Douglas Gilbert</holder>
-  </copyright>
-
-  <legalnotice>
-   <para>
-      Permission is granted to copy, distribute and/or modify this document
-      under the terms of the GNU Free Documentation License, Version 1.1
-      or any later version published by the Free Software Foundation;
-      with no Invariant Sections, with no Front-Cover Texts, and with
-      no Back-Cover Texts.
-   </para>
-   <para>
-    For an online copy of the license see
-    <ulink url="http://www.fsf.org/copyleft/fdl.html">
-    <literal>www.fsf.org/copyleft/fdl.html</literal></ulink>.
-   </para>
-
-  </legalnotice>
-
-  <abstract>
-  <para>
-    This article describes how smartmontools interacts with SCSI storage
-    devices (mainly hard disks and tape drives). Smartmontools is a SMART
-    utility toolset. <acronym>SMART</acronym> is an acronym for
-    Self-Monitoring, Analysis and Reporting Technology. Smartmontools
-    is available for the these operating systems: Darwin (Mac OS X
-    but with no SCSI support yet), FreeBSD, Linux, NetBSD, OpenBSD,
-    OS/2 (no SCSI support), Solaris and Windows.
-  </para>
-  </abstract>
- </articleinfo>
-
-<!--
-<toc></toc>
--->
-
-  <sect1 id="intro">
-      <title>Introduction</title>
-<para>
-Smartmontools controls and monitors storage devices using the
-Self-Monitoring, Analysis and Reporting Technology 
-(<acronym>SMART</acronym>) system. This toolset was originally built
-for the Linux operating system and has been ported to Darwin for
-Mac OS X (no SCSI support yet), FreeBSD, NetBSD, OpenBSD, 
-OS/2 (no SCSI support), Solaris and Windows. 
-This article describes how smartmontools interacts with SCSI devices.
-Passing reference is also made to devices that use the SCSI command
-set such as USB mass storage devices and IEEE1394 devices that use
-the "sbp2" protocol. In many situations SATA disks are accessed
-using a (partial) SCSI command set.
-</para>
-<para>
-The primary web site for smartmontools is at
-<ulink url="http://smartmontools.sourceforge.net">
-<literal>smartmontools.sourceforge.net</literal></ulink> from which the
-latest versions (both source and binaries) can be obtained. Smartmontools
-grew out of the now dormant <emphasis>smartsuite</emphasis> project which
-is still available on its own sourceforge site. The smartmontools main page
-concentrates on ATA devices.
-This article supplies some SCSI specific information for
-those users of smartmontools that wish to monitor SCSI storage devices.
-</para>
-<para>
-This document outlines the features found in smartmontools
-version 5.37 that are relevant to SCSI disks and tape drives.
-This document was last altered on 21st November 2006.
-</para>
-</sect1>
-
-<sect1 id="overv">
-      <title>Overview of Smartmontools</title>
-<para>
-Smartmontools is made up of two executable programs, a configuration file
-and online documentation (on Unix systems in the form of "man" pages).
-The two executable programs are:
-<itemizedlist>
-<listitem><para><command>smartctl</command>: a command line utility
-</para></listitem>
-<listitem><para><command>smartd</command>: a daemon program providing a
-monitoring service
-</para></listitem>
-</itemizedlist>
-</para>
-<para>
-SCSI disks and tape drives allow self tests of their media, often monitor
-the temperature of the device, maintain error counters and report when
-various failure prediction thresholds are exceeded. To view the information
-available try a command like: <command>smartctl -a /dev/sda</command>. If
-<acronym>SMART</acronym> reporting has not been turned on for this disk 
-then use this command
-first: <command>smartctl -s on /dev/sda</command>. [For operating systems
-other than Linux replace <filename>/dev/sda</filename> with a SCSI disk 
-device name.]
-</para>
-<para>
-The <command>smartd</command> daemon program is a service typically started
-when a machine boots up. In can monitor multiple disks (both ATA and SCSI).
-In Unix systems its configuration file can
-be found <filename>/etc/smartd.conf</filename>. It sends alerts to the
-system logs and can be configured to email system administrators when
-pending failures are reported.
-</para>
-<para>
-If smartmontools detects some "bad blocks" then the reader should
-look at this page:
-<ulink url="http://smartmontools.sourceforge.net/badblockhowto.html">
-<literal>smartmontools.sourceforge.net/badblockhowto.html</literal></ulink> .
-</para>
-</sect1>
-
-<sect1 id="oses">
-      <title>Operating Systems</title>
-<para>
-Smartmontools was originally written for Linux. Since then it has been
-ported to various other Unix based systems and Windows. Note that the
-device names are based on the transport that an operating system sees.
-These days it is not uncommon for an operating system to see a
-transport that only conveys SCSI commands connected, via some command
-translation bridge, to an ATA disk. Examples are USB external disk
-enclosures and SATA disks behind a SCSI to ATA Translation Layer (SATL)
-in a SAS or FC domain.
-</para>
-<para>
-The names of SCSI disk and tape devices vary with the operating system.
-Here is a summary:
-
-<table frame="all"><title>SCSI device names in various systems</title>
-<tgroup cols="4" align="left" colsep="1" rowsep="1">
-<thead>
-<row>
-<entry/>
-<entry>disks</entry>
-<entry>tapes</entry>
-<entry>Notes</entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry><command>Linux</command></entry>
-<entry><filename>/dev/sd[a-z]</filename></entry>
-<entry><filename>/dev/[n]st[0-9]</filename></entry>
-</row>
-<row>
-<entry><command>FreeBSD</command></entry>
-<entry><filename>/dev/da[0-9]</filename></entry>
-<entry><filename>/dev/[n|e]sa[0-9]</filename></entry>
-</row>
-<row>
-<entry><command>NetBSD</command></entry>
-<entry><filename>/dev/sd[0-9]+c</filename></entry>
-<entry><filename>/dev/st[0-9]+c</filename></entry>
-</row>
-<row>
-<entry><command>OpenBSD</command></entry>
-<entry><filename>/dev/sd[0-9]+c</filename></entry>
-<entry><filename>/dev/st[0-9]+c</filename></entry>
-</row>
-<row>
-<entry><command>Solaris</command></entry>
-<entry><filename>/dev/rdsk/c?t?d?s?</filename></entry>
-<entry><filename>/dev/rmt/*</filename></entry>
-</row>
-<row>
-<entry><command>Windows</command></entry>
-<entry><filename>/dev/scsi[0-9][0-f]</filename></entry>
-<entry><filename>/dev/scsi[0-9][0-f]</filename></entry>
-<entry>ASPI adapter:0-9, ID:0-15</entry>
-</row>
-<row>
-<entry/>
-<entry><filename>/dev/sd[a-z]</filename></entry>
-<entry/>
-<entry>for '\\.\PhysicalDrive[0-25]'</entry>
-</row>
-<row>
-<entry/>
-<entry><filename>/dev/pd[0-255]</filename></entry>
-<entry/>
-<entry>for '\\.\PhysicalDrive[0-255]'</entry>
-</row>
-<row>
-<entry/>
-<entry/>
-<entry><filename>/dev/tape[0-255]</filename></entry>
-<entry>for '\\.\Tape[0-255]'</entry>
-</row>
-<row>
-<entry><command>Darwin</command></entry>
-<entry/>
-<entry/>
-<entry>no support for SCSI devices</entry>
-</row>
-<row>
-<entry><command>OS/2</command></entry>
-<entry/>
-<entry/>
-<entry>no support for SCSI devices</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-</para>
-<para>
-The above list is a simplification. In Linux there can be multiple
-drive letters followed by a partition number (1 to 15). Smartmontools will
-ignore the partition number if it is given and query the underlying device.
-In Linux the SCSI tape device name can be "nst" and a letter can be
-appended to the device name, both decorations are ignored by smartmontools
-as it accesses the underlying tape drive. Also in Linux, SCSI devices can
-be accessed via their generic name which is of the form
-<filename>/dev/sg[0-9]</filename>.
-</para>
-<para>
-Linux also has an optional Solaris like
-naming scheme for SCSI device (scsidev), devfs (mainly used in the lk 2.4
-series) and udev (devfs's replacement in the lk 2.6 series). In short, device
-naming is a complex area and smartmontools does its best to find
-and identify (i.e. whether ATA or SCSI) a device depending on its name. In
-some cases smartmontools needs guidance from the user and this can be given
-by the '-d ata|scsi|sat|marvell|3ware,N' option in the
-<command>smartctl</command> utility and in <command>smartd</command>
-daemon's configuration file.
-</para>
-<para>
-Windows has several schemes for naming devices. The "scsi[0-9][0-f]" scheme
-uses the aspi dll from Adaptec. That dll is not distributed with Windows. The
-other schemes use the "SCSI Pass Through" interface which is native to
-Windows in NT and later. In all cases for Windows, the leading
-<filename>/dev/</filename> is optional.
-</para>
-</sect1>
-
-<sect1 id="scsidisk">
-      <title>SCSI disks</title>
-<para>
-What is a SCSI disk? A SCSI disk is a storage device that "talks" the SCSI
-command set. An ATA disk is a storage device that "talks" the ATA 
-command set. That seems pretty clear. However the command set that a
-disk uses at its connector (and thus shown on its label) may not be
-the command set that the operating system needs to use due to command
-set translation between the OS and the disk.
-</para>
-<para>
-The ATA command set is used over native ATA transports which are
-parallel ATA (PATA) up to 133 MB/sec and serial ATA (SATA) at link
-speeds of 1.5 Gbps (approximately 150 MB/sec) or 3 Gbps. In the past
-when ATA disks needed to use some other transport (e.g. USB and IEEE1394)
-the SCSI command set was sent over the foreign transport. So in this
-case the operating system sees a device "talking" the SCSI command set
-but the device is really an ATA disk. Many current disk external enclosures
-contains ATA disks yet seen from the operating systems view point are
-USB mass storage devices talking the SCSI command set.  
-</para>
-<para>
-The SCSI command set is used over various transports: the SCSI Parallel
-Interface (SPI), Fibre Channel (FCP), Serial Attached SCSI (SAS),
-IEEE1394 (SBP), USB (mass storage) and iSCSI. Many of these transports can
-convey multiple command sets (i.e. not just the SCSI command set). The
-SAS transport is interesting as it can convey both the SCSI
-and ATA command sets. There is also the case of a RAID made up of ATA
-disks which communicates to host operating system with the SCSI command
-set (e.g. 3ware RAID controller).
-</para>
-<para>
-So what does all this mean for smartmontools? In most cases the answer is
-not good news. Devices such as USB external disk enclosures translate 
-incoming (from the host) SCSI commands to their ATA equivalents and process
-responses as required. This translation is limited typically to a small
-number of SCSI commands (e.g. READ and WRITE) but <emphasis>not</emphasis>
-those commands needed by smartmontools. The author does not know of any 
-SCSI_over_USB devices that support Smartmontools. The 3ware RAID (6000,
-7000, 8000 and 9000 series Escalade) controllers are supported
-on several operating systems with special code.
-<footnote><para>
-The 3ware RAID solution tunnels the ATA commands needed for
-smartmontools (together with a disk number) through a vendor specific 
-SCSI command.
-</para></footnote>
-</para>
-<para>
-There is an emerging SCSI to ATA Translation (SAT) standard
-at <link linkend="t10">www.t10.org</link>
-that may lead to improvements in this area. Apart from defining
-some of the facilities smartmontools needs, it defines two ATA PASS THROUGH
-SCSI commands. These pass through commands could be used in much the
-same way that the 3ware RAID tunnels ATA commands.
-</para>
-<para>
-The device type '-d sat' instructs the <command>smartctl</command>
-command and the <command>smartd</command> daemon, to form SMART
-commands for the ATA command set and then package those commands
-within the ATA PASS THROUGH SCSI commands. The SCSI commands
-are then sent to the "SCSI" device that the operating system
-has been given. In version 5.37 of smartmontools it is no longer
-necessary to specify '-d sat' in this situation. All that is
-needed is a SATL that complies with the emerging SAT standard.
-If the automatic detection of an ATA disk behind a SATL is
-tricked, '-d scsi' (or some other device type) can be used to
-override.
-</para>
-<para>
-It has been reported that many external USB enclosures use a "Cypress"
-chipset. This contains an ATACB proprietary pass through (for ATA
-commands passed through SCSI commands) for which some publicly
-available information is available. Smartmontools has no ATACB specific
-code but may move in this direction in the future. Another approach is
-to hope USB and SBP2 external enclosures adopt the SAT standard in the
-near future. One interesting comment about ATACB is that it should not
-be used at the same time as other types of access to the disk (e.g. a
-mounted file system)! That implies that a disk should be taken
-offline before smartmontools is used on it. It also implies that
-the smartd background daemon should not be used.
-</para>
-</sect1>
-
-<sect1 id="satadisk">
-      <title>SATA disks</title>
-<para>
-SATA disks use a 1.5 or 3 Gbps serial transport which carries the
-ATA command set. The serial connection is point to point so each SATA disk
-needs its own cable and plug on the host adapter or motherboard.
-<footnote><para>
-There are SATA devices called port multipliers that allow up to 15
-SATA drives to be connected to one host. SAS expanders seem to be a
-better approach to the problem of connecting a large number of disks
-to one or more hosts.
-</para></footnote>
-Many aspects of SATA are like SCSI and some operating
-systems use existing SCSI infrastructure to handle SATA hosts (e.g.
-Linux's libata). 
-</para>
-<para>
-Serial Attached SCSI (SAS) can be viewed as a superset of SATA.
-It can directly connect thousands of SAS disks to one or more controllers
-spread across multiple machines in one SAS "domain". Such a domain can
-also contain SATA disks, connected to intermediate fanout devices called
-expanders (similar to switches in networking). Most SAS host adapters
-can also have SATA disks connected directly to the adapter (which
-technically is not a usage of SAS but that is of little concern to
-the end user).
-</para>
-<para>
-So a SATA disk may be connected
-<itemizedlist>
-<listitem><para>
-to a SATA host controller (on a motherboard or an adapter)
-</para></listitem>
-<listitem><para>
-directly to a SAS host adapter
-</para></listitem>
-<listitem><para>
-to a SAS expander which is connected to one or more SAS host adapters
-</para></listitem>
-<listitem><para>
-or connected via a bridge which is connected to the host computer via
-some other transport (e.g. fibre channel)
-</para></listitem>
-</itemizedlist>
-Since all but the first item might have other disks connected which
-use the SCSI command set (e.g. SAS and FC disks) often the SATA disks
-have a SAT layer put in front of them so they look like SCSI disks.
-That SAT layer may be in:
-<itemizedlist>
-<listitem><para>
-the operating system kernel (e.g. libata in Linux)
-</para></listitem>
-<listitem><para>
-in the host adapter firmware (or RAID controller)
-</para></listitem>
-<listitem><para>
-or external to the host computer: within a disk enclosure (e.g.
-associated with a SAS expander)
-</para></listitem>
-</itemizedlist>
-</para>
-<para>
-For normal file system work, a SCSI to ATA Translation Layer (SATL) only
-needs to concern itself with around 6 commands. Unfortunately
-smartmontools uses other commands (both in the SCSI and ATA
-command sets). Probably the simplest way to handle SMART for SATA disks
-behind a SAT layer is to use the ATA PASS THROUGH SCSI commands.
-</para>
-<para>
-smartmontools guesses the disk command set (i.e. ATA or SCSI)
-based on the device node it is given. For example in Linux,
-<filename>/dev/hda</filename> would be assumed to use the ATA command set
-while <filename>/dev/sda</filename> would be assumed to use the SCSI
-command set. 
-<footnote><para>
-Even sending trial ATA and SCSI commands to see which one a device
-responds to could be tricked. ATAPI cd/dvd drives respond to
-both ATA commands (a few, for example IDENTIFY PACKET DEVICE) and SCSI
-commands (found in MMC).
-</para></footnote>
-By using either the '-d ata' or the '-d scsi' option, the command set
-guess made by smartmontools can be overridden. The '-d sat' device
-type causes smartmontools to generate ATA commands which are then packaged
-within the ATA PASS THROUGH SCSI commands (defined by the SAT standard)
-and then sent to the device via a SCSI pass through mechanism.
-As noted in the previous section, version 5.37 of smartmontools now
-automatically detects a SATA disk behind a SAT layer and acts as
-if '-d sat' has been given.
-</para>
-</sect1>
-
-<sect1 id="smart">
-      <title>SMART</title>
-<para>
-<acronym>SMART</acronym> never attained the status of "standard" and its
-original documents have been withdrawn. Its catchy name lives on, especially
-on vendors' web sites and obviously in the name of this toolset. Luckily
-the good ideas in <acronym>SMART</acronym> have been incorporated into the
-ATA and SCSI standards albeit in slightly different forms.
-</para>
-<para>
-Initially <acronym>SMART</acronym> began on SCSI disks as vendor
-specific extensions. Gradually the <acronym>SMART</acronym> functionality has
-moved into the standards (often by other names) and vendors are improving
-their standards' compliance. [In the vendors' defence some of the
-"standards" are drafts and are yet to be ratified.] Some SCSI disk vendors
-have product manuals (available on the net) that cover the parts of the SCSI
-command set that their disks support. Some of these manuals fill in details
-that are left deliberately vague in the the standards.
-<footnote><para>
-For example: Seagate's "Cheetah 15K.3 Product Manual, Rev F" contains 
-sections on <acronym>SMART</acronym>,
-thermal monitor, and drive self test (section 5.2.7 to 5.2.9). It also
-lists the supported mode pages with their default and changeable values.
-</para></footnote>
-</para>
-<para>
-SCSI standards (found at <link linkend="t10">www.t10.org</link>)
-only make one footnote reference to the term <acronym>SMART</acronym>.
-In its place the awkward term "Informational Exceptions" is used. For SCSI
-tapes the term "TapeAlert" is used.
-</para>
-</sect1>
-
-<sect1 id="smartctl">
-      <title>smartctl command line utility</title>
-<para>
-The <command>smartctl</command> command line utility gets
-<acronym>SMART</acronym> information from the nominated device. In some
-cases <acronym>SMART</acronym> information held by the nominated device 
-can be modified by the <command>smartctl</command> command. The command 
-has many options that can be viewed by the long usage message output be
-either of these invocations: <command>smartctl -h</command> or
-<command>smartctl --help</command>. Those options that are only
-available to ATA disks (i.e. not available to SCSI disks or tape drives)
-are marked with "(ATA)". Unix style "man" page documentation is also
-available.
-</para>
-<para>
-The following options are currently available for SCSI disks and tape
-drives unless otherwise noted:
-<itemizedlist>
-<listitem><para><command>-a | --all</command>: equivalent to the
-combination <command>-i -H -A -l error -l selftest</command> options
-invoked in that order.
-</para></listitem>
-<listitem><para><command>-A | --attributes</command>: outputs the
-current device temperature, trip temperature, the number of elements
-in the grown defect list (GLIST) and data from the start-stop log page.
-Outputs some vendor specific information if available.
-</para></listitem>
-<listitem><para><command>-C | --captive</command>: used in conjunction
-with <command>-t short</command> or <command>-t long</command> options to
-do short or long self tests in the foreground. [Has no effect on tape
-drives.]
-</para></listitem>
-<listitem><para><command>-d TYPE | --device=TYPE</command> where TYPE 
-is "ata", "scsi", "sat", "marvell", "3ware,N", "hpt,L/N[,M]"
-or "cciss,N". Overrides utility's guess about the class of the device
-which is based on the form of the nominated device's name.
-</para></listitem>
-<listitem><para><command>-h | --help</command>: outputs lengthy usage
-message and exits without any other action.
-</para></listitem>
-<listitem><para><command>-H | --health</command>: outputs single device
-health metric determined by the device manufacturer. This will be "OK"
-or a failure message. 
-</para></listitem>
-<listitem><para><command>-i | --info</command>: outputs device 
-identification information (derived from a SCSI INQUIRY command) and
-whether the device supports <acronym>SMART</acronym> (and temperature 
-warnings) and if those facilities are currently enabled. The
-type of transport (e.g. FC or SAS) is also reported, if available.
-Some users have reported disks that report the wrong transport.
-</para></listitem>
-<listitem><para><command>-l TYPE | --log=TYPE</command> where TYPE is
-either "background", "selftest" or "error". Decodes are outputs the
-requested log. Note that <command>--all</command> does not include
-<command>--log=background</command> .
-</para></listitem>
-<listitem><para><command>-q TYPE | --quietmode=TYPE</command> where TYPE is
-either "silent" or "errorsonly". When the type is silent then nothing is
-output to the console but the exit status is set (so it is suitable for
-scripts). For "errorsonly" only errors are output to the console. The
-exit status is always set. [See the smartctl man page.]
-</para></listitem>
-<listitem><para><command>-r TYPE | --report=TYPE</command> where TYPE is
-either "ioctl[,&lt;n&gt;]" or "scsiioctl[,&lt;n&gt;]". Turns on low level
-debugging of issued commands and responses. These commands are issued
-through a system command called an "ioctl" in Unix. The debug can be for
-all issued commands (i.e. "ioctl") or only SCSI commands ("scsiioctl").
-Optionally the TYPE can have a comma and a number post pended to increase
-the volume of debug. See this <link linkend="ctldebug">section</link> for
-more details.
-</para></listitem>
-<listitem><para><command>-s VALUE | --smart=VALUE</command> where VALUE is
-either "on" or "off". Enables or disables <acronym>SMART</acronym> 
-monitoring (and temperature warnings).
-</para></listitem>
-<listitem><para><command>-S VALUE | --saveauto=VALUE</command> where VALUE
-is either "on" or "off". Controls whether the error log values are
-preserved across device power cycles.
-</para></listitem>
-<listitem><para><command>-t TEST | --test=TEST</command> where TEST
-is either "offline", "short" or "long". Despite its name "offline" is
-a short foreground test that all SCSI devices should support. A "short"
-self test is typically 2 minutes or less. A "long" self test will be
-considerably longer than 2 minutes, depending on the size of the media.
-The estimated time that a "long" self test will take is printed after
-the "selftest" log (i.e. with '-l selftest' or '-a')
-</para></listitem>
-<listitem><para><command>-V | --version</command>: outputs the smartctl
-version number (including the cvs version of all its source files)
-and build information then exits without any other action.
-</para></listitem>
-<listitem><para><command>-X | --abort</command>: will terminate a
-background short or long self test. Usually the self test log notes
-that a self test has been aborted. [Has no effect on tape drives.]
-</para></listitem>
-</itemizedlist>
-</para>
-<para>
-After the options <command>smartctl</command> expects a device name.
-This device name is not required for the '--help' or '--version' options.
-If no options are given and a valid device name is given then the copyright
-notice is output and the program exits. If the device name is invalid
-then that is reported. Only one device name can be given.
-</para>
-<para>
-Examples of various invocations of <command>smartctl</command> on a
-SCSI disk follow:
-<programlisting>
-# smartctl -i /dev/sdc
-smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-Device: SEAGATE  ST336754SS       Version: 0003
-Serial number: xxxxxxxx
-Device type: disk
-Transport protocol: SAS
-Local Time is: Fri Apr 28 15:55:34 2006 EDT
-Device supports SMART and is Enabled
-Temperature Warning Enabled
-</programlisting>
-</para>
-<para>
-<programlisting>
-# smartctl -H /dev/sdd
-smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-SMART Health Status: O
-</programlisting>
-<programlisting>
-# smartctl -A /dev/sdc
-smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-Current Drive Temperature:     42 C
-Drive Trip Temperature:        68 C
-Elements in grown defect list: 0
-Vendor (Seagate) cache information
-  Blocks sent to initiator = 1666124337
-  Blocks received from initiator = 1517744621
-  Blocks read from cache and sent to initiator = 384030649
-  Number of read and write commands whose size &lt;= segment size = 21193148
-  Number of read and write commands whose size &gt; segment size = 1278317
-Vendor (Seagate/Hitachi) factory information
-  number of hours powered up = 277.08
-  number of minutes until next internal SMART test = 108
-</programlisting>
-</para>
-</sect1>
-
-<sect1 id="selftest">
-      <title>Self Tests</title>
-<para>
-Rather than wait for thresholds to be tripped, an administrator can
-request a self test. Alternatively a self test can be scheduled
-periodically (e.g. at 3 a.m.  every night or perhaps weekly) with
-<command>smartd</command>. All SCSI disks and tape drives should
-support a <emphasis>default</emphasis> self test since it is mandatory.
-This can be invoked with the
-<command>smartctl -t offline &lt;device&gt;</command> command. Despite
-the term "offline" this is actually a foreground test of less than 2
-minutes. On completion the default self test reports any errors detected
-in its response. The default self test makes no entry into the self test
-log. Most SCSI devices perform a default self test when they are being
-powered up.
-</para>
-<para>
-The other self tests that are optionally supported by the device are listed
-here with the <command>smartctl</command> invocation in brackets:
-<itemizedlist>
-<listitem><para>
-background short [<command>smartctl -t short &lt;device&gt;</command>]
-</para></listitem>
-<listitem><para>
-background extended [<command>smartctl -t long &lt;device&gt;</command>]
-</para></listitem>
-<listitem><para>
-foreground short [<command>smartctl -C -t short &lt;device&gt;</command>]
-</para></listitem>
-<listitem><para>
-foreground extended [<command>smartctl -C -t long &lt;device&gt;</command>]
-</para></listitem>
-</itemizedlist>
-Short self tests should take less than two minutes to complete. The extended
-self tests have been known to take more than one hour for disks that are over 
-100 GBytes in size. Care should be taken with foreground tests on disks
-with mounted file systems as the OS may not take kindly to an hour delay
-on a simple READ command.
-<footnote><para>
-Linux has an additional problem with the foreground extended self tests:
-it will attempt to time out the command after 10 seconds. This will appear
-in the self test log page as an aborted self test. This problem is fixed
-in lk 2.4.22 and the lk 2.6 series (by extending the
-timeout to 2 hours). To be on the safe side use the background extended
-test instead. Also some disks silently ignore foreground self 
-tests (e.g. the Seagate Cheetah series).
-</para></footnote>
-</para>
-<para>
-Background self tests can be aborted with the <command>smartctl -X 
-&lt;device&gt; </command> command. The self test log will note that an
-abort was requested.
-</para>
-<para>
-Self tests other than the default self test cause an entry to be placed
-in the self test results log page. The 20 most recent self tests are
-held. The self test results can be viewed with the
-<command>smartctl -l selftest &lt;device&gt;</command> command. All tests
-output the accumulated power on hours when the test was performed and
-the success or otherwise (e.g. the self test was aborted by the user's
-request) of the test. Unsuccessful self tests output a self test segment 
-number (vendor specific), the logical block address of the first failure
-(if appropriate) and a sense_key,asc,ascq triple (see appendix). Following
-the self test result table is the expected duration of an uninterrupted 
-extended self test (when that figure is provided by the device). 
-</para>
-<para>
-Here is an example of a self test log:
-<programlisting>
-# smartctl -l selftest /dev/sdd
-smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-
-SMART Self-test log
-Num  Test              Status                 segment  LifeTime  LBA_first_err [SK ASC ASQ]
-     Description                              number   (hours)
-# 1  Background long   Completed                   -     100                 - [-   -    -]
-# 2  Background long   Completed                   -      25                 - [-   -    -]
-# 3  Background long   Completed                   -      24                 - [-   -    -]
-# 4  Background short  Completed                   -       0                 - [-   -    -]
-
-Long (extended) Self Test duration: 603 seconds [10.1 minutes]
-</programlisting>
-</para>
-</sect1>
-<sect1 id="errorlog">
-      <title>Error Logs</title>
-<para>
-The <command>smartctl -l error &lt;device&gt;</command> command displays
-the error counters maintained in the device's log pages. Here is an
-example of an error log:
-<programlisting>
-# smartctl -l error /dev/sdd
-smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-
-Error counter log:
-           Errors Corrected by           Total   Correction     Gigabytes    Total
-               ECC          rereads/    errors   algorithm      processed    uncorrected
-           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
-read:       5805        0         0      5805       5805        121.451           0
-write:         0        0         0         0          0        471.291           0
-
-Non-medium error count:        0
-</programlisting>
-The displayed error logs (if available) are displayed on separate lines:
-<itemizedlist>
-<listitem><para>
-write error counters
-</para></listitem>
-<listitem><para>
-read error counters
-</para></listitem>
-<listitem><para>
-verify error counters (only displayed if non-zero)
-</para></listitem>
-<listitem><para>
-non-medium error counter (only a single number displayed). This represents
-the number of recoverable events other than write, read or verify errors.
-</para></listitem>
-<listitem><para>
-error events are held in the "Last n error events" log page. The number
-of error event records held (i.e. "n") is vendor specific (e.g. up to 23
-records are held for Hitachi 10K300 model disks). The contents of each
-error event record is in ASCII and vendor specific. The parameter code
-associated with each error event record indicates the relative time at
-which the error event occurred. A higher parameter code indicates that the
-error event occurred later in time.
-If this log page is not supported by the device then "Error Events logging
-not supported" is output. If this log page is supported and there are
-error event records then each one is prefixed by "Error event &lt;n&gt;:"
-where &lt;n&gt; is the parameter code.
-</para></listitem>
-</itemizedlist>
-Each of the write, read and verify error counter logs has various
-parameters codes. They are itemized below with the smartctl column
-name followed, in brackets, with SCSI standard's description and
-parameter code). A description taken from Seagate's SCSI
-manual (publication 77738479, Rev J) is then given.
-<itemizedlist>
-<listitem><para>
-Errors Corrected by ECC, fast [Errors corrected without substantial delay:
-00h]. An error correction was applied to get perfect data (a.k.a. ECC
-on-the-fly). "Without substantial delay" means the correction did not
-postpone reading of later sectors (e.g. a revolution was not lost). The
-counter is incremented once for each logical block that requires correction.
-Two different blocks corrected during the same command are counted as two
-events.
-</para></listitem>
-<listitem><para>
-Errors Corrected by ECC: delayed [Errors corrected with possible delays: 01h].
-An error code or algorithm (e.g. ECC, checksum) is applied in order to
-get perfect data with substantial delay. "With possible delay" means the
-correction took longer than a sector time so that reading/writing of
-subsequent sectors was delayed (e.g. a lost revolution). The counter is
-incremented once for each logical block that requires correction. A
-block with a double error that is correctable counts as one event and
-two different blocks corrected during the same command count as two
-events.
-</para></listitem>
-<listitem><para>
-Error corrected by rereads/rewrites [Total (e.g. rewrites and rereads): 02h].
-This parameter code specifies the counter counting the number of errors
-that are corrected by applying retries. This counts errors recovered,
-not the number of retries. If five retries were required to recover one
-block of data, the counter increments by one, not five. The counter is
-incremented once for each logical block that is recovered using retries.
-If an error is not recoverable while applying retries and is recovered
-by ECC, it isn't counted by this counter; it will be counted by the
-counter specified by parameter code 01h - Errors Corrected With Possible
-Delays.
-</para></listitem>
-<listitem><para>
-Total errors corrected [Total errors corrected: 03h].
-This counter counts the total of parameter code errors 00h, 01h and
-02h (i.e. error corrected by ECC: fast and delayed plus errors corrected
-by rereads and rewrites). There is no "double counting" of data errors
-among these three counters. The sum of all correctable errors can be
-reached by adding parameter code 01h and 02h errors, not by using this
-total. [The author does not understand the previous sentence from the
-Seagate manual.]
-</para></listitem>
-<listitem><para>
-Correction algorithm invocations [Total times correction algorithm
-processed: 04h]. This parameter code specifies the counter that counts
-the total number of retries, or "times the retry algorithm is invoked".
-If after five attempts a counter 02h type error is recovered, then five
-is added to this counter. If three retries are required to get stable
-ECC syndrome before a counter 01h type error is corrected, then those
-three retries are also counted here. The number of retries applied to
-unsuccessfully recover an error (counter 06h type error) are also
-counted by this counter.
-</para></listitem>
-<listitem><para>
-Gigabytes processed {10^9} [Total bytes processed: 05h]. This parameter
-code specifies the counter that counts the total number of bytes either
-successfully or unsuccessfully read, written or verified (depending
-on the log page) from the drive. If a transfer terminates early because
-of an unrecoverable error, only the logical blocks up to and including
-the one with the uncorrected data are counted. [smartmontools divides
-this counter by 10^9 before displaying it with three digits to the
-right of the decimal point. This makes this 64 bit counter easier to
-read.]
-</para></listitem>
-<listitem><para>
-Total uncorrected errors [Total uncorrected errors: 06h]. This parameter
-code specifies the counter that contains the total number of blocks for
-which an uncorrected data error has occurred.
-</para></listitem>
-</itemizedlist>
-</para>
-<para>
-The SCSI standard (SPC-3) cautions that the <emphasis>exact</emphasis>
-definitions of the error counters is not part of the standard (i.e. they
-are vendor specific). As noted the above list contains Seagate's
-explanation for its disk products (the last revision of that document
-was 1999). Seagate's disk product manuals imply that the disk firmware
-collects these counter values and periodically commit them to persistent
-storage (disk or non-volatile RAM).
-<footnote><para>
-This is why some models spring to life after minutes of inactivity and
-perform some operation even though there are no external commands
-pending.
-</para></footnote>
-They also imply that their firmware is monitoring these error counters
-and if they exceed some threshold (e.g. in a certain time interval)
-then the firmware will report a thresholds exceeded.
-</para>
-<para>
-The error counter logs for some disks (e.g. some Seagate models) can
-look worrying:
-<programlisting>
-# smartctl -l error /dev/sdc
-smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-
-Error counter log:
-           Errors Corrected by           Total   Correction     Gigabytes    Total
-               ECC          rereads/    errors   algorithm      processed    uncorrected
-           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
-read:    1111396        0         0   1111396    1113203        781.138          13
-write:         0        0         0         0         92        822.450           4
-verify:   341115        0         0    341115     341115         42.159           0
-
-Non-medium error count:        1
-</programlisting>
-The "fast" ECC corrected number is high. However the '-H' option reports the disk is
-in good health as does an extended (long) background self test. The uncorrected errors
-would be a problem had in not been for the fact that the author caused them on
-purpose (by writing a bad sector with the SCSI WRITE LONG command).
-</para>
-</sect1>
-
-<sect1 id="background">
-      <title>Background scan</title>
-<para>
-Recent SCSI disks can perform what are termed as "background scans". These
-are reads of the whole media with recoverable errors acted on and
-unrecoverable errors noted. If a sector (block) is found with a recoverable
-error (i.e. the error correction codes (ECC) detect a problem but contain
-enough redundant information to fix the problem) it may be fixed with a
-re-write "in place". Alternatively the disk may decide to re-assign the
-recovered data to another physical sector which is assigned the same logical
-block address (and the original faulted sector is unmapped and placed on
-the grown defect list (GLIST)). Since unrecoverable errors potentially
-involve user data being lost, no automatic recovery action is undertaken by
-the disk. However logical block addresses that contain either recovered
-data or unrecoverable errors are noted in the Background Scan Results
-log page. The <command>smartctl --log=background</command> command decodes
-and outputs that log page.
-</para>
-<para>
-Background scans may be performed periodically (e.g. every 24 hours) or
-every time the disk is powered up (or both). These parameters can be
-controlled via the Background Control mode page. The 
-<link linkend="sdparm">sdparm</link> utility can be used to access and
-modify this mode page.
-</para>
-<para>
-Here is an example of the output from the Background Scan Results log page.
-The first descriptor in that log page shows the status followed by up
-to 2048 entries for background scan "events". In this case a background
-scan is still in progress and 3 scans have been completed in the past.
-The "events" shown are all recoverable errors that the disk dealt with
-by rewriting the block.
-<programlisting>
-# smartctl -l background /dev/sda
-smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
-Home page is http://smartmontools.sourceforge.net/
-
-Background scan results log
-  Status: scan is active
-    Accumulated power on time, hours:minutes 618:01 [37081 minutes]
-    Number of background scans performed: 3,  scan progress: 59.81%
-
-   #  when        lba(hex)    [sk,asc,ascq]    reassign_status
-   1  617:13  0000000001fbc5b2  [1,17,1]   Recovered via rewrite in-place
-   2  617:13  00000000022756d2  [1,17,1]   Recovered via rewrite in-place
-   3  617:14  000000000227727f  [1,17,1]   Recovered via rewrite in-place
-   4  617:18  00000000023568e5  [1,17,1]   Recovered via rewrite in-place
-   5  617:22  00000000024fab5f  [1,17,1]   Recovered via rewrite in-place
-   6  617:23  00000000025aa29a  [1,17,1]   Recovered via rewrite in-place
-   7  617:27  000000000275d0bc  [1,17,1]   Recovered via rewrite in-place
-</programlisting>
-In this case the reassign_status shows that no user intervention is
-required. The other "don't worry (too much)" reassign_status is "Logical
-block successfully reassigned". Any other reassign_status will require
-user intervention to correct. There is a LOWIR ("log only when intervention
-required") bit in the Background Control mode page that the user can
-set (e.g. with the <link linkend="sdparm">sdparm</link> utility) to filter
-out "noisy" entries like those shown above.
-</para>
-<para>
-The user can manually re-assign logical blocks with a utility like
-<command>sg_reassign</command> found in the
-<link linkend="sg3utils">sg3_utils</link> package. The background scan
-output contains a "[sk,asc,ascq]" tuple of numbers. The one shown above
-translates to "recovered error, recovered data with retries". Unrecoverable
-errors would most likely have 3 ("medium eror") or 4 ("hardware error")
-as the first number. A decoding of the latter two numbers can be found
-in the "Numeric Order Codes" annex of SPC-4 (see <link linkend="t10">
-www.t10.org</link>) in the Additional Sense Codes section.
-</para>
-</sect1>
-
-
-<sect1 id="smartd">
-      <title>smartd daemon</title>
-<para>
-<command>smartd</command> is a daemon for monitoring disks (both ATA and
-SCSI). It is recommended that tape drives and medium changers are monitored
-in a more manual fashion with the <command>smartctl</command> command
-as discussed in <xref linkend="tapes"/>.
-</para>
-<para>
-The configuration file for <command>smartd</command>
-is called <filename>/etc/smartd.conf</filename> and has a man page (as does
-the <command>smartd</command> command). The controlling daemon script
-is placed in the normal place for a distribution, typically
-<filename>/etc/rc.d/init.d/smartd</filename>.
-</para>
-<para>
-<command>smartd</command> polls the devices it has recognized when it
-was started. By default it polls every 30 minutes. It reports any adverse
-finding and noteworthy occurrences (e.g. disk drive temperature changes)
-to a log file (<filename>/var/log/messages</filename>). <command>smartd
-</command> can be configured to take other actions, for example send
-email to a system administrator.
-</para>
-<para>
-SCSI disks can be discovered by <command>smartd</command> via a scan of 
-device nodes (for linux: <filename>/dev/sda</filename> through to 
-<filename>/dev/sdz</filename>) by placing the word "DEVICESCAN" in
-<filename>/etc/smartd.conf</filename> file. Alternatively the
-"DEVICESCAN" word can be removed (or commented out) and SCSI devices
-named explicitly:
-<programlisting>
-/dev/sda -a -d scsi
-/dev/sdb -a -d scsi
-</programlisting>
-</para>
-<para>
-The "-d scsi" argument overrides what <command>smartd</command> would
-guess as the device
-class (i.e. "ata", "scsi", "sat", "marvell", "3ware,N", "hpt,L/N[,M]"
-or "cciss,N"). In smartmontools version 5.37 the <command>smartd</command>
-daemon guesses SCSI device nodes on the basis of their name (i.e. without
-querying the device beforehand). However it does query the device
-after it has been placed in the SCSI group and if it notices that the
-vendor name is "ATA     " and that it responds to SCSI ATA PASS THROUGH
-commands then a informational message is sent to the log suggesting
-that the user try adding '-d sat' (or perhaps a '-d scsi' should be
-changed to '-d sat'). After such a warning for node <filename>/dev/sdb
-</filename> the code snippet from the <filename>/etc/smartd.conf</filename>
-file might be changed to:
-<programlisting>
-/dev/sda -a -d scsi
-/dev/sdb -a -d sat
-</programlisting>
-</para>
-<para>
-This may be automated in a later version of
-smartmontools (the <command>smartctl</command> command does automatic
-detection in version 5.37).
-</para>
-</sect1>
-
-<sect1 id="tapes">
-      <title>TapeAlert</title>
-<para>
-TapeAlert (or "tape alerts") is closely related to the 
-<acronym>SMART</acronym> infrastructure provided for SCSI disks.
-TapeAlert is specialized for tape and medium changer devices. An example of
-a TapeAlert is an indication that the tape drive heads need to be cleaned.
-</para>
-<para>
-Pending TapeAlert errors can be read from the TapeAlert log page
-(using <command>smartctl</command>). This can be done even when 
-<acronym>SMART</acronym>
-monitoring is disabled (e.g. after <command>smartctl -s off &lt;tape_device
-&gt;</command>).  In fact, the best way to use the TapeAlert mechanism is 
-to poll the flags (with <command>smartctl</command>) at relevant times when
-using the tape, for example:
-<itemizedlist>
-<listitem><para>
-when starting a new job using the tape drive
-</para></listitem>
-<listitem><para>
-after an unrecoverable error
-</para></listitem>
-<listitem><para>
-at the end of using each tape (and before it is unloaded)
-</para></listitem>
-</itemizedlist>
-</para>
-<para>
-The TapeAlert information is divided into three severity classes:
-Critical, Warning, and Information. The critical messages require
-urgent user intervention. Both critical and warning errors may lead to
-loss of data. Some of the errors are related to the medium and others
-to the tape drive itself. This is why the TapeAlert information should be
-checked when the tape is in use and not polled periodically (i.e. the 
-<command>smartd</command> daemon with its periodic polling is not
-particularly useful for TapeAlert mechanism).
-</para>
-<para>
-Different sets of flags are defined for tape drives and media
-changers. Most of the flags are optional and the set of flags
-supported depends on the device. TapeAlert is being included into the
-SCSI-3 standards. Many SCSI-2 drives support TapeAlert but the
-implementation may not fully conform to the SCSI-3 draft definition
-used by smartmontools.
-</para>
-<para>
-It is important that only one application
-(or OS driver) is monitoring tape alerts since reading the TapeAlert log 
-page deactivates all flags after they are read. 
-<footnote><para>
-In a multi initiator environment (e.g. several computers sharing the same
-tape jukebox) there should only be one application monitoring tape alerts
-per initiator.
-</para></footnote>
-Currently the Linux SCSI tape drivers (st and osst) do not check the 
-TapeAlert log page. In Linux, a medium changer device (i.e. the robot in
-a tape jukebox) is accessed via its SCSI generic (sg) device name.
-</para>
-<para>
-Code and information on the TapeAlert mechanism have been provided by 
-Kai M&auml;kisara <email>Kai.Makisara at kolumbus dot fi</email>.
-</para>
-</sect1>
-
-<sect1 id="examples">
-      <title>Examples</title>
-<para>
-Here is some output from the <command>smartctl</command>
-command. Mostly it is for the '--all' option.
-<itemizedlist>
-<listitem><para>
-StorageTek LT20 tape 'jukebox': the
-<ulink url="examples/bnch_DLT1.html">
-<literal>tape reading mechanism</literal></ulink>
-and the
-<ulink url="examples/bnch_robot.html">
-<literal>medium changer</literal></ulink> (robot).
-Note the TapeAlert warnings in the medium changer output.
-</para></listitem>
-<listitem><para>
-HP DDS-4 
-<ulink url="examples/hp_c5713a_smt_a.html">
-<literal>tape</literal></ulink>
-drive.
-</para></listitem>
-<listitem><para>
-Generic ATAPI CD-RW
-<ulink url="examples/atapi_cdrw_smt_a.html">
-<literal>cd writer</literal></ulink> is an example of a device that
-does not support <acronym>SMART</acronym>.
-</para></listitem>
-<listitem><para>
-IBM DDRS 39130
-<ulink url="examples/ddrs_39130_smt_a.html">
-<literal>disk</literal></ulink>
- manufactured in 1998. 
-</para></listitem>
-<listitem><para>
-Fujitsu MAM3184MP 18 GigaByte 
-<ulink url="examples/mam3184_smt_a.html">
-<literal>disk</literal></ulink> when all is well. Here is the output from
-the <command>smartctl -H</command> command after the IEC Test bit has been 
-set (with the <command>smartctl -s on -r ioctl,3</command> command) on the
-same Fujitsu <ulink url="examples/mam3184_smt_health.html">
-<literal>disk</literal></ulink> .
-</para></listitem>
-<listitem><para>
-Fujitsu MAP3735NP 73 GigaByte 
-<ulink url="examples/map3735_smt_a.html">
-<literal>disk</literal></ulink>
-</para></listitem>
-<listitem><para>
-Quantum ATLAS IV 36 WLS, 36 GigaByte 
-<ulink url="examples/ativ_36_smt_a.html">
-<literal>disk</literal></ulink>
-</para></listitem>
-<listitem><para>
-Seagate Cheetah ST336754 36 GigaByte
-<ulink url="examples/st336754_smt_a.html">
-<literal>disk</literal></ulink>.
-</para></listitem>
-</itemizedlist>
-
-</para>
-</sect1>
-
-<sect1 id="raid">
-      <title>RAID, JBOD and Enclosures</title>
-<para>
-It is unlikely that a hardware RAID controller will directly support 
-smartmontools. A SCSI RAID controller is a virtual target device that 
-essentially remaps the SCSI commands it receives to the physical disks on its 
-internal buses. The physical disks in a "SCSI" RAID could be ATA or sATA
-disks, in this case a SCSI bus is used between the host computer and an
-external RAID controller since LVD SCSI buses (SPI-2,3 and 4) can run 
-up to 25 metres (plus other protocol related issues).
-</para>
-<para>
-Some SCSI RAIDs equipped internally with SCSI disks allow access to the 
-physical disks via logical unit numbers (LUNs) greater than 0. The SCSI RAID
-controller itself takes a LUN equal to 0. In this case smartmontools could
-be applied to the LUNs greater than 0 that refer to physical disks.
-</para>
-<para>
-Some SCSI RAIDs equipped internally ATA disks have a mechanism that
-allows ATA commands to be tunnelled to the ATA disks. The 3ware 6000
-and 7000 series Escalade controllers are examples. In this case,
-special provision has been made in smartmontools (starting with
-release 5.1-16) to tunnel the ATA command required through to the
-physical disks.  This is done by using the <command>-d 3ware,N</command>
-option/Directive. See the <command>smartctl</command> 
-and <command>smartd</command> man pages for details.
-</para>
-<para>
-The approach that smartmontools takes is to communicate directly
-with physical storage devices (e.g. a disk). Another approach is
-to collectively monitor and manage a group of disks and/or tape
-drives (be they a RAID, "Just a Bunch Of Disks" <acronym>JBOD</acronym>
-or a collection of disks and tape drives) in an enclosure. The SCSI
-Enclosure Services <acronym>SES</acronym> (reference: SES-2 at
-<link linkend="t10">www.t10.org</link>) is designed for this task.
-Both SCSI device and recent SATA disk enclosures are using SES. Amongst
-other things SES can monitor the state of individual devices within the
-enclosure, the temperature, power supplies and fans. A user can set
-thresholds, define alarm types and remotely administer the enclosure.
-</para>
-</sect1>
-
-<appendix id="Details">
-      <title>Details</title>
-<sect1 id="stand">
-      <title>Standards</title>
-<para>
-One of the first surprises working with SCSI devices and smartmontools
-is that the SCSI standards (found at <link linkend="t10">www.t10.org</link>)
-do <emphasis>not</emphasis> use the term <acronym>SMART</acronym>. In its
-place the awkward term "Informational Exceptions" (IE) is used.
-</para>
-<para>
-The original SCSI standard (over 20 years old now) and the SCSI-2 standard
-were monolithic documents. In SCSI-3 and beyond the SCSI standards have
-been sub-divided and three categories of interest are the:
-<itemizedlist>
-<listitem><para>architectural model [SAM-4]</para></listitem>
-<listitem><para>command sets [SPC-4, SBC-3, SSC-3, SMC-2, etc]
-</para></listitem>
-<listitem><para>transports [SPI-4, SBP-2, FCP-3, SAS, etc]</para></listitem>
-</itemizedlist>
-The architectural model while interesting says nothing specific about
-Informational Exceptions or related topics. With respect to the transports
-the term <emphasis>SCSI</emphasis> has often been synonymous with one
-of the SCSI Parallel Interface transports (e.g. SPI-4 which is often know
-as "Ultra320") however this is unhelpful. For the purpose of smartmontools
-the SCSI command sets are more interesting. The main reference is the
-SCSI Primary Commands (SPC-4) document, specifically these sections:
-<itemizedlist>
-<listitem><para>self test operations; SEND DIAGNOSTIC command (which is
-the mechanism for requesting self tests)
-</para></listitem>
-<listitem><para>MODE SENSE and MODE SELECT commands (both 6 and 10 byte
-variants); Mode parameters [the Informational Exceptions Control (IEC) mode
-page and the Control mode page]
-</para></listitem>
-<listitem><para>LOG SENSE and LOG SELECT commands;
-Log parameters [these log pages: Informational exceptions,
-read/write/verify error counters, non medium error count, temperature, 
-start-stop cycle counter and the self test results]
-</para></listitem>
-</itemizedlist>
-The SCSI Block Commands (SBC-3) document covers random access storage
-devices such as disks (but excluding CD/DVD readers and writers which are
-covered by MMC-4) while the SCSI Streaming Commands (SSC-3) document covers 
-tape systems.  The SBC-3 standard does not contain any additional 
-information (compared with SPC-4) about Informational Exceptions. 
-The SSC-3 standard covers TapeAlert (section 4.2.15), some extra facilities in
-the IEC mode page (see the mode parameters section) and some additional
-log pages. Medium changers, typically the "robots" in jukebox tape systems,
-often support the TapeAlert mechanism and are described in the SMC-2 standard. 
-</para>
-</sect1>
-
-<sect1 id="infoexc">
-      <title>Informational Exceptions</title>
-<para>
-So what are Informational Exceptions in the SCSI context? They are a
-set of vendor specific parameters that the device firmware monitors and 
-if a "failure prediction threshold" is exceeded then an exception is
-reported. A user is also able to set thresholds on error counters and
-have an exception reported if a condition is met. Additionally most
-modern disks monitor their temperature and will issue a warning if
-a temperature threshold is exceeded.
-</para>
-<para>
-The "failure prediction threshold" exception reporting and the temperature
-warning are separately controlled (in byte 2 of the Informational Exceptions
-Control (IEC) mode page).
-<footnote><para>
-Henceforth the term <emphasis>Informational Exceptions</emphasis>
-(or IE) will include both Informational Exceptions and the
-temperature (or "enclosure degraded") warnings.
-</para></footnote>
-In smartmontools the
-<command>smartctl -s on &lt;device&gt;</command> command turns on IE.
-There are various reasons why this may not (fully) work (e.g. IEC mode
-page not available or not changeable) so this command queries the device
-again after it has attempted the change and reports the state.
-The <command>smartctl -s off &lt;device&gt;</command> command turns off
-IE reporting.
-<footnote><para>
-IE have a (minor) performance impact on a disk. There are various other
-settings in the IEC mode page (e.g. PERF, EBF and LOGERR) that address
-this. The standard gives a lot of latitude to the vendor in implementing
-these additional flags. This finer level of control may be added to 
-smartmontools if the need arises.
-</para></footnote>
-</para>
-<sect2 id="iereport">
-      <title>IE reporting</title>
-<para>
-Informational Exceptions are reported via the standard SCSI status
-reporting mechanism of an additional sense code (asc) and an additional
-sense code qualifier (ascq) pair. A selection of these pairs and the 
-associated message (there is full list in the SPC-3 document) is listed 
-here:
-<programlisting>
-asc    ascq   message
--------------------------------------------------------
-0xb    0x1    Warning - specified temperature exceeded
-0x5d   0x0    Failure prediction threshold exceeded
-0x5d   0x2    Media failure prediction threshold exceeded
-0x5d   0x10   Hardware impending failure general hard drive failure
-0x5d   0x11   Hardware impending failure drive error rate too high
-0x5d   0x56   Spindle impending failure start unit times too high
-0x5d   0xff   Failure prediction threshold exceeded (false)
-</programlisting>
-The last entry in the above table results from setting the TEST bit and
-is for exercising the reporting mechanism rather than the indication
-of an actual error.
-See this <link linkend="testbit">footnote</link> for more information.
-</para>
-<para>
-One difficulty with IE is that the device firmware may detect these
-conditions independently of any command executing. Even if it detects
-an informational exception during a command it needs to be careful
-sending IE error notifications back with a command especially if
-that command succeeded (Linux will not handle this too well in the
-2.4 kernel series). 
-There is asynchronous event notification (AEN) in SCSI but it is not
-reliably supported across all transports. So smartmontools relies
-on a poll from the <command>smartd</command> daemon (the default
-is every 30 minutes) to detect informational exceptions.
-</para>
-<para>
-The additional sense code and its qualifier are part of what is termed as
-the <emphasis>sense buffer</emphasis> which is the response to a 
-REQUEST SENSE command. The sense key is also found in the sense buffer.
-Synchronous SCSI commands that fail return a single byte status code of
-CHECK CONDITION. An OS kernel would see this error/warning status and
-then check the sense buffer (by doing a REQUEST SENSE or by other means)
-and decide how to continue. From smartmontools's point of view, its
-<command>smartd</command> daemon would like to process Informational 
-Exceptions without interference from the OS. This is done by setting up
-the IEC mode page's MRIE field set to 6. This instructs the SCSI 
-device to hold a pending exception until an unsolicited REQUEST SENSE is 
-sent. If an exception is pending then the sense key will be "NO SENSE"
-and the asc, ascq pair will be set accordingly. In the case of no pending
-exception the asc,ascq pair will both be zero. The pending exception is 
-also visible in the IE log page, if that is supported. So 
-<command>smartd</command> can check the device during its normal polling 
-cycle.
-</para>
-<para>
-Pending informational exceptions can also be checked by running
-<command>smartctl -H &lt;device&gt;</command>. A message of
-"SMART Health Status: OK" indicates that there is no pending IE.
-<footnote><para>
-<anchor id="testbit"/>
-One might worry whether the <command>smartd</command> daemon is properly set
-up or if the device really will issue IE when the need arises. The mechanism
-can be tested by setting the TEST bit in the IEC mode page. That is
-done by this command: <command>smartctl -r ioctl,3 -s on &lt;device&gt;
-</command> [ignore the extra debugging output that "-r ioctl,3" causes]. A
-special asc/ascq pair is reserved for testing (0x5d,0xff)
-and the standard associates with it this awkward message: "Failure prediction 
-threshold exceeded (false)". A call to 
-<command>smartctl -H &lt;device&gt;</command> or waiting until the next 
-<command>smartd</command> poll should produce that message if the mechanism 
-is working. The IEC mode page TEST bit can be turned off (i.e. back to normal
-IE) with <command>smartctl -s on &lt;device&gt;</command>. The output
-after the TEST bit has been activated is shown in the 
-Examples section for the Fujitsu MAM3184 disk.
-</para></footnote>
-</para>
-</sect2>
-</sect1>
-
-<sect1 id="ctldebug">
-      <title>smartctl debug</title>
-<para>
-Debug information for <command>smartctl</command> is output when 
-the <command>-r ioctl</command> or the <command>-r scsiioctl</command>
-option is used.  More debug is output when the <command>-r ioctl,&lt;n&gt;
-</command> form is used (where "n" is a number greater or equal to 1). Both 
-<command>-r ioctl</command> and <command>r scsiioctl,1</command> select
-the same amount of SCSI debug information. The debug levels currently 
-defined are:
-<itemizedlist>
-<listitem><para>
-1 - output SCSI commands sent to the device and the status received from
-the device
-</para></listitem>
-<listitem><para>
-2 - additionally, output the first 64 bytes of data sent to or received from
-the device
-</para></listitem>
-<listitem><para>
-3 - additionally, set the IEC mode page TEST bit if accompanying the '-s on'
-option
-</para></listitem>
-</itemizedlist>
-See this <link linkend="testbit">footnote</link> for more information about the
-use of the IEC mode page TEST bit.
-</para>
-<para>
-One shortcoming of the Informational Exception data provided by
-SCSI devices (at least as defined in the current standard) is that
-no LOG SENSE page tells the user how many hours the device has been
-in use for. The device needs to track its "age" for applying timestamps
-to self test results (seen in the "Lifetime (hours)" column of the
-<command>smartctl -l selftest</command> command) if they are supported.
-So one way to circumvent this shortcoming is to do dummy self 
-tests. Hence do a <command>smartctl -t short</command> command and then
-wait 2 minutes to see the result in the self test log in which the most
-recent self test row (i.e. the first) will have the current lifetime of
-the device.
-</para>
-</sect1>
-
-<sect1 id="links">
-      <title>Links</title>
-<para>
-Here are some links to related projects and packages:
-<itemizedlist>
-<listitem><para>
-<anchor id="t10"/>
-the primary reference site for SCSI architecture, command sets and transports
-is <ulink url="http://www.t10.org">
-<literal>www.t10.org</literal></ulink>. The main documents of interest
-to smartmontools are the "Primary Commands" (SPC-4), the "Block
-Commands" (SBC-3) for disks and the "Streaming Commands" (SSC-3) for
-tape drives. This <ulink url="http://www.t10.org/scsi-3.htm">
-<literal>www.t10.org/scsi-3.htm</literal></ulink> page contains a diagram
-showing the relationships of various SCSI standards.
-<footnote><para>
-The documents found on the t10 site are actually <emphasis>draft</emphasis>
-standards. Once they are ratified they become available from ANSI for
-a fee. The t10 site maintains the last draft prior to ratification and
-the most recent draft of yet to be ratified standards.
-</para></footnote>
-</para></listitem>
-<listitem><para>
-<anchor id="scsirastools"/>
-SCSI raid monitoring tools plus a firmware update utility and other low level
-tools <ulink url="http://scsirastools.sourceforge.net">
-<literal>scsirastools.sourceforge.net</literal></ulink> .
-</para></listitem>
-<listitem><para>
-<anchor id="sdparm"/>
-The <command>sdparm</command> utility allows mode page settings to be
-viewed and changed. It can decode Vital Product Data (VPD) pages.
-It implements a small number of commands to start and stop media,
-and to eject and load removable media.
-See this page <ulink url="http://www.torque.net/sg/sdparm.html">
-<literal>www.torque.net/sg/sdparm.html</literal></ulink> .
-<command>sdparm</command> is available on Linux with ports to
-FreeBSD, Tru64 and Windows.
-</para></listitem>
-<listitem><para>
-<anchor id="sg3utils"/>
-A package of SCSI low level tools for Linux called sg3_utils can be found
-on this page <ulink url="http://www.torque.net/sg/sg3_utils.html">
-<literal>www.torque.net/sg/sg3_utils.html</literal></ulink> (the most recent
-version is sg3_utils-1.22). Allows command level access to SCSI devices
-and is available on Linux with ports to FreeBSD, Tru64 and Windows.
-</para></listitem>
-<listitem><para>
-<anchor id="howto"/>
-There is a HOWTO on the Linux SCSI subsystem in the 2.4 series here:
-<ulink url="http://www.tldp.org/HOWTO/SCSI-2.4-HOWTO">
-<literal>www.tldp.org/HOWTO/SCSI-2.4-HOWTO</literal></ulink>.
-</para></listitem>
-</itemizedlist>
-</para>
-
-<para>
-CVS $Id: smartmontools_scsi.xml,v 1.16 2006/11/21 20:23:07 dpgilbert Exp $
-</para>
-</sect1>
-</appendix>
-
-</article>
-