WebUI and Command Line interface unresponsive when Parity Check commences

[scottcru]

Hi,

 

I've had a problem with my parity check scheduling recently (now solved by a very helpful user on this forum), but helped to highlight a problem I have had pretty much since setting my unraid server up. When the parity check is running my server becomes unresponsive via the WebGUI or the CLI. When I hard reset and get access to the WebGUI and turn off the Docker and VM service the server remains responsive when the parity check restarts. 

 

Is there any advice or experience others have had they can share. Is there a way to limiting the amount of processor capacity used by parity check? can the docker service be shutdown prior to a parity check being commenced? could I have a resource hungry Docker container?

 

I'm still quite new to seeking support via these forums, so if there are any diagnosis reports I can run please do let me know.

 

Many thanks for your help in advance.

[itimpi]

You are likely to get better informed feedback if you attach your system’s diagnostics zip file (obtained via Tools->Diagnostics) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

[scottcru]

Thank-you for the guidance, diagnosis run and now attached.

 

Just to note, parity check not running when diagnosis just run, and if it was, I then wouldn't be able to access the WebGUI to then run the diagnosis.

scott-nas-diagnostics-20240623-2124.zip

[JorgeB]

Enable the syslog server, start a parity check, and when it stops responding post that.

[scottcru]

Thank-you will do this evening and post