So...I've run into a weird issue(s).  I had this issue last week:

 

Thanks to mod help I'm ok on the original issue. (thanks again!!)

TLDR: Issue with an array disk, I was able to recover it, but blew my parity away because I'm a dummy. 

 

I got things running again, but NGINX crashed on me during initial parity rebuild. No GUI. I let it run for a while, and SSH went as well. Reboot. Start again, same deal. I then started ONE more time and formatted parity disks and left docker in the minimal state with no VMs. It took a few days, but it was successful. I think?  I had another NGINX lockup. I ended up having to hard boot again. On reboot, I have a parity sync going on with this status as of now:

 

That's a LOT of errors. I guess parity was never good? Not sure. I had a few reallocated sectors on a parity disk, but this seems to be ok/not increasing. My array data is all in-tact as well. 

 

The ONLY thing I can nail down is this NGINX lockup issues happen when I connect to the GUI from my Pixel 8 PRO. The log EXPLODES with NCHAN errors.  I see a reference to these errors here (Specifically Android from @SimonF  So maybe two issues here, but sorta related.  

Is my parity going to be any good after this!? Is there a  known Android browser issue? (Using Brave on the phone...)

 

Diags attached. 

zeus-diagnostics-20231219-1711.zip

Edited December 19, 20232 yr by dja
Clarity

If the data looks correct just run a correcting parity check.