<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Just for the record this is the output from smartctl for one of the
drives:<br>
<br>
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-12-generic]
(local build)<br>
Copyright (C) 2002-11 by Bruce Allen,
<a class="moz-txt-link-freetext" href="http://smartmontools.sourceforge.net">http://smartmontools.sourceforge.net</a><br>
<br>
=== START OF INFORMATION SECTION ===<br>
Device Model: WDC WD10EARX-00N0YB0<br>
Serial Number: WD-WCC0S0207719<br>
LU WWN Device Id: 5 0014ee 25b70161a<br>
Firmware Version: 51.0AB51<br>
User Capacity: 1,000,204,886,016 bytes [1.00 TB]<br>
Sector Sizes: 512 bytes logical, 4096 bytes physical<br>
Device is: Not in smartctl database [for details use: -P
showall]<br>
ATA Version is: 8<br>
ATA Standard is: Exact ATA specification draft version not
indicated<br>
Local Time is: Wed Dec 21 10:16:06 2011 GMT<br>
SMART support is: Available - device has SMART capability.<br>
SMART support is: Enabled<br>
<br>
=== START OF READ SMART DATA SECTION ===<br>
SMART overall-health self-assessment test result: PASSED<br>
<br>
General SMART Values:<br>
Offline data collection status: (0x85) Offline data collection
activity<br>
was aborted by an interrupting command from
host.<br>
Auto Offline Data Collection: Enabled.<br>
Self-test execution status: ( 0) The previous self-test
routine completed<br>
without error or no self-test has ever <br>
been run.<br>
Total time to complete Offline <br>
data collection: (17760) seconds.<br>
Offline data collection<br>
capabilities: (0x7b) SMART execute Offline immediate.<br>
Auto Offline data collection on/off support.<br>
Suspend Offline collection upon new<br>
command.<br>
Offline surface scan supported.<br>
Self-test supported.<br>
Conveyance Self-test supported.<br>
Selective Self-test supported.<br>
SMART capabilities: (0x0003) Saves SMART data before
entering<br>
power-saving mode.<br>
Supports SMART auto save timer.<br>
Error logging capability: (0x01) Error logging supported.<br>
General Purpose Logging supported.<br>
Short self-test routine <br>
recommended polling time: ( 2) minutes.<br>
Extended self-test routine<br>
recommended polling time: ( 174) minutes.<br>
Conveyance self-test routine<br>
recommended polling time: ( 5) minutes.<br>
SCT capabilities: (0x30b5) SCT Status supported.<br>
SCT Feature Control supported.<br>
SCT Data Table supported.<br>
<br>
SMART Attributes Data Structure revision number: 16<br>
Vendor Specific SMART Attributes with Thresholds:<br>
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE<br>
1 Raw_Read_Error_Rate 0x002f 194 173 051 Pre-fail
Always - 7565<br>
3 Spin_Up_Time 0x0027 118 116 021 Pre-fail
Always - 7100<br>
4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 382<br>
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail
Always - 0<br>
7 Seek_Error_Rate 0x002e 200 200 000 Old_age
Always - 0<br>
9 Power_On_Hours 0x0032 100 100 000 Old_age
Always - 252<br>
10 Spin_Retry_Count 0x0032 100 100 000 Old_age
Always - 0<br>
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age
Always - 0<br>
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 365<br>
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age
Always - 252<br>
193 Load_Cycle_Count 0x0032 200 200 000 Old_age
Always - 1667<br>
194 Temperature_Celsius 0x0022 117 106 000 Old_age
Always - 30<br>
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age
Always - 0<br>
197 Current_Pending_Sector 0x0032 200 200 000 Old_age
Always - 0<br>
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age
Offline - 0<br>
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age
Always - 0<br>
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age
Offline - 0<br>
<br>
SMART Error Log Version: 1<br>
No Errors Logged<br>
<br>
SMART Self-test log structure revision number 1<br>
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error<br>
# 1 Extended offline Completed: read failure 70%
248 566231424<br>
# 2 Short offline Completed without error 00%
247 -<br>
# 3 Extended offline Completed: read failure 70%
242 566231424<br>
# 4 Extended offline Completed: read failure 70%
221 566231424<br>
# 5 Extended offline Completed: read failure 70%
215 566231424<br>
# 6 Extended offline Completed: read failure 70%
213 566231424<br>
# 7 Extended offline Completed: read failure 70%
206 566231424<br>
# 8 Extended offline Completed: read failure 70%
194 566231424<br>
# 9 Conveyance offline Completed without error 00%
189 -<br>
#10 Extended offline Completed: read failure 70%
187 566231424<br>
#11 Short offline Completed without error 00%
150 -<br>
#12 Extended offline Completed: read failure 70%
150 566231424<br>
#13 Short offline Completed without error 00%
149 -<br>
<br>
SMART Selective self-test log data structure revision number 1<br>
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS<br>
1 0 0 Not_testing<br>
2 0 0 Not_testing<br>
3 0 0 Not_testing<br>
4 0 0 Not_testing<br>
5 0 0 Not_testing<br>
Selective self-test flags (0x0):<br>
After scanning selected spans, do NOT read-scan remainder of disk.<br>
If Selective self-test is pending on power-up, resume after 0 minute
delay.<br>
<div class="moz-signature"><br>
<br>
</div>
<br>
On 08/01/12 00:05, PJR wrote:
<blockquote cite="mid:4F08DDD7.6020707@metronet.co.uk" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
The reason I said the discs were 'faulty' was because on running
smartctrl on both discs it terminated with an error, it reported
Read Failures consistently for the same LBA_of_first_error <u>not</u>
because of the Load_Cycle_count value (I mentioned this in my
first post to this thread and the reason the discs have been
returned to the supplier). I was just reporting my
Load_Cycle_count_values since this seemed to be a direction the
thread was going and the info might be useful.<br>
<div class="moz-signature"><br>
</div>
<br>
On 07/01/12 17:28, Simon Hobson wrote:
<blockquote
cite="mid:p06240826cb2e2e8965bb@simon.thehobsons.co.uk"
type="cite">
<pre wrap="">PJR wrote:
</pre>
<blockquote type="cite">
<pre wrap="">My two WDC WD10EARX-00N0YB0 (possibly faulty) drives have:
9 Power_on_Hours 190
193 Load_Cycle_Count 1064
9 Power_on_Hours 175
193 Load_Cycle_Count 1064
I assume, if they weren't faulty this is not good?
</pre>
</blockquote>
<pre wrap="">Why faulty ?
The whole essence of this thread is that these drives have (by
default) very aggressive power saving. If idle for just 8 seconds
they will unload the heads - which I assume means moving them to a
safe zone on the disk and lifting them. After this, I suspect there's
another fairly short timer before they also spin down the drive.
On a typical Unix [like] system, there are frequent disk accesses -
checking this, logging that, etc, etc. So what tends to happen is the
drive goes idle, unloads the heads, the system accesses it so it
loads the heads, rinse and repeat often. So the Load_Cycle_Count
which counts these will increment quite rapidly.
The suggestion is that it better to increase the timeout, so under
normal use they won't unload the heads very often, if at all.
Say you accessed the drive every 30 seconds. On each access, the
drive would load the heads, do the access, then 8 seconds later
unload the heads again. So that's 120 load cycles per hours, or 2880
load cycles per day !
Increase the timeout to a minute or two, and under the same scenario
you'd probably have none.
Which reminds me I need to twiddle with some drives I use for
backups. I bought a SATA card for the old Mac I use to run
Retrospect, but kept getting some rather oddball errors, kernel
panics, and so on. I thought the card might be faulty, but then
twigged ...
I've done a cron job which every minute updates a file on any of the
backup disks that are mounted - which prevents the drive going to
sleep and spinning down. I suspect the load cycle count will be going
up quite nicely on them - up to 1440 per day while the drive isn't
actually being accessed by the backup software.
What was happening was that the backup software accesses the drive to
see what it is, then goes off to find a client - it then scans the
client, does a bit of thinking to decide what files need copying, and
then starts copying files by which time the drive has got bored and
spun down resulting in an error and/or kernel panic.
</pre>
</blockquote>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a>
</pre>
</blockquote>
</body>
</html>