 |  |
This tutorial uses unsupported features of the IOMEGA Storcenter ix4-200d and Crashplan does not support a client for ARM processors. The steps I described worked for me but use at your own risk!
Tutorial tested on IOMEGA Storcenter ix4-200d firmware 3.1.14.995
It should be fairly easy to adapt it to the Iomega ix2 NAS and with a little bit more work, even other devices using the ARM processor Marvell Kirkwood 6281 CPU (aka Feroceon).
First of all, it was much more complex than I anticipated. Crashplan is running on java, I was hoping for a quick java install and go! Actually it is much more complex because nothing is supported by either Iomega or Crashplan, some libraries are missing from the NAS and the custom linux (EMC Lifeline OS) does not behave as expected (read only file system and strange daemon startup mechanism)...
This tutorial assumes some basic linux and vi knowledge...
EDIT: This tutorial was used as a base for tutorials for Synology on powerpc at http://chreggy.fr/thegeek/2012/01/10/crashplan-sur-un-synology-powerpc-ds109/ and also for a packaged form of the installer for Synology on a Marvell Kirkwood or Intel CPU at http://pcloadletter.co.uk/2012/01/30/crashplan-syno-package/. If this tutorial helps you to install crashplan for another architecture/device, please link to this page and leave a comment. I am always glad to know that the hours I spent have served the community!
1. Enable SSH on the NAS
Go to
http://your-nas-adress/diagnostics.html
click "enable SSH"
on older firware versions, I understand an equivalent page could be found at:
http://your-nas-adress/support.html
If the admin password of the NAS is "pass" the root password to use in ssh is sohopass.(thanks http://planetkris.com/2010/05/iomega-storcenter-ix2-ssh-email-notifications-and-busybox-init-d)
2. Create a share where we will install our stuff
Create a share called NAS_Extension using the web interface
EDIT: now that I understand better the way the OS is organized, It would have been better to install everthing in /opt/ (/opt/ejre1.7.0 and /opt/crasplan3.0.3) the partition /opt/ is on is 15GB, so no risk to run out of space (type df to see the mount points and free space)
3. Install java
Because of oracle licensing, you can't download the file directly. Go there:
http://www.oracle.com/technetwork/java/embedded/downloads/javase/index.html
and download the ejre corresponding to "ARMv5 Linux - Headless" under "Java SE for Embedded 7"
The file should be called ejre-7-fcs-b147-linux-arm-sflt-headless-27_jun_2011.tar.gz
Store it into the NAS_Extension partition you just created using your regular way of accessing the NAS.
TODO: Everything should work with openJDK as well. I'll try to update the tutorial when I get a chance.
configure ssh on you computer and access the NAS (windows users can use putty.exe available here http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)
In the NAS command line, type:
cd /mnt/pools/A/A0/NAS_Extension tar -xvf ejre-7-fcs-b147-linux-arm-sflt-headless-27_jun_2011.tar.gzThat's it!
4. Install crashplan
cd /mnt/pools/A/A0/NAS_Extension/ wget http://download.crashplan.com/installs/linux/install/CrashPlan/CrashPlan_3.0.3_Linux.tgz tar -xvf CrashPlan_3.0.3_Linux.tgz cd CrashPlan-install ./install.shand leave the default setting (press enter) for all the questions except:
What directory do you wish to install CrashPlan to? /mnt/pools/A/A0/NAS_Extension/crashplan/
vi /etc/init.d/crashplanAnd add at the beginning of the script (line 18)
PATH=$PATH:/mnt/pools/A/A0/NAS_Extension/ejre1.7.0/bin export PATH
Now, some shared objects (native libraries) need to be replaced in order for Crashplan to work (precompiled versions are available).
Replace libjtux.so in /mnt/pools/A/A0/NAS_Extension/crashplan/:
cd ../crashplan/ cp libjtux.so libjtux.so.bak wget http://dl.dropbox.com/u/50398581/crashplan%20on%20NAS/libjtux.so(credit to https://crashplan.zendesk.com/entries/390250-crashplan-on-sheevaplug)
Replace jna.jar in /mnt/pools/A/A0/NAS_Extension/crashplan/lib/:
cd lib/ cp jna-3.2.5.jar jna-3.2.5.jar.bak wget http://dl.dropbox.com/u/50398581/crashplan%20on%20NAS/jna-3.2.5.jar(shared object extracted from the debian package http://packages.debian.org/sid/armel/libjna-java/download and reinjected into Crashplan jna jar. Thanks to http://www.opticality.com/blog/2011/07/16/installing-crashplan-on-a-pogoplug-pro/ for the idea)
Replace libffi.so (required for jna and not available by default):
cd /mnt/pools/A/A0/NAS_Extension/ wget http://dl.dropbox.com/u/50398581/crashplan%20on%20NAS/libffi.so.5 vi /etc/ld.so.confadd
/mnt/pools/A/A0/NAS_Extension/at the end of /etc/ld.so.conf
Start crasplan
/etc/init.d/crashplan startRemember to give it some time (like 5 minutes) before connecting. Crashplan can be slow to start up.
Connect to crashplan using ssh tunnel
See how to do that here:
http://support.crashplan.com/doku.php/how_to/configure_a_headless_client
log in, configure your backup sets etc....
It seems like it is working, but you are not done yet!
5. resolve idendity problem
The OS seems to wipe clean /var/lib at each reboot. The problem is that's where crashplan stores your login information!
To solve the problem:
cp -p /var/lib/crashplan/.identity /mnt/pools/A/A0/NAS_Extension/crashplan/ vi /mnt/pools/A/A0/NAS_Extension/crashplan/bin/CrashPlanEngineand add:
mkdir -p /var/lib/crashplan cp -p .identity /var/lib/crashplan/after:
echo "Using standard startup" cd $TARGETDIR
6. Get crashplan to start automatically on reboot
You can see how to do that in this post How to run a program at boot on Iomega Storcenter
You need to add the command:
/etc/init.d/crashplan start >> /opt/init-opt.logto the script /opt/init-opt.sh
The script will look like this:
#!/bin/sh # modified from http://techmonks.net/installing-transmission-and-dnsmasq-on-a-nas/ rm /opt/init-opt.log echo "Last bootup:" >> /opt/init-opt.log date >> /opt/init-opt.log /etc/init.d/crashplan start >> /opt/init-opt.log while true; do sleep 1d doneafterwards.
You are all done!
Please note that it takes quite some time for crashplan to be available after a reboot. Because of the 'nice' level, the process basically waits for all the other boot processes (mostly twonkymediaserv) to finish before being available and sarting to listen on the socket. This takes a good 12 minutes for me.
Let me know if you manage to get the tutorial working for other NAS devices and what you had to change to do that. I'll try to compile your remarks into another post.
If this tutorial saved you 10 hours of messing around with your NAS, you can offer me a beer (a coffe or a tea would do as well)!
7. Faq:
Q1: The Crashplan engine starts but fails after a few seconds/minutes
Chances are you libjtux is not properly updated.... retry to download it.
You should see the following stack trace when you do
cat /mnt/pools/A/A0/NAS_Extension/crashplan/log/engine_error.log
java.lang.UnsatisfiedLinkError: /mnt/pools/A/A0/NAS_Extension/crashplan/libjtux.so: /mnt/pools/A/A0/NAS_Extension/crashplan/libjtux.so: cannot open shared object file: No such file or directory (Possible cause: can't load IA 32-bit .so on a ARM-bit platform)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1928)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1854)
at java.lang.Runtime.loadLibrary0(Runtime.java:845)
at java.lang.System.loadLibrary(System.java:1084)
at jtux.UUtil.init(UUtil.java:14)
at jtux.UProcess.(UProcess.java:30)
at com.code42.os.posix.PosixProcessCommands.getuid(PosixProcessCommands.java:57)
at com.backup42.service.CPService.logIds(CPService.java:1164)
at com.backup42.service.CPService.start(CPService.java:396)
at com.backup42.service.CPService.main(CPService.java:1552)
Q2: The Crashplan engine seems fine but it is never backing up anything
You should see the following stack trace when you do (it takes some time (like 5-10 minutes) before you get the stack trace, just be patient):
cat /mnt/pools/A/A0/NAS_Extension/crashplan/log/engine_error.log
Exception in thread "W10189988_ScanWrkr" java.lang.NoClassDefFoundError: Could not initialize class com.code42.jna.inotify.InotifyManager
at com.code42.jna.inotify.JNAInotifyFileWatcherDriver.(JNAInotifyFileWatcherDriver.java:21)
at com.code42.backup.path.BackupSetsManager.initFileWatcherDriver(BackupSetsManager.java:376)
at com.code42.backup.path.BackupSetsManager.startScheduledFileQueue(BackupSetsManager.java:314)
at com.code42.backup.path.BackupSetsManager.access$1600(BackupSetsManager.java:64)
at com.code42.backup.path.BackupSetsManager$ScanWorker.delay(BackupSetsManager.java:1007)
at com.code42.utils.AWorker.run(AWorker.java:158)
at java.lang.Thread.run(Thread.java:722)
In this case, it is likely jna-3.2.5.jar is not working. Try to install it again.The same error can be caused by the fact that you miss libffi.so.5 or it is not found by ld. To make sure your problem is linked to libffi, you can try:
cd /mnt/pools/A/A0/NAS_Extension/crashplan/ mkdir tmp cd tmp unzip ../jna-3.2.5.jar ld com/sun/jna/linux-arm/libjnidispatch.soif ld tells you it can not find libffi.so.5, that's your problem and you should try to re install libffi.so.5 (don't forget to change /etc/ld.so.conf).
EDIT 28/10/2012
I am having this problem now:
root@IOMEGA_NAS:/mnt/pools/A/A0/NAS_Extension/crashplan/log# tail -40 engine_error.log
java.lang.UnsatisfiedLinkError: /mnt/pools/A/A0/NAS_Extension/crashplan/libmd5.so: /mnt/pools/A/A0/NAS_Extension/crashplan/libmd5.so: cannot open shared object file: No such file or directory (Possible cause: can't load IA 32-bit .so on a ARM-bit platform)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1928)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1854)
at java.lang.Runtime.loadLibrary0(Runtime.java:845)
at java.lang.System.loadLibrary(System.java:1084)
at com.twmacinta.util.MD5._loadNativeLibrary(MD5.java:727)
at com.twmacinta.util.MD5._initNativeLibrary(MD5.java:703)
at com.twmacinta.util.MD5.(MD5.java:124)
at com.code42.utils.OsPatternList.getChecksum(OsPatternList.java:142)
at com.code42.utils.PatternList.equals(PatternList.java:350)
at com.code42.config.ConfigItem.setValue(ConfigItem.java:66)
at com.code42.config.ConfigXmlTransformer.fromXmlConfigItem(ConfigXmlTransformer.java:445)
at com.code42.config.ConfigXmlTransformer.fromXmlAConfigItem(ConfigXmlTransformer.java:405)
at com.code42.config.ConfigXmlTransformer.fromXml(ConfigXmlTransformer.java:306)
at com.code42.config.ConfigXmlTransformer.fromXmlConfigComponent(ConfigXmlTransformer.java:487)
at com.code42.config.ConfigXmlTransformer.fromXml(ConfigXmlTransformer.java:308)
at com.code42.config.ConfigXmlTransformer.fromXml(ConfigXmlTransformer.java:74)
at com.code42.xml.XmlTool.fromXml(XmlTool.java:176)
at com.code42.xml.XmlTool.fromXml(XmlTool.java:155)
at com.code42.config.AConfig.fromXml(AConfig.java:77)
at com.backup42.common.config.AppConfig.load(AppConfig.java:106)
at com.backup42.common.config.ServiceConfig.load(ServiceConfig.java:326)
at com.backup42.service.CPService.loadConfig(CPService.java:675)
at com.backup42.service.CPService.start(CPService.java:331)
at com.backup42.service.CPService.main(CPService.java:1622)
to fix it, just do:
cd /mnt/pools/A/A0/NAS_Extension/crashplan/ mv libmd5.so libmd5.so.old wget http://dl.dropbox.com/u/50398581/crashplan%20on%20NAS/libmd5.so
EDIT 08/11/2015
it looks like you need a more recent version of jna version with Crashplan 4.4.1
cd /mnt/pools/A/A0/NAS_Extension/crashplan/lib mv jna.jar jna.jar.old wget https://dl.dropboxusercontent.com/u/50398581/crashplan%20on%20NAS/jna-4.2.1.jar ln -s jna-4.2.1.jar jna.jar
