Advertisement
CrashPlan Community Forum – Support & Assistance

Fixing “Synology repairing upgrade in” issue

Affiliate Links

If your CrashPlan installation is stuck with one of these two upgrade errors:

Upgrade Failed
Stopping CrashPlan
Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1427864400430.

Or

Installing upgrade - version 1435726800450
Upgrade failed - version 1435726800450

 

Take notice of the last string of numbers that is currently appearing on your own CrashPlan log (this is the DSM’s package log, you can also find it in /var/packages/CrashPlan/log/history.log.X). In the examples above you can find 1427864400430 and 1435726800450. The last three digits are the current CrashPlan package version (4.3.0 and 4.5.0).

 

Important!

You’ll need to edit all the corresponding commands below with the right file name on your NAS!

 

You have two options, both described below:

  • No Upgrade button available on DSM’s Package Manager
  • Upgrade button available on DSM’s Package Manager

 

If you don’t see an Upgrade button, first stop the package if it is running. After that:

  1. SSH to your DiskStation as root
  2. Enter command:
    cd /var/packages/CrashPlan/target/upgrade
  3. Enter command:
    ls -la
  4. At this point you should see some files and directories that look something like “1435726800441_59.1446145554237“. Take notice that the numbers after the dot “.” are random, so different on each machine. Also, if you see different files and folders with different numbers left to the dot, take under consideration only the highest (i.e. most recent):
    1. 1435726800450_264.*
    2. 1435726800450_269.*
    3. 1435726800450_270.* <<<—-  We’re using this one
  5. From here you can use one of the directories available (e.g. consider the last one) but I’m showing how to extract the updates anyway. Delete all files and folders except the one we’re using:
    1. Considering the file we’re using is “1435726800450_270.jar”, we’ll temporarily rename it by adding a “_” prefix and use a wildcard to delete the rest.
    2. Enter command:
      mv 1435726800450_270.jar _1435726800450_270.jar
    3. Enter command (removes all files and folders that begin with “143”):
      rm -r ./143*
    4. Enter command:
      mv _1435726800450_270.jar 1435726800450_270.jar
  6. Enter command:
    unzip -o /var/packages/CrashPlan/target/upgrade/1435726800450_270.jar “*.jar” -d /var/packages/CrashPlan/target/lib/ (deprecated in latest versions)

    • sudo 7z e -y /var/packages/CrashPlan/target/upgrade/1435813200470_317.jar “*.jar” -o/var/packages/CrashPlan/target/lib/
  7. Enter command:
    unzip -o /var/packages/CrashPlan/target/upgrade/1435726800450_270.jar “lang/*” -d /var/packages/CrashPlan/target/ (deprecated in latest versions)

    • sudo 7z e -y /var/packages/CrashPlan/target/upgrade/1435813200470_317.jar “lang/*” -o/var/packages/CrashPlan/target/lib/
  8. Run the package again an check CrashPlan’s version (double-click the CrashPlan logo and enter command: version). It should read the updated version:4.5.0 – 1435726800450 (2015-07-01T05:00:00:450+0000) – Build: 270
  9. If the CrashPlan app on your computer is request login credentials, you need to update your local computer .ui_info file with the content from the Synology file. Copy and paste it after entering this command:
    cat /var/lib/crashplan/.ui_info ; echo

 

Built from: http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/

 


Looking for an alternative solution? Try setting up CrashPlan using Docker:

http://crashplan.setepontos.com/crashplan-in-docker-on-synology-nas/


In case there’s an Upgrade button, try these instructions that our community user @stone shared with us:

Launch the CrashPlan client that is pointed to your NAS. You will probably see a status of “Stopped”. You may also see an “Upgrade” button. The upgrade button didn’t show up right away for me. I went to the Package Center > Community and at that point the CrashPlan app displayed the need for an Upgrade. The instructions for upgrading are included in the description:

EITHER completely remove and reinstall the package (which will require a rescan of the entire backup set) OR alternatively please delete all except for one of the failed upgrade numbered subfolders in /var/packages/CrashPlan/target/upgrade before upgrading.

Here is how to do the second option:

  1. SSH to your DiskStation as root.
  2. Enter command:
    cd /var/packages/CrashPlan/target/upgrade
  3. Enter command:
    ls -la
  4. At this point you should see some directories that look something like “1435726800441_59.1446145554237
  5. Enter command:
    rm -r ./1435726800441_59.1446145554237
  6. Repeat for all BUT ONE of the directories (e.g. last one)
  7. Go back to the CrashPlan Client and press the Upgrade button.
  8. Follow the prompts to complete the upgrade
  9. Press the Run button at the end if necessary

Hope this helps.

 

 

Advertisement

Comments are closed.

Here's what other Users are reading:

Affiliate Links
Advertisement