Threaded Mode | Linear Mode

simoncn · 21-12-2015, 23:04

(21-12-2015 22:57)ted_b Wrote: I will try those configs, but keep in mind that those music players/servers also hanging off the Diablo switch also buffer like crazy anything of size from the NAS (redbook is about all they digest without buffering). Yet when the NAS is not involved (CAPS->Diablo switch -> Rendu) my music is fine.

I'll report back tonight. Thx again
Ted

It could be an issue with the NAS -> Diablo connection or the Diablo -> router connection. My guess is that auto-negotiation of the link speed on one of these connections isn't working correctly.

ted_b · 22-12-2015, 02:27

simoncn · 22-12-2015, 07:52

Thanks for this. As you have suspected, it seems to be an issue with the NAS as this is the only component that is involved in all the problem scenarios.

How is the NAS network connection configured? Are you using link aggregation for the two Ethernet ports on the NAS or are there any other custom settings? It would be a good idea to post to the Synology forums about this problem if you haven't done so already.

ted_b · 22-12-2015, 14:24

Thx. No link aggregation, just using bottom Ethernet port (LAN 4) and set up for static IP and IPv6 turned off (as per Synology). Using 8.8.8.8 as DNS server, etc. As you could see whether I go through Diablo (fiber LC multimode-via FMC converter) or go to router (copper Cat6A) something is causing bandwidth/buffering issues.

I will virtually copy and paste my posts here to create a Synology thread. Thx so much for your efforts, even though we, early on, determined Minimserver to not be the culprit.

simoncn · 22-12-2015, 14:38

(22-12-2015 14:24)ted_b Wrote: Thx. No link aggregation, just using bottom Ethernet port (LAN 4) and set up for static IP and IPv6 turned off (as per Synology). Using 8.8.8.8 as DNS server, etc. As you could see whether I go through Diablo (fiber LC multimode-via FMC converter) or go to router (copper Cat6A) something is causing bandwidth/buffering issues.

I will virtually copy and paste my posts here to create a Synology thread. Thx so much for your efforts, even though we, early on, determined Minimserver to not be the culprit.

Good luck with this and I hope you are successful! If/when you find a solution, please post back here for the benefit of others who might have a similar problem.

ted_b · 22-12-2015, 16:54

Thanks. Will do. For those wishing to follow along, here is my Synology post:
http://forum.synology.com/enu/viewtopic....7&t=108311

ted_b · 11-01-2016, 15:36

Update: With the help of Synology support folks (ticket issued, email support) we found the culprit to the above bandwidth buffering issues. It ended up being a bad disk (disk 3 of 9) that, although reported healthy, was about to crash soon and when removed (and then replaced) cleared up all bandwidth/buffering issues. So...the big questions are still bugging me: 1) why did my Synology NAS report it as healthy, and require deeper reporting: 2) why would a fault tolerant (one disk hot swappable) RAID setup be bothered by a bad disk, but not a crashed or removed disk?

Anyway, thanks Simon! I appreciate the help to spur me on to uncover the culprits.

simoncn · 11-01-2016, 16:03

(11-01-2016 15:36)ted_b Wrote: Update: With the help of Synology support folks (ticket issued, email support) we found the culprit to the above bandwidth buffering issues. It ended up being a bad disk (disk 3 of 9) that, although reported healthy, was about to crash soon and when removed (and then replaced) cleared up all bandwidth/buffering issues. So...the big questions are still bugging me: 1) why did my Synology NAS report it as healthy, and require deeper reporting: 2) why would a fault tolerant (one disk hot swappable) RAID setup be bothered by a bad disk, but not a crashed or removed disk?

Anyway, thanks Simon! I appreciate the help to spur me on to uncover the culprits.

Thanks for posting this. It might help other users who experience a similar problem.