Joe L.

If writing to the protected array, about 20 to 30 MB/s sustained is usual IF the system sending the data can sustain that rate. Some people will report faster speeds on smaller files, but in most cases they are writing to the disk buffer cache. If the source PC only has a 100Mb/s LAN port, then best you'll see is 10 to 12 MB/s. If writing to the cache drive, you can expect faster speeds, but again limited by the LAN and the source PC. Joe L.

Didn't see a response to this one...Tom? That's trivial to put into your 'go' script and/or implemented via a plugin, not something necessarily I want to put as a 'hardcoded' policy. I guess I could be talked into it. Since emhttp cannot be re-started without core-dumping in the 5.X series (or, at least not without un-mounting all the disks), it is best if emhttp is not the best candidate to be killed in an out-of-memory condition. Once emhttp is killed, there is no easy way for most unRAID users to stop the array cleanly If an add-on used all the memory, best let the add-on be killed first. Yes, it can be a plugin to be optionally installed, or even a line in the config/go script. (I can accept either solution since it does not need to be compiled into emhttp.)

Or, once you've set any package to auto_install on reboot a line is added to the end of your config/go script that will invoke all the whatever.auto_install files in /boot/packages Type this command to create your own unmenu.auto_install echo "/boot/unmenu/uu" >/boot/packages/unmenu.auto_install It is not part of the unMENU distribution. For it to be invoked you must set at least one package to be re-installed on reboot in the unMENU package manager. I suggest installing the clean-powerdown and setting it to be re-installed on reboot. The "image_server" is another package I suggest you install and set to re-install on reboot. Joe L.

This topic has been moved to User Customizations. [iurl]http://lime-technology.com/forum/index.php?topic=27756.0[/iurl]

It was removed many versions of unRAID ago. It was replaced with the "Utils->New Config" button on the 5.X series. Joe L.

I've been running my older unRAID server on 512 Meg of RAM for the past 8 Years. Most of my movies are 4 to 5 GB ISO Images with the newer Blu-Ray images much larger. I've never run a cache drive except to perform tests. (I really don't care how fast I write to the array. It is fast enough for me. The "cache" drive concept was originally conceived and added by lime-tech when write speeds were about 8 or 10 MB/s. unRAID and the linux kernel have improved greatly since then making the cache drive largely not needed.) The basic file-serving capability of unRAID does not take much memory. 2GB of RAM is more than enough.

First, unRAID itself is NOT hot-swap capable for the protected array. However, if your motherboard AND disk controller AND power supply can handle plugging in a new disk drive without being powered off first, it might work for disks not assigned to the array. You don't specifically need a hot-swap bay, perhaps an external SATA docking adapter might suit your needs. (not one connected via USB, but one connected via an ESATA cable. Although USB would work for preclearing, it would be much slower.) Something like this using the ESATA cable: http://www.newegg.com/Product/Product.aspx?Item=N82E16817153071R

Did you make your script executable? chmod +x /mnt/cache/Minecraft/go Are you using the correct "case" (Linux is case-sensitive.) Minecraft != minecraft Is "java" in your path? is it even installed? (it does not come with unRAID) Joe L.

There is NO NEED for you to do anything to save the results. The results are automatically saved to the directory /boot/preclear_reports. The instructions you have seen to "grep" the syslog pre-date the automatic saving of results. under /boot/preclear_reports will be three files per disk. 1. the initial SMART report 2. the final SMART report 3. and the summary results comparing the two SMART reports. Those files are put there upon completion of the process for a given disk. (don't look for them there until each disk is done) Joe L.

Yes, there is a step-by-step set of instructions here: http://lime-technology.com/wiki/index.php/Configuration_Tutorial Joe L.

It is not a part of simple-features, it is available here http://lime-technology.com/forum/index.php?topic=2817.0 and invoked from the command line.

If all you have are 3TB drives you'll not be able to assign any of them when running 4.7 unRAID. It does not support drives over 2.2TB. You could easily download unRAID 5.0-rc13 and upgrade your new unRAID USB drive, or wait a few days (predicted/hopefully) and download 5.0-final. In the interim, even though you cannot assign them to the array, you can preclear the drives on your existing 4.7 version to exercise them and weed-out those that will fail in their initial few hours. (With 24 drives I predict you'll have a few that fail soon after being put into service.) Forum experience of other unRAID users seems to show about 10 to 20% will experience unreadable sectors or some other fault in the first few hours of use. The number of supported drives has been incrementally increased over the years and unRAID versions. (Eight years ago unRAID was originally limited to 11 data drives+parity, and that was when the largest drive you could purchase was 500Gig) The increase from 21 to 24 data drives was very recent. ( I think it was 5.0-rc8) Joe L.

Tom#1, Has the issue where disks could not be added to the array unless precleared been resolved in this release? (I saw no mention of that fix in the release notes) Is there a reason you did not set the oom_score_adj for emhttp to -1000 in rc13? I saw it is still set to "0", making emhttp as likely a candidate as any to be killed in an OOM situation. Joe L.

And, you should REBOOT with the old release before upgrading. So many of the issues I've been seeing with either the array not stopping, OR the array not completing startup are because of a plugin or add-on that will either not allow shut down or start-up. If your current handling of start-u or shut down is flawed, no sense upgrading until AFTER you've disabled the plugin/addon and can cleanly stop the arrray/reboot correctly.

Three questions: What URL are you using to access emhttp? Can you access it by IP address? Have you disabled ALL the add-ons you might have added? Open a thread in the rc support forum, attach a zipped copy of your syslog. Joe L.

Whoa nice! Button is re-enabled. I started a restore from Crashplan... as soon as that is done, will fire off a parity check. Thanks for the quick update Joe! You were the first to report the issue. (most people do not leave open slots) Fix was easy.

Guys can someone answer this please? I am getting nervous. The wiki is out of date. Do not stress over it.

let me take a quick look. Joe L. You should now be able to check for/install updates (on the user-scripts page) and have that button work as expected.

let me take a quick look. Joe L.

They are NOT errors. They are just matching a pattern in unMENU that used to only match on a different message that was an error. I'll update unMENU so it does not highlight those lines. You should be able to use its Check-for-Updates feature later today to update your version of unMENU. Again, those are NOT errors. They are only lines describing how your memory is being allocated. Joe L.

There are two issues. First, your syntax A line like this will do it /mnt/cache/Minecraft/go HOWEVER... At the time the command is being run in the config/go script the odds are emhttp has not yet started the array or mounted the cache drive. you need to wait for it to be present. Something like this might work. while [[ ${LOOP:=30} -gt 1 && ! -d /mnt/cache/Minecraft ]] do (( LOOP=LOOP-1 )) echo "Waiting for /mnt/cache to come online ($LOOP)" sleep 1 done /mnt/cache/Minecraft/go Add those lines to the END of the config/go script. There will be another issue though in that the server will likely NOT stop properly since the cache drive will be busy unless you STOP the minecraft server first. A much better method is to tie int the "event" system in unRAID. See this post for how http://lime-technology.com/forum/index.php?topic=26201.0

This topic has been moved to User Customizations. [iurl]http://lime-technology.com/forum/index.php?topic=27730.0[/iurl]

You can ignore them, as they will occur if you have no plugins loading.

That is not an error, it is just a syslog line with the word "kernel" within it.

It booted! (on the C2SEE SuperMicro MB... without needing an additional Realtk driver version 13a) No other report so far, but it is important first step. Joe L.