So I searched the forums for this issue but haven't found a solution.  I can see one of my drives had 2 errors on the daily tests run.  Under the disk info, it says there are 2 raw read error rate errors.  So my question is:

 

1) Is there a way to acknowlege the errors so the daily check stop showing a failed, orange state?  Or can I get the daily check to ignore the bad sectors, if any?

That SMART attribute is not monitored by default. You can set which are monitored on a per disk basis by clicking on a disk to go to its setting page.

 

I don't think that attribute would normally trigger this so I have to wonder if you don't have something else going on. Post your diagnostics.

Here's diagnostics.

 

Looks like you are referring to disk5. If you see here that SMART attribute is not usually considered important.

 

From Main, click on Disk 5 to get to the Disk 5 Settings, and post a screenshot of the section labeled SMART Settings.

 

Warning you're getting is because of this:

 

Nov 26 10:35:13 muddRAID kernel: blk_update_request: critical medium error, dev sdg, sector 4651304312
Nov 26 10:35:13 muddRAID kernel: md: disk5 read error, sector=4651304248
Nov 26 10:35:13 muddRAID kernel: md: disk5 read error, sector=4651304256

 

There are no pending sectors but this does look like a disk problem, you should do an extended SMART test.

I ran an extended SMART test yesterday morning.  Page is showing that SMART 'completed without errors'.

Here is the SMART test log in case you want to check it out yourselves.

I would keep the disk for now, you can reboot to clear the errors.

 

If it happens again I would replace it.

I interpreted your OP to mean you were getting notified about the SMART attribute you mentioned. What is the exact message you are getting?

 

If it is just telling you that you had read errors, you can reset the error counts by rebooting.

Thanks for the help guys.  A reboot changed the status back to green.

 

I'm not sure if this should be a feature request, but as a user some additional information about the error, or some dialog to reboot the system to reset the error would have been helpful.