jowi

Can you tell us what you are working on? I'm hoping you are focussed on porting addins like the SF stats etc? Or just minor fixes, like the spindown icon which is missing?

It works on v5.0. I do agree it takes a long time for updates, but the basics work just fine, and its a nice improvement over the stock gui.

Yeah, i can't imagine it would take so much time to convert some of the existing SF plugins to make them compliant to the v5 gui... They don't have to be built from scratch. And especially now SpeedingAnt and Tom are both involved, troubleshooting etc is much easier. @Tom, @SpeedingAnt, is there a roadmap for the webgui?

Any progress on the webgui itself? Would love to have the stats from SF e.g.

So these 3 parameters only influence the parity check speed, and have nothing to do with overall transfer speed or disk/data reading or writing speed?

I ran the first parity check with stock values; after that i experimented with your scripts. Basically, i did not run your script with stock values. Should i have done that? So: - Parity check 1 with stock values aug. 21st - ran the 1.1 script a few times for testing and used those values after that - ran the 2.0 script this morning in FULLAUTO, rebooted using the values it gave - ran the 2nd parity check.

Here it is. Tunables Report from unRAID Tunables Tester v2.0 by Pauven NOTE: Use the smallest set of values that produce good results. Larger values increase server memory use, and may cause stability issues with unRAID, especially if you have any add-ons or plug-ins installed. Test | num_stripes | write_limit | sync_window | Speed --- FULLY AUTOMATIC TEST PASS 1 (Rough - 20 Sample Points @ 3min Duration)--- 1 | 1408 | 768 | 512 | 151.7 MB/s 2 | 1536 | 768 | 640 | 157.7 MB/s 3 | 1664 | 768 | 768 | 159.7 MB/s 4 | 1920 | 896 | 896 | 160.3 MB/s 5 | 2176 | 1024 | 1024 | 161.4 MB/s 6 | 2560 | 1152 | 1152 | 161.8 MB/s 7 | 2816 | 1280 | 1280 | 161.0 MB/s 8 | 3072 | 1408 | 1408 | 161.9 MB/s 9 | 3328 | 1536 | 1536 | 161.9 MB/s 10 | 3584 | 1664 | 1664 | 161.9 MB/s 11 | 3968 | 1792 | 1792 | 162.2 MB/s 12 | 4224 | 1920 | 1920 | 162.4 MB/s 13 | 4480 | 2048 | 2048 | 162.5 MB/s 14 | 4736 | 2176 | 2176 | 162.4 MB/s 15 | 5120 | 2304 | 2304 | 162.5 MB/s 16 | 5376 | 2432 | 2432 | 162.4 MB/s 17 | 5632 | 2560 | 2560 | 162.5 MB/s 18 | 5888 | 2688 | 2688 | 162.5 MB/s 19 | 6144 | 2816 | 2816 | 162.6 MB/s 20 | 6528 | 2944 | 2944 | 162.6 MB/s --- Targeting Fastest Result of md_sync_window 2816 bytes for Medium Pass --- --- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)--- 21 | 5984 | 2696 | 2696 | 162.5 MB/s 22 | 6008 | 2704 | 2704 | 162.5 MB/s 23 | 6024 | 2712 | 2712 | 162.5 MB/s 24 | 6040 | 2720 | 2720 | 162.4 MB/s 25 | 6056 | 2728 | 2728 | 162.5 MB/s 26 | 6080 | 2736 | 2736 | 162.5 MB/s 27 | 6096 | 2744 | 2744 | 162.4 MB/s 28 | 6112 | 2752 | 2752 | 162.5 MB/s 29 | 6128 | 2760 | 2760 | 162.2 MB/s 30 | 6144 | 2768 | 2768 | 162.1 MB/s 31 | 6168 | 2776 | 2776 | 162.2 MB/s 32 | 6184 | 2784 | 2784 | 162.2 MB/s 33 | 6200 | 2792 | 2792 | 162.4 MB/s 34 | 6216 | 2800 | 2800 | 162.2 MB/s 35 | 6240 | 2808 | 2808 | 162.0 MB/s 36 | 6256 | 2816 | 2816 | 162.0 MB/s Completed: 2 Hrs 7 Min 1 Sec. Best Bang for the Buck: Test 3 with a speed of 159.7 MB/s Tunable (md_num_stripes): 1664 Tunable (md_write_limit): 768 Tunable (md_sync_window): 768 These settings will consume 45MB of RAM on your hardware. Unthrottled values for your server came from Test 21 with a speed of 162.5 MB/s Tunable (md_num_stripes): 5984 Tunable (md_write_limit): 2696 Tunable (md_sync_window): 2696 These settings will consume 163MB of RAM on your hardware. This is 41MB more than your current utilization of 122MB. NOTE: Adding additional drives will increase memory consumption. In unRAID, go to Settings > Disk Settings to set your chosen parameter values.

Did a before and after parity check. Before is with stock settings: Last checked on Wed Aug 21 18:04:00 2013 CEST (today), finding 0 errors. > Duration: 8 hours, 24 minutes, 50 seconds. Average speed: 132.1 MB/sec After is a full parity check after first optimizing settings with the script 2.0: Last checked on Tue Aug 27 20:41:17 2013 CEST (today), finding 0 errors. > Duration: 8 hours, 24 minutes, 13 seconds. Average speed: 132.2 MB/sec As you can see... no difference at all on the parity check speed. (4TB parity disk)

