NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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 minute or so "Application failed to initialize. Empty resource error. Bad NML call. Code 22002010000".
Not sure what to try from here.
Not sure what to try from here.
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.
81 Replies
Replies have been turned off for this discussion
I am getting real tired of this, its getting really embarrassing at this time that no working Plex software in any way is available for the Netgear Ready NAS . The main reason I bought this **bleep** 3 days or so before the dread update was the possibillity to run the Plex server. I dont give a rats ass about transcoding, I just want the damn thing to stream my media to my devices in any way it can thru Plex now. I have terrabytes of media that is just worthless space for me without getting Plex to work. PLEX was specially mentioned in BIG LETTERS on the package when I bought it. Well so I am the one who is a complete idiot, or does BOTH Netgear and Plex have a responsability to make this work, together or for themselves if that is neccessary? This is getting REALLY ridiculous at this time. I spent a lot of money on this setup, and a lot of time to get all my things from different machines and disks over to the NAS, making it work for a rather big household here.. Right now I do regret it, because I cannot even get back to the software versions that did work so great the first few days..
Royalgipsy wrote:I am getting real tired of this, its getting really embarrassing at this time that no working Plex software in any way is available for the Netgear Ready NAS . The main reason I bought this **bleep** 3 days or so before the dread update was the possibillity to run the Plex server. I dont give a rats ass about transcoding, I just want the damn thing to stream my media to my devices in any way it can thru Plex now. I have terrabytes of media that is just worthless space for me without getting Plex to work. PLEX was specially mentioned in BIG LETTERS on the package when I bought it. Well so I am the one who is a complete idiot, or does BOTH Netgear and Plex have a responsability to make this work, together or for themselves if that is neccessary? This is getting REALLY ridiculous at this time. I spent a lot of money on this setup, and a lot of time to get all my things from different machines and disks over to the NAS, making it work for a rather big household here.. Right now I do regret it, because I cannot even get back to the software versions that did work so great the first few days..
Well, i understand the frustration, been there done that several times...
I have been running PLEX several years now and so far, fingers crossed it have more or less worked flawless.
Since there are several different PLEX versions and several Readynas versions to use and combine this issues occur now and then.Just sit back and give it some time and it will be solved. It always have.. Let the geniuses work and you will see.
My setup is an old RN Pro Business (6x4TB) with upgraded cpu and more memory, running os 6.6.0. (and that is a gamble every update) :-)
So my advice is, keep cool and check the forums all the time. The solution will be there sooner or later..
Best regards
Hans
I am shure.. But really? The geniuses are paid for solving this, it's going in the direction of a certain company and it's selfcombusting units where the geniuses did not even find the real cause of the problem and just called of the entire product line. Since we dont hear a single word about progression, bad or good, I feel they are preparing to give up from both netgear and plex to support this software. We are after all in the lords year of 2016, in the age of information and development, with no lack of digital prodigys in the firms..
- Yes of course the app is built by Plex etc etc. Plex however didn't sell me a readynas advertised as being able to run a transcoding PMS - Netgear did that. Plex didn't update the firmware of my readynas without confirming that one if it's main selling points would continue to work. This is my problem with Netgear. They should have checked and communicated with the main app providers (especially Plex as it was all over their advertising) before releasing the update. That would be the professional way to do it....
And how would Netgear feel if, when it's time to purchase a new NAS, those of us stung by this, look at other options??
- You may well be right about that.
I'm hoping though that me harping on about it might plant a seed that improves the way they roll out their firmware updates in the future, with the customer in mind.
Here's hoping! - I've some practical suggestions on what Netgear can do:
Help the Plex developers return a working service to the customer. I'm sure they can assist despite the fact that Plex "develops, distributes, and supports the plex server app."
Learn from this incident - put in place proper measures to protect the end user from such an outage in the future. - It's good to see Netgear on the case too. Thanks mdgm for your efforts.
- Some interesting info posted on the thread over on the Plex forums. The latest seems to indicate that Netgear haven't published all the neccessary packages with 6.6.0, the resolution may well be in Netgears hands......time will tell. They seem to be making headway which is good to see.
I SSH'd in and ran:
apt-get update
Then rebooted and installed PMS 1.1.4 (which was stuck on previous version unable to uninstall or remove)...and I'm streaming again.
- Good stuff!
I'm hesitant to ssh in due to potential warranty issues.....nas is only out of the box a couple of weeks.I was leary about installing some of the other pkg's discussed in the thread, but felt an "apt-get update" was safe enough. It worked for me and I'm streaming (and transcoding) once again.
BTW, I've since disabled the SSH service.
This sounds positive but with me only being a non-tech user i'm not comfortable using the SSH/Putty method to fix. Is there any timescale on when a consumer friendly update to PMS will be available to fix this issue?
- Update.
A number of users are now up and running.
It seems that updating the readynad firmware is fixing the issue. There appear to be some missing packages from the original 6.6.0 release which have now been published.
For now, only ssh'ing into the nas and forcing the update will fix it. Guess we are now waiting on Netgear to roll up a complete 6.6? For those not wanting to run the apt-get update command manually, it is ran after a fresh boot and after one week of uptime (by the rn-update service). It is also ran daily (by the apt-update service).
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.
mdgm wrote:
If you did happen to have done a factory reset on 6.6.0 and installed the 1.2.2 app you could do:
# apt-get update
# apt-get install libgcc1:armhf libc6:armhfAlternatively 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.
- Ok guys. What i needed to do to get up and running was download the package from the netgear repository and upload (see last paragraph of mdgm post). It failed to install but plex did work after attempting to upload the libc6:armhf package. Maybe because the apt-update was performed when i tried to install the package?
Yes, I had exactly the same experience. It's good to have a fully working Plex back. Now I just need to wait three days for my libraries to rebuild and redo all my Playlists...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
