Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jamieburchell]

Should I be worried about the Raw_Read_Error_Rate, Seek_Error_Rate and Hardware_ECC_Recovered values constantly increasing? If I'm reading the table correctly, no reallocated sectors. No spin up time either? I can't find anywhere that explains this table properly. The Wiki entry is sketchy at best.  

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   117   099   006    Pre-fail  Always       -       147705572
  3 Spin_Up_Time            0x0003   095   089   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       2628
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   072   060   030    Pre-fail  Always       -       16312004
  9 Power_On_Hours          0x0032   083   083   000    Old_age   Always       -       14988
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       2
 12 Power_Cycle_Count       0x0032   100   037   020    Old_age   Always       -       90
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   058   057   045    Old_age   Always       -       42 (Lifetime Min/Max 29/43)
194 Temperature_Celsius     0x0022   042   043   000    Old_age   Always       -       42 (0 8 0 0)
195 Hardware_ECC_Recovered  0x001a   045   035   000    Old_age   Always       -       147705572
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

[tentimes]

looks fine. about the right ratio for size of drive compared to what i normally see

[m2k3423]

ID#
5     Reallocated_Sector_Ct
197  Current_Pending_Sector

If these two are anything other than 0, it indicate bad media, and you should back-up and send in for RMA.

If you zero the drive (will force the drive to remap bad sectors), and test the drive again, you will likely see the bad sector go away, if the drive electronics remap the bad sector. However, after power-recycling, depending on your luck and the nature of surface damage, the bad sectors may re-appear later.

For Tera-byte size drive, once you see bad sectors, most likely you will see a lot of bad sectors appearing very quickly. 

[jamieburchell]

Thanks guys. Why do the Raw_Read_Error_Rate, Seek_Error_Rate and Hardware_ECC_Recovered values keep increasing at an alarming (to me) rate?

[tentimes]

That's just standard fodder for any drive - it sometimes won't pick up a sector correctly first read and needs a second go at it. If it takes too many goes then it gest marked bad. All drives have high numbers for these, it's just part of the nature of magnetic media.

I found an article you might be interested in that is about drive failures and the reasons for it: http://www.tomshardware.co.uk/hdd-reliability-storelab,review-31968.html

[gunrunnerjohn]

What exactly is the "alarming rate" they are increasing at over a specific period of time?

[jamieburchell]

What exactly is the "alarming rate" they are increasing at over a specific period of time?

I ran smartctl a few times consecutively, it was a different value each time - maybe 100 more than the last. I think I was streaming a single MP3 from the disk at the time. By virtue of the fact that it's called "Raw_Read_Error_Rate" and not "nothing_to_worry_about_rate" made me concerned

[jamieburchell]

Actually, I'm being stupid - it has happened once before

It's a rate rather than a cumulative value - so of course it will fluctuate during disk usage. Here's some more info:


8:44
1 Raw_Read_Error_Rate    0x000f  117  099  006    Pre-fail  Always      -      154964518
7 Seek_Error_Rate        0x000f  072  060  030    Pre-fail  Always      -      16366525

9:27
1 Raw_Read_Error_Rate    0x000f  105  099  006    Pre-fail  Always      -      7674486
7 Seek_Error_Rate        0x000f  072  060  030    Pre-fail  Always      -      16456073

12:27
1 Raw_Read_Error_Rate    0x000f  108  099  006    Pre-fail  Always      -      15135422
7 Seek_Error_Rate        0x000f  072  060  030    Pre-fail  Always      -      16475086

12:30
1 Raw_Read_Error_Rate    0x000f  108  099  006    Pre-fail  Always      -      15310680
7 Seek_Error_Rate        0x000f  072  060  030    Pre-fail  Always      -      16475575

[gunrunnerjohn]

Where do you find smartctl for this box?  I'm assuming you're running from SSD or telnet, right?

[jamieburchell]

It's one of the FFP packages (smartmontools-5.39.1-1.tgz).

I asked Fonz if he would update the version yesterday - and he did! I was hoping I'd be able to utilise the JMicron USB enclosure support in the new version to test externally connected drives. It didn't work for my enclosue though.

[gunrunnerjohn]

I loaded the earlier version, decided to try Google.

You do seem to get bigger numbers and more of them for your drives, not sure what that means.



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   062   062   011    Pre-fail  Always       -       12210
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       485
  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      -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       5343
 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       -       21
 13 Read_Soft_Error_Rate    0x000e   100   100   000    Old_age   Always       -       0
183 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
184 Unknown_Attribute       0x0033   100   100   000    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   064   064   000    Old_age   Always       -       36 (Lifetime Min/Max 21/36)
194 Temperature_Celsius     0x0022   067   067   000    Old_age   Always       -       33 (Lifetime Min/Max 21/40)
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       100557941
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   253   253   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

SMART Error Log Version: 1
No Errors Logged

[jamieburchell]

Was you accessing the disk at the time? Yours are zero! My read rate also seems to match the ECC recovered value, unlike yours.

[jamieburchell]

Here's a side question for the hard drive gurus in here. I read that after time hard drive data "fades" due to the nature of magnetism. There's talk about "refreshing" a drive periodically which involves reading the entire drive. Would a periodic rsync each month satisfy the criteria or will I find one day that all my backup drives are empty

[gunrunnerjohn]

I think the time required for data to fade is measured in decades.  I've had old drives from MS-DOS computers in the closet from the early 90's, and I've stuck them in a USB enclosure and read them error-free.  You'll be more likely to lose data from optical media, some of which has trouble remembering more than a couple of years, than a hard disk.

[jamieburchell]

I guess it depends which articles you read...

E.g. this article suggests as early as a year
http://www.larryjordan.biz/articles/lj_restore_hard_disk_data.html