![crashplan upgrade failed crashplan upgrade failed](https://2.bp.blogspot.com/-bCg07I0RlRw/WlV78fda_QI/AAAAAAAAALE/jt2RotbqTtshkV098h_2gxInV3JDIi5swCPcBGAYYCw/s1600/background%2B-%2Blaptop%2B2.jpg)
While I’ve used CrashPlan for many years, the company has held off on updates to its home product for some time, and it just announced on August 22 that it will no longer develop this version. Restoring also took about a day due to the unfortunately outdated and somewhat primitive controls still found in Code42’s CrashPlan for Home.
Crashplan upgrade failed full#
Between diagnosing and running tests, it took parts of a full day. (That’s not great behavior for utility software that’s supposed to cope with terrible system problems.)įortunately, we had the six-week-old clone-and I was kicking myself for not having updated it more recently-and a CrashPlan backup that was up to date as of just moments before the system went bad. Sure enough, it started reporting piles of bad blocks and then stalled. I installed that onto an SSD I had handy, and after running through basic diagnostics that confirmed the Mac was fine, I used its Surface Scan tool to see if it could identify whether bad blocks (unusable small segments) on the disk.
Crashplan upgrade failed pro#
I purchased and installed TechTools Pro 9.5, which can create a bootable Mac system that includes itself. Sometimes, even a failing drive can be duplicated, but it was in too bad a shape for that, whether through Recovery mode and Disk Utility or Target Disk Mode.I used Target Disk Mode to mount the Mac onto another Mac to see if Disk Utility might be able to perform magic that way, and it also failed.I could launch Terminal in recovery to use the diskutil program to force the drive to unmount, but Disk Utility would always wind up reporting that it was unrepairable.The Mac could boot into Recovery, but Disk Utility couldn’t perform a repair on the drive, as it wouldn’t unmount.However, the same symptoms resulted when exiting into a full startup environment. Starting into single-user mode worked, as did performing the fsck command-line function to make sure a drive was left in the correct state for booting.Very quickly, it appeared the drive was damaged, not just corrupted. This worked just fine for six weeks, until she started to receive errors while using her mail client, restarted, and had screens of Matrix-like text scrolling down.