PARITY ERRORS IN UNRAID 6.5.3

[shagz]

Woke up this morning to 605 Parity Drive errors and my 8tb parity Drive marked as faulty 

 

I have not rebooted and have the diagnostic report in hand . Looking for assistance in determining if the drive is done .. do i just rebuild etc .. ? 

Dockers i use are Filezilla - Plex Media Swerver & Resilio Sync - although i do not believe it to be a docker issue 

 

Can the community chime in and have a look and discuss my options 

Thanks  

NOV 7 .txt

omicron-diagnostics-20181107-0953.zip

omicron-smart-20181123-1534.zip

[trurl]

You will have to rebuild parity. Only question is whether to rebuild to the same disk or new one.

 

There is no SMART report for parity in those diagnostics. Check connections and post a new diagnostic so we can see if the disk is OK to use.

[shagz]

 Ive added the SMART report to the original post if this helps -  Before i shutdown and rebuild and check cables etc .. Id like to see if that SMART report has any clues .. ? once confirmed i will go ahead with your suggested action 

 

Thanks 

[JorgeB]

Like trurl mentioned there's no SMART report for parity since it dropped offline, you'll need to reboot/check cables to see if it comes back online but based on the syslog error and unless the disk just died looks more like a connection problem.

[shagz]

update : 

 

I have since changed the SATA cable and rebuilt parity - worked well for apppx a week or so but coming back with additional errors on my 8tb parity drive in question . 

 

I have included the SMART report on the drive As of 11.23.18 and looking to see if anyone can pinpoint as to what is going on here ? 

 

thanks 

[trurl]

Please don't edit a post from weeks ago and expect us to know it! It is very confusing and might even lead to your getting bad advice.

 

If I hadn't wondered where your new diagnostics were I would have never even looked. Anytime you need to post new diagnostics do so with a new post. In fact, do so right now with the complete diagnostics zip.

 

Just a SMART report can only tell us so much, and most of the time it won't show us anything about a simple I/O error since they are often caused by things other than the disk itself.

[trurl]

I am locking this thread since the OP misunderstood my advice above and started a new topic here:

 

 

They have already linked back to this thread so I guess that plus this post closes the loop.