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 and also for a packaged form of the installer for Synology on a Marvell Kirkwood or Intel CPU.
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. Site de baixar jogos para pc. 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. 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!
Install Nas On Pogoplug 4
/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.
How can the answer be improved? King of fighters 97 play online. Play King of Fighters '97, The SNK NEO GEO game online for free in your browser. No download required. The King of Fighters '97 is an online NEO-GEO game that you can play at Emulator Online. This free Neo Geo game is the United States of America region version for the USA. It has been played 2,111 times so far and was posted on January 28, 2016.
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.
Iomega's StorCenter is a rugged, low-end NAS box that can be attached directly to your PC's Ethernet port or your router. It's also a Universal Plug and Play (UPnP) media server that can stream multimedia files to a digital media adapter for playback on your home A/V system. Sadly, its write performance lagged well behind that of the rival and NAS drives. The Iomega StorCenter won't be winning any awards for revolutionary design. Its boxy, charcoal-gray case looks just like the ones in Iomega's -a tad boring, but discreet.
The drive's cooling fan emits a low but audible whir, which may annoy some but will also keep the StorCenter's hard disk running longer than the passive cooling found in many other low-priced NAS boxes. The StorCenter also has two USB 2.0 ports for daisy-chaining USB hard drives or connecting to network USB printers. The 250GB unit we tested (it's also available in a 160GB version) was easy to install, as most NAS units are. After we powered it up and attached it to our test router, it automatically popped up in Network Places.
For easier access from within Windows Explorer, we assigned it a drive letter by right-clicking on the drive and selecting Map Network Drive. For those unacquainted with Windows networking or who expect the drive to turn up automatically in Windows Explorer, Iomega provides a utility that will locate the drive and launch the StorCenter's HTML setup app. Once you're up to speed, you can access the setup app directly from a browser by typing in the unit's URL, which you'll find in your router's DHCP table. Iomega rounds out the software bundle with Automatic Backup Pro, the company's reliable, easy-to-configure utility that works in the background to automatically back up files to the StorCenter at intervals you specify. As we mentioned up front, the StorCenter is also a UPnP media server that can stream audio, video, and photo files to a PC, or even better, to a digital media adapter such as, which will display them on your A/V equipment. If there's a home multimedia network in your future, this is a feature you should be looking for in a NAS box.
The StorCenter's performance was more than a little on the slow side for a Gigabit NAS box. Reading our 5GB folder of data back, the box was sprightly enough, taking only a couple of minutes longer than and. But writing the same 5GB folder to the StorCenter in the first place took nearly seven minutes longer. In terms of tasks, it's fine for serving files but a slowpoke for backing up.
Contents. Download imager firmware For the EZ Media, download. For the ix2-ng, download Create imager stick Extract the file to a FAT formatted USB stick, of at least 1GB. Prepare disk Ensure both disks are initialized with GPT partition table.
Use the utility gdisk or fdisk to do this. Now extract the files zImage and initrd from emctools/xxximages/xxx.tgz. Connect the disk to your (Linux) PC, and write the files to the raw disk: dd if=/path/to/zImage of=/dev/sdb seek=2048 dd if=/path/to/initrd of=/dev/sdb seek=8192 Of course doublecheck that sdb is your intended nas disk. Dd will happily overwrite whatever you offer as target. Install firmware Put the disk in the nas, plugin the stick, power it up, and after about 10 minutes (depending on your USB stick), the box should power-off. Remove the stick, and power it on again. After a few minutes you can connect to the webinterface.
Iomega Home Page
If there is an indication in the web page that the box is still starting, leave it alone until it's done. It is initializing the data volume. If you interrupt it, there will be No shares When there are no shares available, do a factory reset (System-Factory Reset). After rebooting, connect to webinterface. If there is an indication in the web page that the box is still starting, leave it alone until it's done. It is initializing the data volume.
Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.
Iomega Storcenter Ix4 200d
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: If you have any problems with the registration process or your account login, please. If you need to reset your password,. Having a problem logging in?
Please visit to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
To receive this Complete Guide absolutely free.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |