Hi all, 

I have a problem with my server pretty much identical to the one described ~2 years ago by AceRimmer (https://forums.unraid.net/topic/103712-solved-parity-check-after-every-reboot-version-690-rc2/

 

Whenever my server restarts or I shut it down and restart it (I had some router changes / network changes etc. that required me to shutdown the server a few times over the last weeks), the server starts a parity scan suggesting that there was a unclean shutdown. Based on the log file that is exactly what happens for me ("Jul 14 20:20:05 MHPlex emhttpd: unclean shutdown detected"), however, I am not sure why that is and was wondering if someone could take a look at my diagnostics zip and help me out to confirm as well as maybe have a hint on what the problem is?

 

EDIT: should mention that I am on the Version: 6.12.2.

 

Based on my timing 90second timeout time should be plenty for graceful shutdown (which is my current setting, even 60 would be plenty), so I am not sure where the problem comes in. 

Thanks very much for the help!

 

Edited July 15, 20232 yr by hoembi
removed Diagnostics file and will update after system has been updated to 6.12.3

17 minutes ago, hoembi said:

Hi all, 

I have a problem with my server pretty much identical to the one described ~2 years ago by AceRimmer (https://forums.unraid.net/topic/103712-solved-parity-check-after-every-reboot-version-690-rc2/

 

Whenever my server restarts or I shut it down and restart it (I had some router changes / network changes etc. that required me to shutdown the server a few times over the last weeks), the server starts a parity scan suggesting that there was a unclean shutdown. Based on the log file that is exactly what happens for me ("Jul 14 20:20:05 MHPlex emhttpd: unclean shutdown detected"), however, I am not sure why that is and was wondering if someone could take a look at my diagnostics zip and help me out to confirm as well as maybe have a hint on what the problem is?

 

EDIT: should mention that I am on the Version: 6.12.2.

 

Based on my timing 90second timeout time should be plenty for graceful shutdown (which is my current setting, even 60 would be plenty), so I am not sure where the problem comes in. 

Thanks very much for the help!

diagnostics.zip 122.01 kB · 0 downloads

you should update to 6.12.3 as it contains a docker related fix that might fix this.    Post again if it does not.

38 minutes ago, itimpi said:

you should update to 6.12.3 as it contains a docker related fix that might fix this.    Post again if it does not.

The update did solve the issue. Thanks very much, I didn't see that the update was available so was completely unaware of the option to do it :). 

I have the same issue. I have my parity check set to last day of the month. Today I upgraded to 6.12.3 and rebooted after the update and woke up this morning to find out that parity check had started. 

On 7/16/2023 at 1:40 AM, nanohits said:

I have the same issue. I have my parity check set to last day of the month. Today I upgraded to 6.12.3 and rebooted after the update and woke up this morning to find out that parity check had started. 

Same issue here, upgraded to 6.12.3 and still the same, every restart..

Edited July 17, 20232 yr by Reason

On 7/16/2023 at 12:40 AM, nanohits said:

Today I upgraded to 6.12.3 and rebooted after the update and woke up this morning to find out that parity check had started.

If you upgraded from v6.12.2 there was a known issue with docker not unmounting that would cause an unclean shutdown, if you roboot again now do you still get an unclean shutdown?

22 minutes ago, Reason said:

Same issue here, upgraded to 6.12.3 and still the same, every restart..

If Unraid forces a shutdown it will save the diags in the flash drive /logs folder, post those to see if the cause if visible.