March 26, 200719 yr I posted this in anther thread, but have done some more research today. I've taken out any variables I can think of. I already have an identical UnRaid running on 3.1beta2 that's working fine, but all these tests were done on this machine. Mobo: Asus P5LD2-SE R2.0 (RTL8111B PCI-E Gb LAN controller) I'm getting REALLY slow speeds reading from this Mobo under v4.0 betas. Xfer rate approx 0.36Mbps. Some info:- Copying an exactly 10gb file from Disk1 on UnRaid to my DesktopPC Under version 4.0beta4 Under version 3.1beta2 These are copying the same file on the same server to the same location on my PC, only difference in UnRaid software version . ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes ifconfig eth0 Link encap:Ethernet HWaddr 00:1A:92:09:A0:34 inet addr:10.0.0.10 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1713 errors:0 dropped:0 overruns:0 frame:0 TX packets:3379 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:177450 (173.2 KiB) TX bytes:3982875 (3.7 MiB) Interrupt:17 Base address:0xa000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) The following things checked but made no difference:- 2nd UnRaid on same network shut down in case some Samba conflict issue Ethernet cable replaced One of the 2 GigLan switches on the route bypassed Transfers to this server are fine under v4, pretty fast actually. Mark.
March 27, 200719 yr Author Is anyone else trying v4 on a RTL8111B PCI-E network motherboard? I note that had I bought the P5LD2-VM SE I thought I was ordering I'd be OK, that has the Intel Chipset. I'm wondering whether to take this server back to 3.1beta2 as I need a lot of files from it moved to another server. If it's sortable within a few days I'll wait, but if it's causing problems I'll need to revert to v3 for a while. I'd rather not go back to v3 as I think my shrinking/expanding drives between v3 & v4 are what are causing perceived HDD integrity problems & forcing parity issues. I'm fine if I stick on v3, I'm fine on v4 (except for network speed), it's swapping between the 2 that's causing problems. I just tried using the 100M Network port on my PC to force the UnRaid to communicate at that speed, it makes little difference, network utilisation peaks at around 1% instead of around 0.5% Mark.
March 28, 200719 yr Author Anything I can try that may improve network performance on the RTL8111B under v4.0beta? I currently can't even stream FLAC music properly at current performance levels. Thanks, Mark.
March 28, 200719 yr Hi Mark, The proper driver for your network chip is in -beta6... will be posted today.
March 28, 200719 yr Author Hi Mark, The proper driver for your network chip is in -beta6... will be posted today. Thanks Tom, I'll post the results straight away (assuming I'm still up). Mark.
March 28, 200719 yr Author Ok, 4.0-beta6 is up. And unfortunately not a whole lot better for me Using Beta 6 for same file as previous tests Peaks at 0.09%, average 0.05% What could be up here Tom? v3.1 works just fine with this chipset. Mark.
March 28, 200719 yr Author In telnet window, type this command: lsmod and tell me what it outputs. lsmod Module Size Used by md_mod 52264 8 sata_promise 9092 3 ata_piix 11524 0 libata 85796 2 sata_promise,ata_piix r1000 15000 0 r8169 22808 0 Thanks Tom, Mark.
March 28, 200719 yr There are two drivers for your chip loaded: r1000 - Realtek's linux driver r8169 - the Open Source linux driver for Realtek NIC's The preferred driver is r8169, which is why we didn't build in r1000 originally; but, apparently r8169 has problems with your motherboard. But now we're in a case where both are loaded, and this is not right. From console (not telnet window), type this: rmmod r1000 rmmod r8169 modprobe r1000 ifconfig The first two commands remove both drivers. The 'modprobe' command will reload only the r1000 driver. In the output of the 'ifconfig' command you should see an entry for 'eth0'. Now see if you can connect via network and re-run your transfer test. If this solves the problem then we'll remove the r8169 driver entirely.
March 28, 200719 yr Author Solved the problem! Beta6 with r8169 "Modprobed out" If this solves the problem then we'll remove the r8169 driver entirely. Not as good performance as under 3.1, but perfectly useable I suspect. I did some "googling" regarding Linux 2.6+ Kernels & RTL8111B, lots of problems under many different Linux flavours. Let's hope they get the driver sorted properly soon. Thanks Tom, Mark.
March 28, 200719 yr Author I'm not sure whather this is of any help but here is the "lsmod" info after modprobe driver removal:- lsmod Module Size Used by r1000 15000 0 md_mod 52264 8 sata_promise 9092 3 ata_piix 11524 0 libata 85796 2 sata_promise,ata_piix Thanks, Mark.
March 28, 200719 yr I'm not sure whather this is of any help but here is the "lsmod" info after modprobe driver removal:- lsmod Module Size Used by r1000 15000 0 md_mod 52264 8 sata_promise 9092 3 ata_piix 11524 0 libata 85796 2 sata_promise,ata_piix Thanks, Mark. That's how I would expect it. I'll remove the r8169 in next beta. BTW, the unRAID 3.x releases only had the r1000 driver.
March 29, 200719 yr I'll remove the r8169 in next beta. BTW, the unRAID 3.x releases only had the r1000 driver. Removed in 4.0-beta7.
Archived
This topic is now archived and is closed to further replies.