diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-15 17:14:48 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-15 17:14:48 +0000 |
| commit | 9021c15fadb3638b6d118fdba8cf19cc4ca9e063 (patch) | |
| tree | 3971b5280a3877d4d1c9d1b729f860c6c4752d54 /debian | |
| parent | Adding upstream version 7.4. (diff) | |
| download | smartmontools-9021c15fadb3638b6d118fdba8cf19cc4ca9e063.tar.xz smartmontools-9021c15fadb3638b6d118fdba8cf19cc4ca9e063.zip | |
Adding debian version 7.4-2.debian/7.4-2debian
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'debian')
34 files changed, 3061 insertions, 0 deletions
diff --git a/debian/10mail b/debian/10mail new file mode 100644 index 0000000..f921a33 --- /dev/null +++ b/debian/10mail @@ -0,0 +1,13 @@ +#!/bin/bash -e + +# Send mail if /usr/bin/mail exists +if ! [ -x /usr/bin/mail ]; then + echo "Your system does not have /usr/bin/mail. Install the mailx or mailutils package" + exit 1 +fi + +input=$1 +shift + +/usr/bin/mail "$@" < $input + diff --git a/debian/NEWS b/debian/NEWS new file mode 100644 index 0000000..3f98f7d --- /dev/null +++ b/debian/NEWS @@ -0,0 +1,48 @@ +smartmontools (7.0-1) unstable; urgency=medium + + This release re-introduces "update-smart-drivedb" utility that now uses + GPG to validate downloaded file. + + -- Dmitry Smirnov <onlyjob@debian.org> Thu, 10 Oct 2019 12:39:16 +1100 + +smartmontools (6.4+svn4214-1) unstable; urgency=medium + + Previous versions of the smartmontools package included a tool + update-smart-drivedb which downloaded updated drive definitions + from the smartmontools website and stored them at + + /var/lib/smartmontools/drivedb/drivedb.h + + This tool did not download the definitions in a secure manner and + so the feature has been removed in this version. Future drive DB + updates will be propagated via normal Debian package updates, + including backports. + + If you already have a drivedb.h file at that location, smartctl + will continue to use it. + + -- Jonathan Dowland <jmtd@debian.org> Mon, 01 Feb 2016 21:19:47 +0000 + +smartmontools (5.37-1) unstable; urgency=low + + Prior to 5.37 temperature logging was enabled per default on SCSI disks, as + of version 5.37 please use the -W option in smartd.conf. + + -- Guido Guenther <agx@sigxcpu.org> Thu, 05 Apr 2007 10:18:10 +0200 +smartmontools (7.0-1) unstable; urgency=medium + + Previous versions of the smartmontools package included a tool + update-smart-drivedb which downloaded updated drive definitions + from the smartmontools website and stored them at + + /var/lib/smartmontools/drivedb/drivedb.h + + This tool did not download the definitions in a secure manner and + so the feature has been removed in this version. Future drive DB + updates will be propagated via normal Debian package updates, + including backports. + + If you already have a drivedb.h file at that location, smartctl + will continue to use it. + + -- Dmitry Smirnov <onlyjob@debian.org> Thu, 10 Oct 2019 12:39:16 +1100 diff --git a/debian/README.Debian b/debian/README.Debian new file mode 100644 index 0000000..c1c06a8 --- /dev/null +++ b/debian/README.Debian @@ -0,0 +1,54 @@ +smartmontools for Debian +------------------------ + +Disabling the service +--------------------- + +By default smartmontools service is starting automatically. + +To disable the service + + on Systemd: + + sudo systemctl disable smartmontools.service + + on SysV: + + sudo update-rc.d smartmontools disable + + +update-smart-drivedb +-------------------- + +There were number of tickets discussing removal of "update-smart-drivedb" +utility (#894534, #824795, #804299, #85404). Maintainer's position is to +provide this utility. If admin (i.e. root) decides to service they system +then they can download drivedb manually using browser or a download +utility. Upstream provides "update-smart-drivedb" as a _glove_ to protect +admin from mistakes and since 7.0 script uses GPG to ensure integrity of +the downloaded database. Maintainer assumes that admins understand risks of +using "update-smart-drivedb" utility and that updating drivedb is better to +be done with this utility rather than without it. + +Maintainer advises to update drivedb _only when necessary_. + + +Notes +----- + +Don't use enable_smart for any disk monitored by smartd, this is likely to +cause problems, especially for SATA (see e.g. +http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=365027). + +Package Maintainers and system administrators can put scripts to be run +when smartd detects an error into /etc/smartmontools/run.d. These +scripts will be run by smartd-runner using run-parts(8). The script will +receive the filename of the file containing the errormessage as first +parameter. See /etc/smartmontools/run.d/10mail for an example. + +Upstream recommends running short self tests every day and long self tests once +per week. + +Please read http://www.smartmontools.org/wiki/Warnings + + -- Guido Guenther <agx@sigxcpu.org>, Wen, 03 May 2006 21:47:00 +0000 diff --git a/debian/badblockhowto.html b/debian/badblockhowto.html new file mode 100644 index 0000000..52ea120 --- /dev/null +++ b/debian/badblockhowto.html @@ -0,0 +1,1044 @@ +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Bad block HOWTO for smartmontools</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><meta name="description" content="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."></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article" title="Bad block HOWTO for smartmontools"><div class="titlepage"><div><div><h2 class="title"><a name="index"></a>Bad block HOWTO for smartmontools</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bruce</span> <span class="surname">Allen</span></h3><div class="affiliation"><div class="address"><p><br> + <code class="email"><<a class="email" href="mailto:smartmontools-support@lists.sourceforge.net">smartmontools-support@lists.sourceforge.net</a>></code><br> + </p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Douglas</span> <span class="surname">Gilbert</span></h3><div class="affiliation"><div class="address"><p><br> + <code class="email"><<a class="email" href="mailto:smartmontools-support@lists.sourceforge.net">smartmontools-support@lists.sourceforge.net</a>></code><br> + </p></div></div></div></div><div><p class="copyright">Copyright © 2004, 2005, 2006, 2007 Bruce Allen</p></div><div><div class="legalnotice" title="Legal Notice"><a name="id2541562"></a><p> + 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. + </p><p> + For an online copy of the license see + <a class="ulink" href="http://www.fsf.org/copyleft/fdl.html" target="_top"> + <code class="literal">www.fsf.org/copyleft/fdl.html</code></a>. + </p></div></div><div><p class="pubdate">2007-01-23</p></div><div><div class="revhistory"><table border="1" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 1.1</td><td align="left">2007-01-23</td><td align="left">dpg</td></tr><tr><td align="left" colspan="3"> + add sections on ReiserFS and partition table damage + </td></tr><tr><td align="left">Revision 1.0</td><td align="left">2006-11-14</td><td align="left">dpg</td></tr><tr><td align="left" colspan="3"> + merge BadBlockHowTo.txt and BadBlockSCSIHowTo.txt + </td></tr></table></div></div><div><div class="abstract" title="Abstract"><p class="title"><b>Abstract</b></p><p> + 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. + </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#intro">Introduction</a></span></dt><dt><span class="sect1"><a href="#rfile">Repairs in a file system</a></span></dt><dd><dl><dt><span class="sect2"><a href="#e2_example1">ext2/ext3 first example</a></span></dt><dt><span class="sect2"><a href="#e2_example2">ext2/ext3 second example</a></span></dt><dt><span class="sect2"><a href="#unassigned">Unassigned sectors</a></span></dt><dt><span class="sect2"><a href="#reiserfs_ex">ReiserFS example</a></span></dt></dl></dd><dt><span class="sect1"><a href="#sdisk">Repairs at the disk level</a></span></dt><dd><dl><dt><span class="sect2"><a href="#partition">Partition table problems</a></span></dt><dt><span class="sect2"><a href="#lvm">LVM repairs</a></span></dt><dt><span class="sect2"><a href="#bb">Bad block reassignment</a></span></dt></dl></dd></dl></div><div class="sect1" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="intro"></a>Introduction</h2></div></div></div><p> +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. +</p><p> +Can smartmontools help? As the <acronym class="acronym">SMART</acronym> acronym +<sup>[<a name="id2506421" href="#ftn.id2506421" class="footnote">1</a>]</sup> +suggests, the <span class="command"><strong>smartctl</strong></span> command and the +<span class="command"><strong>smartd</strong></span> 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. +</p><p> +When a bad block is reported 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 number of replacement files that are retrieved from +some backup store. This approach requires knowledge of the file system +involved and this document uses the Linux ext2/ext3 and ReiserFS 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 causing a momentary blank into a 1 +second pause (while the disk retries the faulty sector, often accompanied +by a telltale clicking sound). +</p><p> +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 on this low level approach. +</p></div><div class="sect1" title="Repairs in a file system"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="rfile"></a>Repairs in a file system</h2></div></div></div><p> +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/ext3 or ReiserFS file system. The +various Linux commands shown have man pages and the reader is encouraged +to examine these. Of note is the <span class="command"><strong>dd</strong></span> command which is +often used in repair work +<sup>[<a name="id2506498" href="#ftn.id2506498" class="footnote">2</a>]</sup> +and has a unique command line syntax. +</p><p> +The authors would like to thank Sergey Vlasov, Theodore Ts'o, +Michael Bendzick, and others for explaining this approach. The authors would +like to add text showing how to do this for other file systems, in +particular XFS, and JFS: please email if you can provide this +information. +</p><div class="sect2" title="ext2/ext3 first example"><div class="titlepage"><div><div><h3 class="title"><a name="e2_example1"></a>ext2/ext3 first example</h3></div></div></div><p> +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. +</p><p> +</p><pre class="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 +</pre><p> +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: +</p><pre class="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 +</pre><p> +</p><p> +First Step: We need to locate the partition on which this sector of +the disk lives: +</p><pre class="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 +</pre><p> + +The partition <code class="filename">/dev/hda3</code> starts at LBA 5269320 and +extends past the 'problem' LBA. The 'problem' LBA is offset +23421417 - 5269320 = 18152097 sectors into the partition +<code class="filename">/dev/hda3</code>. +</p><p> +To verify the type of the file system and the mount point, look in +<code class="filename">/etc/fstab</code>: +</p><pre class="programlisting"> +root]# grep hda3 /etc/fstab +/dev/hda3 /data ext2 defaults 1 2 +</pre><p> +You can see that this is an ext2 file system, mounted at +<code class="filename">/data</code>. +</p><p> +Second Step: we need to find the block size of the file system +(normally 4096 bytes for ext2): +</p><pre class="programlisting"> +root]# tune2fs -l /dev/hda3 | grep Block +Block count: 29119820 +Block size: 4096 +</pre><p> +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: +</p><pre class="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. +</pre><p> + +In our example, L=23421417, S=5269320, and B=4096. Hence the +'problem' LBA is in block number +</p><pre class="programlisting"> + b = (int)18152097*512/4096 = (int)2269012.125 +so b=2269012. +</pre><p> +</p><p> +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. +</p><p> +Fourth Step: we use debugfs to locate the inode stored in this block, +and the file that contains that inode: +</p><pre class="programlisting"> +root]# debugfs +debugfs 1.32 (09-Nov-2002) +debugfs: open /dev/hda3 +debugfs: testb 2269012 +Block 2269012 not in use +</pre><p> + +If the block is not in use, as in the above example, then you can skip +the rest of this step and go ahead to Step Five. +</p><p> +If, on the other hand, the block is in use, we want to identify +the file that uses it: +</p><pre class="programlisting"> +debugfs: testb 2269012 +Block 2269012 marked in use +debugfs: icheck 2269012 +Block Inode number +2269012 41032 +debugfs: ncheck 41032 +Inode Pathname +41032 /S1/R/H/714197568-714203359/H-R-714202192-16.gwf +</pre><p> +In this example, you can see that the problematic file (with the mount +point included in the path) is: +<code class="filename">/data/S1/R/H/714197568-714203359/H-R-714202192-16.gwf</code> +</p><p> +When we are working with an ext3 file system, it may happen that the +affected file is the journal itself. Generally, if this is the case, +the inode number will be very small. In any case, debugfs will not +be able to get the file name: +</p><pre class="programlisting"> +debugfs: testb 2269012 +Block 2269012 marked in use +debugfs: icheck 2269012 +Block Inode number +2269012 8 +debugfs: ncheck 8 +Inode Pathname +debugfs: +</pre><p> +</p><p> +To get around this situation, we can remove the journal altogether: +</p><pre class="programlisting"> +tune2fs -O ^has_journal /dev/hda3 +</pre><p> + +and then start again with Step Four: we should see this time that the +wrong block is not in use any more. If we removed the journal file, at +the end of the whole procedure we should remember to rebuild it: +</p><pre class="programlisting"> +tune2fs -j /dev/hda3 +</pre><p> +</p><p> +Fifth Step +<span class="emphasis"><em>NOTE:</em></span> This last step will <span class="emphasis"><em>permanently + +</em></span> and irretrievably <span class="emphasis"><em>destroy</em></span> the contents +of the file system block that is damaged: if the block was allocated to +a file, some of the data that is in this file is going to be overwritten +with zeros. You will not be able to recover that data unless you can +replace the file with a fresh or correct version. +</p><p> +To force the disk to reallocate this bad block we'll write zeros to +the bad block, and sync the disk: +</p><pre class="programlisting"> +root]# dd if=/dev/zero of=/dev/hda3 bs=4096 count=1 seek=2269012 +root]# sync +</pre><p> +</p><p> +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: +</p><pre class="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 +</pre><p> + +Note: for some disks it may be necessary to update the SMART Attribute values by using +<span class="command"><strong>smartctl -t offline /dev/hda</strong></span> +</p><p> +We have corrected the first errored block. If more than one blocks +were errored, we should repeat all the steps for the subsequent ones. +After we do that, the disk will pass its self-tests again: + +</p><pre class="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 - +</pre><p> +</p><p> +and no longer shows any offline uncorrectable sectors: + +</p><pre class="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 +</pre><p> +</p></div><div class="sect2" title="ext2/ext3 second example"><div class="titlepage"><div><div><h3 class="title"><a name="e2_example2"></a>ext2/ext3 second example</h3></div></div></div><p> +On this drive, the first sign of trouble was this email from smartd: +</p><pre class="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 +</pre><p> +</p><p> +Running <span class="command"><strong>smartctl -a /dev/hda</strong></span> confirmed the problem: + +</p><pre class="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 +</pre><p> +</p><p> +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. +</p><p> +The device also shows errors in the SMART error log: +</p><pre class="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 +</pre><p> +</p><p> +Signs of trouble at this LBA may also be found in SYSLOG: +</p><pre class="programlisting"> +[root]# grep LBA /var/log/messages | awk '{print $12}' | sort | uniq + LBAsect=35495748 + LBAsect=35495750 +</pre><p> +</p><p> +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: +</p><pre class="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 + +<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> +</pre><p> +</p><p> +which shows that the seventeen sectors 35495735-35495751 (inclusive) +are not readable. +</p><p> +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 +<code class="filename">/dev/hda3</code>. So we have: +</p><pre class="programlisting"> + L=35495735 to 35495751 + S=5269320 + B=4096 +</pre><p> +so that b=3778301 to 3778303 are the three bad blocks in the file +system. + +</p><pre class="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 +</pre><p> +Note that the first few steps of this procedure could also be done +with a single command, which is very helpful if there are many bad +blocks (thanks to Danie Marais for pointing this out): +</p><pre class="programlisting"> +debugfs: icheck 3778301 3778302 3778303 +</pre><p> +</p><p> +And finally, just to confirm that this is really the damaged file: +</p><p> +</p><pre class="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 +</pre><p> +</p><p> +Finally we force the disk to reallocate the three bad blocks: +</p><pre class="programlisting"> +[root]# dd if=/dev/zero of=/dev/hda3 bs=4096 count=3 seek=3778301 +[root]# sync +</pre><p> +</p><p> +We could also probably use: +</p><pre class="programlisting"> +[root]# dd if=/dev/zero of=/dev/hda bs=512 count=17 seek=35495735 +</pre><p> +</p><p> +At this point we now have: +</p><pre class="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 +</pre><p> +</p><p> +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.. +</p><p> +A device self test: +</p><pre class="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 +</pre><p> +</p></div><div class="sect2" title="Unassigned sectors"><div class="titlepage"><div><div><h3 class="title"><a name="unassigned"></a>Unassigned sectors</h3></div></div></div><p> +This section was written by Kay Diederichs. Even though this section +assumes Linux and the ext2/ext3 file system, the strategy should be +more generally applicable. +</p><p> +I read your badblocks-howto at and greatly +benefited from it. One thing that's (maybe) missing is that often the +<span class="command"><strong>smartctl -t long</strong></span> scan finds a bad sector which is +<span class="emphasis"><em> not</em></span> 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 ... +</p><p> +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. +</p><pre class="programlisting"> + dd if=/dev/zero of=/some/mount/point bs=4k +</pre><p> +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 <span class="command"><strong>smartctl -a</strong></span> 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. +</p></div><div class="sect2" title="ReiserFS example"><div class="titlepage"><div><div><h3 class="title"><a name="reiserfs_ex"></a>ReiserFS example</h3></div></div></div><p> +This section was written by Joachim Jautz with additions from Manfred +Schwarb. +</p><p> +The following problems were reported during a scheduled test: +</p><pre class="programlisting"> +smartd[575]: Device: /dev/hda, starting scheduled Offline Immediate Test. +[... 1 hour later ...] +smartd[575]: Device: /dev/hda, 1 Currently unreadable (pending) sectors +smartd[575]: Device: /dev/hda, 1 Offline uncorrectable sectors +</pre><p> +</p><p> +[Step 0] The SMART selftest/error log +(see <span class="command"><strong>smartctl -l selftest</strong></span>) indicated there was a problem +with block address (i.e. the 512 byte sector at) 58656333. The partition +table (e.g. see <span class="command"><strong>sfdisk -luS /dev/hda</strong></span> or +<span class="command"><strong>fdisk -ul /dev/hda</strong></span>) indicated that this block was in the +<code class="filename">/dev/hda3</code> partition which contained a ReiserFS file +system. That partition started at block address 54781650. +</p><p> +While doing the initial analysis it may also be useful to take a copy +of the disk attributes returned by <span class="command"><strong>smartctl -A /dev/hda</strong></span>. +Specifically the values associated with the "Reallocated_Sector_Ct" and +"Reallocated_Event_Count" attributes (for ATA disks, the grown list (GLIST) +length for SCSI disks). If these are incremented at the end of the procedure +it indicates that the disk has re-allocated one or more sectors. +</p><p> +[Step 1] Get the file system's block size: +</p><pre class="programlisting"> +# debugreiserfs /dev/hda3 | grep '^Blocksize' +Blocksize: 4096 +</pre><p> +</p><p> +[Step 2] Calculate the block number: +</p><pre class="programlisting"> +# echo "(58656333-54781650)*512/4096" | bc -l +484335.37500000000000000000 +</pre><p> +It is re-assuring that the calculated 4 KB damaged block address in +<code class="filename">/dev/hda3</code> is less than "Count of blocks on the +device" shown in the output of <span class="command"><strong>debugreiserfs</strong></span> shown above. +</p><p> +[Step 3] Try to get more info about this block => reading the block +fails as expected but at least we see now that it seems to be unused. +If we do not get the `Cannot read the block' error we should +check if our calculation in [Step 2] was correct ;) +</p><pre class="programlisting"> +# debugreiserfs -1 484335 /dev/hda3 +debugreiserfs 3.6.19 (2003 http://www.namesys.com) + +484335 is free in ondisk bitmap +The problem has occurred looks like a hardware problem. +</pre><p> +</p><p> +If you have bad blocks, we advise you to get a new hard drive, because +once you get one bad block that the disk drive internals cannot hide from +your sight, the chances of getting more are generally said to become +much higher (precise statistics are unknown to us), and this disk +drive is probably not expensive enough for you to risk your +time and data on it. If you don't want to follow that +advice then if you have just a few bad blocks, try writing to the +bad blocks and see if the drive remaps the bad blocks (that means +it takes a block it has in reserve and allocates it for use for +of that block number). If it cannot remap the block, use +<span class="command"><strong>badblock</strong></span> option (-B) with reiserfs utils to handle +this block correctly. +</p><pre class="programlisting"> +bread: Cannot read the block (484335): (Input/output error). + +Aborted +</pre><p> +So it looks like we have the right (i.e. faulty) block address. +</p><p> +[Step 4] Try then to find the affected file +<sup>[<a name="id2550815" href="#ftn.id2550815" class="footnote">3</a>]</sup>: +</p><pre class="programlisting"> +tar -cO /mydir | cat >/dev/null +</pre><p> +If you do not find any unreadable files, then the block may be free or +located in some metadata of the file system. +</p><p> +[Step 5] Try your luck: bang the affected block with +<span class="command"><strong>badblocks -n</strong></span> (non-destructive read-write mode, do unmount +first), if you are very lucky the failure is transient and you can provoke +reallocation +<sup>[<a name="id2550862" href="#ftn.id2550862" class="footnote">4</a>]</sup>: +</p><pre class="programlisting"> +# badblocks -b 4096 -p 3 -s -v -n /dev/hda3 `expr 484335 + 100` `expr 484335 - 100` +</pre><p> +<sup>[<a name="id2550876" href="#ftn.id2550876" class="footnote">5</a>]</sup> +</p><p> +check success with <span class="command"><strong>debugreiserfs -1 484335 /dev/hda3</strong></span>. +Otherwise: +</p><p> +[Step 6] Perform this step <span class="emphasis"><em>only</em></span> if Step 5 has failed +to fix the problem: overwrite that block to force reallocation: +</p><pre class="programlisting"> +# dd if=/dev/zero of=/dev/hda3 count=1 bs=4096 seek=484335 +1+0 records in +1+0 records out +4096 bytes transferred in 0.007770 seconds (527153 bytes/sec) +</pre><p> +</p><p> +[Step 7] If you can't rule out the bad block being in metadata, do +a file system check: +</p><pre class="programlisting"> +reiserfsck --check +</pre><p> +This could take a long time so you probably better go for lunch ... +</p><p> +[Step 8] Proceed as stated earlier. For example, sync disk and run a long +selftest that should succeed now. +</p></div></div><div class="sect1" title="Repairs at the disk level"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sdisk"></a>Repairs at the disk level</h2></div></div></div><p> +This section first looks at a damaged partition table. Then it ignores +the upper level impact of a bad block and just repairs the underlying +sector so that defective sector will not cause problems in the future. +</p><div class="sect2" title="Partition table problems"><div class="titlepage"><div><div><h3 class="title"><a name="partition"></a>Partition table problems</h3></div></div></div><p> +Some software failures can lead to zeroes or random data being written +on the first block of a disk. For disks that use a DOS-based partitioning +scheme this will overwrite the partition table which is found at the +end of the first block. This is a single point of failure so after the +damage tools like <span class="command"><strong>fdisk</strong></span> have no alternate data to use +so they report no partitions or a damaged partition table. +</p><p> +One utility that may help is +<a class="ulink" href="http://www.cgsecurity.org/wiki/TestDisk" target="_top"> +<code class="literal">testdisk</code></a> which can scan a disk looking for +partitions and recreate a partition table if requested. +<sup>[<a name="id2550980" href="#ftn.id2550980" class="footnote">6</a>]</sup> +</p><p> +Programs that create DOS partitions +often place the first partition at logical block address 63. In Linux +a loop back mount can be attempted at the appropriate offset of a disk +with a damaged partition table. This approach may involve placing the +disk with the damaged partition table in a working computer or perhaps +an external USB enclosure. Assuming the disk with the damaged partition +is <code class="filename">/dev/hdb</code>. Then the following read-only loop back +mount could be tried: +</p><pre class="programlisting"> +# mount -r /dev/hdb -o loop,offset=32256 /mnt +</pre><p> +The offset is in bytes so the number given is (63 * 512). If the file +system cannot be identified then a '-t <fs_type>' +may be needed (although this is not a good sign). If this mount is +successful, a backup procedure is advised. +</p><p> +Only the primary DOS partitions are recorded in the first block of +a disk. The extended DOS partition table is placed elsewhere on +a disk. Again there is only one copy of it so it represents another +single point of failure. All DOS partition information can be +read in a form that can be used to recreate the tables with the +<span class="command"><strong>sfdisk</strong></span> command. Obviously this needs to be done +beforehand and the file put on other media. Here is how to fetch the +partition table information: +</p><pre class="programlisting"> +# sfdisk -dx /dev/hda > my_disk_partition_info.txt +</pre><p> +Then <code class="filename">my_disk_partition_info.txt</code> should be placed on +other media. If disaster strikes, then the disk with the damaged partition +table(s) can be placed in a working system, let us say the damaged disk is +now at <code class="filename">/dev/hdc</code>, and the following command restores +the partition table(s): +</p><pre class="programlisting"> +# sfdisk -x -O part_block_prior.img /dev/hdc < my_disk_partition_info.txt +</pre><p> +Since the above command is potentially destructive it takes a copy of the +block(s) holding the partition table(s) and puts it in +<code class="filename">part_block_prior.img</code> prior to any changes. Then it +changes the partition tables as indicated by +<code class="filename">my_disk_partition_info.txt</code>. For what it is worth the +author did test this on his system! +<sup>[<a name="id2551099" href="#ftn.id2551099" class="footnote">7</a>]</sup> +</p><p> +For creating, destroying, resizing, checking and copying partitions, and +the file systems on them, GNU's +<a class="ulink" href="http://www.gnu.org/software/parted" target="_top"> +<code class="literal">parted</code></a> is worth examining. +The <a class="ulink" href="http://www.tldp.org/HOWTO/Large-Disk-HOWTO.html" target="_top"> +<code class="literal">Large Disk HOWTO</code></a> is also a useful resource. +</p></div><div class="sect2" title="LVM repairs"><div class="titlepage"><div><div><h3 class="title"><a name="lvm"></a>LVM repairs</h3></div></div></div><p> +This section was written by Frederic BOITEUX. It was titled: "HOW TO +LOCATE AND REPAIR BAD BLOCKS ON AN LVM VOLUME". +</p><p> +Smartd reports an error in a short test : +</p><pre class="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 +</pre><p> +So the disk has a bad block located in LBA block 37383668 +</p><p> +In which physical partition is the bad block ? +</p><pre class="programlisting"> +# sfdisk -luS /dev/hdb # or 'fdisk -ul /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 +</pre><p> + +It's in the <code class="filename">/dev/hdb3</code> partition, a LVM2 partition. +From the LVM2 partition beginning, the bad block has an offset of +</p><pre class="programlisting"> +(37383668 - 1188810) = 36194858 +</pre><p> +</p><p> +We have to find in which LVM2 logical partition the block belongs to. +</p><p> +In which logical partition is the bad block ? +</p><p> +<span class="emphasis"><em>IMPORTANT</em></span> : 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 ! +</p><p> +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. +</p><p> +The 'pvdisplay' command gives the size of the PE (in KB) of the +LVM partition : +</p><pre class="programlisting"> +# part=/dev/hdb3 ; pvdisplay -c $part | awk -F: '{print $8}' +4096 +</pre><p> +</p><p> +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. +</p><p> +To find the offset from the beginning of the physical partition is a +bit more difficult : if you have a recent LVM2 version, try : +</p><pre class="programlisting"> +# pvs -o+pe_start $part +</pre><p> +</p><p> +Either, you can look in /etc/lvm/backup : +</p><pre class="programlisting"> +# grep pe_start $(grep -l $part /etc/lvm/backup/*) + pe_start = 384 +</pre><p> +</p><p> +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) = +</p><pre class="programlisting"> +36194858 / 8192 = 4418.3176 +</pre><p> +</p><p> +So we have to find in which LVM2 logical partition is used the PE +number 4418 (count starts from 0) : +</p><pre class="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 +</pre><p> +</p><p> +So the PE #4418 is in the <code class="filename">/dev/WDC80Go/ext1</code> +LVM logical partition. +</p><p> +Size of logical block of file system on <code class="filename">/dev/WDC80Go/ext1 +</code> : +</p><p> +It's a ext3 fs, so I get it like this : +</p><pre class="programlisting"> +# dumpe2fs /dev/WDC80Go/ext1 | grep 'Block size' +dumpe2fs 1.37 (21-Mar-2005) +Block size: 4096 +</pre><p> +</p><p> +bad block number for the file system : +</p><p> +The logical partition begins on PE 3072 : +</p><pre class="programlisting"> + (# PE's start of partition * sizeof(PE)) + parttion offset[pe_start] = + (3072 * 8192) + 384 = 25166208 +</pre><p> +512b block of the physical partition, so the bad block number for the +file system is : +</p><pre class="programlisting"> +(36194858 - 25166208) / (sizeof(fs block) / 512) += 11028650 / (4096 / 512) = 1378581.25 +</pre><p> +</p><p> +Test of the fs bad block : +</p><pre class="programlisting"> +dd if=/dev/WDC80Go/ext1 of=block1378581 bs=4096 count=1 skip=1378581 +</pre><p> +</p><p> +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 +renounce ! +</p><p> +Search / correction follows the same scheme as for simple +partitions : +</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> +find possible impacted files with debugfs (icheck <fs block nb>, +then ncheck <icheck nb>). +</p></li><li class="listitem"><p> +reallocate bad block writing zeros in it, *using the fs block size* : +</p></li></ul></div><p> +</p><p> +</p><pre class="programlisting"> +dd if=/dev/zero of=/dev/WDC80Go/ext1 count=1 bs=4096 seek=1378581 +</pre><p> +</p><p> +Et voilà ! +</p></div><div class="sect2" title="Bad block reassignment"><div class="titlepage"><div><div><h3 class="title"><a name="bb"></a>Bad block reassignment</h3></div></div></div><p> +The SCSI disk command set and associated disk architecture are assumed +in this section. 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. +</p><p> +The terms <span class="emphasis"><em>block</em></span> and <span class="emphasis"><em>sector</em></span> are +used interchangeably, although block tends to get used in higher level or +more abstract contexts such as a <span class="emphasis"><em>logical block</em></span>. +</p><p> +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. +</p><p> +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. +</p><p> +Once a SCSI disk format has completed successfully, other problems +may appear over time. These fall into two categories: +</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> +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. +</p></li><li class="listitem"><p> +unrecoverable: try as it may, the disk logic and ECC algorithms +cannot recover the data. This is often reported as a +<span class="emphasis"><em>medium error</em></span>. +</p></li></ul></div><p> +</p><p> +Other things can go wrong, typically associated with the transport and +they will be reported using a term other than +<span class="emphasis"><em>medium error</em></span>. 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. +</p><p> +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 +<sup>[<a name="id2551516" href="#ftn.id2551516" class="footnote">8</a>]</sup> +? +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 +<sup>[<a name="id2551535" href="#ftn.id2551535" class="footnote">9</a>]</sup> +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. +</p><p> +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. +</p><p> +Unrecoverable errors will cause a <span class="emphasis"><em>medium error</em></span> 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 <a class="xref" href="#rfile" title="Repairs in a file system">the section called “Repairs in a file system”</a>. +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. +</p><p> +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 authors are 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 <span class="command"><strong>smartctl</strong></span> 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. +</p><p> +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. +</p><div class="sect3" title="Example"><div class="titlepage"><div><div><h4 class="title"><a name="sexample"></a>Example</h4></div></div></div><p> +Given a "bad block", it still may be useful to look at the +<span class="command"><strong>fdisk</strong></span> command (if the disk has multiple partitions) +to find out which partition is involved, then use +<span class="command"><strong>debugfs</strong></span> (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 <a class="xref" href="#rfile" title="Repairs in a file system">the section called “Repairs in a file system”</a>. +</p><p> +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 <span class="command"><strong>sg_reassign</strong></span> utility in the sg3_utils +package can be used. Also found in that package is +<span class="command"><strong>sg_verify</strong></span> which can be used to check that a block is +readable. +</p><p> +Assume that logical block address 1193046 (which is 123456 in hex) is +corrupt +<sup>[<a name="id2551756" href="#ftn.id2551756" class="footnote">10</a>]</sup> +on the disk at <code class="filename">/dev/sdb</code>. A long selftest command like +<span class="command"><strong>smartctl -t long /dev/sdb</strong></span> may result in log results +like this: +</p><pre class="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 - [- - -] +</pre><p> +</p><p> +The <span class="command"><strong>sg_verify</strong></span> utility can be used to confirm that there +is a problem at that address: +</p><pre class="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 +</pre><p> +</p><p> +Now the GLIST length is checked before the block reassignment: +</p><pre class="programlisting"> +# sg_reassign --grown /dev/sdb +>> Elements in grown defect list: 0 +</pre><p> +</p><p> +And now for the actual reassignment followed by another check of the GLIST +length: +</p><pre class="programlisting"> +# sg_reassign --address=1193046 /dev/sdb + +# sg_reassign --grown /dev/sdb +>> Elements in grown defect list: 1 +</pre><p> +</p><p> +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 <span class="command"><strong>sg_reassign</strong></span> utility can also do bulk +reassigns, see <span class="command"><strong>man sg_reassign</strong></span> for more information. +</p><p> +The <span class="command"><strong>dd</strong></span> command could be used to read the contents of +the "new" block: +</p><pre class="programlisting"> +# dd if=/dev/sdb iflag=direct skip=1193046 of=blk.img bs=512 count=1 +</pre><p> +</p><p> +and a hex editor +<sup>[<a name="id2551874" href="#ftn.id2551874" class="footnote">11</a>]</sup> +used to view and potentially change the +<code class="filename">blk.img</code> file. An altered <code class="filename">blk.img</code> +file (or <code class="filename">/dev/zero</code>) could be written back with: +</p><pre class="programlisting"> +# dd if=blk.img of=/dev/sdb seek=1193046 oflag=direct bs=512 count=1 +</pre><p> +</p><p> +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. +</p><p> +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 +<span class="command"><strong>sg_format</strong></span> in the sg3_utils package)) and re-use the +disk later (not unlike the way a replacement disk from a manufacturer +might be used). +</p><p> +$Id: badblockhowto.xml 2873 2009-08-11 21:46:20Z dipohl $ +</p></div></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2506421" href="#id2506421" class="para">1</a>] </sup> +Self-Monitoring, Analysis and Reporting Technology -> SMART +</p></div><div class="footnote"><p><sup>[<a name="ftn.id2506498" href="#id2506498" class="para">2</a>] </sup> +Starting with GNU coreutils release 5.3.0, the <span class="command"><strong>dd</strong></span> +command in Linux includes the options 'iflag=direct' and 'oflag=direct'. +Using these with the <span class="command"><strong>dd</strong></span> 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 <span class="command"><strong>dd --help</strong></span> to see if your +version of dd supports these options. If not, the latest code for dd +can be found at <a class="ulink" href="http://alpha.gnu.org/gnu/coreutils" target="_top"> +<code class="literal">alpha.gnu.org/gnu/coreutils</code></a>. +</p></div><div class="footnote"><p><sup>[<a name="ftn.id2550815" href="#id2550815" class="para">3</a>] </sup> +Do not use <span class="command"><strong>tar -c -f /dev/null</strong></span> or +<span class="command"><strong>tar -cO /mydir >/dev/null</strong></span>. GNU tar does not +actually read the files if <code class="filename">/dev/null</code> is used as +archive path or as standard output, see <span class="command"><strong>info tar</strong></span>. +</p></div><div class="footnote"><p><sup>[<a name="ftn.id2550862" href="#id2550862" class="para">4</a>] </sup> +Important: set blocksize range is arbitrary, but do not only test a single +block, as bad blocks are often social. Not too large as this test probably +has not 0% risk. +</p></div><div class="footnote"><p><sup>[<a name="ftn.id2550876" href="#id2550876" class="para">5</a>] </sup> +The rather awkward `expr 484335 + 100` (note the back quotes) can be replaced +with $((484335+100)) if the bash shell is being used. Similarly the last +argument can become $((484335-100)) . +</p></div><div class="footnote"><p><sup>[<a name="ftn.id2550980" href="#id2550980" class="para">6</a>] </sup> +<span class="command"><strong>testdisk</strong></span> scans the media for the beginning of file +systems that it recognizes. It can be tricked by data that looks +like the beginning of a file system or an old file system from a +previous partitioning of the media (disk). So care should be taken. +Note that file systems should not overlap apart from the fact that +extended partitions lie wholly within a extended partition table +allocation. Also if the root partition of a Linux/Unix installation +can be found then the <code class="filename">/etc/fstab</code> file is a useful +resource for finding the partition numbers of other partitions. +</p></div><div class="footnote"><p><sup>[<a name="ftn.id2551099" href="#id2551099" class="para">7</a>] </sup> +Thanks to Manfred Schwarb for the information about storing partition +table(s) beforehand. +</p></div><div class="footnote"><p><sup>[<a name="ftn.id2551516" href="#id2551516" class="para">8</a>] </sup> +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 <span class="command"><strong>smartctl -l error</strong></span> output. +</p></div><div class="footnote"><p><sup>[<a name="ftn.id2551535" href="#id2551535" class="para">9</a>] </sup> +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. +</p></div><div class="footnote"><p><sup>[<a name="ftn.id2551756" href="#id2551756" class="para">10</a>] </sup> +In this case the corruption was manufactured by using the WRITE LONG +SCSI command. See <span class="command"><strong>sg_write_long</strong></span> in sg3_utils. +</p></div><div class="footnote"><p><sup>[<a name="ftn.id2551874" href="#id2551874" class="para">11</a>] </sup> +Most window managers have a handy calculator that will do hex to +decimal conversions. More work may be needed at the file system level, +</p></div></div></div></body></html> diff --git a/debian/changelog b/debian/changelog new file mode 100644 index 0000000..7182503 --- /dev/null +++ b/debian/changelog @@ -0,0 +1,995 @@ +smartmontools (7.4-2) unstable; urgency=medium + + [ Guillem Jover ] + * Hurd portability and dpkg arch fixes (Closes: #1056745). + + [ Dmitry Smirnov ] + * postinst: check if "update-smart-drivedb" is executable and fall + back to "cp" if necessary. (#1056736) + * rules: corrected "systemdsystemunitdir" path (Closes: #1056940). + + -- Dmitry Smirnov <onlyjob@debian.org> Thu, 30 Nov 2023 18:30:49 +1100 + +smartmontools (7.4-1) unstable; urgency=medium + + * New upstream release. + + fixed service startup without devices (Closes: #1029210). + + fixed "increasing number of Error Log entries" (Closes: #1041745). + + updated "pkg.m4" that fixed second build (Closes: #1048143). + * Depends: lsb-base --> sysvinit-utils. + * Postinst: install "drivedb.h" using "update-smart-drivedb --install"; + invoke configure script with "--with-drivedbinstdir" (Closes: #1006019). + + [ Debian Janitor ] + * Bump debhelper from old 12 to 13. + * Set upstream metadata fields: Archive, Bug-Database, Repository. + + [ Samuel Thibault ] + * d/control: Generalize hurd-i386 into hurd-any. + + -- Dmitry Smirnov <onlyjob@debian.org> Sat, 25 Nov 2023 11:15:24 +1100 + +smartmontools (7.3-1) unstable; urgency=medium + + * New upstream release. + * Standards-Version: 4.6.0. + * Updated Homepage URL (Closes: #979547). + Thanks, Paul Wise. + * Removed "default_never-quit.patch" (Closes: #1006630). + Thanks, Christian Franke. + + -- Dmitry Smirnov <onlyjob@debian.org> Wed, 27 Apr 2022 15:39:01 +1000 + +smartmontools (7.2-1) unstable; urgency=medium + + * New upstream release. + + fixed failure with Micron 2200S NVME (Closes: #947803). + + service: removed "StandardOutput=syslog" (Closes: #969048, #968168). + * smartd-runner: replaced "tmpfile" with "mktemp" (Closes: #969667) + Thanks, Bob Proulx. + * rules: don't set INSTALL_PROGRAM and CFLAGS optimisation flags + (Closes: #968526). + Thanks, Simon McVittie. + * Install "drivedb.h" to "/usr/share/smartmontools" and copy it into + "/var/lib/smartmontools/drivedb/" in postinst (Closes: #976696). + Thanks, Paul Wise. + * Removed ancient workaround from postinst. + * Standards-Version: 4.5.0 + * Rules-Requires-Root: no + + -- Dmitry Smirnov <onlyjob@debian.org> Thu, 07 Jan 2021 20:47:11 +1100 + +smartmontools (7.1-1) unstable; urgency=medium + + * New upstream release. + * rules: removed get-orig-source target. + * New patch to start daemon even on diskless system (Closes: #862908). + + -- Dmitry Smirnov <onlyjob@debian.org> Sat, 04 Jan 2020 19:33:20 +1100 + +smartmontools (7.0-2) unstable; urgency=medium + + * SysV: don't (re)start daemon during upgrade (Closes: #942118). + * rules/configure: detect systemd automatically. + * Build-Depends: + = libsystemd-dev [!kfreebsd-any] + + -- Dmitry Smirnov <onlyjob@debian.org> Fri, 11 Oct 2019 14:05:51 +1100 + +smartmontools (7.0-1) unstable; urgency=medium + + [ Jean-Michel Vourgère ] + * Update README.Debian. (Closes: #878752). + + [ Dmitry Smirnov ] + * New upstream release (Closes: #918535). + + NVMe devices support (Closes: #911280). + + no longer fails on nvme/Optane (Closes: #924892). + + Type=notify for systemd service (Closes: #865912). + * Re-introduced "update-smart-drivedb", now with GPG validation; + (Closes: #894534, #824795, #804299, #854043, #824149). + * Removed obsolete "10powersave-notify" (Closes: #893646). + * Added note how to disable the service to README.Debian. + No longer use "start_smartd" in defaults. (Closes: #907736, #767569). + * Install smartd.service alias (Closes: #808987). + * DH & compat to version 12; rules to DH sequence. + * Pre-Depends: ${misc:Pre-Depends} + * Standards-Version: 4.4.1. + * In-depth copyright documentation. + * Build-Depends: + * automake1.11 --> automake (Closes: #865202). + + pkg-config + + libsystemd-dev + * Demoted MTA from Recommends to Suggests (Closes: #898121). + * Suggests += "curl | wget | lynx, gpg". + * Addressed some lintian warnings: + - maintainer-script-should-not-use-dpkg-maintscript-helper + - init.d-script-possible-missing-stop + * Added bug-presubj file with information about upstream bug tracker. + * watch: fixed and converted to v4; checking upstream signature. + * Replaced Giuseppe Iuculano as Maintainer by request of the MIA team + (Closes: #866838). + + -- Dmitry Smirnov <onlyjob@debian.org> Thu, 10 Oct 2019 12:39:16 +1100 + +smartmontools (6.6-1) unstable; urgency=medium + + [ Jonathan Dowland ] + * Update Vcs-* headers in control file: replace Alioth/anonscm URIs + with salsa.debian.org. + * new upstream version. Closes: #889033. + Patches refreshed: + - 61_cciss-doc.patch + Patches removed: + - 50_manpage_improvements.diff + - 3w-sas (merged by upstream) + - 60_remove-redhatism.diff (removed by upstream) + + [ SZ Lin (林上智) ] + Patches refreshed: + - 52_remove-pragma.diff + - 53_use-smartd-runner-by-default.diff + - 54_remove-Id-from-smartd.conf.diff + - 61_cciss-doc.patch + - 63_removable.patch + - kfreebsd.patch + - manpage.diff + - removesyslogtarget.patch + + [ Jonathan Dowland ] + * Bump debhelper dependency to 11, remove dh-systemd (deprecated) + in favour of dh_installsystemd + + -- Jonathan Dowland <jmtd@debian.org> Mon, 15 Oct 2018 21:03:35 +0100 + +smartmontools (6.5+svn4324-1) unstable; urgency=low + + * [a86ec89] Imported Upstream version 6.5+svn43204 (Closes: #831504) + + -- Giuseppe Iuculano <iuculano@debian.org> Sat, 30 Jul 2016 19:10:13 +0200 + +smartmontools (6.4+svn4214-1) unstable; urgency=medium + + [ Helmut Grohne ] + * Fix FTCBFS. (Closes: #794035) + + Pass --build and --host to configure + + [ Tobias Frost ] + * Import patch from Helmut (see above) + * Remove '/var/lib/smartmontools' on purge (Closes: #766145) + * Fixed postinst script: Version is only valid when configuring. + (Closes: #766146) + + [ Jonathan Dowland ] + * Portability improvements, thanks Robert Millan. Closes: #634506. + * Update debian/copyright to Format 1.0., resolve GPL-2/GPL-2+ + ambiguity. Closes: #777583. + * Get rid of update-smart-drivedb. Closes: #783317, #804299, #706909. + * Bump standards version (no further changes required) + * Enhance rules clean target to make repeated builds easier + * Stop installing duplicate/irrelevant docs (COPYING, changelog, INSTALL) + * add 'set -e' to postrm. + * Switch to xz for orig.tar compression and update get-orig-source rule. + * Stop passing explicit runlevels to dh_installinit. Closes: #732045. + * Remove duplicate use of dh_systemd_enable: The second one should have + been dh_systemd_start. Closes: #813102. + * Various manpage improvements. Thanks Bjarni Ingi Gislason. + Closes: #669053. + + -- Jonathan Dowland <jmtd@debian.org> Thu, 04 Feb 2016 23:21:58 +0000 + +smartmontools (6.4+svn4109-1) unstable; urgency=medium + + * New upstream version. Closes: #789721. + * Add myself to uploaders. + * refresh 54_remove-Id-from-smartd.conf.diff and 61_cciss-doc.patch + + -- Jonathan Dowland <jmtd@debian.org> Wed, 18 Nov 2015 19:52:41 +0000 + +smartmontools (6.3+svn4002-2) unstable; urgency=low + + * [12d5f9d] Correct maintscript syntax (Closes: #766178) + + -- Giuseppe Iuculano <iuculano@debian.org> Tue, 21 Oct 2014 13:30:40 +0200 + +smartmontools (6.3+svn4002-1) unstable; urgency=low + + * [03a62f0] Set EnvironmentFile=-/etc/default/smartmontools in smartd.service + (Closes: #764136) + * [59c55ae] Remove /etc/smartd_warning.sh (Closes: #765519) + * [1d06b80] Imported Upstream version 6.3+svn4002 + * [1aabc0a] Do not build-depends on hardening-wrapper, + instead use the new buildflags.mk file + + -- Giuseppe Iuculano <iuculano@debian.org> Fri, 17 Oct 2014 15:55:45 +0200 + +smartmontools (6.3+svn3990-1) unstable; urgency=low + + * [d2e702c] Imported Upstream version 6.3+svn3990 + - Support for TOSHIBA STOR.E Plus 2 TB (0x0480:0xa00a) (Closes: #734395) + * [901fe9c] Refreshed patches + * [9804b75] Included systemd service file. + Thanks to Michael Stapelberg (Closes: #639631, #757973, #762039) + * [a64e022] Remove the obsolete bug helper (Closes: #757975) + * [3478a98] moved smartd_warning.sh in + /usr/share/smartmontools/smard_warning.sh (Closes: #710815) + * [a5a9d5b] Removed source less os_solaris_ata.s (Closes: #729842) + * [fb337c9] Update to Standards-Version 3.9.5, no changes need + * [6a8e2b9] smartd.service.in: declaring After=syslog.target is unnecessary + by now because syslog is socket-activated and will therefore be started + when needed + + -- Giuseppe Iuculano <iuculano@debian.org> Sun, 05 Oct 2014 10:58:13 +0200 + +smartmontools (6.2+svn3841-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/control: Switch to automake1.11. (Closes: #724436) + + -- Eric Dorland <eric@debian.org> Sun, 16 Feb 2014 16:27:11 -0500 + +smartmontools (6.2+svn3841-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS on GNU/kFreeBSD. (Closes: #736660) + + -- Robert Millan <rmh@debian.org> Thu, 06 Feb 2014 13:48:48 +0100 + +smartmontools (6.2+svn3841-1) unstable; urgency=low + + * [3d17a85] Imported Upstream version 6.2+svn3841 + * [8251afb] Fix FTBFS[kfreebsd] + Thanks to Christoph Egger (Closes: #717567) + * [e57fafb] Refreshed patches + + -- Giuseppe Iuculano <iuculano@debian.org> Thu, 05 Sep 2013 14:53:36 +0200 + +smartmontools (6.1+svn3812-1) unstable; urgency=low + + * [ee38a43] Imported Upstream version 6.1+svn3812 (Closes: #691646) + - Support for WD MyBook Essential 0x1058:0x0910 (Closes: #633724) + - Added USB bridge to known IDs (Closes: #643928) + - Added support for Seagate Expansion Desk external (usb) disks + (Closes: #621411) + * [1855d63] Refreshed patches and removed patches applied upstream + * [d3fc9d1] Remove quilt from depends + * [841c1a8] CHANGELOG file has been renamed, install Changelog + * [3502e16] Updated VCS control fields + * [8f14e44] debian/rules: Provide build-arch and build-indep + * [0f1c16c] Harden smartmontools binaries + * [555346e] Bump to 3.9.4 standards version + * [5ae3fa9] Use /var/lib/smartmontools/drivedb for drivedb.h updates + (Closes: #706909) + * [c16ffdc] Create /var/lib/smartmontools/drivedb dir + * [79a3dc2] Trigger the removal of /etc/init.d/smartd when upgrading + (Closes: #684617, #704081) + * [a0a5725] Also remove /etc/init.d/smartd in preinst script + * [a26a490] Added man page for update-smart-drivedb. + Thanks to Hannes von Haugwitz (Closes: #708433) + + -- Giuseppe Iuculano <iuculano@debian.org> Sun, 02 Jun 2013 11:14:02 +0200 + +smartmontools (5.42+svn3561-3) unstable; urgency=high + + * [f10872d] Really fix FTBFS on kfreebsd. + Thanks to Petr Salinger (Closes: #677393) + + -- Giuseppe Iuculano <iuculano@debian.org> Mon, 16 Jul 2012 15:21:56 +0200 + +smartmontools (5.42+svn3561-2) unstable; urgency=high + + * [743e0f4] Fixed FTBFS in kfreebsd. + Thanks to Petr Salinger (Closes: #677393) + + -- Giuseppe Iuculano <iuculano@debian.org> Mon, 16 Jul 2012 12:06:15 +0200 + +smartmontools (5.42+svn3561-1) unstable; urgency=low + + * [f4e463d] Imported Upstream version 5.42+svn3561 + * [23f7a2f] Refreshed patches + * [16216c8] Fixed FTBFS on kfreebsd. + Thanks to Petr Salinger (Closes: #676142) + * [6652700] Fixed regression introduced in 10mail script (Closes: #649515) + * [fd647e5] Remove /etc/init.d/smartd (Closes: #677095) + + -- Giuseppe Iuculano <iuculano@debian.org> Wed, 20 Jun 2012 16:36:24 +0200 + +smartmontools (5.42+svn3539-1) unstable; urgency=low + + * [e165493] Imported Upstream version 5.42+svn3539 + (Closes: #668391, #608953) + * [9fcd449] Refreshed patches + * [65c801f] Do not install upstream init (Closes: #631075) + * [9a19418] Fixed check for /usr/bin/mail. + Thanks to Martin von Gagern (Closes: #649515) + + -- Giuseppe Iuculano <iuculano@debian.org> Sat, 12 May 2012 13:02:49 +0200 + +smartmontools (5.41+svn3365-1) unstable; urgency=low + + * [a7e8ffe] Imported Upstream version 5.41+svn3365 + * [471d14a] Refreshed patches, removed install.diff applied upstream + * [fae0ec9] Added a missing include for hurd-i386. + Thanks to Pino Toscano (Closes: #619208) + + -- Giuseppe Iuculano <iuculano@debian.org> Sun, 19 Jun 2011 17:28:10 +0200 + +smartmontools (5.40+svn3296-1) unstable; urgency=low + + * [cfbba5b] Imported Upstream version 5.40+svn3296 + - Intel X18-M/X25-M/X25-V G2 SSDs: Add firmware bug warning + (Closes: #581996) + - handles missing attributes and prints attributes of SandForce based SSDs + correctly (Closes: #601258) + - Added a note about smartctl is unable to print a warning if autosave is + disabled (Closes: 570892) + - Print help message if no option is specified (Closes: 435579) + - Only some of the controller specific parts of the code may still use the + old ioctl (LP: #658469) + - New drive database entry for F4EG (LP: #684809) + * [b5b85ba] Refreshed patches + * [2b7f0f1] Update to Standards-Version 3.9.1, no changes needed + * [3ed7206] debian/rules: remove make -C examplescripts + * [f8250f3] Pass exampledir in configure + * [0711e68] Install examples files and update-smart-drivedb (Closes: #607689) + (Closes: #593502) + * [f36e375] Do not install CHANGELOG COPYING INSTALL and initd files + * [a76819a] Re-enabled capability-dropping on armel (Closes: #552044) + + -- Giuseppe Iuculano <iuculano@debian.org> Sun, 20 Mar 2011 19:09:39 +0100 + +smartmontools (5.39.1+svn3124-2) unstable; urgency=low + + [ Florian Weimer ] + * [88b6d44] 3w-sas support (from upstream changeset r3128) (Closes: + #604016) + + -- Giuseppe Iuculano <iuculano@debian.org> Sun, 26 Dec 2010 12:26:16 +0100 + +smartmontools (5.39.1+svn3124-1) unstable; urgency=low + + * [1e46e09] Set state and attribute file directory to + /var/lib/smartmontools/ (Closes: #582158) + * [e20147c] Don't warn about being disabled unless verbose (Closes: #583386) + * [3390c07] Fixed example path in man pages (Closes: #588134) + * [e9583e0] Imported Upstream version 5.39.1+svn3124 + * [789e123] Refreshed patches + * [cbecf14] Bump to Standards-Version 3.9.0, no changes needed + + -- Giuseppe Iuculano <iuculano@debian.org> Tue, 13 Jul 2010 13:16:54 +0200 + +smartmontools (5.39.1+svn3077-1) unstable; urgency=low + + * [ffe62ea] Removed powersaved from Suggests (Closes: #570956) + * [7f0798e] Imported Upstream version 5.39.1+svn3077 (Closes: #575435) + * [b1b3452] Enabled drivedb, savestates, and attributelog + * [9f28fd4] Switch to dpkg-source 3.0 (quilt) format + * [52be6ce] Updated to Standards-Version 3.8.4, no changes needed + + -- Giuseppe Iuculano <iuculano@debian.org> Fri, 26 Mar 2010 22:01:58 +0100 + +smartmontools (5.39.1+svn3060-1) unstable; urgency=low + + * [a23d511] Imported Upstream version 5.39.1+svn3060 + - A regression caused by capabilities was fixed. (Closes: #564876) + * [89c9890] Removed patches merged in upstream + + -- Giuseppe Iuculano <iuculano@debian.org> Thu, 04 Feb 2010 08:16:37 +0100 + +smartmontools (5.39-3) unstable; urgency=low + + * [3d32778] Fixed quietmode option (Closes: #545784) + * [e66f4fd] Allow smartd 'DEVICESCAN -d sat' (Closes: #546566) + + -- Giuseppe Iuculano <iuculano@debian.org> Fri, 22 Jan 2010 20:02:53 +0100 + +smartmontools (5.39-2) unstable; urgency=low + + * [f7f4c51] Fixed crash on kfreebsd. (Closes: #561113) - thanks to + Petr Salinger and Axel Beckert + + -- Giuseppe Iuculano <iuculano@debian.org> Sat, 26 Dec 2009 11:11:58 +0100 + +smartmontools (5.39-1) unstable; urgency=low + + * [e9e8c2b] Imported Upstream version 5.39 + * [b00706e] Adeed libusb2-dev for kfreebsd in Build-Depends. + (Closes: #560241) + + -- Giuseppe Iuculano <iuculano@debian.org> Mon, 14 Dec 2009 12:24:35 +0100 + +smartmontools (5.38+svn2993-1) unstable; urgency=low + + * [bed9426] Imported Upstream version 5.38+svn2993 + * [4a5d1d1] Fixed status action in init script (LP: #491324) + * [9dd2a1d] Add selinux for avr32 in build-depends + * [26ec4bc] Refreshed patches + + -- Giuseppe Iuculano <iuculano@debian.org> Wed, 09 Dec 2009 17:45:19 +0100 + +smartmontools (5.38+svn2956-1) unstable; urgency=low + + * [283f281] Updated my email address and removed DM-Upload-Allowed + control field + * [eb07ddf] Imported Upstream version 5.38+svn2956 + + Added a note in smartctl (8) about 2^16 wrap of LifeTime value in + Self-test log. (Closes: #535298) + * [ed382e8] Refreshed patches + * [f4ff277] Updated lowcap patch, make capabilities optional and + clarify that mail notification could not work when used. (Closes: + #544940) + * [a7e19a3] Do not Build-depends in libcap-ng-dev in armel, libcap-ng + is broken in this arch. (Closes: #548438) + + -- Giuseppe Iuculano <iuculano@debian.org> Sun, 11 Oct 2009 09:42:47 +0200 + +smartmontools (5.38+svn2920-2) unstable; urgency=low + + * [a117ede] Enable Selinux only in linux platforms + + -- Giuseppe Iuculano <giuseppe@iuculano.it> Tue, 22 Sep 2009 13:22:39 +0200 + +smartmontools (5.38+svn2920-1) unstable; urgency=low + + * [a94eb83] run.d/10mail: Do not exit silently if /usr/bin/mail is + missing (Closes: #541192) - thanks to Francesco Potorti` + * [0197215] Enabled SELinux support + * [091eb3a] debian/smartmontools-bug: Fixed a spelling error (Closes: + #547197) - thanks to Sandro Tosi + * [5496574] Imported Upstream version 5.38+svn2920 + * [5d593fa] Removed patches merged in upstream: 64_r2898.patch, + 65_freebsd.patch + + -- Giuseppe Iuculano <giuseppe@iuculano.it> Sun, 20 Sep 2009 14:51:52 +0200 + +smartmontools (5.38+svn2879-4) unstable; urgency=low + + * [af11f9b] debian/patches/65_freebsd.patch: The os_freebsd.cpp uses + reallocf(), which is specific for *BSD libc. Added an implementation + directly into os_freebsd.cpp - thanks to Petr Salinger + * [b2a680f] debian/watch: Removed uupdate + * [4fe54cf] Do not Build-depends on libcap-ng-dev on avr32 + + -- Giuseppe Iuculano <giuseppe@iuculano.it> Mon, 07 Sep 2009 20:55:53 +0200 + +smartmontools (5.38+svn2879-3) unstable; urgency=low + + * [1b75411] Freebsd patch was not entirely merged in upstream. Applied + remaining changes and try to fix FTBFS on GNU/kFreeBSD (Closes: #537856) + + -- Giuseppe Iuculano <giuseppe@iuculano.it> Mon, 07 Sep 2009 15:33:34 +0200 + +smartmontools (5.38+svn2879-2) unstable; urgency=low + + * [51c0fd9] Build-depends on libcap-ng-dev only on linux. - thanks to + Petr Salinger + * [94843b0] Fixed Vcs-Browser field + * [c2d3bf4] Do not Build-depends on libcap-ng-dev on sparc + * [27a32a3] Dereference '/dev/disk/by-*/*' symlink before device type + autodetection. (Closes: #544823) + + -- Giuseppe Iuculano <giuseppe@iuculano.it> Mon, 07 Sep 2009 14:24:17 +0200 + +smartmontools (5.38+svn2879-1) unstable; urgency=low + + [ Guido Günther ] + * [d5c8d71] suggest graphical helpers (Closes: #524752) + * [b11b96e] support status action in init script (Closes: #525196) - + thanks to Peter Eisentraut + * [b092558] fix Vcs-Browser URL + + [ Giuseppe Iuculano ] + * [101b745] New maintainers, thanks to Guido Günther for the prior + work on smartmontools. (Closes: #543861) + * [35bece3] debian/rules: Added a get-orig-source target to retrieve a + svn snapshot + * [4482c05] Bump to debhelper 7 compatibility levels + * [2127e19] Imported Upstream version 5.38+svn2879 + - Fixed FTBFS (Closes: #539430) + - GNU/kFreeBSD patches merged in upstream (Closes: #537856) + - More drives recognized: Fujitsu MHW2 BJ series, WD Caviar Black family, + Western Digital AV-GP series, Transcend Solid-State Drive and Transcend + Solid-State Drive V series, Seagate Momentus 5400.5 series. + * [6052436] Refreshed patches + * [91ad575] move badblockhowto.html in debian/ (Closes: #538631) + * [bbdf8c9] debian/control: Depend on lsb >= 3.2-14, which has the + status_of_proc() function. + * [9afe5af] Removed stop links from rc0 and rc6 (Closes: #494951) - + thanks to James Westby + * [6dcd8ec] Updated to standards version 3.8.3 (No changes needed) + * [608687b] debian/rules: Use dh_prep instead of dh_clean -k + * [a52f90d] debian/rules: Do not ignore make clean errors + * [31e40f7] debian/rules: use dh_install to install files + * [9ca7a79] debian/control: Added Florian Maier in Uploaders, fixed + VCS field, added DM-Upload-Allowed field + * [d494f00] Updated debian/badblockhowto.html (Closes: #540359) - + thanks to Francesco Potorti` + * [3db595a] Use the `-n standby' option by default in smartd.conf + (Closes: #531325) + * [52b4501] Added /etc/smartmontools/run.d/10powersave-notify to + enable desktop notification over powersave-notify and added + powersaved in Recommends + * [0dcf301] debian/patches/62_lowcap.patch: Drop all unnecessary + capabilities + * [5afdd10] Added the removable option by default. This indicates to + smartd that it should continue if the device does not appear to be + present when smartd is started. (Closes: #406130) + + -- Giuseppe Iuculano <giuseppe@iuculano.it> Tue, 01 Sep 2009 12:59:13 +0200 + +smartmontools (5.38-3) unstable; urgency=low + + * [3ea288e] add Homepage, Vcs-{Git,Browser} fields (Closes: #500530) + * [76a9163] check if daemon is running befor starting it (Closes: #516430) + * [8a3e8a3] fix maintainer name + + -- Guido Günther <agx@sigxcpu.org> Sat, 21 Feb 2009 17:19:19 +0100 + +smartmontools (5.38-2) unstable; urgency=low + + * [fd9c675] add lintian override Full stop at end of synopsis is OK - + it doesn't end a sentence but is part of an abbreviation. + * [fab76b4] update copyright + * [1731d9e] bump standards version + * [d0f2f2e] add README.source + * [2d3e4b9] new patch 61_cciss-doc.patch update ccis examples/docs + (Closes: #488371) - thanks to Matt Taggart + + -- Guido Guenther <agx@sigxcpu.org> Thu, 24 Jul 2008 12:15:34 -0400 + +smartmontools (5.38-1) unstable; urgency=low + + * new upstream version + * drop 51_add-kfreebsd-support.diff, applied upstream + * add watch file from dehs.debian.org + + -- Guido Guenther <agx@sigxcpu.org> Tue, 11 Mar 2008 20:54:41 +0100 + +smartmontools (5.38~rc0-2) unstable; urgency=low + + [ Petter Reinholdtsen ] + * smartmontools: Problem with LSB header in init.d script (Closes: + Bug#469377) + + -- Guido Guenther <agx@sigxcpu.org> Wed, 05 Mar 2008 08:55:46 +0100 + +smartmontools (5.38~rc0-1) unstable; urgency=low + + * New Upstream Version release candidate + * detects Hitachi drives with newer kernels (Closes: #314629) + * updated drives table (Closes: #381251) + * correct logfile location (Closes: #464193) + * drop 01_sat-error-handling.diff - originally pulld from upstream + * drop 05_wait-for-daemon-startup.diff - applied upstream + * refresh 51_add-kfreebsd-support.diff + * bump standards version + * ship badblockshowto.html (Closes: #454565) + + -- Guido Guenther <agx@sigxcpu.org> Tue, 26 Feb 2008 11:59:50 +0100 + +smartmontools (5.38~cvs20071118-2) experimental; urgency=low + + * add LSB header (Closes: #458391) + * move debian specific patches to >= 50 + * pull 01_sat-error-handling.diff from upstream CVS to improve SAT + handling of aborted ATA commands - thanks to Doug Gilbert! + + -- Guido Guenther <agx@sigxcpu.org> Sun, 09 Dec 2007 14:51:57 +0100 + +smartmontools (5.38~cvs20071118-1) experimental; urgency=low + + * new upstream CVS snapshot 20071118 + * update patches: + * rework 01_add-kfreebsd-support.diff to apply again + * rework 05_wait-for-daemon-startup.diff to apply again + * rediff 10_remove-redhatism.diff + * drop 20_fix-scsi-disk-detection.diff - merged upstream + * drop 30_gcc4.3.diff - fixed upstream + * drop 40_fix-sata-hsm-violation.diff - pulled from upstream + + -- Guido Guenther <agx@sigxcpu.org> Mon, 19 Nov 2007 13:54:42 +0100 + +smartmontools (5.37-6) unstable; urgency=low + + * don't redefine CISS_MAX_LUN (Closes: #441598) + * Patch pulled from upstream to fix HSM violation errors on SATA systems + (Closes: #448781) - thanks to Sven Hartge for sorting this out + + -- Guido Guenther <agx@sigxcpu.org> Thu, 01 Nov 2007 13:29:11 +0100 + +smartmontools (5.37-5) unstable; urgency=low + + * NEWS.Debian: SCSI disks need -W for temperature logging, thanks to GSR for + feedback and testing. (Closes: #411932) + + -- Guido Guenther <agx@sigxcpu.org> Thu, 05 Apr 2007 10:15:52 +0200 + +smartmontools (5.37-4) unstable; urgency=low + + * 05_wait-for-daemon-startup.diff: fix startup race condition (Closes: #246032) + * document good testing practice (Closes: #412543) + + -- Guido Guenther <agx@sigxcpu.org> Sat, 31 Mar 2007 16:01:27 +0200 + +smartmontools (5.37-3) unstable; urgency=low + + * rebuild with pbuilder (Closes: #415950) + + -- Guido Guenther <agx@sigxcpu.org> Fri, 23 Mar 2007 13:51:43 +0100 + +smartmontools (5.37-2) unstable; urgency=low + + * switch from dpatch to quilt + * 20_fix-scsi-disk-detection.diff: patch from Douglas Gilbert to fix scsi + disk detection (Closes: #411932) + + -- Guido Guenther <agx@sigxcpu.org> Mon, 19 Mar 2007 23:04:15 +0100 + +smartmontools (5.37-1) unstable; urgency=low + + * New Upstream Version + * adjusted 04_remove-Id-from-smartd.conf.dpatch + + -- Guido Guenther <agx@sigxcpu.org> Thu, 21 Dec 2006 13:12:26 +0100 + +smartmontools (5.37~cvs20061111-1) experimental; urgency=low + + * The No Narro ihr Mäschkerle release + * New upstream cvs release candidate (Closes: #398055, #398054, #391999) + * dropped 60_cciss.dpatch, merged upstream + * adjusted 04_remove-Id-from-smartd.conf.dpatch + + -- Guido Guenther <agx@sigxcpu.org> Sat, 11 Nov 2006 19:19:27 +0100 + +smartmontools (5.37~cvs20061002-1) experimental; urgency=low + + * New upstream CVS release candidate + * adjusted patches: 60_cciss, 04_remove-Id-from-smartd.conf + + -- Guido Guenther <agx@sigxcpu.org> Mon, 2 Oct 2006 17:45:51 +0200 + +smartmontools (5.36-8) unstable; urgency=low + + * 60_cciss (smartd.c): make sure we pass the correct mode and device + parameters to the lower level functions (the code assumed "SCSI" in those + places although it was "CCISS"). Patch by Frédéric BOITEUX + <fboiteux@calistel.com>, thanks a lot! (Closes: #36802) + + -- Guido Guenther <agx@sigxcpu.org> Fri, 29 Sep 2006 15:22:19 +0200 + +smartmontools (5.36-7) unstable; urgency=low + + * README.Debian: actually mention the term "smartd-runner" in README.Debian + instead of only explaining what it does + * /etc/init.d/smartmontools: use LSB logging, patch by David Härdeman + <david@hardeman.nu> (Closes: #385903) + * Bump standards version to 3.7.2 (no other changes necessary) + + -- Guido Guenther <agx@sigxcpu.org> Mon, 25 Sep 2006 11:41:21 +0200 + +smartmontools (5.36-6) unstable; urgency=low + + * Explicitly discourage using enable_smart with SATA disks in README.Debian + (Closes: #365027) - many thanks to Francois Marier and Doug Gilbert for + their feedback and help. + * Document what smartd-runner really does (Closes: #352244) + + -- Guido Guenther <agx@sigxcpu.org> Wed, 3 May 2006 21:44:01 +0200 + +smartmontools (5.36-5) unstable; urgency=low + + * apply current version of the cciss patch, updated to be less intrusive + by Douglas Gilbert + + -- Guido Guenther <agx@sigxcpu.org> Wed, 26 Apr 2006 23:10:07 +0200 + +smartmontools (5.36-4) unstable; urgency=low + + * really apply the cciss patch, thanks again to Frederic Boiteux + * adjust the cciss patch to include <linux/cciss.h> instead of + "cciss.h", we don't ship a local copy. + + -- Guido Guenther <agx@sigxcpu.org> Tue, 25 Apr 2006 13:54:17 +0200 + +smartmontools (5.36-3) unstable; urgency=low + + * depend on debianutils (>= 2.2) for run-parts --lsbsysinit, thanks to + Frederic Boiteux (Closes: #364713) + + -- Guido Guenther <agx@sigxcpu.org> Tue, 25 Apr 2006 10:59:37 +0200 + +smartmontools (5.36-2) unstable; urgency=low + + * Build depend on automake/autoconf since we run autogen.sh + from debian/rules + + -- Guido Guenther <agx@sigxcpu.org> Mon, 24 Apr 2006 16:02:42 +0200 + +smartmontools (5.36-1) unstable; urgency=low + + * new upstream version (Closes: #363087) + * use dpatch + * bump standards version + * update cciss patch + + -- Guido Guenther <agx@sigxcpu.org> Mon, 24 Apr 2006 14:39:19 +0200 + +smartmontools (5.33+5.34cvs20050802-6) experimental; urgency=low + + * update cciss patch to also support smartd not only smartctl + + -- Guido Guenther <agx@debian.org> Thu, 13 Apr 2006 09:34:39 +0200 + +smartmontools (5.33+5.34cvs20050802-5) experimental; urgency=low + + * add (experimental) cciss patch by Praveen Chidambaram + <bunchofmails@gmail.com>, with slight modfifications to apply and work + with current CVS + * Build depend on libcam-dev for kfreebsd-amd64 too (Closes: #361478) + * Remove $Id$ from smartd.conf (Closes: #324703) + + -- Guido Guenther <agx@debian.org> Mon, 10 Apr 2006 17:33:18 +0200 + +smartmontools (5.33+5.34cvs20050802-4) unstable; urgency=low + + * avoid usage of cat in 10mail (Closes: #327338) + * add patch by Aurelin Jano to build on kfreebsd (Closes: #327642) + + -- Guido Guenther <agx@debian.org> Tue, 24 Jan 2006 09:56:28 +0100 + +smartmontools (5.33+5.34cvs20050802-3) unstable; urgency=low + + * add note about 3ware raid controlers to NEWS.Debian (Closes: #322265) + + -- Guido Guenther <agx@debian.org> Thu, 11 Aug 2005 11:04:56 +0200 + +smartmontools (5.33+5.34cvs20050802-2) unstable; urgency=low + + * rules: make ./configure executable (Closes: #321060) + * smartd.conf: add smartd-runner to the default DEVICESCAN directive + * README.Debian: mention smartd-runner + * control: remove debianutils, it's an essential package + + -- Guido Guenther <agx@debian.org> Wed, 3 Aug 2005 11:32:53 +0200 + +smartmontools (5.33+5.34cvs20050802-1) unstable; urgency=low + + * New CVS snapshot as of 2005-08-02 (Closes: #269051) + + * added smartd-runner which runs scripts in /etc/smartmontools/run.d + * added /etc/smartmontools/run.d/10mail to emulate smartd's -m option + * add a comment on howto use this to /etc/smartd.conf + * Many thanks for this go to Brian Sutherland <jinty@web.de> + + -- Guido Guenther <agx@debian.org> Tue, 2 Aug 2005 20:58:47 +0200 + +smartmontools (5.33-1) experimental; urgency=low + + * new upstream version + * upload to experimental since we want 5.32 in sarge for now + + -- Guido Guenther <agx@debian.org> Sat, 20 Nov 2004 19:52:39 +0100 + +smartmontools (5.32-2) unstable; urgency=medium + + * urgency medium since the sarge version is unusable on arm + * use __attribute__((packed)) instead of #pragma(packed) since the later + causes alignment problems on arm - based on a patch by armcc@lycos.com, + many thanks! (Closes: #278459) + * simplify /usr/share/bug/smartmontools a bit (Closes: #262055) + + -- Guido Guenther <agx@debian.org> Thu, 28 Oct 2004 09:20:57 +0200 + +smartmontools (5.32-1) unstable; urgency=low + + * new upstream version + + -- Guido Guenther <agx@debian.org> Mon, 19 Jul 2004 10:57:53 +0200 + +smartmontools (5.30-6) unstable; urgency=low + + * be more verbose in /etc/init.d/smartmontools iff smartd has been disabled + via /etc/default/smartmontools (Closes: #246615) + * explain removal of cron selftests in NEWS.Debian (Closes: #247622) + + -- Guido Guenther <agx@debian.org> Thu, 6 May 2004 09:05:40 +0200 + +smartmontools (5.30-5) unstable; urgency=low + + * rm selftests from CVS, so they don't get picked up by cvs-buildpackage + (Closes: #242580), sigh + * thanks again to Jean-Luc Coulon and Bruce Allen for resolving #208964 + + -- Guido Guenther <agx@debian.org> Wed, 7 Apr 2004 19:07:58 +0200 + +smartmontools (5.30-4) unstable; urgency=low + + * improve restart in init.d script so that smartd can shut down + properly (Closes: #242344) + * remove cron selftests at all, use smartd's -s option instead + + -- Guido Guenther <agx@debian.org> Tue, 6 Apr 2004 12:18:52 +0200 + +smartmontools (5.30-3) unstable; urgency=low + + * deprecated cron selftests, this is now better handled by smartd's "-s" + option + * check for existence of smartmontools-selftests in cron.d snippet + * in accordance with upstream (who adopted our naming scheme) use smartd's + compiled in default values in /etc/default/smartmontools + + -- Guido Guenther <agx@debian.org> Sat, 27 Mar 2004 07:11:12 +0100 + +smartmontools (5.30-2) unstable; urgency=low + + * clarify usage of enable_smart in (Closes: #239737) + * add reload to /etc/init.d/smartmontools + + -- Guido Guenther <agx@debian.org> Thu, 25 Mar 2004 14:43:33 +0100 + +smartmontools (5.30-1) unstable; urgency=low + + * new upstream version (Closes: #238790) + * logging severity fixed upstream (Closes: #234519) + + -- Guido Guenther <agx@debian.org> Tue, 23 Mar 2004 00:40:25 +0100 + +smartmontools (5.26-5) unstable; urgency=low + + * install /u/s/bug/smartmontools as reportbug helper + * use install instead of cp/chmod + * remove no longer needed debian/dirs + + -- Guido Guenther <agx@debian.org> Wed, 11 Feb 2004 19:08:49 +0100 + +smartmontools (5.26-4) unstable; urgency=low + + * remove sections not relevant on debian systems from smartd.8.in manpage + * include /etc/smartd.conf again, thanks Wolfram Quester. + * change smartd.conf to only use DEVICESCAN + + -- Guido Guenther <agx@debian.org> Tue, 3 Feb 2004 15:25:32 +0100 + +smartmontools (5.26-3) unstable; urgency=low + + * The "where did the chmod go" release + * make sure selftests is executable (Closes: #223627) + + -- Guido Guenther <agx@debian.org> Thu, 11 Dec 2003 12:33:56 +0100 + +smartmontools (5.26-2) unstable; urgency=low + + * actually include /usr/share/smartmontools/selftests again + + -- Guido Guenther <agx@debian.org> Tue, 9 Dec 2003 12:45:22 +0100 + +smartmontools (5.26-1) unstable; urgency=low + + * new upstream version + + -- Guido Guenther <agx@debian.org> Fri, 5 Dec 2003 22:12:33 +0100 + +smartmontools (5.1.18-3) unstable; urgency=low + + * make sure /usr/share/smartmontools/selftests is executable + + -- Guido Guenther <agx@debian.org> Wed, 12 Nov 2003 01:08:20 +0100 + +smartmontools (5.1.18-2) unstable; urgency=low + + * Conflict: ucsc-smartsuite (Closes: #218573) + * introduce run_cron_selftests in /etc/defaults/smartmontools which + contains a list of devices to run regular selftests on via cron + + -- Guido Guenther <agx@debian.org> Mon, 3 Nov 2003 22:36:34 +0100 + +smartmontools (5.1.18-1) unstable; urgency=low + + * new upstream version + * bump Standards-Version to 3.6.1 + + -- Guido Guenther <agx@debian.org> Thu, 28 Aug 2003 21:54:06 +0200 + +smartmontools (5.1.16-1) unstable; urgency=low + + * new upstream version + - log normal exit at LOG_INFO, not LOG_CRIT (Closes: #201173) + - allows to acces disks behind 3ware RAID controllers, maybe + closes: #188515, the submitter never specified any details. + * bump Standards-Version to 3.6.0 + * add NEWS.Debian file + + -- Guido Guenther <agx@debian.org> Thu, 7 Aug 2003 13:54:26 +0200 + +smartmontools (5.1.14-1) unstable; urgency=low + + * new upstream version + * fix the regexp in smartmontools-cron matching the first disk only + * bump Standards-Version to 3.5.10 + + -- Guido Guenther <agx@debian.org> Sun, 22 Jun 2003 14:07:11 +0200 + +smartmontools (5.1.11-1) unstable; urgency=low + + * new upstream version (Closes: #191831) + * rework debian/rules since we can now pass most of the + needed options to the Makefile + + -- Guido Guenther <agx@debian.org> Wed, 7 May 2003 21:43:53 +0200 + +smartmontools (5.1.10-1) unstable; urgency=low + + * new upstream version (Closes: #186213) + * add ${misc:Depends} to control file + * bump debhelper Build-Depends to >=4 + * bump Standards-Version to 3.5.9 + * smartd now writes a pidfile, use it in the init script + * add smartd_opts to /etc/defaults/smartmontools + * add cron.daily example + + -- Guido Guenther <agx@debian.org> Mon, 21 Apr 2003 19:32:46 +0200 + +smartmontools (5.1.9-3) unstable; urgency=low + + * init.d script prints more sensible error messages (Closes: #187697) + + -- Guido Guenther <agx@debian.org> Sat, 5 Apr 2003 19:17:43 +0200 + +smartmontools (5.1.9-2) unstable; urgency=low + + * /etc/init.d/smartmontools cleanup: + - Don't fail when the package was removed but not purged + (Closes: #186091). + - sleep 1 second on restart + - fix wrong scriptname in usage output + * install smartd.conf to /etc + * adjust README.Debian + * don't install CHANGELOG, dh_installchangelogs handles this for us + + -- Guido Guenther <agx@debian.org> Mon, 24 Mar 2003 19:24:53 +0100 + +smartmontools (5.1.9-1) unstable; urgency=low + + * new upstream version (Closes: #178151) + * Recommends: mailx | mailutils (Closes: #184890) + * add '-e' to shebang line of init script + * use debian/compat not DH_COMPAT + + -- Guido Guenther <agx@debian.org> Sat, 15 Mar 2003 12:40:04 +0100 + +smartmontools (5.1.4-2) unstable; urgency=low + + * remove 'function' bashism from initscript (Closes: #178411), + Thanks Martin Waitz. + + -- Guido Guenther <agx@debian.org> Sun, 26 Jan 2003 00:52:49 +0100 + +smartmontools (5.1.4-1) unstable; urgency=low + + * new upstream version + * turn on S.M.A.R.T. for devices listed in enable_smart + * honor DEB_BUILD_OPTIONS + * bump standards version to 3.5.8 + + -- Guido Guenther <agx@debian.org> Sat, 25 Jan 2003 19:40:14 +0100 + +smartmontools (5.1.1-3) unstable; urgency=low + + * conflict with smartsuite (Closes: #178010) + * remove superflous whitespaces in description + * remove usr/bin from debian/dirs + + -- Guido Guenther <agx@debian.org> Fri, 24 Jan 2003 00:51:26 +0100 + +smartmontools (5.1.1-2) unstable; urgency=low + + * only start smartd if start_smartd=yes in /etc/default/smartmontools. + * initial upload (Closes: #174828). + + -- Guido Guenther <agx@debian.org> Fri, 17 Jan 2003 23:04:50 +0000 + +smartmontools (5.1.1-1) unstable; urgency=low + + * Initial Release. + + -- Guido Guenther <agx@debian.org> Tue, 14 Jan 2003 12:58:00 +0000 diff --git a/debian/clean b/debian/clean new file mode 100644 index 0000000..a117ae9 --- /dev/null +++ b/debian/clean @@ -0,0 +1,3 @@ +## Debian CI: +debian/.gitlab-ci.yml + diff --git a/debian/control b/debian/control new file mode 100644 index 0000000..40544ac --- /dev/null +++ b/debian/control @@ -0,0 +1,41 @@ +Source: smartmontools +Section: utils +Priority: optional +Standards-Version: 4.6.0 +Maintainer: Dmitry Smirnov <onlyjob@debian.org> +Uploaders: Florian Maier <contact@marsmenschen.com>, + Jonathan Dowland <jmtd@debian.org>, +Build-Depends: autoconf, + automake, + debhelper-compat (= 13), + freebsd-glue [kfreebsd-any], + libcam-dev [kfreebsd-any], + libcap-ng-dev [linux-any], + libselinux1-dev [linux-any], + libusb2-dev [kfreebsd-any], + libsystemd-dev [linux-any], + pkg-config, +Vcs-Git: https://salsa.debian.org/debian/smartmontools.git +Vcs-Browser: https://salsa.debian.org/debian/smartmontools +Homepage: https://www.smartmontools.org/ +Rules-Requires-Root: no + +Package: smartmontools +Architecture: any +Conflicts: smartsuite, ucsc-smartsuite +Pre-Depends: ${misc:Pre-Depends} +Depends: debianutils (>= 2.2), + sysvinit-utils (>= 3.05-4~), + ${misc:Depends}, + ${shlibs:Depends} +Recommends: ${misc:Recommends} +Suggests: gsmartcontrol, smart-notifier + ,mailx | mailutils +# update-smart-drivedb + ,curl | wget | lynx, gpg +Description: control and monitor storage systems using S.M.A.R.T. + The smartmontools package contains two utility programs (smartctl and smartd) + to control and monitor storage systems using the Self-Monitoring, Analysis and + Reporting Technology System (S.M.A.R.T.) built into most modern ATA and SCSI + hard disks. It is derived from the smartsuite package, and includes support + for ATA/ATAPI-5 disks. It should run on any modern Linux system. diff --git a/debian/copyright b/debian/copyright new file mode 100644 index 0000000..4f19665 --- /dev/null +++ b/debian/copyright @@ -0,0 +1,155 @@ +Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Upstream-Name: smartmontools +Upstream-Contact: Christian Franke <Christian.Franke@t-online.de> +Source: http://smartmontools.sourceforge.net/ + +Files: * +Copyright: + 2004-2023 Christian Franke + 2016 Casey Biemiller <cbiemiller@intelliprop.com> + 2014 Alex Samorukov <samm@os2.kiev.ua> + 2000 Andre Hedrick <andre@linux-ide.org> + 1999-2000 Michael Cornwell <cornwell@acm.org> + 2002-2018 Bruce Allen + 2003-2015 Casper Dik + 2004-2010 David Snyder + 2003-2023 Douglas Gilbert <dgilbert@interlog.com> + 2003-2010 Eduard Martinescu + 2012 Hank Wu <hank@areca.com.tw> + 2013 Hannes von Haugwitz <hannes@vonhaugwitz.com> + 2018 Harry Mallon <hjmallon@gmail.com> + 2004-2008 Geoff Keating <geoffk@geoffk.org> + 2007 Joerg Hering + 2008 Jordan Hargrave <jordan_hargrave@dell.com> + 2016 Kimihiro Nonaka + 2015 Nidhi Malhotra <nidhi.malhotra@pmcs.com> + 2008 Oliver Bock <brevilo@users.sourceforge.net> + 2003-2008 Philip Williams + 2014 Raghava Aditya <raghava.aditya@pmcs.com> + 2003-2008 Sergey Svishchev + 2003-2008 SAWADA Keiji + 2004-2008 Yuri Dario + 1999-2003 3ware Inc. + 2021-2023 Seagate Technology LLC and/or its Affiliates + 2022 3SNIC Inc. +License: GPL-2+ + +Files: + linux_nvme_ioctl.h +Copyright: + 2011-2014 Intel Corporation. +License: GPL-2 + +Files: + m4/pkg.m4 +Copyright: + 2004 Scott James Remnant <scott@netsplit.com>. + 2012-2015 Dan Nicholson <dbn.lists@gmail.com> +License: GPL-2+ + +Files: + getopt/* + regex/* +Copyright: + 1987-2018 Free Software Foundation, Inc. +License: LGPL-2.1+ + +Files: + netbsd_nvme_ioctl.h +Copyright: 2014 David Gwynne <dlg@openbsd.org> +License: Expat-like + Permission to use, copy, modify, and distribute this software for any + purpose with or without fee is hereby granted, provided that the above + copyright notice and this permission notice appear in all copies. + . + THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES + WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF + MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR + ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES + WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN + ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF + OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + +Files: + cissio_freebsd.h + freebsd_nvme_ioctl.h + sg_unaligned.h +Copyright: + 2014-2018 Douglas Gilbert + 2012-2013 Intel Corporation + 2001 Michael Smith +License: BSD-2-Clause + +Files: + os_freebsd.h +Copyright: + 2000 BSDi + 2000 Michael Smith + 2003-2005 Vinod Kashyap + 2003-2010 Eduard Martinescu + 2003 Paul Saab + 2004-2005 Applied Micro Circuits Corporation. +License: BSD-2-Clause and GPL-2+ + +Files: debian/* +Copyright: + 2019-2023 Dmitry Smirnov <onlyjob@debian.org> + 2003-2009 Guido Guenther <agx@debian.org> + 2009-2015 Giuseppe Iuculano <giuseppe@iuculano.it> + 2010 Florian Weimer <fweimer@bfk.de> + 2014 Eric Dorland <eric@debian.org> + 2015 Tobias Frost <tobi@coldtobi.de> + 2015-2016 Jonathan Dowland <jmtd@debian.org> +License: GPL-2 + +License: GPL-2+ + This package is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + . + On Debian systems, the complete text of the GNU General + Public License version 2 can be found in "/usr/share/common-licenses/GPL-2". + +License: GPL-2 + This package is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; version 2. + . + On Debian systems, the complete text of the GNU General + Public License version 2 can be found in "/usr/share/common-licenses/GPL-2". + +License: LGPL-2.1+ + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Lesser General Public + License as published by the Free Software Foundation; either + version 2.1 of the License, or (at your option) any later version. + ․ + This library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Lesser General Public License for more details. + ․ + On Debian systems, the complete text of the GNU Lesser General Public + License Version 2.1 can be found in "/usr/share/common-licenses/LGPL-2.1". + +License: BSD-2-Clause + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions are met: + . + 1. Redistributions of source code must retain the above copyright notice, this + list of conditions and the following disclaimer. + 2. Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution. + . + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND + ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED + WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE + DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR + ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES + (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; + LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND + ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT + (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS + SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. diff --git a/debian/dirs b/debian/dirs new file mode 100644 index 0000000..a9002d6 --- /dev/null +++ b/debian/dirs @@ -0,0 +1,3 @@ +etc/smartmontools/run.d +usr/share/smartmontools +usr/sbin diff --git a/debian/docs b/debian/docs new file mode 100644 index 0000000..aa1badc --- /dev/null +++ b/debian/docs @@ -0,0 +1,3 @@ +README +AUTHORS +debian/badblockhowto.html diff --git a/debian/patches/52_remove-pragma.diff b/debian/patches/52_remove-pragma.diff new file mode 100644 index 0000000..5a92422 --- /dev/null +++ b/debian/patches/52_remove-pragma.diff @@ -0,0 +1,265 @@ +From: Giuseppe Iuculano <iuculano@debian.org> +Date: Thu, 27 Sep 2018 19:03:07 +0800 +Subject: _remove-pragma + +--- + atacmds.h | 15 --------------- + 1 file changed, 15 deletions(-) + +--- a/atacmds.h ++++ b/atacmds.h +@@ -110,9 +110,8 @@ + #define NUMBER_ATA_SMART_ATTRIBUTES 30 + + // Needed parts of the ATA DRIVE IDENTIFY Structure. Those labeled + // word* are NOT used. +-#pragma pack(1) + struct ata_identify_device { + unsigned short words000_009[10]; + unsigned char serial_no[20]; + unsigned short words020_022[3]; +@@ -132,9 +131,8 @@ + #pragma pack() + STATIC_ASSERT(sizeof(ata_identify_device) == 512); + + /* ata_smart_attribute is the vendor specific in SFF-8035 spec */ +-#pragma pack(1) + struct ata_smart_attribute { + unsigned char id; + // meaning of flag bits: see MACROS just below + // WARNING: MISALIGNED! +@@ -193,9 +191,8 @@ + + + // Format of data returned by SMART READ DATA + // Table 62 of T13/1699-D (ATA8-ACS) Revision 6a, September 2008 +-#pragma pack(1) + struct ata_smart_values { + unsigned short int revnumber; + struct ata_smart_attribute vendor_attributes [NUMBER_ATA_SMART_ATTRIBUTES]; + unsigned char offline_data_collection_status; +@@ -226,9 +223,8 @@ + 05 - Read scan + */ + + /* Vendor attribute of SMART Threshold (compare to ata_smart_attribute above) */ +-#pragma pack(1) + struct ata_smart_threshold_entry { + unsigned char id; + unsigned char threshold; + unsigned char reserved[10]; +@@ -237,9 +233,8 @@ + STATIC_ASSERT(sizeof(ata_smart_threshold_entry) == 12); + + /* Format of Read SMART THreshold Command */ + /* Compare to ata_smart_values above */ +-#pragma pack(1) + struct ata_smart_thresholds_pvt { + unsigned short int revnumber; + struct ata_smart_threshold_entry thres_entries[NUMBER_ATA_SMART_ATTRIBUTES]; + unsigned char reserved[149]; +@@ -249,9 +244,8 @@ + STATIC_ASSERT(sizeof(ata_smart_thresholds_pvt) == 512); + + + // Table 42 of T13/1321D Rev 1 spec (Error Data Structure) +-#pragma pack(1) + struct ata_smart_errorlog_error_struct { + unsigned char reserved; + unsigned char error_register; + unsigned char sector_count; +@@ -268,9 +262,8 @@ + STATIC_ASSERT(sizeof(ata_smart_errorlog_error_struct) == 30); + + + // Table 41 of T13/1321D Rev 1 spec (Command Data Structure) +-#pragma pack(1) + struct ata_smart_errorlog_command_struct { + unsigned char devicecontrolreg; + unsigned char featuresreg; + unsigned char sector_count; +@@ -284,18 +277,16 @@ + #pragma pack() + STATIC_ASSERT(sizeof(ata_smart_errorlog_command_struct) == 12); + + // Table 40 of T13/1321D Rev 1 spec (Error log data structure) +-#pragma pack(1) + struct ata_smart_errorlog_struct { + struct ata_smart_errorlog_command_struct commands[5]; + struct ata_smart_errorlog_error_struct error_struct; + } ATTR_PACKED; + #pragma pack() + STATIC_ASSERT(sizeof(ata_smart_errorlog_struct) == 90); + + // Table 39 of T13/1321D Rev 1 spec (SMART error log sector) +-#pragma pack(1) + struct ata_smart_errorlog { + unsigned char revnumber; + unsigned char error_log_pointer; + struct ata_smart_errorlog_struct errorlog_struct[5]; +@@ -313,9 +304,8 @@ + // T13/1699-D Revision 6a (Working Draft), September 6, 2008. + + // Command data structure + // Table A.9 of T13/1699-D Revision 6a +-#pragma pack(1) + struct ata_smart_exterrlog_command + { + unsigned char device_control_register; + unsigned char features_register; +@@ -338,9 +328,8 @@ + STATIC_ASSERT(sizeof(ata_smart_exterrlog_command) == 18); + + // Error data structure + // Table A.10 T13/1699-D Revision 6a +-#pragma pack(1) + struct ata_smart_exterrlog_error + { + unsigned char device_control_register; + unsigned char error_register; +@@ -363,9 +352,8 @@ + STATIC_ASSERT(sizeof(ata_smart_exterrlog_error) == 34); + + // Error log data structure + // Table A.8 of T13/1699-D Revision 6a +-#pragma pack(1) + struct ata_smart_exterrlog_error_log + { + ata_smart_exterrlog_command commands[5]; + ata_smart_exterrlog_error error; +@@ -374,9 +362,8 @@ + STATIC_ASSERT(sizeof(ata_smart_exterrlog_error_log) == 124); + + // Ext. Comprehensive SMART error log + // Table A.7 of T13/1699-D Revision 6a +-#pragma pack(1) + struct ata_smart_exterrlog + { + unsigned char version; + unsigned char reserved1; +@@ -390,9 +377,8 @@ + STATIC_ASSERT(sizeof(ata_smart_exterrlog) == 512); + + + // Table 45 of T13/1321D Rev 1 spec (Self-test log descriptor entry) +-#pragma pack(1) + struct ata_smart_selftestlog_struct { + unsigned char selftestnumber; // Sector number register + unsigned char selfteststatus; + unsigned short int timestamp; +@@ -403,9 +389,8 @@ + #pragma pack() + STATIC_ASSERT(sizeof(ata_smart_selftestlog_struct) == 24); + + // Table 44 of T13/1321D Rev 1 spec (Self-test log data structure) +-#pragma pack(1) + struct ata_smart_selftestlog { + unsigned short int revnumber; + struct ata_smart_selftestlog_struct selftest_struct[21]; + unsigned char vendorspecific[2]; +@@ -422,9 +407,8 @@ + // T13/1699-D Revision 6a (Working Draft), September 6, 2008. + + // Extended Self-test log descriptor entry + // Table A.13 of T13/1699-D Revision 6a +-#pragma pack(1) + struct ata_smart_extselftestlog_desc + { + unsigned char self_test_type; + unsigned char self_test_status; +@@ -437,9 +421,8 @@ + STATIC_ASSERT(sizeof(ata_smart_extselftestlog_desc) == 26); + + // Extended Self-test log data structure + // Table A.12 of T13/1699-D Revision 6a +-#pragma pack(1) + struct ata_smart_extselftestlog + { + unsigned char version; + unsigned char reserved1; +@@ -452,17 +435,15 @@ + #pragma pack() + STATIC_ASSERT(sizeof(ata_smart_extselftestlog) == 512); + + // SMART LOG DIRECTORY Table 52 of T13/1532D Vol 1 Rev 1a +-#pragma pack(1) + struct ata_smart_log_entry { + unsigned char numsectors; + unsigned char reserved; + } ATTR_PACKED; + #pragma pack() + STATIC_ASSERT(sizeof(ata_smart_log_entry) == 2); + +-#pragma pack(1) + struct ata_smart_log_directory { + unsigned short int logversion; + struct ata_smart_log_entry entry[255]; + } ATTR_PACKED; +@@ -470,17 +451,15 @@ + STATIC_ASSERT(sizeof(ata_smart_log_directory) == 512); + + // SMART SELECTIVE SELF-TEST LOG Table 61 of T13/1532D Volume 1 + // Revision 3 +-#pragma pack(1) + struct test_span { + uint64_t start; + uint64_t end; + } ATTR_PACKED; + #pragma pack() + STATIC_ASSERT(sizeof(test_span) == 16); + +-#pragma pack(1) + struct ata_selective_self_test_log { + unsigned short logversion; + struct test_span span[5]; + unsigned char reserved1[337-82+1]; +@@ -507,9 +486,8 @@ + // T13/1699-D Revision 3f (Working Draft), December 11, 2006. + + // SCT Status response (read with SMART_READ_LOG page 0xe0) + // Table 194 of T13/BSR INCITS 529 (ACS-4) Revision 20, October 26, 2017 +-#pragma pack(1) + struct ata_sct_status_response + { + unsigned short format_version; // 0-1: Status response format version number (2, 3) + unsigned short sct_version; // 2-3: Vendor specific version number +@@ -540,9 +518,8 @@ + STATIC_ASSERT(sizeof(ata_sct_status_response) == 512); + + // SCT Error Recovery Control command (send with SMART_WRITE_LOG page 0xe0) + // Table 88 of T13/1699-D Revision 6a +-#pragma pack(1) + struct ata_sct_error_recovery_control_command + { + unsigned short action_code; // 3 = Error Recovery Control + unsigned short function_code; // 1 = Set Current, 2 = Return Current, 3 = Set Power-on, 4 = Return Power-on, 5 = Restore Default +@@ -554,9 +531,8 @@ + STATIC_ASSERT(sizeof(ata_sct_error_recovery_control_command) == 512); + + // SCT Feature Control command (send with SMART_WRITE_LOG page 0xe0) + // Table 72 of T13/1699-D Revision 3f +-#pragma pack(1) + struct ata_sct_feature_control_command + { + unsigned short action_code; // 4 = Feature Control + unsigned short function_code; // 1 = Set, 2 = Return, 3 = Return options +@@ -569,9 +545,8 @@ + STATIC_ASSERT(sizeof(ata_sct_feature_control_command) == 512); + + // SCT Data Table command (send with SMART_WRITE_LOG page 0xe0) + // Table 73 of T13/1699-D Revision 3f +-#pragma pack(1) + struct ata_sct_data_table_command + { + unsigned short action_code; // 5 = Data Table + unsigned short function_code; // 1 = Read Table +@@ -582,9 +557,8 @@ + STATIC_ASSERT(sizeof(ata_sct_data_table_command) == 512); + + // SCT Temperature History Table (read with SMART_READ_LOG page 0xe1) + // Table 75 of T13/1699-D Revision 3f +-#pragma pack(1) + struct ata_sct_temperature_history_table + { + unsigned short format_version; // 0-1: Data table format version number (2) + unsigned short sampling_period; // 2-3: Temperature sampling period in minutes diff --git a/debian/patches/53_use-smartd-runner-by-default.diff b/debian/patches/53_use-smartd-runner-by-default.diff new file mode 100644 index 0000000..40520ba --- /dev/null +++ b/debian/patches/53_use-smartd-runner-by-default.diff @@ -0,0 +1,21 @@ +From: Giuseppe Iuculano <iuculano@debian.org> +Date: Thu, 27 Sep 2018 19:03:07 +0800 +Subject: _use-smartd-runner-by-default + +--- + smartd.conf | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/smartd.conf ++++ b/smartd.conf +@@ -14,9 +14,9 @@ + # ATA and SCSI devices. DEVICESCAN may be followed by any of the + # Directives listed below, which will be applied to all devices that + # are found. Most users should comment out DEVICESCAN and explicitly + # list the devices that they wish to monitor. +-DEVICESCAN ++DEVICESCAN -n standby -m root -M exec /usr/share/smartmontools/smartd-runner + + # Alternative setting to ignore temperature and power-on hours reports + # in syslog. + #DEVICESCAN -I 194 -I 231 -I 9 diff --git a/debian/patches/61_cciss-doc.patch b/debian/patches/61_cciss-doc.patch new file mode 100644 index 0000000..db56950 --- /dev/null +++ b/debian/patches/61_cciss-doc.patch @@ -0,0 +1,46 @@ +From: Giuseppe Iuculano <iuculano@debian.org> +Date: Thu, 27 Sep 2018 19:03:07 +0800 +Subject: Update cciss examples/docs + +Here is a patch that adds examples for cciss to the default smartd.conf +file and adds some more cciss documentation to the manpages. I think this +patch gets things to parity with the 3ware documentation with a couple +minor exceptions + +Refreshed by jmtd@debian.org 2018-08-10 +Refreshed by nirgal@debian.org 2019-09-17 +--- + smartd.conf | 6 ++++++ + smartd.conf.5.in | 10 ++++++++++ + 2 files changed, 16 insertions(+) + +--- a/smartd.conf.5.in ++++ b/smartd.conf.5.in +@@ -164,8 +164,14 @@ + /dev/sda \-d cciss,1 \-a \-s (L/../../7/03|S/../.././03) \-m root + .\" %ENDIF OS Linux + .\" %IF OS FreeBSD Linux + # ++# Monitor 2 disks connected to the first HP SmartArray controller which ++# uses the cciss driver. Start long tests on Sunday nights and short ++# self-tests every night and send errors to root ++# \ /dev/sda -d cciss,0 -a -s (L/../../7/02|S/../.././02) -m root ++# \ /dev/sda -d cciss,1 -a -s (L/../../7/03|S/../.././03) -m root ++# + # Three SATA disks on a HighPoint RocketRAID controller. + # Start short self\-tests daily between 1\-2, 2\-3, and + # 3\-4 am. + .\" %ENDIF OS FreeBSD Linux +@@ -231,8 +237,12 @@ + # + ################################################ + .Ve + .Sp ++.B If a cciss controller is used ++then the corresponding block device (/dev/sd?) must be listed, ++along with the \'\-d cciss,N\' Directive (see below). ++.TP + .SH DEVICESCAN + If a non-comment entry in the configuration file is the text string + .B DEVICESCAN + in capital letters, then diff --git a/debian/patches/63_removable.patch b/debian/patches/63_removable.patch new file mode 100644 index 0000000..048fa52 --- /dev/null +++ b/debian/patches/63_removable.patch @@ -0,0 +1,24 @@ +From: Giuseppe Iuculano <iuculano@debian.org> +Date: Thu, 27 Sep 2018 19:03:07 +0800 +Subject: _removable + +Added the removable option by default. This indicates to smartd that it should continue if the device does not appear to be present when smartd is started. + +Closes: #406130 +--- + smartd.conf | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/smartd.conf ++++ b/smartd.conf +@@ -14,9 +14,9 @@ + # ATA and SCSI devices. DEVICESCAN may be followed by any of the + # Directives listed below, which will be applied to all devices that + # are found. Most users should comment out DEVICESCAN and explicitly + # list the devices that they wish to monitor. +-DEVICESCAN -n standby -m root -M exec /usr/share/smartmontools/smartd-runner ++DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner + + # Alternative setting to ignore temperature and power-on hours reports + # in syslog. + #DEVICESCAN -I 194 -I 231 -I 9 diff --git a/debian/patches/manpage.diff b/debian/patches/manpage.diff new file mode 100644 index 0000000..ca99941 --- /dev/null +++ b/debian/patches/manpage.diff @@ -0,0 +1,22 @@ +From: Giuseppe Iuculano <iuculano@debian.org> +Date: Thu, 27 Sep 2018 19:03:07 +0800 +Subject: manpage + +Fixed example path in man pages +--- + smartd.conf.5.in | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/smartd.conf.5.in ++++ b/smartd.conf.5.in +@@ -1776,9 +1776,9 @@ + /sbin/shutdown \-hf now + .Ve + .Sp + Some example scripts are distributed with the smartmontools package, +-in /usr/local/share/doc/smartmontools/examplescripts/. ++in /usr/local/share/doc/smartmontools/examples/. + .Sp + Please note that these scripts typically run as root, so any files + that they read/write should not be writable by ordinary users or + reside in directories like /tmp that are writable by ordinary users diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 0000000..5914327 --- /dev/null +++ b/debian/patches/series @@ -0,0 +1,6 @@ +52_remove-pragma.diff +53_use-smartd-runner-by-default.diff +61_cciss-doc.patch +63_removable.patch +manpage.diff +service-alias.patch diff --git a/debian/patches/service-alias.patch b/debian/patches/service-alias.patch new file mode 100644 index 0000000..dd36803 --- /dev/null +++ b/debian/patches/service-alias.patch @@ -0,0 +1,13 @@ +Last-Update: 2019-10-10 +Forwarded: not-needed +Author: Dmitry Smirnov <onlyjob@debian.org> +Description: register service alias, as per original service name. + +--- a/smartd.service.in ++++ b/smartd.service.in +@@ -13,4 +13,5 @@ + ExecReload=/bin/kill -HUP $MAINPID + + [Install] + WantedBy=multi-user.target ++Alias=smartd.service diff --git a/debian/rules b/debian/rules new file mode 100755 index 0000000..92bce4f --- /dev/null +++ b/debian/rules @@ -0,0 +1,73 @@ +#!/usr/bin/make -f +# Sample debian/rules that uses debhelper. +# GNU copyright 1997 to 1999 by Joey Hess. + +# Uncomment this to turn on verbose mode. +#export DH_VERBOSE=1 + +export DEB_BUILD_MAINT_OPTIONS = hardening=+all +DPKG_EXPORT_BUILDFLAGS = 1 +include /usr/share/dpkg/buildflags.mk + +DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) + +ifeq ($(DEB_HOST_ARCH_OS),linux) + CONFIGURE_ARGS += --with-selinux + CONFIGURE_ARGS += --with-systemdenvfile=/etc/default/smartmontools + CONFIGURE_ARGS += --with-systemdsystemunitdir=/usr/lib/systemd/system + CONFIGURE_ARGS += --with-libsystemd=auto +endif + +ifeq ($(DEB_HOST_ARCH_OS),kfreebsd) + CFLAGS += -I/usr/include/freebsd +endif + +CFLAGS += -fsigned-char -Wall + +%: + dh $@ + +override_dh_autoreconf: + dh_autoreconf + ./autogen.sh + +override_dh_auto_configure: + CFLAGS="${CFLAGS}" CXXFLAGS="${CFLAGS}" \ + dh_auto_configure -- \ + --build=$(DEB_BUILD_GNU_TYPE) \ + --host=$(DEB_HOST_GNU_TYPE) \ + --prefix=/usr \ + --sysconfdir=/etc \ + --mandir=/usr/share/man \ + --with-initscriptdir=no \ + --docdir=/usr/share/doc/smartmontools \ + --with-attributelog=/var/lib/smartmontools/attrlog. \ + --with-drivedbinstdir=/usr/share/smartmontools \ + --with-drivedbdir=/var/lib/smartmontools/drivedb \ + --with-exampledir=/usr/share/doc/smartmontools/examples/ \ + --with-savestates=/var/lib/smartmontools/smartd. \ + --with-smartdplugindir=/etc/smartmontools/smartd_warning.d \ + --with-smartdscriptdir=/usr/share/smartmontools \ + ${CONFIGURE_ARGS} \ + ; + +override_dh_installinit: + dh_installinit --no-start + +override_dh_install: + dh_install + $(RM) -v \ + debian/smartmontools/lib/systemd/system/smartd.service \ + debian/smartmontools/usr/share/doc/smartmontools/ChangeLog \ + debian/smartmontools/usr/share/doc/smartmontools/COPYING \ + debian/smartmontools/usr/share/doc/smartmontools/INSTALL \ + debian/smartmontools/usr/share/doc/smartmontools/TODO \ + ; + +override_dh_fixperms: + dh_fixperms + chmod -c 755 \ + $(CURDIR)/debian/smartmontools/etc/smartmontools/run.d/10mail \ + $(CURDIR)/debian/smartmontools/usr/share/smartmontools/smartd-runner \ + ; diff --git a/debian/smartd-runner b/debian/smartd-runner new file mode 100644 index 0000000..218da39 --- /dev/null +++ b/debian/smartd-runner @@ -0,0 +1,10 @@ +#!/bin/bash -e + +tmp=$(mktemp) +cat >$tmp + +run-parts --report --lsbsysinit --arg=$tmp --arg="$1" \ + --arg="$2" --arg="$3" -- /etc/smartmontools/run.d + +rm -f $tmp + diff --git a/debian/smartmontools.bug-presubj b/debian/smartmontools.bug-presubj new file mode 100644 index 0000000..2b056fc --- /dev/null +++ b/debian/smartmontools.bug-presubj @@ -0,0 +1,4 @@ +If bug is not specific to Debian then please consider reporting it directly +to upstream developers: + + https://www.smartmontools.org/report diff --git a/debian/smartmontools.default b/debian/smartmontools.default new file mode 100644 index 0000000..6a8a6e2 --- /dev/null +++ b/debian/smartmontools.default @@ -0,0 +1,9 @@ +# Defaults for smartmontools initscript (/etc/init.d/smartmontools) +# This is a POSIX shell fragment + +# List of devices you want to explicitly enable S.M.A.R.T. for +# Not needed (and not recommended) if the device is monitored by smartd +#enable_smart="/dev/hda /dev/hdb" + +# uncomment to pass additional options to smartd on startup +#smartd_opts="--interval=1800" diff --git a/debian/smartmontools.dirs b/debian/smartmontools.dirs new file mode 100644 index 0000000..43ec7da --- /dev/null +++ b/debian/smartmontools.dirs @@ -0,0 +1 @@ +/var/lib/smartmontools/drivedb diff --git a/debian/smartmontools.init b/debian/smartmontools.init new file mode 100644 index 0000000..7584d02 --- /dev/null +++ b/debian/smartmontools.init @@ -0,0 +1,123 @@ +#!/bin/sh -e +# +# smartmontools init.d startup script +# +# (C) 2003,04,07 Guido Günther <agx@sigxcpu.org> +# +# loosely based on the init script that comes with smartmontools which is +# copyrighted 2002 by Bruce Allen <smartmontools-support@lists.sourceforge.net> +# +### BEGIN INIT INFO +# Provides: smartmontools +# Required-Start: $syslog $remote_fs +# Required-Stop: $syslog $remote_fs +# Default-Start: 2 3 4 5 +# Default-Stop: 0 1 6 +# Short-Description: SMART monitoring daemon +### END INIT INFO + +SMARTCTL=/usr/sbin/smartctl +DAEMON=/usr/sbin/smartd +PIDFILE=/var/run/smartd.pid +[ -x $SMARTCTL ] || exit 0 +[ -x $DAEMON ] || exit 0 +. /lib/lsb/init-functions + +RET=0 + +[ -r /etc/default/rcS ] && . /etc/default/rcS +[ -r /etc/default/smartmontools ] && . /etc/default/smartmontools + +smartd_opts="--pidfile $PIDFILE $smartd_opts" + +enable_smart() { + log_action_begin_msg "Enabling S.M.A.R.T." + for device in $enable_smart; do + log_action_cont_msg "$device" + if ! $SMARTCTL --quietmode=errorsonly --smart=on $device; then + log_action_cont_msg "(failed)" + RET=2 + fi + done + log_action_end_msg 0 +} + +running_pid() +{ + # Check if a given process pid's cmdline matches a given name + pid=$1 + name=$2 + [ -z "$pid" ] && return 1 + [ ! -d /proc/$pid ] && return 1 + cmd=`cat /proc/$pid/cmdline | tr "\000" "\n"|head -n 1 |cut -d : -f 1` + # Is this the expected child? + [ "$cmd" != "$name" ] && return 1 + return 0 +} + +running() +{ +# Check if the process is running looking at /proc +# (works for all users) + # No pidfile, probably no daemon present + [ ! -f "$PIDFILE" ] && return 1 + # Obtain the pid and check it against the binary name + pid=`cat $PIDFILE` + running_pid $pid $DAEMON || return 1 + return 0 +} + +case "$1" in + start) + [ -n "$enable_smart" ] && enable_smart + log_daemon_msg "Starting S.M.A.R.T. daemon" "smartd" + if running; then + log_progress_msg "already running" + log_end_msg 0 + exit 0 + fi + rm -f $PIDFILE + if start-stop-daemon --start --quiet --pidfile $PIDFILE \ + --exec $DAEMON -- $smartd_opts; then + log_end_msg 0 + else + log_end_msg 1 + RET=1 + fi + ;; + stop) + log_daemon_msg "Stopping S.M.A.R.T. daemon" "smartd" + start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE + log_end_msg 0 + ;; + reload|force-reload) + log_daemon_msg "Reloading S.M.A.R.T. daemon" "smartd" + if start-stop-daemon --stop --quiet --signal 1 \ + --pidfile $PIDFILE; then + log_end_msg 0 + else + log_end_msg 1 + RET=1 + fi + ;; + restart) + log_daemon_msg "Restarting S.M.A.R.T. daemon" "smartd" + start-stop-daemon --stop --quiet --oknodo --retry 30 --pidfile $PIDFILE + rm -f $PIDFILE + if start-stop-daemon --start --quiet --pidfile $PIDFILE \ + --exec $DAEMON -- $smartd_opts; then + log_end_msg 0 + else + log_end_msg 1 + RET=1 + fi + ;; + status) + status_of_proc $DAEMON smartd && exit 0 || exit $? + ;; + *) + echo "Usage: /etc/init.d/smartmontools {start|stop|restart|reload|force-reload|status}" + exit 1 +esac + +exit $RET diff --git a/debian/smartmontools.install b/debian/smartmontools.install new file mode 100644 index 0000000..14bc3ad --- /dev/null +++ b/debian/smartmontools.install @@ -0,0 +1,2 @@ +debian/smartd-runner usr/share/smartmontools +debian/10mail etc/smartmontools/run.d diff --git a/debian/smartmontools.lintian-overrides b/debian/smartmontools.lintian-overrides new file mode 100644 index 0000000..8672816 --- /dev/null +++ b/debian/smartmontools.lintian-overrides @@ -0,0 +1,3 @@ +# Full stop at end of synopsis is OK - it doesn't end a sentence but is part of +# an abbreviation. +smartmontools: synopsis-is-a-sentence diff --git a/debian/smartmontools.maintscript b/debian/smartmontools.maintscript new file mode 100644 index 0000000..6b5e6a7 --- /dev/null +++ b/debian/smartmontools.maintscript @@ -0,0 +1,3 @@ +rm_conffile /etc/smartd_warning.sh 6.3+svn4002-2~ +rm_conffile /etc/init.d/smartd 6.1+svn3812-1~ +rm_conffile /etc/smartmontools/run.d/10powersave-notify 7.0~ diff --git a/debian/smartmontools.postinst b/debian/smartmontools.postinst new file mode 100644 index 0000000..bc04f19 --- /dev/null +++ b/debian/smartmontools.postinst @@ -0,0 +1,15 @@ +#!/bin/sh +set -e + +# Remove shutdown and reboot links; this init script does not need them. +case "$1" in + configure) + if [ -x "$(command -v update-smart-drivedb)" ]; then + update-smart-drivedb --install + else + cp -f /usr/share/smartmontools/drivedb.h /var/lib/smartmontools/drivedb/ + fi + ;; +esac + +#DEBHELPER# diff --git a/debian/smartmontools.postrm b/debian/smartmontools.postrm new file mode 100644 index 0000000..8790b1d --- /dev/null +++ b/debian/smartmontools.postrm @@ -0,0 +1,15 @@ +#!/bin/sh +set -e + +case "$1" in + purge) + if [ -d /var/lib/smartmontools ] ; then + rm -rf /var/lib/smartmontools + fi + ;; + +esac + +#DEBHELPER# + +exit 0 diff --git a/debian/smartmontools.service b/debian/smartmontools.service new file mode 120000 index 0000000..ab1d1d1 --- /dev/null +++ b/debian/smartmontools.service @@ -0,0 +1 @@ +../smartd.service
\ No newline at end of file diff --git a/debian/source/format b/debian/source/format new file mode 100644 index 0000000..163aaf8 --- /dev/null +++ b/debian/source/format @@ -0,0 +1 @@ +3.0 (quilt) diff --git a/debian/source/lintian-overrides b/debian/source/lintian-overrides new file mode 100644 index 0000000..d6b3c58 --- /dev/null +++ b/debian/source/lintian-overrides @@ -0,0 +1,2 @@ +## False-positive: +source-is-missing [debian/badblockhowto.html] diff --git a/debian/upstream/metadata b/debian/upstream/metadata new file mode 100644 index 0000000..577740b --- /dev/null +++ b/debian/upstream/metadata @@ -0,0 +1,4 @@ +--- +Archive: SourceForge +Bug-Database: http://www.smartmontools.org/wiki/Help +Repository: https://svn.code.sf.net/p/smartmontools/code/ diff --git a/debian/upstream/signing-key.asc b/debian/upstream/signing-key.asc new file mode 100644 index 0000000..a612392 --- /dev/null +++ b/debian/upstream/signing-key.asc @@ -0,0 +1,29 @@ +-----BEGIN PGP PUBLIC KEY BLOCK----- + +mQINBF/gs9YBEADyn0P5OLnlgjujm1VsVyltEqFm3iOtniHoeiUAZYhBdG0b9gQE +G/NFMtyd5h9WY4ZWUu3rlD30cHKK52IHz1zvHFoscz+T32hBAPN6xG+990PCRtZ7 +9qZRt6KlfV/7gCQk31W5BBUOaQaquhP5Ud1m+VFUjShta4r0bXya00PZvfI02Ky2 +l+9mwrD5FsGP3ri7Yf81Lx2xLmiW2BwphDYmqJ0uzGBKeJgi5myUjqTbfWTRAsaX +ji0n570Pd6xtEvCjWdPU7q+/3XmD8rIoizOB0ChGoLLQc5cjNCzAeuiExFd9ule2 +RomO+czylB2rsmxbw2vUlkcZ2LmRBvZskMAZWmc0z9LGnGQA9RZZFyEOTC10cC69 +YMae5JHp+veS/2qw/5UOsR6RfbT+BUPLLJW+/RrUvgfxs36oG/DCxSNqrQpRuvlk +gGsmrl+W8s+pxL8dn5F1W4mkkiR6g5P5xVrYckkQnXblQL8qAVtBLFClvyme9ilf +ZzeGpamk8+m/8P1omlnfJjMTXueWz47+XXFLj37+lnWhRo+B+u7orphTUCYi7zYy +fYYXQcZsT2j+804aKTRyNDksoaAp1fa6oqOvBkkHq/FlkIDsxfCbF++WFgRZZfyK +R8HAdn9MrRkSWjUoJLVd+1EEr3OZYk/lYhOFYfwlGpuY5VPmkRxfS2FSOQARAQAB +tFJTbWFydG1vbnRvb2xzIFNpZ25pbmcgS2V5ICh0aHJvdWdoIDIwMjUpIDxzbWFy +dG1vbnRvb2xzLXN1cHBvcnRAbGlzdGkuanBiZXJsaW4uZGU+iQI+BBMBAgAoBQJf +4LPWAhsDBQkJdIIABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRAKMIEu/zrv +9VjhEADLuXMN7pRyOj9sMcio72fI2rmATxawd3vxWuW6aaGqwJlO78r7yxTI7Myi +EmZ4qCJWvR7/98t/1NXPDB1mMedicVcLl154EyJeeYhWJxtKe95yuib5lSlJmGTu +gue/n1dbIIqPSd4v3s8Y7DUpsjnebnShqXSoSXhq3hGpcL3cYsL1M0+4vEweHEeN +aE2URjb2eaQMYBvI25upH+cQ5YEa3X5XpCv72oAJvgGJFckAKUasuDMAYxWNenJw +quREHffotRtOOycdET2as3dapF8NuZXUJTPJBX76ctAng6UF5B4uqn/e9+j8Ch40 +SJkg/Em0xNmNeu790HPkQxlpoPyRv8HNpaWZb2JLqPhGFVruiIBDKq3jXCWNpjba +g2ZYM+eHXyWg/w5OkDfeEnlBo7d3AhuE5b3k1GQgcyob1yt0QAUiDRUW3AlBSRQo +LJAorU+QEoTQR2uUOWbk51Kecoyd1YEPbcbIpEQASddDxyzgsipFcKRszUDBYSYs +bZIR1mp1QUQ6SX2/Vi7xyBGrCRnv8S7SWLISQp2wgI7qEqRG7S+0NEyDn87ju7q5 +MxAk99iCTBBSWk95q1e9uf5tFJO5deWfwNlWTIGWK9nvJt1VGLGr+oZ4qe2aBC8K +lLWNbng9PX/1L1WIAUvYa4xooXClGC6nthrC381A6d93/mG0uQ== +=D1Nc +-----END PGP PUBLIC KEY BLOCK----- diff --git a/debian/watch b/debian/watch new file mode 100644 index 0000000..b27120f --- /dev/null +++ b/debian/watch @@ -0,0 +1,10 @@ +# watch control file for uscan +# See uscan(1) for format +version=4 + +opts="\ +pgpmode=default,\ +repack,compression=xz,\ +uversionmangle=s{\-}{.}g,\ +pgpsigurlmangle=s/$/.asc/\ +" https://sf.net/smartmontools/smartmontools-(\d[\d.]+)\.tar\.(?:gz|xz|bz2) |