bugmenot

SMART Hardware_ECC_Recovered values

Recommended Posts

BACKGROUND

I run linux and my computer had been up for 43 days so far, then I had a power failure, and in the next morning I power my computer again.

Since it has been a long time, my linux system does a filesystem check.

The fsck process died unexpectadly.

I force another check an reboot.

FYI, the fsck tool keeps a percentage progress bar.

I noticed that the drive seems to get stuck at some points. While it is expected that the fsck process isn't at a constant speed (on some sectors of the disk your have lots of small files, other a few big files), I don't think it's supposed to be that way. I mean, I was left a couple of time holding by breath :(

fsck finishes and no error or bad block was detected.

PROBLEM/DOUBT

I do a check on the SMART values, with smartctl and this value pops up:

ID# ATTRIBUTE_NAME		  FLAG	 VALUE WORST THRESH TYPE	  UPDATED  WHEN_FAILED RAW_VALUE
195 Hardware_ECC_Recovered  0x001a   100   100   000	Old_age   Always	   -	   3866372

Should I be concerned?

EDIT:

I have a SAMSUNG SpinPoint F1 DT series, HD103UJ. 1TB drive.

The SMART values I have for my drive:

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   069   069   011	Pre-fail  Always	   -	   10130
 4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   43
 5 Reallocated_Sector_Ct   0x0033   100   100   010	Pre-fail  Always	   -	   0
 7 Seek_Error_Rate		 0x000f   253   253   051	Pre-fail  Always	   -	   0
 8 Seek_Time_Performance   0x0025   100   100   015	Pre-fail  Offline	  -	   12383
 9 Power_On_Hours		  0x0032   099   099   000	Old_age   Always	   -	   5797
10 Spin_Retry_Count		0x0033   100   100   051	Pre-fail  Always	   -	   0
11 Calibration_Retry_Count 0x0012   100   100   000	Old_age   Always	   -	   0
12 Power_Cycle_Count	   0x0032   100   100   000	Old_age   Always	   -	   43
13 Read_Soft_Error_Rate	0x000e   100   100   000	Old_age   Always	   -	   0
183 Runtime_Bad_Block	   0x0032   100   100   000	Old_age   Always	   -	   0
184 End-to-End_Error		0x0033   100   100   000	Pre-fail  Always	   -	   0
187 Reported_Uncorrect	  0x0032   100   100   000	Old_age   Always	   -	   0
188 Command_Timeout		 0x0032   100   100   000	Old_age   Always	   -	   0
190 Airflow_Temperature_Cel 0x0022   070   042   000	Old_age   Always	   -	   30 (Lifetime Min/Max 14/30)
194 Temperature_Celsius	 0x0022   066   040   000	Old_age   Always	   -	   34 (0 58 36 14)
195 Hardware_ECC_Recovered  0x001a   100   100   000	Old_age   Always	   -	   3866372
196 Reallocated_Event_Count 0x0032   100   100   000	Old_age   Always	   -	   0
197 Current_Pending_Sector  0x0012   100   100   000	Old_age   Always	   -	   0
198 Offline_Uncorrectable   0x0030   100   100   000	Old_age   Offline	  -	   0
199 UDMA_CRC_Error_Count	0x003e   100   100   000	Old_age   Always	   -	   0
200 Multi_Zone_Error_Rate   0x000a   100   100   000	Old_age   Always	   -	   0
201 Soft_Read_Error_Rate	0x000a   100   100   000	Old_age   Always	   -	   0

Edited by bugmenot

Share this post


Link to post
Share on other sites

Thanks for your post, but using a third party service to post here is not what this site is about. Perhaps if you want the advice from this forum you'll consider registering on your own.

Share this post


Link to post
Share on other sites

Welcome to the wonderful world of large capacity drives. The correction unfortunately is 'normal' due to many factors (pathetic Bit error rates; media imperfections (not holding a strong magnetic field); not getting the head aligned close enough to the track to read the field; et al).

Here's a sample from some drives that I have here (all 1TB ones)

---

195 Hardware_ECC_Recovered 0x001a 057 027 000 Old_age Always - 171013308

195 Hardware_ECC_Recovered 0x001a 060 031 000 Old_age Always - 159991661

195 Hardware_ECC_Recovered 0x001a 065 036 000 Old_age Always - 123860779

195 Hardware_ECC_Recovered 0x001a 057 030 000 Old_age Always - 37720032

195 Hardware_ECC_Recovered 0x001a 057 028 000 Old_age Always - 225205302

195 Hardware_ECC_Recovered 0x001a 063 030 000 Old_age Always - 60721690

195 Hardware_ECC_Recovered 0x001a 060 031 000 Old_age Always - 199233436

195 Hardware_ECC_Recovered 0x001a 060 036 000 Old_age Always - 7949073

195 Hardware_ECC_Recovered 0x001a 054 025 000 Old_age Always - 229066473

195 Hardware_ECC_Recovered 0x001a 059 032 000 Old_age Always - 113518138

195 Hardware_ECC_Recovered 0x001a 062 035 000 Old_age Always - 16343214

195 Hardware_ECC_Recovered 0x001a 055 029 000 Old_age Always - 115304097

195 Hardware_ECC_Recovered 0x001a 057 030 000 Old_age Always - 160386391

195 Hardware_ECC_Recovered 0x001a 059 030 000 Old_age Always - 118706962

195 Hardware_ECC_Recovered 0x001a 058 027 000 Old_age Always - 191379401

195 Hardware_ECC_Recovered 0x001a 062 032 000 Old_age Always - 16185991

195 Hardware_ECC_Recovered 0x001a 060 031 000 Old_age Always - 104533978

195 Hardware_ECC_Recovered 0x001a 059 033 000 Old_age Always - 195334052

195 Hardware_ECC_Recovered 0x001a 058 031 000 Old_age Always - 104621545

195 Hardware_ECC_Recovered 0x001a 057 033 000 Old_age Always - 150078009

195 Hardware_ECC_Recovered 0x001a 059 029 000 Old_age Always - 64454221

195 Hardware_ECC_Recovered 0x001a 058 028 000 Old_age Always - 48640199

195 Hardware_ECC_Recovered 0x001a 050 022 000 Old_age Always - 221569377

195 Hardware_ECC_Recovered 0x001a 060 031 000 Old_age Always - 150885196

---

The more you use the drive (heaver the workload) the more you'll get statistically which is one of the reasons why I am very leary to use large capacity drives and won't use ones larger than 1TB until they improve. (This is showing you how many errors happened and were corrected (re-read et al), statistically the more you have the higher the likelyhood that you'll have ones that are NOT corrected. Now say that happens when you're rebuilding or in degraded mode, you've just lost data and depending on the array controller you may not even be notified of the error at all.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now