Dear all,

 

Since a few weeks I am experiencing a parity check each reboot, I did some tests based in other posts like stopping the array before restarting, or increase the timeout of the shutdown, but unfortunately it did not work. 

 

I attach my diagnostics file and hopefully someone will be able to point me to the good direction.

 

Thanks in advance,

 

tuxz440-diagnostics-20220417-0755.zip

Have you checked out all the items mentioned in this section of the online documentation that can be accessed via the Manual link at the bottom of the GUI?

Hi,

I believe so, I checked time outs and as a final test I stop the array before shutdown the server. Even with this, having all VM, dockers and terminals stopped is starting the parity check.

 

Is there any specific string I should find in the logs? 
 

thanks in advance 

I would suspect that the 'array stopped' flag is not being written to your boot drive.  I would stop the array and shut the server down completely.  The pull the drive and run a chkdsk on it on your PC. 

Thanks @Frank1940, the server is my only machine so I can not run a chkdsk in a separate machine.  Is there any possibility to check this array stopped flag  within the boot drive?

4 hours ago, ttuuxxeerr said:

 Is there any possibility to check this array stopped flag  within the boot drive?

 

I do not believe so as I think this is stored in the super.dat file which is a binary file and not human readable.