I’ve been running an Iomega IX4 in my home vSphere lab 24×7 for the past two years and have found it to be a nice reliable NAS device. Though like with anything regular maintenance is required whether this be removing the dust or fluff from the fan at the back or keeping the firmware up-to-date.
The latter being the topic of this blog post. The Iomega IX2 or IX4 NAS has two parts to it than can have firmware revisions applying to it. The first is the most obvious and is for the actual IX4 unit itself. You can check to see the current firmware revision of your IX2 or IX4 by clicking on the Dashboard tab of the IX’s web based management interface, see below. UPDATE THE IX DEVICE FIRMWARE To check to see if your IX NAS device is running the latest firmware version you have a couple of options. Either visit the ‘Support’ section of the and select your model of Iomega NAS device or click on the ‘Settings’ tab and then on the ‘Update’ icon (below).
After clicking on the ‘Update’ icon you’ll be presented with a screen that shows the current firmware revision and a link to the ‘Iomega Software Update Web Site’. By clicking this link you’ll be taken through to the Iomega site where you can then navigate to the ‘Support’ section and download any required firmware revision. The following is a list of the recent firmware updates available along with a description of the main enhancements and fixes for each. Hi Ely, From the firmware version number you provided it would appear that you have mixed the updating the hard drives method (via USB pen/key drive), and updating your actual ix2’s firmware. The StorCenter ix2-200, Cloud Edition — Firmware Version 3.2.10.30101 (see: )is for the ix2’s firmware and not the drives contained within the unit.
To update this firmware you’d typically use the web based management interface to do this, and not use a USB key/pen drive. Have you tried restarting your ix2 and then accessing the management console again via its IP adddress? Cheers, Simon.
I have an old ix2 Storcenter (iomega). One drive is blown. I am looking for information regarding what I can replace the drive with. Current configuration is as follows regarding drives. Two (2) 500GB 7200 RPM SATA Hard Drives (8MB cache each) Seagate ST3500820AS. I was looking at using a 500 gig sata solid state drive.
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).
![Storcenter Storcenter](http://photos.macnn.com/news/0911/iomega_5.jpg)
This tutorial assumes some basic linux and vi knowledge. EDIT: This tutorial was used as a base for tutorials for Synology on powerpc at and also for a packaged form of the installer for Synology on a Marvell Kirkwood or Intel CPU at. 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! Enable SSH on the NAS Go to click 'enable SSH' on older firware versions, I understand an equivalent page could be found at: If the admin password of the NAS is 'pass' the root password to use in ssh is sohopass.(thanks ) 2.
Create a share where we will install our stuff Create a share called NASExtension 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: 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-27jun2011.tar.gz Store it into the NASExtension 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 ) In the NAS command line, type: cd /mnt/pools/A/A0/NASExtension tar -xvf ejre-7-fcs-b147-linux-arm-sflt-headless-27jun2011.tar.gzThat's it! Install crashplan cd /mnt/pools/A/A0/NASExtension/ wget tar -xvf CrashPlan3.0.3Linux.tgz cd CrashPlan-install./install.sh and leave the default setting (press enter) for all the questions except: What directory do you wish to install CrashPlan to? /mnt/pools/A/A0/NASExtension/crashplan/ vi /etc/init.d/crashplan And add at the beginning of the script (line 18) PATH=$PATH:/mnt/pools/A/A0/NASExtension/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/NASExtension/crashplan/: cd./crashplan/ cp libjtux.so libjtux.so.bak wget to ) Replace jna.jar in /mnt/pools/A/A0/NASExtension/crashplan/lib/: cd lib/ cp jna-3.2.5.jar jna-3.2.5.jar.bak wget object extracted from the debian package and reinjected into Crashplan jna jar. Thanks to for the idea) Replace libffi.so (required for jna and not available by default): cd /mnt/pools/A/A0/NASExtension/ wget vi /etc/ld.so.conf add /mnt/pools/A/A0/NASExtension/ 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: log in, configure your backup sets etc. It seems like it is working, but you are not done yet!
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/NASExtension/crashplan/ vi /mnt/pools/A/A0/NASExtension/crashplan/bin/CrashPlanEngine and 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 You need to add the command: /etc/init.d/crashplan start /opt/init-opt.log to the script /opt/init-opt.sh The script will look like this: #!/bin/sh # modified from 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 done afterwards. 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.
![Freenas Freenas](http://t2k.wdfiles.com/local--files/freenas/freenas-disk-2013-12-21-01.jpg)
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)! 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. Thanks for this great tutorial.
I used it on my StorCenter ix2 You seem to be missing a couple of steps. After installing the JRE, you need to add it to your path before you can run the crashplan installer: PATH=$PATH:/mnt/pools/A/A0/NASExtension/ejre1.7.0/bin;export PATH Before you can configure the ssh tunnel you need to start the crashplan engine: /etc/init.d/crashplan start Also, if you are on an internal network, you don't need to use an ssh tunnel.
If you edit conf/my.service.xml and change the from 127.0.0.1 to 0.0.0.0 you can directly connect to the engine. I've tried to install CrashPlan on my Iomega Home Media Network nas. Some remarks: 1) The public downloadable file Ejre-7-fcs-b147-linux-arm-sflt-headless-27jun2011.tar.gz file has not the first letter capitalized. I have to use 'e' in place of 'E' in following commands. 2) As already pointed out by the previous commenter, the PATH has to be updated before installing CrashPlan. 3) Please write 'jna-3.2.5.jar' in place to 'jna-3.2.2.jar'.
4) Please write '/etc/ld.so.conf' in place of '/etc/ld.conf'. Now I need your help.
I have read page but I am unable to connect to my nas, nor using putty nor using ssh (I get always 'connection refused'), even if CrashPlan appears correctly installed, and ports 4242 and 4243 are listed by netstat command. Moreover, I am not able to undestand the suggestion of previous commenter (which my.service.xml have I to change? The one on the nas, or the one on the pc?) So, how can I configure CP on my nas? Sorry for the late answer. @TWForeman Regarding adding the jre to the path: that was the purpose of step 4: vi /etc/init.d/crashplan adding it to the path should serve the same purpose.
/etc/init.d/crashplan start: thanks for that, I edited the tutorial @Unknown Thanks for correcting the typos. I updated the post. I don't have access to my NAS right now, I'll look into TWForeman suggestion and I'll come back to you. If ssh is running correctly on the NAS, you should be able to open a tunnel. When you open putty on your computer to set up the tunnel, do you press the add button (step 3 of How It Works - Using PuTTY in the 'configure a headless client' tutorial)? Did you try the telnet connection: telnet localhost 4200 to see if the tunnel works? Maybe the problem is not the tunnel but the setup of crashplan on your computer.
I've verified all of the steps form the FQA and especially libjna and libffi. However, things seem to be dieing at an earlie stage in the backup, and it looks like inotify is not working at all. The GUI just sits there with a 'Waiting for Backup' message. @urban tried copying the whole com/ directory tree to crashplan but it made no difference.
I also tried finding updated libffi.so and libjnidispatch.so for armv5tel. This didn't help though I'm still stuck with errors from ld: # ld com/sun/jna/linux-arm/libjnidispatch.so ld: warning: cannot find entry symbol start; defaulting to 00008298 com/sun/jna/linux-arm/libjnidispatch.so: undefined reference to `dlsym' com/sun/jna/linux-arm/libjnidispatch.so: undefined reference to `dlerror' com/sun/jna/linux-arm/libjnidispatch.so: undefined reference to `dlopen' com/sun/jna/linux-arm/libjnidispatch.so: undefined reference to `dlclose' #ld libffi.so.5 ld: warning: cannot find entry symbol start; defaulting to 00008244. OK, I think I figured it out. Despite editing /etc/ld.so.conf it wasn't picking up the shared libraries, and specifically the LDLIBRARYPATH environment variable wasn't set.
I added 'export LDLIBRARYPATH=/mnt/pools/A/A0/NASExtension/libraries/:/mnt/pools/A/A0/NASExtension/crashplan/com/sun/jna/linux-arm/' after 'cp -p /mnt/pools/A/A0/NASExtension/crashplan/.identity /var/lib/crashplan/' in crashplan/bin/CrashPlanEngine and off it goes! /mnt/pools/A/A0/NASExtension/libraries/ is where I put libffi.so.5 and /pools/A/A0/NASExtension/crashplan/com/sun/jna/linux-arm/ is the extracted jar file.
I may not need the later but I haven't tried it without yet. Anonymous Thanks for a great tutorial. I got stuck right near the end with the shared libraries problem. I had installed everything under /opt (eg; /opt/crashplan) so to get things working I made sure I have all the libraries in /opt/crashplan and that I add this to /etc/ld.so.conf and I did Brad's addition to CrashPlanEngine as well. My Iomega IX2-200 didn't have 'unzip' so I manually extracted libjnidispatch.so on another machine and copied it over. Put it in /opt/crashplan - not neat but it worked Thanks again. As there is no JDK for ARM/linux, I don't manage to compile the MD5 lib for ARM/linux.
I tried to update bin/run.conf to add: -Dcom.twmacinta.util.MD5.NONATIVELIB=true to disable the native MD5 lib (and avoid the error message) but it does not seem to work. If you really want to avoid the error message, you could change the file com/twmacinta/util/MD5.class in lib/com.backup42.desktop.jar to disable the native lib. I don't think that's necessary: crasplan still works ok in spite of the error message. Bill Forsyth There have a been a few updates to crashplan that require the.uiinfo. You can basically follow instruction at to fix it. As far as the ix2/ix4 is concerned, with the latest version as of now (4.4.1) you need to edit the my.service.xml to make serviceHost the ip of your NAS. Then start the engine and let it create.uiinfo, then get this over to your UI client.
Note that as of 4.4.1, it appears that you have to have at least one valid connection from the UI client to the NAS server for it to resume backing up. Also, it looks like in the current jna.jar they included the ARM, so no need to follow the instructions for overwriting the jna-3.2.5.jar. Delete this file if it is still there.