sacretagent

Well it works but all SF plugins are not working now as they are depending on the SF core package Stats are giving an error no icon and page for cachedirs and so on .... SO I hope somebody is going to address that as otherwise we will have to all go back to hacking the go file ..... and that then again is not good for the safe mode option and there we go again in that vicious circle .... anyway not really Tom's problem ... just wanted it mentioned so the newbies know what is happening .... and we get this 20 times in this thread ... not that this will stop them

hahaha found that one myself to let the snowy mountain dissapear.... but still all our SF plugins are not working ? Speeding_Ant you gonna make them work with this new GUI ?

same question ... does this mean the end for simple features? we will have to live with the snowy mountain ?

Does this mean the end of Simple Features ? just checking ..... before i reboot both servers with this new gui...

Let's just hope he doesn't forget the realtek drivers for the rest i have time ... and my unraid is humming fine....

guess somebody would have to make a cron editor plg script that loads the saved cron jobs .... just first idea what comes in my head ... or tom could make it a gui feature

Zoggy i hope you plan to have a look at the powerdown script too Thanks in advance

batt01 remove the # before var $consoleHost = '192.168.1.40'; the line should become var $consoleHost = '192.168.1.40'; just be sure to have the right ip too

HI most of these storageworks enclosures have a build in smart array controller and an expander the smart array controller will not work with unraid as it is a hardware raid controller ... so you will need to check if the one you saw has only he expander ... otherwise you are not going to get it to work ...

unraid 16B break the SF frontpage no more totals and the normal table is malformed now see underneath

well new version broke definately simple features.... diskinventory symbol is all the way left nearly .... where it was all the way right side normally! also no array totals any more... no more x gb free and a total of all writes and reads... but that is a SF problem... speeding ant said something about talking with Tom so he might be working at an update for that.... anyway nothing functional missing and it seems to be working as usual.... gonna do a parity check now

didn't forget the realtek nic drivers ? just kidding.. don't want a c release

I have one ... 8 gb big mm which reminds me i changed this too last week went from the unmenu swapfile to theone's plugin as it has a rc.d stop command can the issue be there ??

Since last week i get OOM messages on both of my servers now i don't want to point the finger yet to unraid that's why i ask if something was changed as last week i upgraded on both machines unraid plex and made changes to the cache dirs script .... which should normally result in less memory usage in my eyes i went from starting cached dirs with -m 5 -M 20 -d 5 -p 200 to -d 4 so less parameters and so i guess less memory used anyway i nearly never got OOM kills on any of these machines even with vbox installed ..... now i get like 3 a day most of the time Java gets killed from crashplan plugin sometimes python ... but i would like to know if you changed something at the memory parameters in the last release ? i am thinking going back to 12a to see if i still have them there .... modified to add syslog syslog-2013-06-27.zip

bump... i hope somebody is looking into this? IF not what would be the way to call the right urls? what are the urls? 1. to stop array? 2. To powerdown ? how to put this in a cron job ?

Hi Joe I found the culprit i put a -e for the sabnzbd and utorrent and sickbeard program folder and now we are seeing seconds returns no real need to keep those in memory i guess ... especially the utorrent one gonna see now a bit if the sickbeard page with the banners is slow or not seems to be OK ... anyway THX for the help disks are spinning down much more now

mine also spin down

thx and HURRAY for the autoupdate feature

BOTEZ you are a hero !!! didn't know that was in phpvirtualbox mine was set to /root/virtualbox vms which is in ram of course

the flag file unraidsafemode not yet in 15a, but you'll be able to do that in the next version. Thank you. So conceivably in the future the browser might be able to create the file on the user's behalf (I know it's little, but it's one less thing to remember). Yes, we might even convince Tom to add another "checkbox" next to the existing "Reboot" button to indicate we wish to reboot in safe mode. (It could create the flag file if checked, and delete it when un-checked.) +1 on that as a lot of us are running headless... so the enable safe mode we need to attach a monitor for the moment if we can tick a reboot in safe mode from the GUI would be much easier most of us boot anyway with every plugin installed so we only need safe mode when it is not working as intended

LOL i am running plex for television series on a e-6500 core2duo no issues see sig

let me know when you want to test something .... last 2 nights i stopped the server manually by doing as above and no issues but i would like it to go by cron ASAP

HI joe you said me to look what is keeping my finds busy by running verbose and in the foreground From commandline root@p5bplus:~# cache_dirs -w -F -v -B -M 20 -d 5 -e .custom -e plex -e NZB -e .dropbox -e BIN -e Crashplan -e Thai_Torrents_complete -p 200 the -p 200 you told me one time to put that in a LOOOONG time ago... not sure if it is still needed... it returns these after going through the dirs no clue what this means though between last 2 lines there was a mover action going on just fyi

ok weebotech I have no more clean powerdown installed i changed the unmenu swap file for the plugin 5.0 script on recommendation of Joe did i remove -m 5 from the cache dirs startup parameters this evening i did following just clicked stop array waited like 3 minutes till the array stopped and all disks unmounted clicked stock power down button in the gui and yes the server shut down after like 4 minutes .... so how do we translate this now into a set of commands that we can put in a cron job ? and i would prefer to do it in commandline style (script) instead of calling url's just in case the emhttp is stalled for any reason that we still can shutdown the server....

i will let "theone" answer that question cachedirs stops with cachedirs -q .... but i asked in the cache dirs thread if we can also kill the finds it spawns.....