I have a WD NAS where I store my contents. I have configured the NAS to power off at night and power on during the day. I am using my NUC as a Plex server so I just mount the share on the NUC. Every time the NAS shuts down as scheduled the CPU and memory usage on my NUC ramps up and causes the CPU fan to go screaming. The fan, CPU and memory usage goes down when I stop the Plex server. This issue does not happen if the NAS share is available but only if it is offline.
The same thing happens on my Nvidia Shield TV if I use it as a Plex server. Apps like Youtube keeps freezing every time the NAS share becomes unavailable. My NAS is 4 bay device so I have to turn it off at night to save electricity.
Please fix this issues. Thanks.
When you have other devices dependent on the NAS (mounted) that happens. The whole configuration, whatever it may be, can go sideways.
Most of us leave our NAS’s on 24/7. To save electricity, spin down the drives after a few hours of idle time. If you spin them down too soon, you’ll wear out the drives (load-retract cycles).
In short, there’s nothing wrong with Plex. The solution, which a lot of us do, is to put Plex ON the NAS.
I have the old WD NAS which is EX4100. It doesnt do hardware transcoding so I prefer to have the NUC or the Nvidia Shield TV as a Plex server. There is definitely wrong with their new code. It was not like this on the previous build. This is a corner case scenario. Good engineering should have this covered.
With a properly-built NAS and appropriate hard drives, powering it off is a bad solution to a non-existent problem. You should be leaving it on.
Well that is my decision to make if I want to shutdown my NAS or not that is none of your concern. Why is it not a problem? Are you one of the developer in Plex that is just too lazy to fix it? Is that how you guys make products? You should have test cases to see how your software reacts in some cases just like this one. I too work in one of the computer related companies in Irvine. We have checklists when testing codes. So if you really think this is not a problem then you in denial my friend.
There is no problem with Plex in this case. PMS is dependent on the underlying OS for handling of TCP/IP based services in such extreme cases. It can only detect a break in connection, the same as if a modem is turned off. If the host OS cannot handle such conditions when the entire file system falls out from underneath it, there is nothing Plex can do. User configuration of the host can mitigate the interruption to some extent
This thread is being closed
