Hi everyone,

I just noticed that when I clean shutdown my system, either via button or GUI, the server starts a parity check after my maintenance.

I see the following notifications:

I already had this twice in the past but never found time to check this. The server runs for weeks without reboot or issues. Now I want to find the reason for this unclean shutdown.

nasty-diagnostics-20260414-1941.zip

Do you guys have any special tool's to analyze the diagnostics.zip, or do you analyze it file by file with an IDE? I like analyzing it myself, but I have no clue where to look first and I don't have that much time if I have no idea to what I could look first. If there would be a intellij or vscode plugin that could make a small report out of that log, that would be awesome.

I appreciate every help.

The first thing you need to do is try stopping the array and timing how long it takes. You then need to set the timeout under Settings->Disk Settings to be at least this value.

Currently it's set to 90 seconds. I haven't stopped my array yet. So in terms of a safe shutdown it's better to have a longer timeout to make sure the whole array had enough time to stop, right?

Do I have to track the time myself or is the time to stop the array displayed on the GUI?

And Thanks for the quick help.

11 minutes ago, W0nderW0lf said:

Do I have to track the time myself or is the time to stop the array displayed on the GUI?

You have to time it yourself and then add on 30 seconds or so. If that timeout is not long enough then you get unclean shutdowns as the timeout shuts down the server before the array is cleanly unmounted.

There are other timeouts you can set controlling how long VMs and docker containers should be given before the system attempts forcible close of them.

Got it!

I stopped the array, set the timeout to 190 seconds and rebooted. No more "crash"