public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: caglar@pardus.org.tr
Cc: Robert Hancock <hancockr@shaw.ca>, Tejun Heo <htejun@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: SATA exceptions
Date: Wed, 11 Jul 2007 16:31:23 -0400	[thread overview]
Message-ID: <46953E1B.1090306@rtr.ca> (raw)
In-Reply-To: <200707080035.05718.caglar@pardus.org.tr>

S.Çag(lar Onur wrote:
> Hi;
> 
> 07 Tem 2007 Cts tarihinde, Robert Hancock şunları yazmıştı: 
>> It's not the free space on the drive that matters, it's the number of
>> free sectors in the spare sector pool on the drive, which is invisible
>> to software.
>>
>> Your SMART log shows 309 reallocated sectors. That seems somewhat high..
> 
> Ah sorry to misinterpret the content:), its a quiet new piece of hardware (at 
> most ~1.5 month old) and  "Reallocated_Event_Count" constantly increases 
> (currently its increased to 313) and although i'm not 100 percent sure these 
> errors only occured with kernels > 2.6.18 (or 2.6.18 didn't report these 
> cause according to kern.log these only visible with 2.6.22+) 
> 
> We bought 3 HP Pavillon dv2385ea and one of them only runs with 2.6.18 and its 
> smartctl output follows as a reference;
> 
> smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
> 
> === START OF INFORMATION SECTION ===
> Device Model:     SAMSUNG HM160JI
> Serial Number:    S0W6J10P331479
> Firmware Version: AD100-16
> User Capacity:    160.041.885.696 bytes
> Device is:        In smartctl database [for details use: -P show]
> ATA Version is:   7
> ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
> Local Time is:    Sun Jul  8 00:22:21 2007 EEST
> 
> ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for 
> details.
> 
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
> 
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
> See vendor-specific Attribute list for marginal Attributes.
> 
> General SMART Values:
> Offline data collection status:  (0x00)	Offline data collection activity
> 					was never started.
> 					Auto Offline Data Collection: Disabled.
> Self-test execution status:      (   0)	The previous self-test routine 
> completed
> 					without error or no self-test has ever 
> 					been run.
> Total time to complete Offline 
> data collection: 		 (5391) seconds.
> Offline data collection
> capabilities: 			 (0x51) SMART execute Offline immediate.
> 					No Auto Offline data collection support.
> 					Suspend Offline collection upon new
> 					command.
> 					No Offline surface scan supported.
> 					Self-test supported.
> 					No Conveyance Self-test supported.
> 					Selective Self-test supported.
> SMART capabilities:            (0x0003)	Saves SMART data before entering
> 					power-saving mode.
> 					Supports SMART auto save timer.
> Error logging capability:        (0x01)	Error logging supported.
> 					General Purpose Logging supported.
> Short self-test routine 
> recommended polling time: 	 (   2) minutes.
> Extended self-test routine
> recommended polling time: 	 (  89) minutes.
> 
> SMART Attributes Data Structure revision number: 16
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  
> WHEN_FAILED RAW_VALUE
>   1 Raw_Read_Error_Rate     0x000f   100   100   051    Pre-fail  
> Always       -       0
>   3 Spin_Up_Time            0x0007   253   253   025    Pre-fail  
> Always       -       2880
>   4 Start_Stop_Count        0x0032   098   098   000    Old_age   
> Always       -       2648
>   5 Reallocated_Sector_Ct   0x0033   253   253   010    Pre-fail  
> Always       -       0
>   7 Seek_Error_Rate         0x000f   253   253   051    Pre-fail  
> Always       -       0
>   8 Seek_Time_Performance   0x0025   253   253   015    Pre-fail  
> Offline      -       0
>   9 Power_On_Hours          0x0032   253   253   000    Old_age   
> Always       -       236
>  10 Spin_Retry_Count        0x0033   100   100   051    Pre-fail  
> Always       -       1
>  11 Calibration_Retry_Count 0x0012   100   100   000    Old_age   
> Always       -       2
>  12 Power_Cycle_Count       0x0032   100   100   000    Old_age   
> Always       -       57
> 187 Unknown_Attribute       0x0032   253   253   000    Old_age   
> Always       -       0
> 188 Unknown_Attribute       0x0032   253   253   000    Old_age   
> Always       -       0
> 190 Temperature_Celsius     0x0022   047   040   040    Old_age   Always   
> In_the_past 1008009269
> 191 G-Sense_Error_Rate      0x0012   100   100   000    Old_age   
> Always       -       5396
> 192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   
> Always       -       40
> 193 Load_Cycle_Count        0x0012   100   100   000    Old_age   
> Always       -       2575
> 194 Temperature_Celsius     0x0022   047   040   000    Old_age   
> Always       -       53 (Lifetime Min/Max 0/15381)
> 195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   
> Always       -       98037
> 196 Reallocated_Event_Count 0x0032   253   253   000    Old_age   
> Always       -       0
> 197 Current_Pending_Sector  0x0012   253   253   000    Old_age   
> Always       -       0
> 198 Offline_Uncorrectable   0x0030   253   253   000    Old_age   
> Offline      -       0
> 199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   
> Always       -       0
> 200 Multi_Zone_Error_Rate   0x000a   100   100   000    Old_age   
> Always       -       0
> 201 Soft_Read_Error_Rate    0x0012   253   253   000    Old_age   
> Always       -       0
> 223 Load_Retry_Count        0x0012   100   100   000    Old_age   
> Always       -       2
> 225 Load_Cycle_Count        0x0012   100   100   000    Old_age   
> Always       -       2575
> 255 Unknown_Attribute       0x000a   253   100   000    Old_age   
> Always       -       0
..

I'm not even sure how to interpret those numbers.
It seems rather odd that nearly all fields are either "100" or "253",
so those are probably pre-programmed numbers rather than actual counts.
The raw value at the end of the line (for the various "Reallocated*" fields)
is probably the real value here.

Tejun ??

  parent reply	other threads:[~2007-07-11 20:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.hBFih6KVHDFsBf6Qfg6XispiIuY@ifi.uio.no>
     [not found] ` <fa.50UJZSgW/ChUl7O1Zks6ydq/1js@ifi.uio.no>
     [not found]   ` <fa.NhBdOmH9+RkW+QO72+TjPRwEKj0@ifi.uio.no>
2007-07-07 18:05     ` SATA exceptions Robert Hancock
2007-07-07 21:35       ` S.Çağlar Onur
2007-07-09 18:37         ` Tejun Heo
2007-07-09 19:06           ` S.Çağlar Onur
2007-07-11 17:20           ` Bill Davidsen
2007-07-12 19:52           ` Pavel Machek
2007-07-13  3:12             ` Tejun Heo
2007-07-13  7:44               ` S.Çağlar Onur
2007-07-11 20:31         ` Mark Lord [this message]
2007-07-12  3:13           ` Tejun Heo
2007-07-05 21:46 S.Çağlar Onur
2007-07-06  1:52 ` Tejun Heo
2007-07-06 11:43   ` S.Çağlar Onur

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46953E1B.1090306@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=caglar@pardus.org.tr \
    --cc=hancockr@shaw.ca \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox