Mapped NAS drive sporadically disconnects which interrupts playback, but is immediately accessible afterward.

I'm at my wits' end for figuring out how to remedy this, I remember a similar problem creeping up perhaps a year ago, but no idea how I was eventually able to fix it. I have a synology NAS (Diskstation DS413j) connected to my local network through which I stream shows using MPC-HC, and a little less than hourly it will drop connection without warning and interrupt playback, while the connection is restored immediately when I try to re-access the drive. This happens to both computers which have the NAS drives mapped and occurs simultaneously between them.

No matter what settings and fixes I've applied to the two computers nothing has changed this behavior, so I have to think it has to do with the settings on the NAS, but changing the firewall settings, hard drive hibernation, user permissions, SMB protocol level, and any other host of fixes I've searched for haven't done a thing. Here's a screenshot of the behavior while I was running a ping -t on the NAS ip, showing a single instance of the ping request timing out which breaks the connection and interrupts playback, but every request following goes through without problem. None of the mapped drives from the second computer drop during this time and the music streaming to it goes uninterrupted as well (edit:worded werid, the mapped drives and music steamed are to/from a second computer, NAS not involved), it's only a problem with the NAS drives dropping without apparent reason or warning.

Being unable to finish even a single hour long show streamed from the NAS without having to re-access the drive and open the file again is driving me up the wall, so any insight into this problem would be greatly appreciated.

Posted Jun 12, 2015, 11:57 PM UTC · edited

16
candidly1•

I've got a 213air and I haven't seen this behavior. Which hard drives are you using?

2
ArkandyOP•

2 3TB WD Reds and 2 3TB WD Greens, no files are actually broken or corrupt, as soon as I reaccess the drive I can pick back up where they broke off due to the mapped drive losing connection. The drives and volume as a whole check out fine, so I would think it has to do with the NAS's networking, though I lack enough experience to actually track down where things could be going wrong.

EDIT: In fact, there are no log entries showing that the drives are entering or exiting hibernation when this takes place, and there's a complete lack of information given toward the networking side of things (oh CIFS client accessed the shared folder when I reaccess the drive but nothing alluding to why it cuts out in the first place, fucking thanks synology.)

2
candidly1•

If I had to guess, I'd blame the Greens. They have a mind of their own when it comes to power saving; they spin down whenever they're in the mood. No rhyme or reason. I bet if you swap them out for Reds, your problems disappear. Everything I read says Greens in a NAS environment will drive you nuts...

2
ArkandyOP•

It's odd that I've had the same 4 drives in this thing for 2+ years, and yet this problem has only surfaced within the last couple weeks (during which time I had my computers down for a separate reason, and after hooking everything back up the NAS now has these sporadic disconnections). I have heard of the green's acting strangly with powersaving features before, so perhaps some setting was changed while everything was down that I didn't notice, though since it had been acting fine for years beforehand without intermittent disconnects I'm still somewhat hesitant to find fault for this issue with the hard drives.

EDIT: Though I will look into the green's power saving features a little more aggressively as I haven't really considered that during my troubleshooting previously, thanks.

2
candidly1•

Good luck!

2
ArkandyOP•

Apparently there's an update for the DSM which I don't have (as I'm 2 updates behind) which improves SMB stability "being accessed by an excessive number of clients" (which I hardly imagine my 2 networked computers would contitute), having now updated I'll see if the problem persists (as updating my NAS should have been my first line of action), and if so update the thread for future clarification if this fixes things.

EDIT: Haha, nope not fixed. Goddamn it

1