Fixing CrashPlan 4.3.0 on Synology

CrashPlan Issue For Synology – Fixing the 4.3.0 update

If your Synology NAS can run docker, you may want to consider an alternative to the CrashPlan package. See here: CrashPlan and CrashPlan Pro on Synology using Docker

Note, see bottom of page for information on DSM 6 and CrashPlan 4.6.0

Recently CrashPlan updated to version 1427864400430, which broke the CrashPlan package Patters had created for Synology installations again. They then (July 2nd?) released 1427864410430 as well, which means that if your CrashPlan installation on Synology broke with version 1427864400430, you will need to upgrade, wait for it to break again, and then fix with version 1427864410430. In general the fix process has been the same over the last few breaks, and I’ve outlined those steps below for the latest version.

There is one major change introduced from CrashPlan. Starting with the 1427864400430 update, a guid (think of it as a key) is needed to securely log into the headless client. Thanks to Mathew Stocks, I’ve made those instructions available as well.

The log for the failing CrashPlan package would look something like this for a failing 1427864400430 upgrade:

Upgrades available at
Downloading a new version of CrashPlan.
Download of upgrade complete – version 1427864400430.
Installing upgrade – version 1427864400430
Upgrade installed – version 1427864400430
CrashPlan stopped, version 4.2.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/1427864400430.

Note that the following instructions are for the 1427864410430 upgrade, which is the latest (as of July 2nd, 2015) update. If your Synology didn’t make it to this version, run the following steps, but substitute “1427864400430” where there are any references to “1427864410430”.

Connect as root to SSH

First, connect to Synology using SSH and the root account (uses admin password).  Connecting as the admin account will give you permission failures!

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.3.0 GUID 559750658046558476

Get the headless key from the .ui_info file

While connected to SSH as root, run the following command to get the headless key file. The funky formatting of this command is because the file does not contain the special newline character:

The command will output a line similar to the following (everyone’s will be different):

Update .ui_info on the computer connecting to Synology

On the computer where you are connecting to CrashPlan on Synology, go to the .ui_info file under the CrashPlan directory. NOTE: I had to manually upgrade my computer’s version of CrashPlan (via in order to see the .ui_info file.

Typically on Windows, this will be found under:

Or on a Mac in the following location (need to have finder set to show hidden files):
/Library/Application Support/CrashPlan/.ui_info

Enter in the new key in the file, replacing the current value, and save it. You should now able able to connect to the headless client. Note that you may need to also update the values in again if you had to upgrade CrashPlan.

CrashPlan 4.6.0

There are some tools referenced in the comments for this page which might make upgrades easier for some people. But I’ll also give the latest files & paths using the original instructions above – the following commands can be used for v4.6.0:

unzip -o /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar "*.jar" -d /var/packages/CrashPlan/target/lib/
unzip -o /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar "lang/*" -d /var/packages/CrashPlan/target/

Find latest package folder:
ls -l /var/packages/CrashPlan/target/upgrade/1435813200460_382.*

Replace the whatevervalue with the folder name:
mv /var/packages/CrashPlan/target/upgrade/1435813200460_382.whatevervalue/ /var/packages/CrashPlan/target/upgrade/1435813200460_382.whatevervalue/

Synology DSM v6

I don’t recommend upgrading to v6 at this time (March 2016) if you do not have an Intel based CPU in your Synology NAS as there have been issues reported with the java packages in the comments here as well as on Patter’s page. If you do have an Intel based CPU you will need to use 7z commands on DSM6 instead of zip commands. Examples for CrashPlan 4.6.0:
sudo 7z e -y -o/var/packages/CrashPlan/target/lib /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar "*.jar"
sudo 7z e -y -o/var/packages/CrashPlan/target/lang /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar "lang/*"

Join the Conversation


  1. Even when I get this last version fixed I still get sick of this problems sorting out and fixing it. I don’t know of any alternative but I am following these close.

  2. I got version 4.7 running on the NAS (ds414 arm) but desktop client keeps saying “waiting for backup” initial backup not complete.
    the engine error log shows a java error:
    Exception in thread “W32836838_ScanWrkr” java.lang.NoClassDefFoundError: Could not initialize class com.code42.jna.inotify.InotifyManager
    at com.code42.jna.inotify.JNAInotifyFileWatcherDriver.(
    at com.code42.backup.path.BackupSetsManager.initFileWatcherDriver(
    at com.code42.backup.path.BackupSetsManager.startScheduledFileQueue(
    at com.code42.backup.path.BackupSetsManager.access$1600(
    at com.code42.backup.path.BackupSetsManager$ScanWorker.delay(

    anyone else seeing this?

  3. Apparently there’s no more jar files in the upgrade archive (1435813200470_317.jar). There is a cpio archive inside the jar archive, but the cpio command in the upgrade script is not on my Synolggy (DSM6.0).

  4. I found a solution to the NoClassDefFoundError (see post above). One of the required steps for java to work is to download the jna-4.2.2.jar file (from and and put it in the /var/packages/CrashPlan/target/bin folder. After, rename the original jna.jar to jna.backup and rename the jna-4.2.2.jar to jna.jar. When i did the last renaming step and renamed the file to jna.jar it registered “.jar” as part of the name. I fixed this by renaming jna.jar to just plain jna
    It is now synchronizing

  5. There is no jar file in /var/packages/CrashPlan/target/upgrade/
    Crashplan 4.7.0 was running ’til july 11th, then it stopped. Reason: The backup destination disconnected. Checked the internet connection on Synology: All ok. Then: Synology extracting upgrade from /var/packages/CrashPlan/target/upgrade/. This is the last message in the log file.

    Synology 412+
    DSM 6.0.1-7393
    Crashplan 4.7.0-0040
    Java SE embedded 8 version 1.8.0_91-0039

  6. @Chris,
    Thanks for your reply. It works. I only changed (after the new install of Crashplan on Synology .ui_info and .identification) the old arrangements and it was starting immediatly with synchronizing (no adopt).

Leave a comment

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