Thanks for this as well

Still, wouldn't hurt to attach your parity drive to the same controller the rest of you drives is on... maybe the Areca is fast enough on its own, but unraid can't handle the thing properly. I know a another user was always having problems with his transfer speeds on unraid, until he removed his Areca card... Sorry for the OT.

My guess is your Areca card... try using the parity disc on the SAS2LP as well. Why use this RAID card anyway?

Nevermind, not interested anymore. My extremely unstable and soon to be crashing server which is running al sorts of weird shit just can't handle it.

You sound very irritated and stressed out. Take a breath or two and try to react normal. FYI, until i upgraded to rc16c a few days ago, my server ran 24/7 over 130 days without any problems.

No need to get so cross, I was just trying to help. I am attaching here the script that I used to test my tunables. It does basically the same thing, but in only 60 lines of code. See if you like it, and canibalize it for your purposes any way you see fit. Enjoy the free fruits of my labor. Your script forces makes the webgui unreachable and forces unraid to start a parity check... i would advice NOT using it. Pauven's script can be run without any weird effects.

I noticed this too when I upgraded. So what I did to resolve this was to copy the green-blink.gif to green-blink0.gif as a temporary fix. cp /usr/local/emhttp/plugins/webGui/images/green-blink.gif /usr/local/emhttp/plugins/webGui/images/green-blink0.gif Encountered this as well, but did not notice it before...? Been running it for a few days now. I swear i've seen green blinking led's before... and now they're gone. Added issue on github.

I know this is not a valid assumption, but for some reason i find the performance of a parity check a good sign of the functioning and speed of the system as a whole. The check should be fast, and not slowed down by opening the webgui (as it did using the latest SF). I'm glad to see that the parity check under v5.0-rc16b running the new webgui is perfect: Last checked on Wed Aug 21 18:04:00 2013 CEST (today), finding 0 errors. > Duration: 8 hours, 24 minutes, 50 seconds. Average speed: 132.1 MB/sec (4TB parity disk)

This is a very good initiative. Can we add requests here as well? For me, if the stats page from SF is added, and the page where you can schedule a parity check, makes it more effective. But i'm sure those will show up in time Offcourse a plugin "manager" should be integrated, at this moment it is a bit confusing that the plugins tab actually does not contain active plugins but a list of available (official?) ones, while the active plugins themselves are placed under the settings tab... and even there they are all over the place. I have dropbox, slimserver and apcupsd under 'network services' (?) while the "unplugged" sickbeard and sabnzbd have there own "unplugged" 'chapter'... probably because the developer of those plugins decided so. Would be nice to remove the plugins from the settings tab and have a "plugin" tab that contains actual active (3rd party?) plugins, and a "plugin library" for a list of available plugins? (should even be a subpage within "plugins") Anyway, keep up the good work!

Loading the 'Plugins' page sometimes times out with an error, takes about 30 seconds of waitcursor & no response resulting in: "Warning: file_get_contents(http://lime-technology.com/wiki/index.php/UnRAID_Plugins): failed to open stream: Connection timed out in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 159 Warning: strpos(): Offset not contained in string in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 166 Warning: strpos(): Offset not contained in string in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 170"

This has been fixed. http://lime-technology.com/forum/index.php?topic=18310.msg256480#msg256480 Get the latest version from my github page. Thanks. Installed it, but it wont start. Complains about 'Starting LMS... lms.pid not created for some reason...' Any ideas? Issue with rights on some files? *edit* re-installed, re-booted, now works.

Thanks. Installed it, and noticed a problem with Logitech Squeezeserver plugin, on the settings page it has no description text, and the plugin page itself the layout is messed up. Could be the plugin is faulty, but it worked perfectly under SimpleFeatures.

What if i try this and for some reason i want to uninstall? On git it says the installer will delete the stock webgui in emhttp... how do we get the stock gui back after uninstalling the new webgui?

If they were for sale, i would get one or 2 myself

You can't just cut the power on the unraid server, i assume you're using a UPS in this scenario, which will do a clean powerdown when you cut power. Besides the fact that you are abusing the UPS this way, there is a bigger risk. Normally, in case of a power loss, you not only want to powerdown the unraid server in a clean way ASAP, but after that is done, also shutdown the UPS. If you don't, in case the power returns for like a minute or a few seconds and powers down AGAIN, you will be in the middel of starting up your unraid server again (because your using 'resume on powerloss') and you can't do a nice powerdown since the UPS probably is empty or near empty... this is why you do NOT want to resume on powerloss. Just stay off. So, do not use the UPS as a handy on/off switch... it's an emergency device, treat it as such.

http://cybershop.ri-vier.nl/5-bay-mobile-rack-module-hdr5-p-104.html

I've precleared 5 of these 4TB puppies at once using the same mainboard as you know, with only 2GB of memory. No problem. I would suspect the SATA contoller is just not up to the challenge. I would replace it with a Supermicro SAS2LP or an IBM 1015.