CrashPlan Community Forum – Support & Assistance

CrashPlan 4.7.0 Installation Fix for Synology (1435813200470_317 May 2016)

Affiliate Links

Apparently the new 4.7.0 version of CrashPlan (which is automatically downloaded) needs one more task done, as it’s packed inside a cpio file.


Latest update: The package has been updated by patters so just install from the Package Manager (it will reanalyze your entire backup set which might take a long time depending on its size). If it throws an error try again:

Hi all, I have updated the package to CrashPlan 4.7.0. I have baked in a check to force using the system JRE and not the bundled Intel one that Code 42 sometimes force, and I have also hopefully fixed the ARMv7 systems broken since 4.6.0 by including a Maven build of JNA 4.1.0. I notice many of you were using a newer one, but I think it’s prudent to keep the version consistent with the one bundled by CrashPlan. Let me know if it fixes the problem.



Forum discussion:



Use the following suggestions only if you’re having some trouble with the revised package.


Suggestion 1:


  • Make cpio accessible (or symlink it instead of copying):
    • sudo cp /var/packages/CrashPlan/target/bin/cpio /bin/cpio
  • Reinstall the latest CrashPlan package from patters
  • Wait for a moment so that 4.7.0 downloads (you can check if the jar file is there via terminal)
  • Edit the file /var/packages/CrashPlan/target/install.vars, redirecting to a correct Java Package:
    • Synology official Java 8 Package:
    • Synology official Java 7 Package:
    • Patters’ Java 7 Package:
  • Start the package, it will throw out an error but you should see it’s running 4.7.0 in the log. Give it another moment and start one more time and it should be good to go.
  • After fixing .ui_token you’ll have to login on your client app.
  • If you were using a custom Java heap size, don’t forget to change it again.


(funny thing, the port there changed from 4243 to 4261).

Working for: DS412+, DS213+, DS1512+ (and probably others) on DSM 6.x

Issues are being reported on 5.2, try Suggestion 5 or 3.



Suggestion 2:

  1. Using terminal, make a local copy of the file (just in case, as it will be deleted after the next commands):
    • sudo cp /var/packages/CrashPlan/bin/cpio /bin/cpiosudo cp 1435813200470_317.jar 1435813200470_317.jar.BAK
  2. Extract “upgrade.cpi” from the jar file:
    1. sudo 7z e 1435813200470_317.jar upgrade.cpi
  3. And run these:
    1. cat upgrade.cpi | gzip -d -c – | cpio -i –no-preserve-owner

Then try to start CrashPlan again.


Suggestion 3 (reportedly working with DSM 5.2):



Got it working on my ds214play: DSM 5.2-5644 Update 5, syno java 7, crashplan 4.7

Used suggestion 3 (fresh install with the update file unpacked before starting up first time) . Tried number 1 but never got it to work. But 3 worked 🙂
0. Save the update .jar file (before it gets deleted)
1. Uninstall CP
2. Install CP, but don’t start it.
3. Unpack the .jar file and use 7zip to extract the content (I did this in windows10).
4. Copy the content to /var/packages/CrashPlan/target replacing any already existing files.
5. Check your JAVACOMMON= in /var/packages/CrashPlan/target/install.vars
6. Start up CP (you will probably get an error)
7. Start up CP again. (Now it will work)
8. Check your /var/lib/crashplan/.ui_info and update the “C:\ProgramData\CrashPlan\.ui_info” (on Windows) if needed.


Suggestion 4:


Here’s how I fixed the issue this time, just in case it could help other people! Before you start, make sure you have a good hour in front of you.. 😉
The commands are assumed to be executed as root…

  • close your eyes and update the package
  • start the package, it’ll download the update file then will crash and burn
  • copy cpio from the CrashPlan package to /bin/cpio: cp /var/packages/CrashPlan/target/bin/cpio /bin/cpio
  • extract the “upgrade” file: 7z e -o./ /var/packages/CrashPlan/target/upgrade.cpi
  • move the upgrade file outside the Crashplan folder
  • uninstall the CrashPlan package
  • install the CrashPlan package again (don’t let it start)
  • move back the upgrade file and put it in the upgrade folder (/var/packages/CrashPlan/target/upgrade)
  • edit install.vars in the CrashPlan folder to point to the correct location of Java on your NAS. To find it, just use ‘which java’. Then put the correct path for the JAVACOMMON property
  • (optional) rename the upgrade file to upgrade.jar (or whatever you like)
  • extract the upgrade file: 7z e -o/var/packages/CrashPlan/target/lib /var/packages/CrashPlan/target/upgrade/upgrade.jar
  • remove the upgrade file (not needed anymore)
  • remove the upgrade.cpi file
  • IF you have enough memory, then add the USR_MAX_HEAP property to /var/packages/CrashPlan/target/syno_package.vars
  • start the CrashPlan package; it should now stay up and running
  • install the latest CrashPlan client version on your machine
  • disable the Crashplan service on your machine
  • get the new Crashplan GUID on your NAS: cat /var/lib/crashplan/.ui_info; echo
  • copy the guid (everything before “,”) in the ‘.ui_info’ file under C:\ProgramData\CrashPlan (assuming you’re on Windows). You must edit the file from a notepad executed as admin. Make sure to replace the IP ( by the one of your NAS
  • Start the CrashPlan client, enter your CrashPlan credentials and passphrase (you do have one, right? :p)
  • Now let CrashPlan sync all your files for a few days :o)

Hope this helps!


Suggestion 5 (for DSM 5.2):

From Aaron (comment section, thanks!):

Here’s what worked for me, since all else failed on DSM 5.2. These steps assume you’ve already done Suggestion 1 above. The paths also assume you are running CrashPlan PRO.

Install ipkg:

Install bash and coreutils via ipkg:
ipkg install -A bash
ipkg install -A coreutils

Symlink so CrashPlan can find them:
ln -s /opt/bin/bash /bin/bash
ln -s /opt/bin/nice /bin/nice

Back up install.vars and syno_package.vars:
cp /var/packages/CrashPlanPRO/target/install.vars ~/
cp /var/packages/CrashPlanPRO/target/syno_package.vars ~/

Uninstall CrashPlan via Package Center
Install CrashPlan via Package Center

Restore .vars files:
cp ~/install.vars /var/packages/CrashPlanPRO/target/
cp ~/syno_package.vars /var/packages/CrashPlanPRO/target

Start CrashPlan via Package Center, wait for upgrade to complete (~2-5 minutes)

Restore syno_package.vars again (it disappeared for me):
cp ~/syno_package.vars /var/packages/CrashPlanPRO/target

Stop/Start CrashPlan via Package Center (I had to do this twice before it started)

Fix your UI connection config per usual.

As always, YMMV and at your own risk.



For more on repairing CrashPlan setups, read on here:




Leave a Reply

Here's what other Users are reading:

Affiliate Links