June 5, 20233 yr Community Expert The diagnostics you have posted are after a reboot. The Unraid logs are by default only in RAM and do not survive a reboot. You may get something useful we can look at if you enable the syslog server to get logs that survive a reboot. You should also check how long it takes to stop the the array. It is possible that something is either stopping this from happening or it is taking too long so that a timeout ends up closing the array forcibly. If you reboot after a successful stop of the array then you should not get an unclean shutdown detected as long as Unraid was able to update the flash drive with the fact the array was successfully stopped.
June 5, 20233 yr Author 1 hour ago, itimpi said: The diagnostics you have posted are after a reboot. The Unraid logs are by default only in RAM and do not survive a reboot. You may get something useful we can look at if you enable the syslog server to get logs that survive a reboot. You should also check how long it takes to stop the the array. It is possible that something is either stopping this from happening or it is taking too long so that a timeout ends up closing the array forcibly. If you reboot after a successful stop of the array then you should not get an unclean shutdown detected as long as Unraid was able to update the flash drive with the fact the array was successfully stopped. I tried to open the system log server again and enter it again. It looks like the CPU is fully occupied. After confirming with the restart button, I am unable to enter the homepage
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.