Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.hardware > #786
| Date | 2011-11-07 23:10 -0800 |
|---|---|
| From | Ant <ant@zimage.comANT> |
| Organization | An Ant Farm |
| Newsgroups | comp.os.linux.hardware |
| Subject | Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? |
| References | <L-6dnVJjDMsKtivTnZ2dnUVZ_r0AAAAA@earthlink.com> <9hnbdlFj3jU1@mid.individual.net> <4EB6C9DF.6010607@t-online.de> <CcSdnfUbN7B7piXTnZ2dnUVZ_sGdnZ2d@earthlink.com> |
| Message-ID | <M_ydnYfNHtZSSCXTnZ2dnUVZ_vGdnZ2d@earthlink.com> (permalink) |
On 11/7/2011 12:13 PM PT, Ant typed:
>>>> Device: /dev/sdb [SAT], Failed SMART usage Attribute: 9 Power_On_Hours.
>>>> For details see host's SYSLOG.
>>>> You can also use the smartctl utility for further investigation.
>>>> Another email message will be sent in 24 hours if the problem persists.
>
>> You can add '-i 9' to the smartd.conf entry for this device to suppress
>> future warning mails.
>
> OK. I just got another e-mail about it this morning. I assume it will
> keep doing that daily until I stop using that old school IDE/PATA HDD.
> :( So, I will tell it to stop telling me about it then.
>
> Do I just add "/dev/sdb -i 9" line (without quotation marks) to the
> bottom of my /etc/smartd.conf file? I am not sure if that is correct or
> not. :)
Hmm, that didn't work and I just got another e-mail about it. Here's
what my smartd.conf file looks like in case I did it wrong or whatever:
$ cat /etc/smartd.conf
# Sample configuration file for smartd. See man smartd.conf.
# Home page is: http://smartmontools.sourceforge.net
# smartd will re-read the configuration file if it receives a HUP
# signal
# The file gives a list of devices to monitor using smartd, with one
# device per line. Text after a hash (#) is ignored, and you may use
# spaces and tabs for white space. You may use '\' to continue lines.
# You can usually identify which hard disks are on your system by
# looking in /proc/ide and in /proc/scsi.
# The word DEVICESCAN will cause any remaining lines in this
# configuration file to be ignored: it tells smartd to scan for all
# 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 -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
# Alternative setting to report more useful raw temperature in syslog.
#DEVICESCAN -R 194 -R 231 -I 9
# Alternative setting to report raw temperature changes >= 5 Celsius
# and min/max temperatures.
#DEVICESCAN -I 194 -I 231 -I 9 -W 5
# First (primary) ATA/IDE hard disk. Monitor all attributes, enable
# automatic online data collection, automatic Attribute autosave, and
# start a short self-test every day between 2-3am, and a long self test
# Saturdays between 3-4am.
#/dev/hda -a -o on -S on -s (S/../.././02|L/../../6/03)
# Monitor SMART status, ATA Error Log, Self-test log, and track
# changes in all attributes except for attribute 194
#/dev/hdb -H -l error -l selftest -t -I 194
# Monitor all attributes except normalized Temperature (usually 194),
# but track Temperature changes >= 4 Celsius, report Temperatures
# >= 45 Celsius and changes in Raw value of Reallocated_Sector_Ct (5).
# Send mail on SMART failures or when Temperature is >= 55 Celsius.
#/dev/hdc -a -I 194 -W 4,45,55 -R 5 -m admin@example.com
# An ATA disk may appear as a SCSI device to the OS. If a SCSI to
# ATA Translation (SAT) layer is between the OS and the device then
# this can be flagged with the '-d sat' option. This situation may
# become common with SATA disks in SAS and FC environments.
# /dev/sda -a -d sat
# A very silent check. Only report SMART health status if it fails
# But send an email in this case
#/dev/hdc -H -C 0 -U 0 -m admin@example.com
# First two SCSI disks. This will monitor everything that smartd can
# monitor. Start extended self-tests Wednesdays between 6-7pm and
# Sundays between 1-2 am
#/dev/sda -d scsi -s L/../../3/18
#/dev/sdb -d scsi -s L/../../7/01
# Monitor 4 ATA disks connected to a 3ware 6/7/8000 controller which uses
# the 3w-xxxx driver. Start long self-tests Sundays between 1-2, 2-3, 3-4,
# and 4-5 am.
# NOTE: starting with the Linux 2.6 kernel series, the /dev/sdX interface
# is DEPRECATED. Use the /dev/tweN character device interface instead.
# For example /dev/twe0, /dev/twe1, and so on.
#/dev/sdc -d 3ware,0 -a -s L/../../7/01
#/dev/sdc -d 3ware,1 -a -s L/../../7/02
#/dev/sdc -d 3ware,2 -a -s L/../../7/03
#/dev/sdc -d 3ware,3 -a -s L/../../7/04
# Monitor 2 ATA disks connected to a 3ware 9000 controller which
# uses the 3w-9xxx driver (Linux, FreeBSD). Start long self-tests Tuesdays
# between 1-2 and 3-4 am.
#/dev/twa0 -d 3ware,0 -a -s L/../../2/01
#/dev/twa0 -d 3ware,1 -a -s L/../../2/03
# Monitor 2 SATA (not SAS) disks connected to a 3ware 9000 controller which
# uses the 3w-sas driver (Linux, FreeBSD). Start long self-tests Tuesdays
# between 1-2 and 3-4 am.
#/dev/twl0 -d 3ware,0 -a -s L/../../2/01
#/dev/twa0 -d 3ware,1 -a -s L/../../2/03
# Same as above for Windows. Option '-d 3ware,N' is not necessary,
# disk (port) number is specified in device name.
# NOTE: On Windows, DEVICESCAN works also for 3ware controllers.
#/dev/hdc,0 -a -s L/../../2/01
#/dev/hdc,1 -a -s L/../../2/03
#
# 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/cciss/c0d0 -d cciss,0 -a -s (L/../../7/02|S/../.././02) -m root
#/dev/cciss/c0d0 -d cciss,1 -a -s (L/../../7/03|S/../.././03) -m root
# Monitor 3 ATA disks directly connected to a HighPoint RocketRAID.
Start long
# self-tests Sundays between 1-2, 2-3, and 3-4 am.
#/dev/sdd -d hpt,1/1 -a -s L/../../7/01
#/dev/sdd -d hpt,1/2 -a -s L/../../7/02
#/dev/sdd -d hpt,1/3 -a -s L/../../7/03
# Monitor 2 ATA disks connected to the same PMPort which connected to the
# HighPoint RocketRAID. Start long self-tests Tuesdays between 1-2 and
3-4 am
#/dev/sdd -d hpt,1/4/1 -a -s L/../../2/01
#/dev/sdd -d hpt,1/4/2 -a -s L/../../2/03
# HERE IS A LIST OF DIRECTIVES FOR THIS CONFIGURATION FILE.
# PLEASE SEE THE smartd.conf MAN PAGE FOR DETAILS
#
# -d TYPE Set the device type: ata, scsi, marvell, removable, 3ware,N,
hpt,L/M/N
# -T TYPE set the tolerance to one of: normal, permissive
# -o VAL Enable/disable automatic offline tests (on/off)
# -S VAL Enable/disable attribute autosave (on/off)
# -n MODE No check. MODE is one of: never, sleep, standby, idle
# -H Monitor SMART Health Status, report if failed
# -l TYPE Monitor SMART log. Type is one of: error, selftest
# -f Monitor for failure of any 'Usage' Attributes
# -m ADD Send warning email to ADD for -H, -l error, -l selftest, and -f
# -M TYPE Modify email warning behavior (see man page)
# -s REGE Start self-test when type/date matches regular expression
(see man page)
# -p Report changes in 'Prefailure' Normalized Attributes
# -u Report changes in 'Usage' Normalized Attributes
# -t Equivalent to -p and -u Directives
# -r ID Also report Raw values of Attribute ID with -p, -u or -t
# -R ID Track changes in Attribute ID Raw value with -p, -u or -t
# -i ID Ignore Attribute ID for -f Directive
# -I ID Ignore Attribute ID for -p, -u or -t Directive
# -C ID Report if Current Pending Sector count non-zero
# -U ID Report if Offline Uncorrectable count non-zero
# -W D,I,C Monitor Temperature D)ifference, I)nformal limit, C)ritical
limit
# -v N,ST Modifies labeling of Attribute N (see man page)
# -a Default: equivalent to -H -f -t -l error -l selftest -C 197
-U 198
# -F TYPE Use firmware bug workaround. Type is one of: none, samsung
# -P TYPE Drive-specific presets: use, ignore, show, showall
# # Comment: text after a hash sign is ignored
# \ Line continuation character
# Attribute ID is a decimal integer 1 <= ID <= 255
# except for -C and -U, where ID = 0 turns them off.
# All but -d, -m and -M Directives are only implemented for ATA devices
#
# If the test string DEVICESCAN is the first uncommented text
# then smartd will scan for devices /dev/hd[a-l] and /dev/sd[a-z]
# DEVICESCAN may be followed by any desired Directives.
/dev/sdb -i 9
--
"Look not to the windmill's turning while the ant still burrows." --unknown
/\___/\ Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.
Back to comp.os.linux.hardware | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
"Failed SMART usage Attribute: 9 Power_On_Hours."? Ant <ant@zimage.comANT> - 2011-11-05 23:39 -0700
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Arno <me@privacy.net> - 2011-11-06 12:04 +0000
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Christian Franke <Christian.Franke@t-online.de> - 2011-11-06 18:54 +0100
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? ANTant@zimage.com (Ant) - 2011-11-07 14:13 -0600
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Ant <ant@zimage.comANT> - 2011-11-07 23:10 -0800
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Bill Marcum <bill@lat.localnet> - 2011-11-09 11:42 -0500
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Ant <ant@zimage.comANT> - 2011-11-10 06:36 -0800
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? "Rod Speed" <rod.speed.aaa@gmail.com> - 2011-11-07 06:33 +1100
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? (thanks!) Ant <ant@zimage.comANT> - 2011-11-06 12:19 -0800
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? philo <philo@invalid.not> - 2011-11-06 20:40 -0600
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? J G Miller <miller@yoyo.ORG> - 2011-11-07 12:57 +0000
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Winniethepooh@100acrewoods.org (GMAN) - 2011-11-07 15:26 +0000
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? J G Miller <miller@yoyo.ORG> - 2011-11-07 15:32 +0000
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2011-11-07 07:39 -0800
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? J G Miller <miller@yoyo.ORG> - 2011-11-07 16:17 +0000
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2011-11-07 08:33 -0800
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Kevin Snodgrass <kdsnodgrass@yahoo.com> - 2011-11-07 19:01 +0000
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? J G Miller <miller@yoyo.ORG> - 2011-11-07 20:20 +0000
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? ANTant@zimage.com (Ant) - 2011-11-07 14:27 -0600
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? J G Miller <miller@yoyo.ORG> - 2011-11-08 10:17 +0000
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Ant <ant@zimage.comANT> - 2011-11-09 05:53 -0800
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? J G Miller <miller@yoyo.ORG> - 2011-11-09 15:03 +0000
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Ant <ant@zimage.comANT> - 2011-11-10 06:30 -0800
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Winniethepooh@100acrewoods.org (GMAN) - 2011-11-07 19:30 +0000
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2011-11-07 07:37 -0800
Re: "Failed SMART usage Attribute: 9 Power_On_Hours."? ANTant@zimage.com (Ant) - 2011-11-07 14:02 -0600
csiph-web