Hey, my monthly parity completed today and it reported errors for the first time - 39 errors. 

 

I do not recall any unclean shut downs (I did do a clean power down during Zeta). 

 

I also forgot the system was running the check and was moving, renaming, deleting files quite a bit during it - which may have added to it?  Regardless, I'm pretty hopeless when it comes to reading the reports and logs so I'm hoping one of you may be able to tell me if all is well or if I have a fire on my hands!

 

unkevin-diagnostics-20201103-0956.zip

There are constant ATA errors on disk1, that by itself shouldn't cause sync errors but if nothing else will make it much slower, replace cables and run another check, then post new diags.

Thanks - I have replaced the sata cable for disk 1.  I checked the logs and no errors are showing  up.

So now you advise running another parity scan correct?  The parity is 14tb so it will take a couple days.  Anything I should be looking for in the meantime?  Or avoid doing?

Look for any ATA and/or sync errors.

Ok I replaced the cable and ran the parity again.

It showed 1 error very early on in the scan but then no more errors the rest of the scan.  Not sure what the means, nor what I should do now - if anything?

Thanks for your help!

unkevin-diagnostics-20201105-0923.zip

Just sector 0 was corrected, which is kind of unusual, run another one.

Will do! 

Also - During parity checks - is it unwise to have active downloads and run dockers like Sonarr and Radarr?

5 minutes ago, kpc180 said:

is it unwise to have active downloads and run dockers like Sonarr and Radarr?

It won't cause any data or parity issues, but obviously other disk access will affect parity check speed, and parity check will affect other disk access speed.

Ok - thanks for the help guys - the 3rd parity check just finished with 0 errors.  So I'm thinking I'm in the clear?

 

However, I checked the logs periodically and there was 1 warning or error on there I didn't understand - though I don't think it had anything to do with the parity check.  

unkevin-diagnostics-20201107-0803.zip

19 minutes ago, kpc180 said:

So I'm thinking I'm in the clear?

Should be.

19 minutes ago, kpc180 said:

1 warning or error on there I didn't understand

What was it?

1 hour ago, trurl said:

What was it?

Sorry - it was what looks like 2 "warning" level events:

 

Nov 5 14:23:43 unKevin nginx: 2020/11/05 14:23:43 [error] 8706#8706: *1457547 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.171, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.18", referrer: "http://192.168.1.18/Main"

 

Nov 5 14:23:43 unKevin php-fpm[8680]: [WARNING] [pool www] child 13228 exited on signal 7 (SIGBUS) after 82.110109 seconds from start