Last night my 2nd parity disk came up with 302 errors.  I am currently running a SMART extended test on it and I will post it once it is complete.  What should I be looking for as far as determining whether to replace it or fix the issues?  Is there anything else I can post to help determine this?

20 minutes ago, mgranger said:

Is there anything else I can post to help determine this?

Tools -> Diagnostics

i am still waiting for it to finish the smart scan. it has been on 90% for a couple of hours now

Here is the diagnostics files.  The SMART scan for the Toshiba drive never finished.  It had been running for over 20 hours (and probably the last 6 or 8 hours at 90%) so I stopped it.  

finalizer-diagnostics-20180331-1325.zip

197 Current_Pending_Sector  -O--CK   100   100   000    -    992

Parity2 needs to be replaced.

ok. on my other server today i now have an error on one of its drives as well  i just started using unraid but seems strange to see these errors on these disks. i guess i never had anything really scanning them but is there something i can do better. the toshiba drive doesn't seem very old

executer-diagnostics-20180331-1458.zip

Pending sectors are always a disk problem, though in some rare cases they can be causes by external issues, e.g. bad power, but since this one is the notorious ST3000DM001 I'd guess it's just another one failing.

so on the first one how do you know when it is an external issues vs failing disk issue. is it the number of sectors?  what is typically acceptable and is there anysthing to do to salvage it. although i don't know if i can trust it now out of concern that it will fail on me. 

99% of the time it's a failing disk, you can start suspecting external issues if it keeps happening to various disks on the same server in a short space of time.