June 27, 201016 yr I recently switched from OpenFiler to unRAID, got my drives in, setup a user share, and started copying my data over. What's weird, is I'll start to copy a 300mb folder and it'll scream along for the first 50-60 megs, but once it hits 70mb -- it just grinds to a halt. Then, maybe will get to ~ 100mb then complete fail, returning an error message in my respective OS. (I've tested in both OSX and Windows) This also happens via both SMB and NFS. I've tried multiple computers, switches, a direct crossover connection and multiple patch cables. My motherboard is a MSI K8NGM2-FID and the onboard LAN chipset is a VITESSE vsc8201RX. I'm also, for the time being, only using the (4) on-board SATA ports. FWIW, This is the same hardware setup I used with OpenFiler for ~ 2 years with no problems. Any help would be greatly appreciated. I've attached my syslog. syslog.txt.zip
June 27, 201016 yr Author Hrm.. I can't even properly stream an MP3 file from an unRAID share. iTunes will begin to play the track, get about 5-6 seconds in, then skip to the next track (which takes about ~ 5 seconds to start playing).
June 27, 201016 yr If I had to guess it would probably be that the network chipset is not 100% stable. Try using a PCI NIC card and see if that helps the situation (you will probably have to disable the onboard NIC).
June 27, 201016 yr Author I don't want to put the cart before the horse here, but I think I may have resolved the issue... I have a local Debian box acting as a gateway/dhcp/dns server on my network, and it's assigns its IPs using DNSMasq. I flushed the DNSMasq cache, forcing "Tower" to renegotiate a DHCP lease -- now my network transfers and iTunes streaming seem to be working. Odd. I still have about 6TB of data to transfer over, so we'll see... If I had to guess it would probably be that the network chipset is not 100% stable. Try using a PCI NIC card and see if that helps the situation (you will probably have to disable the onboard NIC). I figured the same thing initially, so I left a ping test up overnight (~ 8 hours) with 1024 byte packets. 0 lost. So, I think it's safe to say it's not the NIC.
June 27, 201016 yr Author Turns out, I was wrong. The problem seemed to have temporarily been resolved by the refresh, however, once I queued up about 500GB of files -- it crapped out after 100GB. I forgot to mention, I currently have parity sync turned OFF, so that shouldn't be mucking anything up. *sigh*
June 27, 201016 yr Ping will not test the NIC the same way file transfer will. I think your NIC is shot. Try disabling it and using a PCI NIC.
Archived
This topic is now archived and is closed to further replies.