Although it has been a while, in the past I thought I typed "Stop" at the command line prompt to take the drives off-line. Yesterday, when I tried to do this I kept getting a prompt stating thiss is an invalid command. What I seemed to find doing a search, supported my thinking that the  "Stop" command was valid.

 

Can someone please tell me what to type when I am at the root level to take the machine off line so that I can have a clean power down.

 

Thanks

Although it has been a while, in the past I thought I typed "Stop" at the command line prompt to take the drives off-line. Yesterday, when I tried to do this I kept getting a prompt stating thiss is an invalid command. What I seemed to find doing a search, supported my thinking that the  "Stop" command was valid.

 

Can someone please tell me what to type when I am at the root level to take the machine off line so that I can have a clean power down.

 

Thanks

Tom removed it when it was no longer valid on newer releases.

 

See this post for replacement commands. 

 

Best is the "powerdown" command, but you must install it prior to needing it.  A short "stop" script is also given, as well as a series of commands you may type at the command line.

 

Joe L.

 

 

I decided to rework Step 4 of the first section of the Troubleshooting page, Brian's section, but had quite a bit of trouble.  Perhaps I should have asked Brian if he wanted to take a stab at it.  The problem is, as mentioned above, the stop command is not included with unRAID, and therefore this section does not work, has not worked for some time.  Even when we had a stop command, it did not always work well, would not unmount more than 12 drives, was never updated.  Would some of you please take a look at this, come up with some ideas, or edit it yourself.  The changes I've made, while relatively complete, have completely broken the comforting simplicity and continuity of Brian's 10 steps.

 

I took a look at a few of the stop scripts, and the contents aren't suitable for the command line.  Loops have to be in one-line commands.  And some of it looks too complex for error-free typing by non-Linux users, when they are stressed, having server problems, and no recourse but to type at a Linux console, perhaps for the first time.

 

We really need an official stop command again, included in the stock unRAID, or an official way to stop the array and power down at the console, easy enough for new users, but up to date in all of the cleanup currently needed, to close down the array.  Plus, I wonder if it also needs to handle the NFS shares.  Perhaps the powerdown and stop scripts also need updating for NFS?  Has anyone checked to see if all of this has been moved into the normal Linux termination processes, the run level stuff for instance?  (I'm speaking about things I haven't researched, know little of.)

Joe L. Thanks for the heads up on this issue. It has probably been over two years since I used the Stop command and  was unaware of this change. I lost all connectivity with the server and could do a clean shutdown. After fixing that problem, I powered back up and stoped the parity check. I then brought the drives back on line and found that parity was valid. I am assuming this is alright and did not bother to do a full parity check.

 

I should have spent more time visting the forum to learn about these changes, but I have been building a new house and that has taken all of my free time. I will use the procedure described in the link you provided, but I think Rob J has the right idea.

 

Thanks

I decided to rework Step 4 of the first section of the Troubleshooting page, Brian's section, but had quite a bit of trouble.  Perhaps I should have asked Brian if he wanted to take a stab at it.  The problem is, as mentioned above, the stop command is not included with unRAID, and therefore this section does not work, has not worked for some time.  Even when we had a stop command, it did not always work well, would not unmount more than 12 drives, was never updated.  Would some of you please take a look at this, come up with some ideas, or edit it yourself.  The changes I've made, while relatively complete, have completely broken the comforting simplicity and continuity of Brian's 10 steps.

 

I took a look at a few of the stop scripts, and the contents aren't suitable for the command line.  Loops have to be in one-line commands.  And some of it looks too complex for error-free typing by non-Linux users, when they are stressed, having server problems, and no recourse but to type at a Linux console, perhaps for the first time.

 

We really need an official stop command again, included in the stock unRAID, or an official way to stop the array and power down at the console, easy enough for new users, but up to date in all of the cleanup currently needed, to close down the array.  Plus, I wonder if it also needs to handle the NFS shares.  Perhaps the powerdown and stop scripts also need updating for NFS?  Has anyone checked to see if all of this has been moved into the normal Linux termination processes, the run level stuff for instance?  (I'm speaking about things I haven't researched, know little of.)

 

Thanks RobJ.  I think your updates to Step 4 look good.  Since installing the powerdown script and ctrl-alt-delete means of launching it, I have always just pressed ctrl-alt-delete to cleanly powerdown the server.  Everyone should install this.  It is THE BEST way to power down a server from the console.

I decided to rework Step 4 of the first section of the Troubleshooting page, Brian's section, but had quite a bit of trouble.  Perhaps I should have asked Brian if he wanted to take a stab at it.  The problem is, as mentioned above, the stop command is not included with unRAID, and therefore this section does not work, has not worked for some time.  Even when we had a stop command, it did not always work well, would not unmount more than 12 drives, was never updated.  Would some of you please take a look at this, come up with some ideas, or edit it yourself.  The changes I've made, while relatively complete, have completely broken the comforting simplicity and continuity of Brian's 10 steps.

 

I took a look at a few of the stop scripts, and the contents aren't suitable for the command line.  Loops have to be in one-line commands.  And some of it looks too complex for error-free typing by non-Linux users, when they are stressed, having server problems, and no recourse but to type at a Linux console, perhaps for the first time.

 

I agree with this statement entirely.  before in installed the powerdown script with the control-alt-delete function i would have to do a hard shutdown in the rare cases.  Now i don't have to worry about the server coming back up and starting a parity check as this script does a very good job of shutting down the array.

We really need an official stop command again, included in the stock unRAID, or an official way to stop the array and power down at the console, easy enough for new users, but up to date in all of the cleanup currently needed, to close down the array.  Plus, I wonder if it also needs to handle the NFS shares.  Perhaps the powerdown and stop scripts also need updating for NFS?  Has anyone checked to see if all of this has been moved into the normal Linux termination processes, the run level stuff for instance?  (I'm speaking about things I haven't researched, know little of.)

 

Thanks RobJ.  I think your updates to Step 4 look good.  Since installing the powerdown script and ctrl-alt-delete means of launching it, I have always just pressed ctrl-alt-delete to cleanly powerdown the server.  Everyone should install this.  It is THE BEST way to power down a server from the console.