SMART187 Reported uncorrect


pyrater

Recommended Posts

I got a smart 187 today (never seen this one before).  Its an old drive and i am running dual parity....... but should i go ahead and replace the drive? According to what i have found on the net this is a good indicator of a drive that will fail within the next 6ms.  (https://www.backblaze.com/blog/hard-drive-smart-stats/

 

# Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value
1 Raw read error rate 0x000f 110 099 006 Pre-fail Always Never 152291873
3 Spin up time 0x0003 094 094 000 Pre-fail Always Never 0
4 Start stop count 0x0032 095 095 020 Old age Always Never 5717
5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0
7 Seek error rate 0x000f 078 060 030 Pre-fail Always Never 77382975
9 Power on hours 0x0032 063 063 000 Old age Always Never 33040 (3y, 9m, 4d, 16h)
10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0
12 Power cycle count 0x0032 100 100 020 Old age Always Never 192
183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0
184 End-to-end error 0x0032 100 100 099 Old age Always Never 0
187 Reported uncorrect 0x0032 099 099 000 Old age Always Never 1
188 Command timeout 0x0032 100 100 000 Old age Always Never 0 0 0
189 High fly writes 0x003a 099 099 000 Old age Always Never 1
190 Airflow temperature cel 0x0022 068 051 045 Old age Always Never 32 (min/max 27/33)
191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0
192 Power-off retract count 0x0032 100 100 000 Old age Always Never 115
193 Load cycle count 0x0032 001 001 000 Old age Always Never 253410
194 Temperature celsius 0x0022 032 049 000 Old age Always Never 32 (0 12 0 0 0)
197 Current pending sector 0x0012 100 100 000 Old age Always Never 0
198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 0
199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0
240 Head flying hours 0x0000 100 253 000 Old age Offline Never 10762h+34m+18.312s
241 Total lbas written 0x0000 100 253 000 Old age Offline Never 68795191328
242 Total lbas read 0x0000 100 253 000 Old age Offline Never 418855824077

 

 

Just dunno what to do with the pulled drive, maybe an external usb drive from all that shucking?

Edited by pyrater
Link to comment
40 minutes ago, pyrater said:

I got a smart 187 today (never seen this one before).  Its an old drive and i am running dual parity....... but should i go ahead and replace the drive? According to what i have found on the net this is a good indicator of a drive that will fail within the next 6ms.  (https://www.backblaze.com/blog/hard-drive-smart-stats/

 

# Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value
1 Raw read error rate 0x000f 110 099 006 Pre-fail Always Never 152291873
3 Spin up time 0x0003 094 094 000 Pre-fail Always Never 0
4 Start stop count 0x0032 095 095 020 Old age Always Never 5717
5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0
7 Seek error rate 0x000f 078 060 030 Pre-fail Always Never 77382975
9 Power on hours 0x0032 063 063 000 Old age Always Never 33040 (3y, 9m, 4d, 16h)
10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0
12 Power cycle count 0x0032 100 100 020 Old age Always Never 192
183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0
184 End-to-end error 0x0032 100 100 099 Old age Always Never 0
187 Reported uncorrect 0x0032 099 099 000 Old age Always Never 1
188 Command timeout 0x0032 100 100 000 Old age Always Never 0 0 0
189 High fly writes 0x003a 099 099 000 Old age Always Never 1
190 Airflow temperature cel 0x0022 068 051 045 Old age Always Never 32 (min/max 27/33)
191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0
192 Power-off retract count 0x0032 100 100 000 Old age Always Never 115
193 Load cycle count 0x0032 001 001 000 Old age Always Never 253410
194 Temperature celsius 0x0022 032 049 000 Old age Always Never 32 (0 12 0 0 0)
197 Current pending sector 0x0012 100 100 000 Old age Always Never 0
198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 0
199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0
240 Head flying hours 0x0000 100 253 000 Old age Offline Never 10762h+34m+18.312s
241 Total lbas written 0x0000 100 253 000 Old age Offline Never 68795191328
242 Total lbas read 0x0000 100 253 000 Old age Offline Never 418855824077

 

 

Just dunno what to do with the pulled drive, maybe an external usb drive from all that shucking?

 

Here is the definition of reported uncorrect:

 

The count of errors that could not be recovered using hardware ECC

 

Did you receive any read errors in unRAID? You'd think that you'd get one - or maybe this is triggered but it retried and was successful.

 

I would not treat this as a death knell. But if you see this increment even once or twice more, I would certainly look to replace.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.