May 20, 20242 yr Hello everyone, I have a problem with my unraid server. I cannot give it the order to restart. Not via the webUI, nor via terminal or SSH. Terminal and SSH are using the command sudo reboot -n . Currently I restart the server by holding the power button for 5 seconds and turn it on again. But that can't be good for the hard drives and so on. What can I do to restore the "normal" reboot sequence...? I don't know what is causing this problem, but I'll be grateful to get this solved. I added my diagnostics for further error solving. Kind regards, Rik rik-tower-diagnostics-20240520-1951.zip Edited May 20, 20242 yr by rikdegraaff
May 20, 20242 yr Community Expert If you type reboot in the CLI, does it generate the diags for an unclean shutdown, or doesn't even get that far? If not see, if you can get the syslog after it gets stuck: cp /var/log/syslog /boot/syslog.txt
May 20, 20242 yr Author 16 minutes ago, JorgeB said: If you type reboot in the CLI, does it generate the diags for an unclean shutdown, or doesn't even get that far? If not see, if you can get the syslog after it gets stuck: cp /var/log/syslog /boot/syslog.txt No I dont get any errors. Unraid also doesn't get stuck, I reload the webUI and can continue working. It just never executes the reboot command. This also happens when I directly type it in the CLI.
May 21, 20242 yr Author 15 hours ago, itimpi said: Can you successfully stop the array? Yes, I can. It takes a while imho, but finally the array stops.
May 21, 20242 yr Community Expert Determine the time to stop the array. Add 10-20% to that number. Now go to SETTINGS >>> Disk Settings and look for this parameter: Enter that number you just calculated and 'Apply' and 'Done'.
May 21, 20242 yr Author 5 minutes ago, Frank1940 said: Determine the time to stop the array. Add 10-20% to that number. Now go to SETTINGS >>> Disk Settings and look for this parameter: Enter that number you just calculated and 'Apply' and 'Done'. I've timed it and calculated 10% to it. I came out on 127 secs, so replaced that to my Shutdown time-out value. Now I go to main and reboot, and I get immediately System is going down for reboot. Could it be that that new value fixed it?
May 21, 20242 yr Community Expert 13 minutes ago, rikdegraaff said: Could it be that that new value fixed it? I doubt it. Did you restart the array before you tried to reboot? The parameter tells Unraid to wait for that period of time for the array to stop before it forces a shutdown. If Unraid has to force a shutdown, it will be an unclean shutdown and parity will be rebuilt when the server comes back up. (Before this parameter was added, Unraid would wait FOREVER for the array to stop. As I recall, there was considerable discussion about this issue as sometimes server access was an issue and the unclean shutdown was deemed preferable to having to gain access to the server to force a shutdown. The problem of the array not stopping is generally caused by a plugin or Docker container that doesn't close a file when it receives a request to do so!) EDIT: What I did when there was an issue in one of the 6.12.X release with the array not stopping is that I manually stopped all of the Docker containers. Then I manually stopped the array. When the array had stopped, I then rebooted the server. However, I believe the issue has been fixed in ver6.12.10. Edited May 21, 20242 yr by Frank1940
May 21, 20242 yr Author Yes I started the array, before rebooting it. It is still unclear to me why this time it worked... It also didn't trigger a Parity Check, because it was a clean shutdown. But I am happy it would restart, because unclean shutdowns are not good in my eyes, only when you need to they are better.
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.