bdee1 Posted April 24, 2013 Share Posted April 24, 2013 Can someone please tell me the proper way to safely reboot my server from the command line? Unfortunately I cant get the SimpleFeatures GUI to load so i have to reboot my server. Without the SimpleFeatures GUI i will need to do this via a command line. I am running the latest 5.x rc. I know that the powerdown command has worked for me in the past but I need to ensure that the system is rebooted and not shut down. Link to comment
Joe L. Posted April 24, 2013 Share Posted April 24, 2013 If you have the clean-powerdown command installed, you can simply type: /sbin/powerdown If not, the instructions are in the wiki here for the individual commands needed to stop the array: http://www.lime-technology.com/wiki/index.php/Console#To_cleanly_Stop_the_array_from_the_command_line You can verify the status by typing: cat /proc/mdcmd | grep mdState Once stopped, you can simply type reboot Link to comment
bdee1 Posted April 24, 2013 Author Share Posted April 24, 2013 so /sbin/powerdown will reboot the server? not just power it down? Link to comment
Joe L. Posted April 24, 2013 Share Posted April 24, 2013 so /sbin/powerdown will reboot the server? not just power it down? It will probably power it down if just invoked as I described. To reboot, I think you can add a "-r" option to it (disclaimer, I've never tried it, and it entirely depends on your hardware, since the -r is eventually passed to the native powerdown command, and to it, -r indicates reboot.) /sbin/powerdown -r Link to comment
trurl Posted April 24, 2013 Share Posted April 24, 2013 No it will power down. Follow the rest of Joe's instructions to reboot instead. Tapatalk from CM10.1 Kindle Well Joe beat me to the reply. I would be interested in the -r option. Let us know if it works. Link to comment
bdee1 Posted April 24, 2013 Author Share Posted April 24, 2013 ok so I just ran it with the -r and so far this is what I have... Capturing information to syslog. Please wait... version[19198]: Linux version 3.4.36-unRAID (root@Develop) (gcc version 4.4.4 (GCC) ) #1 SMP Wed Mar 20 12:54:40 PDT 2013 ls: cannot access /dev/hd[a-z]: No such file or directory ls: cannot access /dev/hd[a-z]: No such file or directory /etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect /etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect /etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect and now its just hanging - no other response in telnet session for a good 20 minutes now. Link to comment
Joe L. Posted April 24, 2013 Share Posted April 24, 2013 ok so I just ran it with the -r and so far this is what I have... Capturing information to syslog. Please wait... version[19198]: Linux version 3.4.36-unRAID (root@Develop) (gcc version 4.4.4 (GCC) ) #1 SMP Wed Mar 20 12:54:40 PDT 2013 ls: cannot access /dev/hd[a-z]: No such file or directory ls: cannot access /dev/hd[a-z]: No such file or directory /etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect /etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect /etc/rc.d/rc.unRAID: line 84: ${FILE}: ambiguous redirect and now its just hanging - no other response in telnet session for a good 20 minutes now. Assuming it stopped the array, (check using cat /proc/mdcmd | grep mdState as stated above) you can probably just type reboot at this point. (Obviously, it did not shut-down. Also obvious, the "-r" option to rc.unRAID (part of clean powerdown) is broken) Link to comment
bdee1 Posted April 24, 2013 Author Share Posted April 24, 2013 My shares are actually still accessible from my windows machine so it looks like the array is still up but the telnet session has not returned to the prompt yet. It is just hanging there. Link to comment
mrow Posted April 24, 2013 Share Posted April 24, 2013 Do you have any files open anywhere? Close them if you do. Close any open shares you have open in Windows. Make sure you are in the root directory in your telnet session (type "cd /" to go to the root directory) as even accessing a share through telnet can prevent the array from stopping. Also check to make sure there aren't any plugins or anything keeping the array from stopping. Type ps-ax and see if you see any processes from any plugins you have running. If there are, kill the process by typing "kill" and the PID number. Link to comment
bdee1 Posted April 24, 2013 Author Share Posted April 24, 2013 My telnet session has not returned to the command prompt yet though. Should inopen another command prompt to do this? Link to comment
Joe L. Posted April 24, 2013 Share Posted April 24, 2013 My telnet session has not returned to the command prompt yet though. Should inopen another command prompt to do this? yes, or try control-C Link to comment
bdee1 Posted April 25, 2013 Author Share Posted April 25, 2013 control c didnt want to work for me. it just put a ^C in the telnet window. so i did a ps -ax and theres a whole bunch of items listed - how do I know which ones I have to kill? Link to comment
bdee1 Posted April 25, 2013 Author Share Posted April 25, 2013 ok i got it - i found this... 26858 ? Sl 13:43 ./Plex Media Server and once i killed it the server commenced rebooting. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.