August 5, 201213 yr Hi, Newbie here so go easy please! Wanting to fill up my new server with around 6TB of data - once this 6TB is added I'll be adding a 1TB cache drive. All is great until we're around 20GB into the transfer then things start slowing down. My transfer speeds to a brand new array are erratic. My peak is 55-60MB/s, but the lowest can be as low as 2-300KB/s. I transferred 22GB worth of MKV files (so lots of large ones is what I mean) at the peak rate, but then the transfer speed dropped down to the lowest. It's currently hovering between 600k and 2MB/s. See screenshot for what I mean... My hardware is as follows: unRAID Server Pro v5 rc5-8168 Asus P8H77-V LE, BIOS 0237 Intel i3 2120 3.3ghz 8GB RAM TX750W Corsair PSU 1x Supermicro SAS-AOC-SASLP-MV8 2x 3tb drives, 1x 1.5tb and 1x 1tb drives. All precleared successfully (reports attached for what it's worth). What have I done before posting? - I pre-cleared all drives on 2 passes. - I've switched from Unraid rc5 to rc5-8168 without any noticable difference (currently running rc5-8168). - Used two different gigabit switches (identical results) - Swapped all cables several times (identical results) - searched the forums - fiddled around with MTU jumbo frames (identical results, back at default now) Output of ethtool eth0 is: 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 pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes Output from ifconfig is: eth0 Link encap:Ethernet HWaddr c8:60:00:9b:55:64 inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:597591 errors:0 dropped:0 overruns:0 frame:0 TX packets:158244 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:897302441 (855.7 MiB) TX bytes:11382227 (10.8 MiB) Interrupt:43 Base address:0x2000 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:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 B) TX bytes:560 (560.0 B) I've not yet completed the initial parity sync (through sheer impatience!). Would this resolve the issue most likely? Transfers being done over gigabit ethernet from a Windows 7 machine. Read transfer speeds are in excess of 80MBs so I don't suspect network hardware at fault here... Any help please? My gut feeling is that it's related to that initial parity sync? Please tell me I'm right!! syslog.txt preclear_reports.zip
August 5, 201213 yr the syslog says its checking parity. i imagine writing to it and checking at the same time is the cause. it also says unclean shutdown detected. what happened??
August 5, 201213 yr Author i just rebooted. ah yes, i also rebooted via ssh... i get the same results whether a parity check is in progress or not btw.
August 5, 201213 yr Author just an update - have transferred several more files since earlier, one MKV file was 32GB in size. all was going fine until it hit the 22GB mark, transferred at 30MB/s, then suddenly like it hit a wall BAM - down to a 2-300KB/s. Parity sync is still ongoing but I'm curious as to whether this is normal or not...
August 6, 201213 yr Author FYI - parity sync finished this morning. so far am 824GB into my 2.5TB transfer and have seen steady 30-50MB/s write speeds. don't want to count my chickens yet but it looks like waiting for the parity sync was the answer.
Archived
This topic is now archived and is closed to further replies.