BrennstoffBernd

Now I've got the logs I've paused the check at 0.6% and after the restart it would start all over by 0.0% (screenshot of the notification also attached). Thank you in advanced! -- Edit (18:09): I've tried it without stopping the array and directly shutting down and restarting the server. Then it works - it automatically continued the check at around 0.6%. -- galaxy-diagnostics-20240308-1745.zip

Sorry for the late reply. I've updated the Plugin and once again checked the same process, which I have listed above. After the restart, it was reported that the check could be continued. However, it started again at 0% after pressing the "Resume" button. I let it run to about 0.3% before I performed the restart.

I will give this special case a try these days and keep you up to date. Thanks for digging and analyzing my problem.

@itimpi Oh no, you're right. I'm sorry, I've switched back to basic logging. The new one should now provide testing mode and syslog. galaxy-diagnostics-20240214-1017.zip

@itimpi Sounds good - thanks for the first check. Additional: As a "partial workaround" it went completely fine, when not shutting down the server but putting it to sleep (s3). I've tried to re-create the exact process after enabling the syslog server (mirror to flash & local cache drive). Is it enough to export the diagnostics like last time? If so, it is attached. Also attached two screenshots. One for the notification (this time only the one message) and the other one as a side note that it is stated as "Last check incomplete on Tuesday, 13.02.2024, 18:02 (today) | Error code: aborted" after the boot process of the server finished and the array is started all over again. I've turned the syslog server off, once I've finished writing this comment. Thank you! galaxy-diagnostics-20240213-1816.zip

Thanks for the quick reply! I've just let the complete check once finished and then recreated the issue describe in number 2: - Set log output to "testing mode" - Started manual parity check until ~0.1% was reached - Pause the manual parity check - Stop the Array - This time I've got two notifications after stopping the array (see attached screenshot) - Shutdown the Server - Start the Server - Start the Array - No "Resume" function/button is provided and also after waiting for about 5 to 10 minutes, no automatic start was scheduled Also please see the diagnostics logging in the attached files. Thank you in advanced. galaxy-diagnostics-20240213-1658.zip

Hey there - I hope that my question wasn't answered in earlier posts and I didn't find it. Just to be clear, what the option "Resume array operations on next array start" provides and not provides: -- 1. The following operation is possible and working for me: - Pause a manual parity check - Stop the Array - Get a notification ("Restart will be attempted on next array start") - Start the Array again and resume the previous parity check 2. What's not working - shutdown the Server and resuming the check: - Pause a manual parity check - Stop the Array - Get a notification ("Restart will be attempted on next array start") - Shutdown the Server - Start the Server - Start the Array - No "Resume" function/button is provided, parity check will start from the beginning -- Is the pause-state lost, once the Server is shutdown or restarted? Thank you!