Advertisement

Fixing "Synology repairing upgrade in" [v4.4.1-0035 upgrade]

Home Forums CrashPlan on Synology DiskStation NAS Fixing "Synology repairing upgrade in" [v4.4.1-0035 upgrade]

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #291

    Brad Stone
    Participant

    On November 2, 2015, CrashPlan stopped working on my Diskstation.  The log said:

    Upgrade Failed
    Stopping CrashPlan
    Synology repairing upgrade in
    Synology repairing upgrade in
    Synology repairing upgrade in

    Thanks to patters, the solution is in the upgrade package itself.

    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. cd /var/packages/CrashPlan/target/upgrade
    3. ls -la
    4. At this point you should see some directories that look something like “1435726800441_59.1446145554237
    5. rm -r ./1435726800441_59.1446145554237
    6. Repeat for all BUT ONE of the directories
    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.

    #293

    Brad Stone
    Participant

    Hmm.  For some reason, the formatting for the post isn’t working too well.

    Step 3 should read: ls-la

    This provides the directory listing, of course.

    Step 4 should read: rm -r ./{directoryname}

    This removes the directory and all its contents.

    Advertisement
    #318
    an
    an
    Keymaster

    Hi Brad,

    Thanks for writing this, I’ve edited your listing so that it can be read properly.

    Cheers!

    #345

    Emanuele
    Participant

    I’ve followed this step:

    • SSH to your DiskStation as root
    • Enter command:
      cd /var/packages/CrashPlan/target/upgrade
    • Enter command:
      ls -la
    • 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
    • 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
    • Enter command:
      unzip -o /var/packages/CrashPlan/target/upgrade/1435726800450_270.jar “*.jar” -d /var/packages/CrashPlan/target/lib/
    • Enter command:
      unzip -o /var/packages/CrashPlan/target/upgrade/1435726800450_270.jar “lang/*” -d /var/packages/CrashPlan/target/
    • 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
    • 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

    But at step 7 I’ve got the following error message:

    Archive: /var/packages/CrashPlan/target/upgrade/1435726800450_270.jar

    caution: filename not matched: “*.jar”

    Could you please help me?

    #349
    an
    an
    Keymaster

    Hi,

    You need to edit the filename to the one actually in your NAS, just like the earlier steps mention!

    Note that there should be a similar – but not identical – file like this one  “1435726800450_270.jar”, and you need to edit the command to the right one.

    Cheers

Advertisement
Viewing 5 posts - 1 through 5 (of 5 total)
  • The topic ‘Fixing "Synology repairing upgrade in" [v4.4.1-0035 upgrade]’ is closed to new replies.
https://i2.wp.com/crashplanbackup.com/wp-content/uploads/2015/11/crashplan-fix.png?fit=512%2C512&ssl=1https://i2.wp.com/crashplanbackup.com/wp-content/uploads/2015/11/crashplan-fix.png?resize=150%2C150&ssl=1Brad StoneHome › Forums › CrashPlan on Synology DiskStation NAS › Fixing "Synology repairing upgrade in" This topic has 4 replies, 3 voices, and was last updated 1 year, 9 months ago by  an.Viewing 5 posts - 1 through 5 (of 5 total) Author Posts November 10, 2015 at 16:23 #291 Brad StoneParticipant On November 2,...Unofficial Help & Support Forum for CrashPlan, Cloud Backup and Cloud Storage Solutions - Find Help, Support and a Knowledge base

Here's what other Users are reading:

Affiliate Links
Advertisement

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close