bubbaQ

There has been nothing to add for over a year. 4.5, indeed, 4.4 forward had everything needed IICR. CD support is not there, so you can't mount CDs in the VM, but that's not a big issue since you can install from flash.

The right stuff is there. SYSVIPC needed to be enabled for VBox, but that was done some time ago. I've installed VBox and VMWare on unRAID w/o a new kernel.

Found another issue with php.... output buffering does not work.

Yes, it can, but the delay long enough to trigger the payload could be from many different reasons... not failure to unmount. Think a 20+ disk system and all the disks have to first be spun up.

The Revodrive is really just 2 Vertex 2 SSDs, in a Raid1 setup. You can get the same results yourself with a good raid card, and 2 Vertex 2 drives.... and this is what a lot of speed-demons have been doing for a couple of years with SSDs. The advantage of the Revodrive is that it is a self-contained package, and optimized by Ocz as a package, and allows garbage collection (not trim)... and it all fits in a single slot. I'd like to see one in RAID5.

Could we get an event callout after 30 (or some user-configurable number) "Retry unmounting disk share(s)" attempts?

Somethings funny with events. On initial boot, these are the calls that are made to emhttp_event: driver_loaded array_started disks_mounted svcs_restarted <== but no "started" event after this When I press the stop button, these are the calls that are made to emhttp_event: stopping_svcs unmounting_disks stopping_array stopped svcs_started <== this is odd to see after "stopped" After the "start" button: array_started disks_mounted svcs_restarted <== but no "started" event after this

Something else to think about, w/r/t moving to Slackware 13.1. The new package tools, which use .txz file extensions and the xz compression libs. Scripts (and a package manager) will have to take that into consideration. That is why I have tried to limit requests for unRAID changes, to things that essentially can't be done in the field. The /boot/extra and the plugin architecture, makes field modifications a real usable option. Theoretically, with the right build environment, I can build any needed modules with the correct version magic and include them in a package, but they won't work without the kernel support, and they can't be added if something related that needs to be removes was not added as a module, but was built-into the kernel. FWIW, I added all the packages from 12.1 necessary to rebuild the kernel, with gcc4.2.3 and all necessary libs, and a full install of perl, all on a 512MB system, and it all worked fine. With /var and the initramfs working as ramdisks that can be swapped out, a swap file, relocation of part of the root fs (such as /usr) to a different storage device ... there are a lot of ways to skin the cat if the kernel or initramfs grows. Suggestion for a change - when an empty cache drive is installed from scratch and formatted, I'd suggest that unRAID to automatically make a swap partition/file on it too. That way, a cache drive will potentially help a lot of issues, and not just file copying.

Thank you for this... I'll try to put together a plugin to ID the CPU, and test modules, so the Sysstat plugin can be able to get temps, fanspeeds, etc. Perhaps even the fancontol stuff too. It has always irritated me a bit that the lmsensors folks used perl for their scripting of sensors-detect... so Iook forward to redoing it in php.

Sweet! I completely understand if this makes the kernel too big... if the modules are big, but the kernal is not and you need to shrink the initramfs, perhaps you can post the modules separately for plugin devs to install selectively if needed.

My request was *not* for unRAID array disks to use ext3/4... just to have support in the kernel since I often mount drives and dd images from other systems to copy their contents to unRAID... and they are often ext3.

Yes, but it requires ACPI, and some people disable ACPI for stability reasons. p4clockmod does not need ACPI.

+1 ext3... Please add all the frequency scaling modules... (no need for debug or stats). Current Intel SpeedStep options are all for mobile chipsets, and not needed. [*] CPU Frequency scaling [ ] Enable CPUfreq debugging < > CPU frequency translation statistics Default CPUFreq governor (performance) ---> -*- 'performance' governor <M> 'powersave' governor <M> 'userspace' governor for userspace frequency scaling <*> 'ondemand' cpufreq policy governor <M> 'conservative' cpufreq governor *** CPUFreq processor drivers *** <M> ACPI Processor P-States driver <M> AMD Mobile K6-2/K6-3 PowerNow! <M> AMD Mobile Athlon/Duron PowerNow! <M> AMD Opteron/Athlon64 PowerNow! [*] ACPI Support <M> Cyrix MediaGX/NatSemi Geode Suspend Modulation < > Intel Enhanced SpeedStep (deprecated) < > Intel Speedstep on ICH-M chipsets (ioport interface) < > Intel SpeedStep on 440BX/ZX/MX chipsets (SMI interface) <M> Intel Pentium 4 clock modulation <M> nVidia nForce2 FSB changing CD/DVD filesystems support would be nice too. When you get to big changes, I would like to see some type of native encryption... or at least some hooks for it so a plugin could be made that can do it. Nice to hear about the move to 13.1 too.

