cpu stock at 100% - loosing network while copying datas

[fakokay]

Hi all,

Trying to move my datas off one of my unraid servers since i got problems with it (raid controller, cpu stuck at 100%, parity, etc)...
Just hope to be able to move 'quickly' my 21TG of datas (moving with robocopy since i'm dumping the datas to an external drive) !

This diagnostic was when the CPU was stuck at 100% while copying datas of the array during the night... At taht paste, it will take 3 months to move the datas... if ever i can. I've included my last diagnostic, hope someone could pinpoint the problem (also if you can tell me wich file to look at, so i can also troubleshoot the problem - could be great).

My problems started 3 weeks ago, i hardly sleep since i'm looking at the server during the night (moving datas)... Hope one day i'll be able to smash that server without loosing any datas!

Thank for your help.
 

galactus-diagnostics-20220621-0251.zip

[JorgeB]

Diags after after stopping the array so not much to see, grab new ones during data transfer.

[fakokay]

Whats the process to create a diagnotic zip file from the admin panel?

[JorgeB]

Type 'diagnostics' in the console.

[fakokay]

Thx for the reply!

Quick update : still no new CPU 100% usage since yesterday. I think i found the problem : it may be the multitreads flag that was too high for the nas cpu when using robocopy (MT:x flag). i've set it up to the number of CPU and seems to work fine, for now.

 

Another quick question if i may ask... The initial parity process seems to start all over again when rebooting (18hrs paritying the drives, goes to 100% with no errors - reboot - the parity start automaticly all over again). Any reasons why? The only way i found to 'bypass' the parity is to reboot again. After that, the parity says 'Parity is valid'.
 

[itimpi]

4 minutes ago, fakokay said:

Another quick question if i may ask... The initial parity process seems to start all over again when rebooting

This is standard Unraid behaviour.

 

if you want the ability to resume parity checks from the point they had reached then install the Parity Check Tuning plugin and enable this option in its settings.

[fakokay]

thank for your reply!

huh, i was under the impression that since the parity was done and successful, unraid doesn't need to re-check it again (my seetings are at 'one for month'). But i'll install the plugin to see. 👍

[JorgeB]

25 minutes ago, fakokay said:

reboot - the parity start automaticly all over again

This suggests Unraid is detecting an unclean shutdown.

[itimpi]

15 minutes ago, fakokay said:

i was under the impression that since the parity was done and successful

I thought from you statement that it had not yet completed.   As was mentioned then an automatic parity check after a rebooot suggest that you did not have a clean shutdown of the array.    The plugin would have informed you if it thought that an unclean shutdown had been detected and that was triggering an automatic check.
 

You might want to read this section of the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.