Fixing CrashPlan 4.2.0 on Synology after DSM 5.2 update

The latest round of updates from CrashPlan (4.3.0) has broken the CrashPlan package on Synology again. Please see for the newest instructions.

Archived information for 4.2:

After installing Synology DSM 5.2, CrashPlan recently pushed an update (4.2.0) which broke the CrashPlan package Patters had created for Synology. The log for the failing CrashPlan package would look something like this:

CrashPlan started, version 3.7.0, GUID 559750658046558476
Upgrades available at
Downloading a new version of CrashPlan.
Download of upgrade complete – version 1425276000420.
Installing upgrade – version 1425276000420
Upgrade installed – version 1425276000420
CrashPlan stopped, version 3.7.0, GUID 559750658046558476

If the package was attempted to start again, it would write a line similar to the following, and then stop:

Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.

This seemed to be similar to the previous issue seen in 3.7.0, so I used the following steps to fix crashplan on my synology box: Note that this will likely be fixed by Patters soon, this is just a workaround if your CrashPlan install has stopped as a result of the 4.2.0 update.

Connect as root to SSH

First, connect to Synology using SSH and the root account (uses admin password).  Connecting as the admin account will not give you enough permissions.

In SSH, run commands to extract the update

In SSH, run unique command to cleanup the package

The next command will be different for everyone, as part of the file path is randomized.  In this case, you will need to see what your path is first by running ls, and then editing the second statement below, replacing whatevervalue with the rest of  your path:

Start CrashPlan package, check log

After the above completes, you should be able to start the CrashPlan package again in Synology and get it running once more. The log should show:

CrashPlan started, version 4.2.0 GUID 559750658046558476

Join the Conversation


  1. Total beginner here, I am attempting the instructions and keep getting “cannot find or open /var/packages/….” I am logged in as root with my password. The numbers match up, and I am editing the lines as CrashPlanPro, because I am using the pro version obviously. Any help would be appreciated

  2. Total beginner here. I am trying this fix. I am logged in as root. When I copy and paste the commands i get a message “cannot find or open /var/packages…” All of the numbers match up, and I edited the line to read CrahPlanPro to reflect the product that I am using. Any help would be appreciated

  3. Hi,

    I have simular problem as george.When I run the command I get: caution: filename not matched: 1425276000420.jar. Any ideas?

  4. I see that people were having some trouble because of the global matching, the easy thing to do is to put quotes around the wildcards, so the one liners are:

    unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar “*.jar” -d /var/packages/CrashPlan/target/lib/
    unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar “lang/*” -d /var/packages/CrashPlan/target/

  5. Thanks for posting this and thank you even more for assembling this guide. Worked like a charm and was so easy to follow your instructions. Your help is highly appreciated.

  6. Hi, I have an issue, after entering the lines:
    mv /var/packages/CrashPlan/target/upgrade/1425276000420.1431945211031/ /var/packages/CrashPlan/target/upgrade/1425276000420.1431945211031/

    It says ” mv: can’t rename ‘/var/packages/CrashPlan/target/upgrade/1425276000420.1431945211031/’: No such file or directory”

    What’s wrong ?

    Thanks !

  7. Oscar: Just perform the steps and disregard the error “filename not matched” (continue with the other steps). It should work. Did so for me.

  8. Like many others, I’ve benefited from your help on this same problem on several updates now. You have saved me a lot of time for which I’ve very appreciative!

  9. Thank you so much for the instructions. It worked great! And it’s the second time I’ve come to your site to fix something like this.

  10. CrashPlanPRO is case sensitive. Replace CrashPlan with CrashPlanPRO and it works! Thanks, Chris

  11. Thanks this did the trick once I substituted “CrashPlanPRO” for each “CrashPlan” in each command.

  12. Does anyone else notice that the time within the Crashplan logs has set itself to GMT after the latest update?

  13. First thanks for all work on setting up the crashplan backup service and sharing this with everyone. I new to this and don’t understand it all but with your help had my synology backing up to crashplan for a couple years. I had the backup service working with your commands after the 3.7 update…until now

    when I run the first unzip command I get the following:

    DiskStation> unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar
    *.jar -d /var/packages/CrashPlan/target/lib/
    Archive: /var/packages/CrashPlan/target/upgrade/1425276000420.jar
    error: cannot delete old /var/packages/CrashPlan/target/lib/bcprov-jdk15on.jar
    Permission denied
    error: cannot delete old /var/packages/CrashPlan/target/lib/c42_protolib.jar
    Permission denied
    error: cannot delete old /var/packages/CrashPlan/target/lib/com.backup42.desktop.jar
    Permission denied

    when I run the first unzip command with quotes I get the following:

    DiskStation> unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar ?
    ??*.jar” -d /var/packages/CrashPlan/target/lib/
    Archive: /var/packages/CrashPlan/target/upgrade/1425276000420.jar
    caution: filename not matched: “*.jar”

    Am I not running the commands from the right place or should I have done something prior to running the commands. When I use the package center to install the crashplan package it installs and starts running. Then stops. If I try to restart it will ‘think’ for several minutes before defaulting back to stopped.

    I have a DS1512+ running DSM 5.2-5565 with INTEL Atom D2700 processors.

Leave a comment

Your email address will not be published. Required fields are marked *