March 13, 201610 yr Here is an odd thing. I am sitting here streaming some video over my network and I had went to a different share that is on a different drive. When that drive was spinning up my video had lagged. I wouldn't quite say it's an issue but just something to take note. OR maybe I am missing something?
March 13, 201610 yr my bad.. lol Noticed also you didn't say which disk the file you were playing (that had the issues) was playing from. However, after a cursory look at your diagnostics file (before I go to bed) I noticed 2 things: 1. For disk Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4E1992613 it appears that you have an uncommonly high number of UDMA CRC Errors: 199 UDMA_CRC_Error_Count 0x0032 200 198 000 Old_age Always - 1508763 This is usually evidence of a bad data cable / dodgy connection. As I said I am not sure if this has anything to dow with your issue BUT correcting it is not a bad idea. Try reseating / replacing the cable. 2. I noticed that on the 6th minute past the hour EVERY hour your unRAID machine renews its DHCP release. Like above, I am not sure if this could cause an issue BUT I do wonder. Also, is this by design? See below: Mar 12 08:06:49 Tower dhcpcd[1501]: br0: renewing lease of 192.168.1.155 Mar 12 08:06:49 Tower dhcpcd[1501]: br0: rebind in 2700 seconds, expire in 3600 seconds Mar 12 08:06:49 Tower dhcpcd[1501]: br0: sending REQUEST (xid 0x6c44c38b), next in 4.1 seconds Mar 12 08:06:49 Tower dhcpcd[1501]: br0: acknowledged 192.168.1.155 from 192.168.1.1 Mar 12 08:06:49 Tower dhcpcd[1501]: br0: leased 192.168.1.155 for 7200 seconds Mar 12 08:06:49 Tower dhcpcd[1501]: br0: renew in 3600 seconds, rebind in 6300 seconds Mar 12 08:06:49 Tower dhcpcd[1501]: br0: writing lease `/var/lib/dhcpcd/dhcpcd-br0.lease' Mar 12 08:06:49 Tower dhcpcd[1501]: br0: IP address 192.168.1.155/24 already exists Mar 12 08:06:49 Tower dhcpcd[1501]: br0: executing `/lib/dhcpcd/dhcpcd-run-hooks' RENEW Mar 12 08:06:49 Tower dhcpcd[1501]: br0: ARP announcing 192.168.1.155 (1 of 2), next in 2.0 seconds Mar 12 08:06:51 Tower dhcpcd[1501]: br0: ARP announcing 192.168.1.155 (2 of 2) Mar 12 09:06:49 Tower dhcpcd[1501]: br0: renewing lease of 192.168.1.155 Mar 12 09:06:49 Tower dhcpcd[1501]: br0: rebind in 2700 seconds, expire in 3600 seconds Mar 12 09:06:49 Tower dhcpcd[1501]: br0: sending REQUEST (xid 0x859ad49d), next in 4.4 seconds Mar 12 09:06:49 Tower dhcpcd[1501]: br0: acknowledged 192.168.1.155 from 192.168.1.1 Mar 12 09:06:49 Tower dhcpcd[1501]: br0: leased 192.168.1.155 for 7200 seconds Mar 12 09:06:49 Tower dhcpcd[1501]: br0: renew in 3600 seconds, rebind in 6300 seconds Mar 12 09:06:49 Tower dhcpcd[1501]: br0: writing lease `/var/lib/dhcpcd/dhcpcd-br0.lease' Mar 12 09:06:49 Tower dhcpcd[1501]: br0: IP address 192.168.1.155/24 already exists Mar 12 09:06:49 Tower dhcpcd[1501]: br0: executing `/lib/dhcpcd/dhcpcd-run-hooks' RENEW Mar 12 09:06:49 Tower dhcpcd[1501]: br0: ARP announcing 192.168.1.155 (1 of 2), next in 2.0 seconds Mar 12 09:06:51 Tower dhcpcd[1501]: br0: ARP announcing 192.168.1.155 (2 of 2) Mar 12 10:06:49 Tower dhcpcd[1501]: br0: renewing lease of 192.168.1.155 Mar 12 10:06:49 Tower dhcpcd[1501]: br0: rebind in 2700 seconds, expire in 3600 seconds Mar 12 10:06:49 Tower dhcpcd[1501]: br0: sending REQUEST (xid 0x60b5e96b), next in 4.5 seconds Mar 12 10:06:49 Tower dhcpcd[1501]: br0: acknowledged 192.168.1.155 from 192.168.1.1 Mar 12 10:06:49 Tower dhcpcd[1501]: br0: leased 192.168.1.155 for 7200 seconds Mar 12 10:06:49 Tower dhcpcd[1501]: br0: renew in 3600 seconds, rebind in 6300 seconds Mar 12 10:06:49 Tower dhcpcd[1501]: br0: writing lease `/var/lib/dhcpcd/dhcpcd-br0.lease' Mar 12 10:06:49 Tower dhcpcd[1501]: br0: IP address 192.168.1.155/24 already exists Mar 12 10:06:49 Tower dhcpcd[1501]: br0: executing `/lib/dhcpcd/dhcpcd-run-hooks' RENEW Mar 12 10:06:49 Tower dhcpcd[1501]: br0: ARP announcing 192.168.1.155 (1 of 2), next in 2.0 seconds Mar 12 10:06:51 Tower dhcpcd[1501]: br0: ARP announcing 192.168.1.155 (2 of 2) Mar 12 11:06:49 Tower dhcpcd[1501]: br0: renewing lease of 192.168.1.155 Mar 12 11:06:49 Tower dhcpcd[1501]: br0: rebind in 2700 seconds, expire in 3600 seconds Mar 12 11:06:49 Tower dhcpcd[1501]: br0: sending REQUEST (xid 0xc9fb65bc), next in 4.1 seconds Mar 12 11:06:49 Tower dhcpcd[1501]: br0: acknowledged 192.168.1.155 from 192.168.1.1 Mar 12 11:06:49 Tower dhcpcd[1501]: br0: leased 192.168.1.155 for 7200 seconds Mar 12 11:06:49 Tower dhcpcd[1501]: br0: renew in 3600 seconds, rebind in 6300 seconds Mar 12 11:06:49 Tower dhcpcd[1501]: br0: writing lease `/var/lib/dhcpcd/dhcpcd-br0.lease' Mar 12 11:06:49 Tower dhcpcd[1501]: br0: IP address 192.168.1.155/24 already exists Mar 12 11:06:49 Tower dhcpcd[1501]: br0: executing `/lib/dhcpcd/dhcpcd-run-hooks' RENEW Mar 12 11:06:49 Tower dhcpcd[1501]: br0: ARP announcing 192.168.1.155 (1 of 2), next in 2.0 seconds Mar 12 11:06:51 Tower dhcpcd[1501]: br0: ARP announcing 192.168.1.155 (2 of 2) Mar 12 12:06:49 Tower dhcpcd[1501]: br0: renewing lease of 192.168.1.155 Mar 12 12:06:49 Tower dhcpcd[1501]: br0: rebind in 2700 seconds, expire in 3600 seconds Mar 12 12:06:49 Tower dhcpcd[1501]: br0: sending REQUEST (xid 0xabc748cf), next in 4.4 seconds Mar 12 12:06:49 Tower dhcpcd[1501]: br0: acknowledged 192.168.1.155 from 192.168.1.1 Mar 12 12:06:49 Tower dhcpcd[1501]: br0: leased 192.168.1.155 for 7200 seconds Mar 12 12:06:49 Tower dhcpcd[1501]: br0: renew in 3600 seconds, rebind in 6300 seconds Mar 12 12:06:49 Tower dhcpcd[1501]: br0: writing lease `/var/lib/dhcpcd/dhcpcd-br0.lease' Mar 12 12:06:49 Tower dhcpcd[1501]: br0: IP address 192.168.1.155/24 already exists Mar 12 12:06:49 Tower dhcpcd[1501]: br0: executing `/lib/dhcpcd/dhcpcd-run-hooks' RENEW Mar 12 12:06:49 Tower dhcpcd[1501]: br0: ARP announcing 192.168.1.155 (1 of 2), next in 2.0 seconds Mar 12 12:06:51 Tower dhcpcd[1501]: br0: ARP announcing 192.168.1.155 (2 of 2)
March 13, 201610 yr What you saw was a normal limitation of the Windows networking connecting to the server. Happens to everyone unless their player buffers enough video length to play through the pause.
March 13, 201610 yr What you saw was a normal limitation of the Windows networking connecting to the server. Happens to everyone unless their player buffers enough video length to play through the pause. I have never noticed it.
March 13, 201610 yr What you saw was a normal limitation of the Windows networking connecting to the server. Happens to everyone unless their player buffers enough video length to play through the pause. I have never noticed it. I believe that win10 has mitigated this to a certain extent. Win 7 and prior do have this problem, but your mileage will vary
Archived
This topic is now archived and is closed to further replies.