Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SMART Reports "Reported Uncorrect" - Important?

Featured Replies

I've got two drives that have come up with the same error "Reported Uncorrect".  Is this something that indicates the drive is failing?  Or just something to watch?

 

width=200http://my.jetscreenshot.com/12412/20160609-o1ds-111kb.jpg[/img]

 

One is the Parity drive (5TB - ST5000DM000-1FK178), the other is the cache (OCZ-AGILITY2 240GB SSD).  I'm currently running a full test on the parity.  Not sure if its wise to run a test on an SSD?

I would be very worried.  See here:

 

    https://en.wikipedia.org/wiki/S.M.A.R.T.

 

Looking up attribute 187:

 

187 	0xBB 	Reported Uncorrectable Errors  	The count of errors that could not be recovered using hardware ECC (see attribute 195)

 

I, personally, would be replacing that disk ASAP!

It depends on when they occurred, and whether they are still a problem.  Increases in attribute 187 tend to be redundant with other attributes, possibly showing a count of questionable sectors not yet dealt with, but also all UNC's from the past even if dealt with.  When you see an Uncorrectable count, you would normally check other attributes related to bad sectors, and check the ATA error section of the SMART report farther down.  You should normally (but not always) see errors in the ATA error section related to UNC sectors, and then you would compare their age with the current drive operational age (14088 hours on yours), and then decide if it's recent or old.  If it's old, it's been dealt with, especially if you don't see any other issues.  Unfortunately, 187 never drops, so it should be considered an historical count of every questionable sector that has ever occurred on this drive.  You are only worried about new ones, in other words an increasing 187 not a static 187.

  • Author

It depends on when they occurred, and whether they are still a problem...You are only worried about new ones, in other words an increasing 187 not a static 187.

 

Thanks Rob - perfect answer!  Here's ID#13 from the ATA section:

 

Error 13 occurred at disk power-on lifetime: 96 hours (4 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

 

The 187 error appears to be very old, occurring at 96 hours of operation...from the ATA section of the 5 TB Seagate SMART report (attached)...Given ID#9 states total Power_On_Hours at 8342, this meets your criteria.  So I've "acknowledged" that in the list and we'll see if it returns.

 

Ergo, it happened early on and not since.  So no worries about this one I think.  I'm running the Smart Test on the Cache drive now, we'll see what that returns.  I've not run a Smart test on the cache since it was installed a couple of months ago.  I'll post results...

 

Jeff...

ST5000DM000-1FK178_W4J0J1HS-20160609-1109.txt

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.