There is a bug in using: parse_str(str_replace("+","%2B",$argv[2]), $_GET); php's parse_str() function hoses up periods in the string... converts them the underscores. I'm using this now: $_GET = array(); foreach (explode("&", str_replace("+","%2B",$argv[1])) as $item) { list($k, $v) = array_map("urldecode", explode("=", $item)); $_GET[$k] = $v; } If someone is also using php_cgi, they can test for unRAID's php+cli using: if (php_sapi_name() =="cli") { // unRAID php_cli is in use } else { // real php_cgi is in use }

I am working on a plugin for that in -beta2. It also includes disk inventory such as date purchased, date to be replaced, etc. The preliminary parts are in BubbaTools for 5.0

You need to factor in that you mill HAVE to replace the batteries every 3 years. So a larger unit with more runtime will cost more to refurb. No matter what anyone tells you, replace the batteries every 3 years. Stick a label on the front with the battery install and replacement date... so every time you see it, you will be reminded --- "Oh yea... I got to replace those batteries in ____ months." Do NOT trust the weekly tests of the UPS. The only legitimate test is a full run-down test. Do one of those periodically too.

Never mind... I found it... I'll write it up after I redo it again.

Yes -- it has to be for the asus module to work. I'm working on sysstat graphics for temps and such, as well as for alerting. Coretemp reports wrong numbers on asus mobos with the atk0110.

I'll buy that... you could even go as far as the PCH folks did, and remove telnet from the appliance. But I think I failed in communicating my goal -- I am doing a "Shutdown Watchdog" plugin for *me* because I'm a dev.... just like Lundman developed a procedure to get telnet going on the pch. There are going to be plugins that, whether unRAID is an appliance or not, are aimed at making a dev's life easier, and are not necessarily something for a generic "appliance" user. I posted a couple of ideas so other devs could kick the tires. I have long-encouraged the "appliance' model for unRAID, just like the other NAS boxes -- but this idea was just for a dev tool.

Well, that's a theory vs practice thing. I agree with the theory, and in large part in application, but it is not a 100% solution. For example, open terminal sessions.... ."user errors" Many applications that have stock scripts, that record PIDs of the running process when starting, and use that pid file to stop the app, but are pretty stupid if the pid file is lost. The "stop" code in an application start|stop|restart script needs to make SURE the app stops, such as testing the existence of the PID file, and testing if the process is still alive after a "nice" stop command.... and escalate from a sighup to a sigkill. Devs need to closely examine, and recode if needed, the start|stop|restart scripts for their plugins.... stock that comes with the application may likely not be sufficient for unRAID. And just to be clear, I'm not looking for unRAID doing this on its own... I was just thinking out loud about possible approaches for a "Shutdown Watchdog" plugin. About half the time I go to shutdown unRAID, it fails and I have to go hunting for what the problem is.... (i.e user error)... so I'm using a script to kill stuff with open files now.

run this command from telnet: wget http://slackware.cs.utah.edu/pub/slackware/slackware-12.1/slackware/a/usbutils-0.73-i486-2.tgz -O /tmp/lsusb.tgz;installpkg /tmp/lsusb.tgz

Please add ASUS ATK0110 to included hwmon chips. A lot of ASUS mobos have been using this chip for hw monitoring. BTW, I just figured out that if coretemp is loaded, it blocks asus_atk0110.ko.... so building in coretemp into the kernel instead of a module is a problem.

Here's another idea.... In the stop callout, I could launch a watchdog program in the background, that has been configured with: - initial timeout period - list of file that are safe to kill - secondary timeout period - list of programs to never kill After it is launched in the background, it will: - Wait the initial timeout period - Kill "safe to kill" processes that have open files on the array and no children. It could stop there... or optionally it could continue: - wait the secondary timeout period. - Kill other processes not listed in the "never kill" list with open files on the array (checking for children). - umount any loopbacks on the array.

How about an event callout when emhttp has to retry unmounting? Particularly if you can count the loops, and do a callout after every some interval, such as after 10 retries.

Understood.... but being stuck in an infinite look that locks you out of the tools to use to allow the loop to terminate, is a bit Kafkaesque.