sacretagent

Joe any way to include killing the different find threads when you do a cache-dirs -q ? now when you stop cache dirs the find threads go on for sometimes like 15 minutes.. depending in which dir they are... if we can kill these finds then we can stop the array quicker ? or is there something i don't know that makes it dangerous to kill those finds ? OH yeah using cache dirs with these arguments via SF Jun 17 19:27:09 P8H67 cache_dirs: version=1.6.7 Jun 17 19:27:09 P8H67 cache_dirs: command-args=-w -B -m 5 -M 20 -d 10 -e mysql -e plex -e headphones -e couchpotatov2 -e Crashplan -e lazylibrarian -e Thumbnails

You may need to re-engineer your system so that addons/plugins gracefully shutdown via the rc scripts. This script is hooked into those also How is virtual box started and shutdown? Maybe it needs to use the emhttp event system, or a script for it needs to be put there. The power down script is a last ditch effort. While it's been safe for all these years, the complexity of various configurations makes it difficult. I can add a hook to call unRAID's original powerdown script or not replace it at all. However, I'm not sure how to deal with all the other addons and plugins that people use. If there are apps mounted on an array disk, emhttp is going to hang and retry until that is satisfied. Which means, that the apps using array disks, need to really be part of emhttp events. What happens if you don't install the powerdown script? Hi Weebootech virtualbox has it own stop script -> /etc/rc.d/rc.virtualbox stop when i don't install the script and do following 1. disable swap (which i really would also like a new version for... so that it disables when you stop the array) 2. stop the array 3. confirm to stop the server 4. push the stock power down button in the gui then stop the array takes a while.. and most of the time i need to do a few killall find to let it unmount all drives if i don't so that then find keeps some disks spinning but once i see all disks are unmounted and the click the power down button in the gui then the server stops normally i have asked already in few posts is there a command we can use to disable the array ... aka the command that is used when we push the stop button in the gui .... i think if that one can be adapted for cache dirs , find threads to be killed then we are golden or adapt cache dirs so when we do a -q that all open find threads are killed off ..... cause it seems to be find that is keeping my disks busy Update installed THEONE's swap file plugin as it also has a rc.d/rc.swapfile stop script so no need to kill swap file any more

Sorry, what is the "trust array" procedure? I believe he is referring to this old procedure: http://lime-technology.com/wiki/index.php/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily This forum post talks about it and what you can do instead with Release 5.0: http://lime-technology.com/forum/index.php?topic=19385.0 Yep that's the one but even that version 5 workaround is not working .... at least i never got it to work tried with and without page refresh or are we supposed to do it different way ? as you made a check thingie for trust parity ?

Hi tom can you repair one more thing before this goes to final ? the "TRUST ARRAY" procedure this doesn't work properly for a long time now and it would be nice for it to work properly again... maybe a mod can transfer this to issues forum ?

that's the same script see my post here what happens when i try to use it .... don't worry about this thread anymore .... that somehow resolved itself after i killed crashplan ... it seems crashplan was sucking up all bw .... after i closed crashplan the gui came back

speeding ant are we going to see an updated rc15 release of simple features ? as it seems clear we aren't going to see a plugin manager before 5.1 .... and this should be the rc before 5.0 just wondering what your plan is for SF ?

joe mymain.conf is it supposed to be updated automatically ? i just ask as i put some diskattributes in there for temperature collections on a br10 controller but i have to remember every time to copy/paste them ... can i not just put auto update no in it ? #AUTO_UPDATE=NO or are you guys changing this at a regular base ? P.S. could this unmenu.base.lib.awk issue contribute to my shutdown issue ? i also had sames issue that it wouldn't install.. it did today though ....

