Forum Discussion

Tutor

Nov 16, 2016

Solved

All Shares appear to be missing [ReadyNAS Ultra 2; Radiator 4.2.28]

Some weeks ago I (possibly stupidly) ignored a reported filesystem consistency check failure. Have had the check pass successfully since. Today I discovered that I can no longer connect to any o...

Booting

File Sharing

TigerRob
Nov 18, 2016
Thank you all for your help (esp. StephenB for the mention of crashplan)

3.5GB in /usr/local/crashplan/iupgrade ...

Stopped crashplan, moved that directory off to the data partition and softlinked to it, rebooted, and I appear to be back in business.

TigerRob

Tutor

Nov 22, 2016

So, I have a 64-bit JVM. Replacing it with a 32-bit JVM has made my crashplan install work again.

I'm having trouble posting the detail to this thread, my post keeps disappearing. If this is successful then I'll add details.

TigerRob

Tutor

Nov 22, 2016

Not sure why I'm having trouble posting the details to this thread. I'm now removing all formatting (although I wasn;t using much before) and hope it'll get through this time.

So, I have a 64-bit Java installation. On investigation the crashplan install script uses "uname -m" to determine which JVM to install, and so on a ReadyNAS will pick a 64-bit bundled JVM. On upgrade the upgrade scripts looks at the installed JVM (whereever JAVACOMMON points) to determine whether to use a 32- or 64-bit version. So, if you installed a 32-bit Java before Crashplan insisted on using the bundled JVM then your upgrades will have stuck to a 32-bit version. For me it weas keeping a 64-bit version, as that was what was bundled when I did my original install.

I simply replaced /usr/local/crashplan/jre with the 32-bit JVM downl;oaded from code42 (see upgrade.properties for the URL) and I have a happy, working Crashplan again.

Thanks all,

Rob.

StephenB
Guru - Experienced User
Nov 22, 2016
TigerRob wrote:

So, I have a 64-bit Java installation. On investigation the crashplan install script uses "uname -m" to determine which JVM to install, and so on a ReadyNAS will pick a 64-bit bundled JVM. On upgrade the upgrade scripts looks at the installed JVM (whereever JAVACOMMON points) to determine whether to use a 32- or 64-bit version. So, if you installed a 32-bit Java before Crashplan insisted on using the bundled JVM then your upgrades will have stuck to a 32-bit version. For me it weas keeping a 64-bit version, as that was what was bundled when I did my original install.

This explains why some users end up with 32 JVMs (with Crashplan working) while others ended up with 64-bit. Thanks for sharing.
StephenB
Guru - Experienced User
Nov 22, 2016
TigerRob wrote:

Not sure why I'm having trouble posting the details to this thread.

Something was triggering the automatic spam filter - not sure what.