Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

SuperDuper & OS10.15.5

flowrider

flowrider

macrumors 604
Original poster
Nov 23, 2012
7,325
3,006
Has anybody run SuperDuper V3.3.1 (v121) and gotten a bootable clone of 10.15.5? I ran it yesterday and when I booted from the clone, my NcMP 7.1 would startup and then shut down. I don't have a boot screen so I don't know what was showing prior to shutdown.

Lou
 
A known problem with SuperDuper! and Carbon Copy Cloner. CCC has been fixed (v5.1.18) but I have not heard of a fix for SuperDuper! yet.
forums.macrumors.com

APFS Bug in macOS 10.15.5 Catalina Impacts the Creation of Bootable Backups

Is this a bug ... or a ‘feature’? I only say this partially tongue-in-cheek. This is another step—like forcing updates—that is part of Apple’s plan to lock down its OS and correlatively user settings as it marches toward ARM and a walled garden philosophy. 1590751211 I think you mean...
forums.macrumors.com forums.macrumors.com
 
  • Like
Reactions: ABuVA
Downloaded the trial version of CCC, V5.1.18, and that worked. Shirt Pocket tells me they are working on a fix.

Lou
 
It almost pains me to post this, but it is getting frustrating, to say the least! Here is the situation (most likely, some/many of you know about this).

When Apple released the latest version of Catalina recently, OS 10.15.5, it caused issues for both Carbon Copy Cloner (CCC) and SuperDuper! (SD). Specifically, after making a backup of one's OS 10.15.5 system with either program, the backup was not bootable. That of course is a precarious situation. Bombich software issued an update to CCC within 2 days, and just yesterday, issued another update. Meanwhile, nothing has happened with SD.

I have always "waxed poetic justice" on SD, continually praising the program (I also say good things about CCC, even though I have never used it), but this most recent situation has me really unhappy.

I am on OS 10.15.4, and can used SuperDuper! with it. And while OS 10.15.5 does not really contain anything earth shattering that one must have, I still prefer to keep up to date. And while I can install OS 10.15.5 and use the 30 day trial version of CCC, I would prefer to have SD work with OS 10.15.5 before "moving" to OS 10.15.5.

Anyone have any insights as to what is going on with Shirt Pocket Software, and specifically SD? Their site does not really say anything informative.
 
^^^^I eMailed yesterday. He responded that he was working on it. Answer is NOT YET 👎

In the meantime, CCC has had two updates 😗

Lou
 
duanepatrick said:
I do not use SD but upon being with a lot of communities I remember that it has a bug on its current version 3.3.1

Refer to these links:

Download SuperDuper! for Mac | MacUpdate

Download the latest version of SuperDuper! for Mac for free. Read 397 user reviews and compare with similar apps on MacUpdate.
www.macupdate.com www.macupdate.com
Click to expand...
Again, I am well aware of the current short coming in SD, regarding backups of OS 10.15.5 systems. The version of Carbon Copy Cloner prior to V 5.1.18, V5.1.17, had a similar issue. Again, though, Bombich Software came out with V5.1.18 on May 29th, shortly after the release of OS 10.15.5, to fix the issue. They subsequently came out with V5.1.19 on Wednesday. But nothing from Shirt Pocket Software.
 
KALLT said:

They note that 10.15.5 caused unforeseen problems for them and they are working on it.
Click to expand...
I've known that ever since the issue appeared. But typically the fixes for previous issues with SD have come much, much faster. As I mentioned, the fix for CCC came only a few days after the issue with OS 10.15.5 reared its ugly head.
 
I've been using SuperDuper for 7 years without issue and have recommended it to others. I don't blame the developer for this issue, which arose from a change in macOS, but I'm pretty disappointed in their response.

The worse part of this issue is that SuperDuper completes the cloning process and does not notify the user that the cloning process failed. To make this worse, the front page of the SuperDuper site contains the following:

"v3.3.1 now available! The latest version of SuperDuper! is faster, better, fully compatible with macOS Catalina (10.15)"

