jowi

I'm sorry, but you have to be more specific... i don't see a log file in the folders it created, i even bashed into the docker with docker exec but also can't find a log file there, or i am overlooking it. And what url do i need to copy? Where do i get this url?

Probably a stupid question but... where do i enter my dropbox account/password? I've installed the docker, it runs... but now what?

Note to self: info here: https://packaging.python.org/tutorials/installing-packages/#ensure-you-can-run-pip-from-the-command-line pip does not work from scratch, first run: python -m ensurepip --default-pip Then optionally upgrade pip using: pip install --upgrade pip And then just install the package from https://pypi.org/project/requests/ using: pip install requests

Not specifically for unraid, but i'm trying to build some python scripts for calling a REST API from Sonarr, but i seem to be missing some imports, like requests, httplib2 etc. I have no idea how to install these? I do have Python installed and running using the Nerd tools plugin. If i google they keep referencing the pip tool, but it also doesn't seem to be installed?

But... if there is no reason to use XFS over Reiserfs, why did unraid move to XFS in V6?

I've installed the latest unraid v6 on a spare laptop. I formatted the ssd disk, and it defaults to XFS. My V5 unraid server which i plan to update at some moment in time, is formatted as ReiserFS if i'm correct? What is the upgrade plan for XFS when coming from v5? Is there some conversion tool? Or do i have to empty every drive and reformat and put the data back?

I've installed unraid 6 for the first time and added the system temp dynamix plugin, it installs, but where do i find it? It doesn't show up anywhere? The Stats plugin gets it's own menu item... where can i find the temperatures?

I guess that is exactly what happened. Indeed my disk1 is a collection of a lot of smaller files. Maybe preclear could disable cache_dir when it starts, or inform the user that it is better to stop cache_dir while preclearing?

No, all plugins are stopped. I can see the read counter from the webgui on disk1 increasing, also the disk light on the case is blinking... so there is definitly something going on... *edit* i missed one plugin, cache_dirs... stopped it, it looks like all disks are spinned down... still weird, normally cache_dirs does not have that effect...

I've disabled all plugins, the only thing that is running is preclear. Also there is constant reading from disk1? Is preclear causing this, and why?

I remember i noticed this before but i'm not sure what the reason was. I am running preclear on a new WD red, but it keeps all my drives in a spinned up state? If i spin them down, they start right up. Is this a known 'feature'?

Works perfectly on 5.0.4. You're probably doing it wrong. It was DESIGNED for v5.x ...

From the 5.0.4 thread: Maybe Tom should open a 'unraid roadmap' topic.

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.