NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Pinkyg
Oct 07, 2016Apprentice
Problems running Plex Media Server after 6.6.0 update
Plex was running fine until readynas update to 6.6.0. I have removed plex from my rn214 and uploaded the new version 1.2.2 for ARM 6.x RN2xx. Anytime i try to turn it on it returns and error after a m...
- Oct 19, 2016
Short answer:
So if you have problems with starting Plex for RN2XX since the upgrade to 6.6.0 please try rebooting your NAS or wait it out and it should fix itself. It might be about 5-10 minutes (or perhaps a bit longer - it does depend on things such as your internet connection) after a reboot or so before it fixes itself.
Then you should be able to start Plex which is your confirmation that it is fixed.
More info:
We have uploaded the missing package to our repository.
Glad it turned out to be a simple fix.
You can download the logs and look in packages.log to see which packages are installed. This log is generated from
# dpkg -lYou should see ii next to the package if it is installed properly. The version of libc6:armhf should match the one for libc6:armel
I think if I'm reading it right that the 1.2.2 installer only installs the libc6:armhf package if on firmware prior to 6.6.0 so if you last factory reset on 6.6.0 and installed 1.2.2 rather than 1.1.4 or earlier first the necessary package likely won't be installed. Hopefully Plex fixes this in the next PlexPass version of Plex Media Server.
The public 1.1.4 version should work on 6.6.0 now too, I think.
If you did happen to have done a factory reset on 6.6.0 and installed the 1.2.2 app and there is no libc6:armhf in the packages list (not even an old version that needs updating) you could do:
# apt-get update
# apt-get install libgcc1:armhf libc6:armhfto force the missing packages to be installed.
Edit: siigna's suggestion below:
Alternatively the libc6:armhf package can be downloaded from our repository and uploaded to the NAS (Apps > Upload), for those uncomfortable with SSH access. An apt-get update will be performed as part of the installation.
Pinkyg
Oct 11, 2016Apprentice
It's good to hear they release new versions that often :-)
Fingers crossed the next version corrects the problem.
I have to agree with Eckers though, it shouldn't take this long to fix.
In fact, given that the rn214 was heavily marketed towards running PMS, it should never have been allowed to happen in the 1st place.
- jhaggOct 11, 2016Luminary
It is taking too long to fix I agree. This one isn't really Netgears fault, something happened on the Plex end and they are the ones that need to push a solution, although it would be nice if the Netgear techs reached out to them and applied a bit of pressure since as you mentioned, Netgear did use Plex in its marketing.
- PinkygOct 11, 2016Apprentice
I'm not so sure that I place the blame on the Plex side though tbh.
After all, Plex was running fine before I applied the readynas update 6.6.0
Maybe I'm taking too simple an approach to the whole thing....
In my mind, the 6.6.0 update should have been tested with the current release of PMS before rollout. Maybe even communicate to registered users of the rn214 (etc), when they need to update their version of PMS, although this would only work with proper testing.
Again this is just my point of view, it's quite possible there could be something I'm overlooking!
- jhaggOct 11, 2016Luminary
You have changed my mind, you are absolutely correct.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!