Jump to content
tr0910

Warning - reported uncorrect / What is reported uncorrect (unRaid notification)

8 posts in this topic Last Reply

Recommended Posts

But, what is reported uncorrect as a notification from unRaid.  This smart attribute doesn't seem to be related to a preclear of a drive.  This drive has been reporting uncorrect for some time, yet it preclears without issue.

 

Should we panic when we see "reported uncorrect" for a drive on the dashboard?

 

See http://lime-technology.com/forum/index.php?topic=4068.msg440386#msg440386

 

Older discussion here http://lime-technology.com/forum/index.php?topic=14792.0

Share this post


Link to post

Here is some notifications where it appears.

 

31-01-2016 12:54	unRAID device sdp SMART health [187]	Warning [KIM] - reported uncorrect is 39	ST3000DM001-9YN166_W1F0LAFX (sdp)	warning	
31-01-2016 12:54	unRAID device sdp SMART health [5]	Warning [KIM] - reallocated sector ct is 63304	ST3000DM001-9YN166_W1F0LAFX (sdp)	warning	
31-01-2016 12:54	unRAID device sdm SMART health [187]	Warning [KIM] - reported uncorrect is 47	ST3000DM001-9YN166_W1F0N4JK (sdm)	warning	
31-01-2016 12:16	unRAID device sds SMART health [187]	Warning [KIM] - reported uncorrect is 39	ST3000DM001-9YN166_W1F0LAFX (sds)	warning	
31-01-2016 12:16	unRAID device sds SMART health [5]	Warning [KIM] - reallocated sector ct is 63304	ST3000DM001-9YN166_W1F0LAFX (sds)	warning	
30-01-2016 11:19	unRAID device sdn SMART message [198]	Notice [KIM] - offline uncorrectable returned to normal value	ST3000DM001-9YN166_W1F0N4JK (sdn)	normal	
30-01-2016 11:19	unRAID device sdn SMART message [197]	Notice [KIM] - current pending sector returned to normal value	ST3000DM001-9YN166_W1F0N4JK (sdn)	normal	
30-01-2016 06:11	unRAID device sdn SMART health [187]	Warning [KIM] - reported uncorrect is 47	ST3000DM001-9YN166_W1F0N4JK (sdn)	warning	

Share this post


Link to post

Reported_Uncorrect is a SMART counter of just that, uncorrected errors detected and reported to the disk controller.

 

Like many SMART counters, the counter changing is a trigger for concern. If you get a "new" drive with 8 reallocations, and after 3 pre-clear cycles it still says 8 reallocated sectors. The bad bit has been detected and mapped out. This really should caught in the factory. but the extra checks from pre-clear got it and everthing else is good and stable. Not too long ago there was a lot of work involved in G list (grown defect list) and P list (permanent defect list). The realloc counter is just the length of the glist. Now very few people get involved with these. This is a good thing.

 

So saying it has Reported_Uncorrect for some time, does that mean it has been 39/47 since prior to pre-clear, or the value has been changing? If the value is changing, bad things.

 

Typically the only values that change downward are temp :) and pending. Pending often turn into reallocation, so realloc increases.

 

Probably the most talked about counter like this is UDMA_CRC_Error_Count, which so many want to be able to reset to zero. You get a bad/loose cable and this counter goes non-zero. You fix the cable, but now everyone who looks at your smart reports points to the non-zero value, which you (hopefully) know has not changed since the cabling was addressed.

Share this post


Link to post

there doesnt seem much info about this

i just got hit with this a few weeks ago

any input on this?

looks like blackbaze says if they see anything besides 0 they replace it

i have a drive pre-clearing now so i will most likely replace it

 

.

.

 

1 Raw read error rate 0x000f 111 099 006 Pre-fail Always Never 33453960

3 Spin up time 0x0003 093 076 000 Pre-fail Always Never 0

4 Start stop count 0x0032 093 093 020 Old age Always Never 7418

5 Reallocated sector count 0x0033 100 100 036 Pre-fail Always Never 0

7 Seek error rate 0x000f 084 065 030 Pre-fail Always Never 282676411

9 Power on hours 0x0032 060 060 000 Old age Always Never 35225 (4y, 6d, 17h)

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 61

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 089 089 000 Old age Always Never 11

188 Command timeout 0x0032 100 100 000 Old age Always Never 0

189 High fly writes 0x003a 100 100 000 Old age Always Never 0

190 Airflow temperature cel 0x0022 070 059 045 Old age Always Never 30 (min/max 26/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 53

193 Load cycle count 0x0032 097 097 000 Old age Always Never 7752

194 Temperature celsius 0x0022 030 041 000 Old age Always Never 30 (0 21 0 0 0)

195 Hardware ECC recovered 0x001a 015 015 000 Old age Always Never 33453960

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 265059611713651

241 Total lbas written 0x0000 100 253 000 Old age Offline Never 1777833167

242 Total lbas read 0x0000 100 253 000 Old age Offline Never 1581356104

Share this post


Link to post

there doesnt seem much info about this

i just got hit with this a few weeks ago

any input on this?

looks like blackbaze says if they see anything besides 0 they replace it

i have a drive pre-clearing now so i will most likely replace it

1 Raw read error rate 0x000f 111 099 006 Pre-fail Always Never 33453960

3 Spin up time 0x0003 093 076 000 Pre-fail Always Never 0

4 Start stop count 0x0032 093 093 020 Old age Always Never 7418

5 Reallocated sector count 0x0033 100 100 036 Pre-fail Always Never 0

7 Seek error rate 0x000f 084 065 030 Pre-fail Always Never 282676411

9 Power on hours 0x0032 060 060 000 Old age Always Never 35225 (4y, 6d, 17h)

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 61

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 089 089 000 Old age Always Never 11

188 Command timeout 0x0032 100 100 000 Old age Always Never 0

189 High fly writes 0x003a 100 100 000 Old age Always Never 0

190 Airflow temperature cel 0x0022 070 059 045 Old age Always Never 30 (min/max 26/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 53

193 Load cycle count 0x0032 097 097 000 Old age Always Never 7752

194 Temperature celsius 0x0022 030 041 000 Old age Always Never 30 (0 21 0 0 0)

195 Hardware ECC recovered 0x001a 015 015 000 Old age Always Never 33453960

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 265059611713651

241 Total lbas written 0x0000 100 253 000 Old age Offline Never 1777833167

242 Total lbas read 0x0000 100 253 000 Old age Offline Never 1581356104

It's generally best to attach the entire SMART report, so we could see if those are recent or old.  You have 35000 hours on it, and a bit of evidence of wear, but overall the drive looks great, with an unusually good 'Seek error rate' for a Seagate.  Check the error section for when the last error occurred, and compare that with 35225, to see how recent.  The drive doesn't show any current issues, at least not from that SMART piece.

Share this post


Link to post

thanks RobJ

i attached it

 

so which ones should i look out for?

The last error was back at 19860 hours, over 15000 hours ago, so taken care of a long time ago.  And they weren't serious as no sectors were reallocated.

 

The most important one is the 'Current pending sector' count, should always be zero.  There are a few others to monitor, but only if they are currently increasing, not that they are non-zero.

Share this post


Link to post

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.