jowi

With the other driver things look like they've improved: eth0 Link encap:Ethernet HWaddr 00:25:90:24:21:fb inet addr:192.168.1.25 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1173731 errors:0 dropped:133 overruns:0 frame:0 TX packets:742456 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1542232683 (1.4 GiB) TX bytes:341258090 (325.4 MiB) Interrupt:20 Memory:f7800000-f7820000 I'll keep an eye on it...

As a x9scm owner running 5.0.4 i can confirm this i guess: root@UNRAID:/boot/custom# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:25:90:24:21:fb inet addr:192.168.1.25 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:184535543 errors:6 dropped:4257546 overruns:0 frame:3 TX packets:174391691 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:167360230858 (155.8 GiB) TX bytes:152357047663 (141.8 GiB) Interrupt:20 Memory:f7800000-f7820000

Thanks, but then what? I've been running this config for over 1,5 years 24/7 now, never had this issue. Also after rebooting, everything seems to function normal again. Why disable all addons now after all? Its not logical. Maybe if it occurs again and again, disabling addons and plugins is a valid method for troubleshooting, otherwise i dont see why it would have any affect at this moment. I'd rather have some insight in what this error actually was, and if something might be compromised, how to check or test it.

Is there anything i should check or run? Smart reports? Chkdsk or something equal? Change some setting?

I did not find any errors.

I've added the syslog, apart from the message, i can't find any strange things or segfaults. Did a reboot, now all seems fine again. Still, i would like to know what caused this? And furthermore, can i do some checks or run some analysis to find out what might be wrong?

Suddenly i can not get to my shares. /mnt/user shows up in putty/mc as 'user?' Error seems to be : endpoint is not connected (Other emhttp) In webgui when entering contents of share, the msg is: Warning: scandir(/usr/local/emhttp/mnt/user/TVSeries): failed to open dir: Transport endpoint is not connected in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 20 Warning: scandir(): (errno 107): Transport endpoint is not connected in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 20 Warning: array_diff(): Argument #1 is not an array in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 20 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/webGui/include/myPage_content.php(61) : eval()'d code on line 20 from syslog: Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/Backup Transport endpoint is not connected (Other emhttp) Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/DVD Transport endpoint is not connected (Other emhttp) Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/Downloads Transport endpoint is not connected (Other emhttp) Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/Media Transport endpoint is not connected (Other emhttp) Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/Movies Transport endpoint is not connected (Other emhttp) Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/Music Transport endpoint is not connected (Other emhttp) Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/MusicBlurays Transport endpoint is not connected (Other emhttp) Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/New Transport endpoint is not connected (Other emhttp) Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/TVSeries Transport endpoint is not connected (Other emhttp) Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/Time Machine Transport endpoint is not connected (Other emhttp) Jan 27 09:38:21 UNRAID emhttp: get_filesystem_status: statfs: /mnt/user/svn Transport endpoint is not connected (Other emhttp) Jan 27 09:38:36 UNRAID emhttp: Spinning up all drives... (Other emhttp) Jan 27 09:38:36 UNRAID emhttp: shcmd (201): /usr/sbin/hdparm -S0 /dev/sdb $stuff$> /dev/null (Drive related) ..etc etc etc What should i do? Reboot? *edit* have restarted smb from webgui, now all my shares are gone?? please help... syslog-20131227-114815.zip

Ok, i did not know that, everybody is hyping the vm model now and talking about how we should and must now create vm's if we want to run a plugin. Would be nice if the discussion would also cover us 'simple' users and our needs.

To you this is a good thing, for me... as a linux novice, i am affraid that if i HAVE to create vm's and set up a technically advanced system with hypervisors and other stuff i dont understand, only to run unraid... i think i will stop using unraid. I want to know, WHAT is the exact benefit for having unraid as a 64 bits environment, with the abilty to run vm's or be one itself? Will my data be protected better? Will my transfers go faster? In fact, i think if something goes wrong, with the current unraid i think i can manage correcting it, if i have a system that consists of vm's within vm's running vm's... i dont know what the hell i am doing anymore. Point is, i think this 64 bits version with vm support should be considered a professional or business version, not for home use... the power of unraid *was* that even people how did not know linux, could plug in a usb stick and have a solid NAS. With this version, not so much... I'm affraid the simple user will be left behind and unraid becomes something only die hard linux techies can setup and run.

I've been reading on v6 and vm's and plugins, am i correct in thinking that unraid 64 is now able to HOST vm's? So that e.g. unraid hosts a vm running linux, on which sabnzb and sickbeard etc are running? Or hosts vm's that run a 'plugin' each? Or should you install and run some virtualization software on your machine, prior to running unraid, so unriad becomes one of many vm's?

So, on windows 64 its no problem to run 32bits binaries without rebuilding. But on linux this not possible? Things have to be rebuilt for 64 bits otherwise they don't even run?

So, is this something i could just try on my 5.0.4 machine? I dont really care about or have any use for virtualization (i dont really understand what the fuzz is about and why people are excited about it...?) and i have some plugins running (sabnzb, sickbeard, squeezeserver) that might, or might not work...? Is that it? If this 64 bit version doesn't work for me, or doesn't add any value for my use, or if my plugins are incompatible, i can simply revert back to 5.0.4, right?

I did, but the info is mainly on the rs232 protocol, and what i need is the protocol a slave computer has to use over the network, to connect to the master (in our case, our unraid server). Maybe if i can fetch the sourcecode i can reverse engineer something, but the api/description itself would be better.

I am looking for some specs or an API to write my own tool/script (in python or C#) for doing this, but i can't find it so far. Any hints? If i telnet into my unraid machine on that port i get nothing, so i think it is some custom IP protocol?

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