ok why is this old script "working" on garycase setup and not on mine ? don't understand that ... like i said array shuts down ok but computer doesn't turn off .... here is syslog from last night started at 23:40 .. disabled swap at 23:43 and it seems he tried unmounting everything but disk 2 was still in use he unmounted disk 2 finally and unmounted the array as i said before he didn't shut down so at i tried calling the original powerdoen script from unraid /usr/local/sbin/unraid_powerdown but somehow he still didn't want to shut down you can clearly see the drives were not mounted this went on till i stopped the server by pushing the powerbutton till he stopped with as result that he didn't wol this morning ..... but no parity check as the array was unmounted so what is preventing the system to shutdown ? this is driving me bonkers that other people say it works and it won't work here ...... and also that it worked till rc12A only from rc13 it doesn't work any more for those interested the issue is on the P8H67 in my signature Unraid.zip

stock unraid stop array in GUI and stop computer works fine what doesn't work is the powerdown script any more here is what happens with RC15 1. swapoff -a ... swap file gets disabled no issues 2. /sbin/powerdown array gets disabled the right way but seems after the array shuts down that the other addons get activated again i see plex and python in top also the console says going for shutdown .. but the console continues working i had to shutdown the server by keeping the power button till he shutdown this was working well till rc12.a so not sure what has changed ... how can i put my server of gracefully from a cron setting ?

having had issues with rc13 and rc14 with that powerdown script from 2008 am i still a bit reluctant to try it again.... was hoping a new version would be made but it seems we will have to do with this one will test this evening when everything is off on the network

I thought that one was outdated... is somewhere on a blog too as for unraid 4.3

i lost my emhttp somehow last night while the machine was doing it's monthly parity check and probably a crashplan backup anyway i would like to know how to cleanly shutdown the machine from commandline ? i still have access to ssh so i guess it could be done searched everywhere ... but only thing i could find is an article for unraid 4.3 so can somebody help me out and maybe post it to the wikie ? running latest rc5.14

so any of you linux guru's going to have a stab at this new script ? to save energy on my already high power bill i power down every night one of my servers with cron so a new working script would be welcome

upgraded to rc14 but changed the linux.cfg file for the one from rc12a again with the new linux.cfg file i had only 3064440k ram in top with the old one i have again 4064440k in top powerdown with stock script works custom powerdown script still doesn't work so we will need a new one urgently can anybody tell me what the command is that happens when we press stop the array on the gui ? would like to use that command in a cron for the moment till somebody makes a better powerdown script uninstalling the old script now as no use

Lainie are you going to make a release for the rc14? or wait a bit longer till we see where things are going ? MMM Next time look on her site before you create a post new release in on the site already -> http://vbox.a1aina.com/ modified because i am an idiot

as promised my syslog from last nights experiment don't see much difference between them (with powerdown script and without) but you guru's have a crack at it Joe, what would be the command equal to pressing the stop button on the gui ? was thinking of using this in my cron 1. swapoff -a wait 5 minutes 2. use that stop command wait 5 minutes 3. /usr/local/sbin/unraid_powerdown while we wait for a good guy to update the powerdown script syslog11062013.zip

well it seems to be the script it is midnight here and everybody is asleep so i followed what the conclusions were this is what i did 1 swapoff -a 2. waited to be sure that swap file was unmounted 3. pressed stop on the SF gui 4. waited till all drives unmounted (took again a bit of time since find had spawned 3 threads) 5. typed /usr/local/sbin/unraid_powerdown (as this would be the stock unraid powerdown script) and hey my server powered off cleanly so yep in my case it might be the powerdown script i will send the syslog tomorrow morning when i wake up not going to start the machine again to collect the log now.... need ZZZZZzzzzZZZ

Joe answers underneath Do you have SimpleFeatures web-interface installed? YES Do you have the "clean-powerdown" package installed? YES What is the output when you type: 'which powerdown' /sbin/powerdown Do you have the apcupsd UPS package installed (through unMENU, or directly downloaded)?NOPE Do you have the apcupsd UPS plugin installed (through SimpleFeatues)?NOPE Are you stopping the array first using the web-interface?NOPE Are you using the web-interface to power down the array?NOPE Are you using the server chassis "power button" (short press) to initiate a power down?NOPE Are you using "control-Alt-delete" to initiate a power down?NOPE I use cron to 1. swapoff -a 5 minutes wait 2./sbin/powerdown it works like i said 95% of the time in 12a and the 5% it doesn't it seems that something else is keeping the array busy.... most of the time find demons still running in an oddball case old samba threads that do not close for some reason normally powerdown should stop swap too but i noticed depending how much swap usage you have it doesn't always work so i give it some extra time to turn off