There is a workaround, which involves using the Apple Software Restore (ASR) utility to create the initial copy, after which SuperDuper can be used to do smart updates. However, you have to email the developer to learn about this workaround. :(
 
kaibob said:
I've been using SuperDuper for 7 years without issue and have recommended it to others. I don't blame the developer for this issue, which arose from a change in macOS, but I'm pretty disappointed in their response.

The worse part of this issue is that SuperDuper completes the cloning process and does not notify the user that the cloning process failed. To make this worse, the front page of the SuperDuper site contains the following:

"v3.3.1 now available! The latest version of SuperDuper! is faster, better, fully compatible with macOS Catalina (10.15)"

There is a workaround, which involves using the Apple Software Restore (ASR) utility to create the initial copy, after which SuperDuper can be used to do smart updates. However, you have to email the developer to learn about this workaround. :(
Click to expand...

I think that's the worst part. "Fixing" the issue is one thing, but would it have killed them to release a version that detects the point release in question and informs users of the issue and workaround?
 
I sent Dave another eMail yesterday and received the following response:

Lou, we're doing our best here. I can provide you with a pretty simple workaround:

Unfortunately, 10.15.5 has a bug i
As you know, the bug causes the "system" and "data" Catalina volumes to not be connected with firmlinks.

As a one-time fix, assuming a backup of the startup volume, please open the Terminal application and type the following

sudo asr restore --erase --source / --target

followed by a space. Drag in the backup drive volume from your Desktop, which will be "typed" for you.

For example, if the backup drive is called "SuperDuper Backup", the command will end up being

sudo asr restore --erase --source / --target /Volumes/SuperDuper\ Backup

Press Return. Enter your password when prompted, press Return, allow it to erase the volume by typing “y” and then Return, wait for completion. There will be two “percent complete” bars - both have to finish and the prompt has to come back.

Note that the low level copy that's being done will also rename the backup to the same as the source. You can rename it back on completion.

Once done, you'll have a bootable backup, and subsequent Smart Updates will be able to maintain it as expected.
Click to expand...

I will not be using this method. I may buy a license for CCC, but not yet sure. It's been over a month now and no end in sight.

Lou
 
  • Like
Reactions: ProTruckDriver
ProTruckDriver said:
Yeah, I'm getting to that point too of buying a CCC license and dropping SuperDuper. They should of had a fix by now for SuperDuper. :(
Click to expand...
I've been using SD for a few years. Repeatedly I complained about the shown figures being wrong.
E.g. the number of files copied was higher than the total number of files on my disk.
I also suffered from strange completion behaviour. Then I discovered that the recovery part was not included.
After strange media problems I switched to CCC. That seemed to solve all problems.
Indeed, they seem to fix any problem quickly and overcome the "evolutionary problems" APPLE may cause.
So, I trust that my iMacs and I will survive Big Sur too .....
;JOOP!
 
Let's be clear. This is an Apple issue. CCC found a way for their software to work around the issue temporarily but even they have stated that this is likely a move by Apple to prevent cloning. So, if you need cloning then consider an older OS or once SD have found a work around don't upgrade your OSX again as it's likely Apple will break it in the future.

I've been purchasing Macs and other Apple products for over 20 years and I'm sorry to say that my recent purchase will be my last. Ever since the beancounters took over after Steve passed the quality control and innovation at Apple collapsed. You only have to look at the latest keynotes at their Developer Conference to see how far Apple has strayed from the path. Rounding the icons, expanding the number and usage of emojis doesn't translate to significant innovation. Goodbye Apple.
 
The developer of SuperDuper reported that Apple fixed this issue in 10.15.6. Two of his statements are:

Happy to say that Apple has fixed the bug in 10.15.5 that caused firmlinks to not be connected after being copied by backup programs.... Fortunately, it's fixed in 10.15.6, and a normal Smart Update will repair your backups and all will be back to normal.


BTW, after upgrading to 10.15.6, I did a SuperDuper erase and copy then reboot to clone, and everything worked as expected.
 
Last edited:
  • Like
Reactions: treypiepmeier
kaibob said:
The developer of SuperDuper reported that Apple fixed this issue in 10.15.6. Two of his statements are:

Happy to say that Apple has fixed the bug in 10.15.5 that caused firmlinks to not be connected after being copied by backup programs.... Fortunately, it's fixed in 10.15.6, and a normal Smart Update will repair your backups and all will be back to normal.

Click to expand...
Great, now keep your breath for Big Sur.
;JOOP!
 
  • Like
Reactions: ProTruckDriver
So it appears, at least to me, that Dave has purposely not updated SD because he was waiting on Apple to correct the problem. He bet on the come. He should have been more honest and stated his intention up front IMHO.

Lou
 
  • Like
Reactions: mikzn
flowrider said:
So it appears, at least to me, that Dave has purposely not updated SD because he was waiting on Apple to correct the problem. He bet on the come. He should have been more honest and stated his intention up front IMHO.

Lou
Click to expand...
You may be right, but, without very deep knowledge of the OS, it's a hell of a job to find out how and why
certain constructs refuse to work in a new release. F.i.: is a change a bug (it will go) or intentional (it will stay).
I recently had to buy some new product because the product I worked with crashed and the manufacturer gave up.
It just happens.
;JOOP!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back