Hi, I have set up a new Unraid server.

everything seems to work fine, but when I copy or stream movies of the server. I get small hang-ups.

but they are enough to stop the movies or tv series completely.

 

have tried moving the drives over on another computer but still same problem.

also tried another network cable and another port on the switch.

I have another Unraid on same switch with no problems.

 

hoping someone could find the answer.

 

best regards

Christer Fresh

 

 

 

smal-nas-diagnostics-20170730-1017.zip

Give a complete hardware list (MB, CPU, RAM, NIC, etc.).

 

Is the problem only with high bit rate steams (example--BluRay) as compared with lower Resolution streams?

 

List any plugins and Dockers you are using.

 

Have you rebooted all routers and switches on your network?  (These devices all contain little computers and sometimes need a reboot to clean things up.)

 

Go to the Dashboard view.  In the 'System Status' section, select 'Errors' from the dropdown list.  Now look at the 'Network' section for the error counts and report what you see.

Try disabling network bonding and connect to your switch with just one cable.

Sent from my ASUS_Z00AD using Tapatalk

problem is on low bitrate streams also.

 

tried rebooting every network device yesterday.

 

can see there is one transmit error in dropdown menu.

 

disabled bonding, still the same

 

motherboard: MSI - P67S-C43 (MS-7673)

Network card onboard only (Realtek 8111E)

CPU: Intel® CORE™ i5-2300

16bg ddr3 Ram

 

what’s weird is I used only the HDD and "usb Unraid drive" and moved everything over in a new computer (this one) got the same dropouts as previous machine.

 

and where using no addons, but still it drops.

Edited July 30, 20178 yr by chFresh
adding info

Post latest diagnostics

Sent from my ASUS_Z00AD using Tapatalk

Here is a new diag

smal-nas-diagnostics-20170730-2327.zip

only thing i haven't used before is the Usb stick. but as i can understand after Unraid is running its not using it much, so speed doesn't mater?

I also tried switching IP just in case. same old

Edited July 30, 20178 yr by chFresh
typo

I am not a Guru in looking at syslogs but I did take a look at yours.  The only thing that I saw was these entries at the end of the syslog. 

 

Jul 30 17:34:58 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:36:54 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:39:00 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:41:04 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:43:19 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:45:20 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:47:24 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:49:24 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:51:30 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:53:43 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:55:45 Smal-NAS kernel: br0: received packet on eth0 with own address as source address
Jul 30 17:57:47 Smal-NAS kernel: br0: received packet on eth0 with own address as source address

I googled this message and it seems to be a problem that has been seen before.  It seems to be related more to the network side of the issue.  I compared your network.cfg file to mine and found several differences.  (I have both bridging and bonding turned-off on both of my servers.)  I suspect that either bridging and/or bonding has been set up for your NIC.  Did you see this post from @unevent?

 

8 hours ago, unevent said:

Try disabling network bonding and connect to your switch with just one cable.

 

Perhaps, he (or someone else more knowledgeable in network setup) will jump in and provide some insight. 

 

PS---  Your hardware should be able to stream without issue using unRAID.  There were some real streaming  issues a couple of years ago with older (and much, much) slower hardware.  That was the reason for the questions about your hardware setup. 

Edited July 30, 20178 yr by Frank1940

It appears the br0 bridge is causing ARP issues.  Try disabling the bridge, assuming you have no Dockers or VM configured/running.  Don't have the time at the moment to get deeper.  Perhaps others may be able to help more.

Seems like that did the trick   (disabling bridging)

but that means i cant use docker or VM's  ?

 

While I am not an expert in this area, not all Dockers require a special setup of IP access.  And, when it is required, if it is not automatically configured on install, the support thread will provide either instruction or help. If you want more information on Dockers, look here:

 

    https://wiki.lime-technology.com/UnRAID_Manual_6#Using_Docker

 

VM's are a separate issue as, depending on what type of VM you want, there may even be specific hardware requirements for it.  Here is a link with a lot more information:

 

   https://wiki.lime-technology.com/UnRAID_Manual_6#Using_Virtual_Machines

 

9 hours ago, chFresh said:

Seems like that did the trick   (disabling bridging)

but that means i cant use docker or VM's  ?

 

 

You can still use Docker/VMs.  Not sure if the issue goes away when you create a Docker/VM or not, but since you had none created turning off the bridge was simple test.  As for why it does this I am not exactly sure, but I do see this issue in many logs that users post.

Seems i was a bit to fast on the trigger

seems i am still having dropouts.

any more ideas ?

 

seems as there are fewer dropouts than before, but still too many.

smal-nas-syslog-20170803-2258.zip

smal-nas-diagnostics-20170803-2258.zip