January 26, 201214 yr Hi, I just built my 1st unRAID server using the Atlas thread. I am on unRAID 5b11. I would like to know the best way to stop the unRAID server, both from the WebUI and from command line. Command-line: I currently use "showdown -h now" to stop the server. It works for now because I don't have a parity drive assigned but I am assuming that using this command will trigger a parity check once I have assigned a parity drive. I saw a post by Joe L. where he talks about a script but the post is really old. I am not sure if it is still applicable. His script is: # Stop Samba killall smbd nmbd # Kill any processes using the disks for fs in /mnt/user /mnt/disk* do if [ ! -d ${fs} ] ; then continue ; fi for pid in $(fuser -cu $fs 2>/dev/null) do kill -TERM ${pid} done done #un-mouunt the disks for disk in /mnt/disk* do /bin/umount ${disk} done # Stop the unRAID array echo stop > /proc/mdcmd echo "The unRAID array is stopped" WebUI: Is it best to stop the array first and then go to command line and use the shutdown command? Thanks for all the help. Sorry if I missed a post somewhere.
January 26, 201214 yr The best option is to install the powerdown script. It is an old script, but it still works well. With that script installed, you can either stop the array and press 'power down' on the GUI, or type 'powerdown' in the command line interface. Either way will kill all running add-ons and gracefully shut down your server.
March 28, 201511 yr Hi, I just built my 1st unRAID server using the Atlas thread. I am on unRAID 5b11. I would like to know the best way to stop the unRAID server, both from the WebUI and from command line. Command-line: I currently use "showdown -h now" to stop the server. It works for now because I don't have a parity drive assigned but I am assuming that using this command will trigger a parity check once I have assigned a parity drive. I saw a post by Joe L. where he talks about a script but the post is really old. I am not sure if it is still applicable. His script is: # Stop Samba killall smbd nmbd # Kill any processes using the disks for fs in /mnt/user /mnt/disk* do if [ ! -d ${fs} ] ; then continue ; fi for pid in $(fuser -cu $fs 2>/dev/null) do kill -TERM ${pid} done done #un-mouunt the disks for disk in /mnt/disk* do /bin/umount ${disk} done # Stop the unRAID array echo stop > /proc/mdcmd echo "The unRAID array is stopped" WebUI: Is it best to stop the array first and then go to command line and use the shutdown command? Thanks for all the help. Sorry if I missed a post somewhere. Thank you for this method.
March 28, 201511 yr If you stop the array from the UI then you will be given the option to shutdown or reboot from the UI.
March 28, 201511 yr Instead of the rather old wiki link Rajahal posted, I would recommend to use the newer powerdown package by dlandon.
March 28, 201511 yr I had a situation yesterday where the pressing the button to stop the array did nothing and telnetting in to use the power down command did not work either. Is there some way to regain enough control to gracefully shut down under those circumstances? I eventually had to pull the plug, which of course leads to a forced parity check.
March 28, 201511 yr I had a situation yesterday where the pressing the button to stop the array did nothing and telnetting in to use the power down command did not work either. Is there some way to regain enough control to gracefully shut down under those circumstances? I eventually had to pull the plug, which of course leads to a forced parity check. I do not think there is any easy way (at the moment at least). The unRAID supplied powerdown script seems to only work properly if emhttp is still responding. having said that the plugin version of the powerdown script might be more successful as I believe it does not rely on emhttp. I am hoping that the default unRAID powerdown is going to be enhanced to work even when emhttp is not behaving itself (or emhttp made more robust).
Archived
This topic is now archived and is closed to further replies.