well make a gui that allows us to boot in unraid without plugins and one normal boot ?? removing all plugins is simply not practical takes too much time and disabling them in the gui is not same as without loading them (wife want the latest tvshow, kid wants the latest cartoon ) so all time that is left is a quick reboot to activate the new version if there would be some cooperation from lime tech on the plugin standards with a dependency checking then a lot of issues would not arrize also we all thought RC13 would be a quick update from rc12a..... not a kernel upgrade that fucks up everything again anyway it is proven already that it is not the shutdown plugin Well, that package is from Oct 26, 2008. Many things have changed since then. The package may be making some incorrect assumptions about the current unRaid. It may, or may not have anyhing to do with the problem. It is just an interesting coincidence that of all the people who've reported this problem so far, they've all been using that plugin. I've not got it installed and I have the shutdown problem! I'll try replacing all of the files on the flash-drive when I get home to see if that solves it. It appears to have worked for others. Barzija no crash ... just the server not shutting down properly which results in a parity check..... anyhow ... what does this powerdown script from yours do and how to install it ?

From your syslog... Jun 9 11:04:06 P8H67 kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. The filesystem on your USB flash disk is corrupted. Take the USB flash disk to a windows machine and fix that with a chkdsk There's no /sbin/powerdown. Now the powerdown command resides in /usr/local/sbin/ and that's in the searchpath. (If you like, you can use the replacement for it from my signature.) You too have installed some third-party plugin to do your powerdowns in some unusual way. Jun 9 23:13:41 P8H67 rc.unRAID[14748]: Killing active pids on the array drives Jun 9 23:14:09 P8H67 rc.unRAID[15584]: Killing active pids on the array drives Looks like that plugin hooks itself by means of /etc/rc.d/rc.local_shutdown or something and so it gets itself executed every time you try ro powerdown your computer. It will be interesting to see if you can reproduce a server crash after removing that plugin. damn will check the flashdrive once the parity check completes in 8 hours or so the powerdown script is the one from unmenu have been using it since i started and i know it is not the unraid one but this one stops all plugins before it stops the array and is for 95% doing a good job... sometimes it takes it a while to close all find demons but otherwise it always worked anyway i tried yesterday one time to stop the array too with the effect that was described from other people aka no acccess to the server any more but we will see.... i will checkdsk the flashdrive and try again.... pity it is the server with virtualbox so will need to upgrade again

i also went back to 12a the not shutting down issue is a big deal breaker ..... i attached last syslog but i am affraid it ia a bit of a mess first i did swapoff -a then /sbin/powerdown then i saw that was not working so i did another /sbin/shutdown -h now and again not shutting down so i hold the powerbutton of course he is running another parity check again.. third or fourth in last 2 days syslog.zip

hi, have a strange issue an not sure how to solve it virtualbox makes a dir under /root called virtualbox vms he puts in there the vbox files so when i reboot i lose the vm's not sure why this happens the normal vbox dir is /mnt/cache/vbox the linked virtualbox in root links to that folder so am a bit at a loss why this happens

the php sttings from the webplugin have soap disabled standard search through this post the solution is in here maybe do a search for SOAP on the forum it is just changing the soap setting in the PHP.cfg file

ThX Joe it is definately SMB that is accessing it had to do the command a few times to catch it small question the user on the SMBD is nobody if it was another computer lets say mine where i am logged in as bob for example, would the user then not be bob ? i know i used toolbox yesterday evening from my laptop but that is shutdown now ..... going to close explorer windows to see

nothing there the grp command has a lot of activity but all seems normal as it is on the cache drive .. going to increase my putty buffers to see all