NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Crashplan JRE update needed
Crashplan released an update on 21 September 2015 (4.4.0) which fails to install on my pro-6 (running 4.2.28).
The issue is that the new service requires jre 1.7 or jre 1.8, and my system was r...
Here's for those who boldly go ...
https://rnxtras.com/add-ons/update/glibc6-2-13-readynas-os-4-x86-only-60494
Have fun!
-Stefan
I just got the following email from CrashPlan. It looks like 4.5.0 isn't going to work unless we can somehow upgrade the kernel and glibc.
"Hello,
We're contacting you to let you know about some changes made to the newest version of CrashPlan that may affect the CrashPlan app on one of your devices. Starting with the release of CrashPlan version 4.5.0, the System Requirements with regards to Linux have changed. Here are the system requirements that have changed:
Linux kernel version:
CrashPlan app version 4.5.x or later: 2.6.27 or newer and glibc 2.9+
CrashPlan app version 4.4.1 or earlier: 2.6.13 or newer and glibc 2.4+
If you have a Linux device running kernel 2.6.26 or older and are still on CrashPlan version 4.4.1, CrashPlan on this device will not upgrade to version 4.5.0. If your device is on kernel 2.6.26 or older and has already upgraded to CrashPlan version 4.5.0, CrashPlan has likely stopped working.
To continue using up-to-date versions of CrashPlan, we recommend upgrading your operating system to a supported version of the Linux kernel. For instructions on upgrading your Linux device, refer to the documentation for your device or your Linux distribution.
An alternate solution to resolve this is to Uninstall CrashPlan 4.5.0, and install CrashPlan version 4.4.1, which can be found in this direct link:
https://download.crashplan.com/installs/linux/install/CrashPlan/CrashPlan_4.4.1_Linux.tgz
Please Note: Computer-to-computer backups require both devices be on the same version of the CrashPlan app.
We've created a Support Article that explains more about this change, here:
https://support.code42.com/CrashPlan/4/Troubleshooting/Linux_CrashPlan_App_Version_4.5_Cannot_Back_Up
Please let us know if you have any further questions.
Thank you,
Code42 Customer Champion Team"
Just to make sure !
If you ssh into your box and type the following what do you get.
uname -r ldd --version
My kernel may be OK:
2.6.37.6.RNx86_64.2.4
But libc is 2.7, so the upgrade isn't going to be compatible.
This is on an Ultra 4 running 4.2.27
So I guess we are in the same boat and stuck on crashplan 4.4.1 unless for some reason someone here at netgear decides to do a upgrade.
Sadly that makes it almost useless since all of the Windows PCs I back up to it will auto-upgrade and then will no longer connect (according to the email). I am going to have to use the ReadyNAS just as network storage and mount it on a Windows system running CrashPlan.
Can we downgrade our firmware on the NAS? I am running 4.2.28 on an Ultra 2.
Downgrading the firmware won't help unless you go so far back that you'd downgrade the linux kernel to something between 2.6.13-2.6.26.
Options I see are:
(a) upgrade to OS6, restore the NAS data and reinstall crashplan.
(b) Switch to a PC client, backing up the NAS using this procedure: https://support.code42.com/CrashPlan/4/Backup/Backing_Up_A_Windows_Network_Drive
(c) find a way to upgrade glibc on OS 4.2.x (probably this requires setting it up so only Java 1.8 uses the upgraded library)
Or
(d) use my Dropbox add-on v2.0.x which has libc6 2.13 bundled ;)
(e) wait until I find the time to prepare a separate libc6 2.13 add-on bundle (current estimate would be this weekend, maybe earlier if my workload permits)
One can of course try option (c) but I can tell from experience that building eglibc 2.13 is no fun if you want to get it compatible with the ReadyNAS.
-Stefan
WhoCares_ wrote:
(d) use my Dropbox add-on v2.0.x which has libc6 2.13 bundled ;)
(e) wait until I find the time to prepare a separate libc6 2.13 add-on bundle (current estimate would be this weekend, maybe earlier if my workload permits)
-Stefan
I love those options.
Can you post back here when (e) is ready? Will you'll distribute it through rnxtras.com?
Crashplan stopped working after the 4.5.0 upgrade on a ReadyNAS Ultra w/ RAIDiator 4.2.28. uname -r is 2.6.37.6.RNx86_64.2.4 but ldd (GNU libc) 2.7. Is there an addon for RAIDiator to upgrade glibc to 2.9+? Is there a DropBox add-on that will upgrade glibc?
Thanks.
@kgorlen wrote:
Crashplan stopped working after the 4.5.0 upgrade on a ReadyNAS Ultra w/ RAIDiator 4.2.28. uname -r is 2.6.37.6.RNx86_64.2.4 but ldd (GNU libc) 2.7. Is there an addon for RAIDiator to upgrade glibc to 2.9+? Is there a DropBox add-on that will upgrade glibc?
Thanks.See the marked solution - That upgrades glibc to 2.13. whocares_ has chosen not to charge for it (though you will need to go through the checkout motions at rnxtras.com).
The link to the add-on states "ReadyNAS OS 4 x86 only". The Ultra 2 is not running OS 4, and my understanding is that an upgrade is not available.
I just installed in on my Ultra 6 running RAIDiator 4.2.28 this morning and it solved the issue with Crash Plan for me.
@kgorlen wrote:
The link to the add-on states "ReadyNAS OS 4 x86 only". The Ultra 2 is not running OS 4, and my understanding is that an upgrade is not available.
The ultra certainly runs OS 4. That means your firmware is 4.2.x.
Excellent! I just installed the glibc upgrade add-on on the Ultra 2 w/ RAIDiator 4.2.28, and CrashPlan 4.5.0 is running OK. Thanks for all the help--I was beginning to panic!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
