geekette Posted June 7, 2012 Share Posted June 7, 2012 I shutdown the server to do some maintenance .. to move a drive cage back a bit so the fan cleared the front bezels. I started it back up and clicked the button to start the array. It's trying to start up and disk2 says it is still trying to mount.. I see reads AND WRITES (wth?) happening to both disk2 and the parity drive while this is trying to mount.. I dont' understand this.. what's going on sigh. Quote Link to comment
geekette Posted June 7, 2012 Author Share Posted June 7, 2012 okay, it finally started up but not without writing around 5000 blocks to disk2 and the parity drive.. wow. The array consists of parity drive, disk1 and disk2. Quote Link to comment
geekette Posted June 7, 2012 Author Share Posted June 7, 2012 btw it also started a parity check automatically without asking me. Quote Link to comment
geekette Posted June 7, 2012 Author Share Posted June 7, 2012 Btw, when I shut it down it wouldn't not unmount the disks .. it kept trying over and over.. shut down all the clients and it kept trying.. then I finally went to the console and logged in and typed reboot. Then powered it down after it rebooted. did the maintenance and powered it back up and took forever to mount disk2. (and all those reads/writes to disk2 and parity drive occured). Quote Link to comment
JonathanM Posted June 7, 2012 Share Posted June 7, 2012 Totally normal behaviour after a bad shutdown. Never force a shutdown unless you have no other choice, always use the webgui. I'd bet one of your addons is not shutting down properly, or you forgot to shut it down before trying to stop the array. Quote Link to comment
Rajahal Posted June 7, 2012 Share Posted June 7, 2012 What version of unRAID are you using? Are you running any add ons? Can you provide a syslog? If you check your syslog, you will likely see a bit about 'replaying journaled transactions'. This is the reiser file system performing its own data recovery automatically, which explains all the read/write activity on disk2. As jonathanm said, this is all normal behavior after an unclean shutdown (caused by typing 'reboot' at the system console). The server taking a long time to unmount the disks was likely from an add on or other program trying to access one of them. Quote Link to comment
geekette Posted June 7, 2012 Author Share Posted June 7, 2012 I have no add-ons. Running 5.0 rc3 Quote Link to comment
dikkiedirk Posted June 7, 2012 Share Posted June 7, 2012 For me it was SABNZB causing the fact that I could never stop the array and then cleanly powerdown. I now stop SABNZB first and/or use the powerdown script. Will the powerdown script also be invoked by simply pressing the on/off button? Quote Link to comment
geekette Posted June 7, 2012 Author Share Posted June 7, 2012 Where is this power down script in case I need to shut it down from the console--i.e. if it won't unmount from the webgui. Quote Link to comment
geekette Posted June 7, 2012 Author Share Posted June 7, 2012 Never force a shutdown unless you have no other choice, always use the webgui. Whenever I have to shutdown the system I always first stop the array with the webgui, then i do the shutdown from the webgui as well. However it would not unmount the volumes no matter what I tried. I wanted to do some sort of shutdown on the system instead of just powering it off so I logged into the console and shut it down there with a "reboot" command. Is there some other script I could try running instead of "reboot" if it comes to this again? Quote Link to comment
BetaQuasi Posted June 7, 2012 Share Posted June 7, 2012 The powerdown script people refer to is installed from unmenu. Quote Link to comment
dgaschk Posted June 7, 2012 Share Posted June 7, 2012 But unmenu is not required for the script. It is just a shell script. Quote Link to comment
Recommended Posts
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.