If the SSD in a M series Mac goes down, it is impossible to boot from an external device. Why would you waste time trying to make a bootable backup?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
PSA: macOS Sequoia 15.2 Breaks SuperDuper Bootable Backups
- Thread starter MacRumors
- Start date
- Sort by reaction score
yup. I used to think nothing of buying the largest fusion drive they offered back in the day.
Reliable, bootable backups with SuperDuper or Carbon Copy Cloner have been a very mixed bag according to what I’ve read about the subject. In my own case with my M1 Studio Max it has never worked. I select the SuperDuper clone for the startup disk, it begins and after ten seconds or so it fails. Other posters here report the same.
Are we saying that there are files in macOS where I can't run `sudo cp`?
Here I was thinking about maybe replacing my 7 year old Raspberry Pi with a MacMini.
Here I was thinking about maybe replacing my 7 year old Raspberry Pi with a MacMini.
While he’s waiting for Apple to fix this issue, maybe the dev could work on updating the superduper website to not look like it’s from the Stone Age.
iPadOS 18.2 is just fine, BUT my iPad is a ninth generation, which means A13 processor, and that means no AI.
You’re talking about SSD failure. If the recovery partition is in working order and you’ve enabled external boot, it’s still relevant.
It’s also a better way to do “stuff” to your internal SSD without jumping through as many SIP hoops.
Maybe I am missing a practical purpose and welcome insight but, how is making a bootable backup in that scenario important?
It definitely is possible nowadays. Here's a link to an article on Apple support: https://support.apple.com/en-us/111336. I think your (justifiable) confusion is that wasn't when the first M1s ones came out. I have done it for the purposes of testing beta versions of macOS when Sonoma-ish was in beta.
If you look at your previous post I had responded to, you said that you had been trying to make bootable backups in case your internal drive went down on your M Series Mac. I replied by stating that you can't boot an M series Mac using an external drive if the internal SSD has failed (for whatever reason). I believe my reply was accurate.
What you linked to here is something different from what you said previously and what I responded to.
To be fair it is less important nowadays. In the spindle drive era it was a frequent scenario to have a disk go bad. Not so much nowadays. Really the only scenario is if data on your drive is corrupted. That can still happen, but SSDs are so good nowadays and things like SIP make this unlikely.
What I'm trying to say is that nowadays the amount of problems that a bootable backup worth the increasing amount of hassle is such that it's impractical.
It's not a bug if you don't update. Almost nothing can take me from Sonoma 14.1.
Any updates to Time Machine would be appreciated.
It hasn't really seen any meaningful updates in a VERY long time.
I'd love to see it improved to do stuff like properly backup iCloud Drive and Photos where items are stored in iCloud. Currently it only backs up what's downloaded to the Mac at the time of the backup.
Typical Apple releasing something and letting it die due to exposure and lack of follow through
How can a company with the resources of Apple allow such a thing to occur? Shouldn't they be testing this functionality?
Exactly my case!
I have used CCC some times since the "change", but didn't realise other apps could do a bootable backup.
Let's hope this is fixed.
Actually this is exactly where I ended up. Doing the bootable thing with CCC just turned into a PITA.
Apple needs to stop pushing the gimmicky AI toys that are thusly making the OS less stable.
Back in the Days when Storage was slow and space was rare..... i used CCC for Boot Clones but now..
Migration Assistant with TM Backup or Original HD/SSD/NVME is doing a Clone in no Time.
I do not have any need for a boot clone these days.
Just did it to prove the possibility to boot and work from a Acasis TB3/4 with WD SN770 2TB for a possible MacMini M4 Base.
Installed the System from my internal booted external migrated from internal bam-> Clone.
Could do it from the TM Backup also.
Did this when changed to MBA M2 just used Migration Assistant and imported TM Backup, bam-> Clone.
Doing this on my Hackintosh, install Beta on second NVME and import with Migration Assistant from the non Beta Internal, bam-> Clone.
There is no way to do this for Windows. You have to Clone to get a Clone.
When you cannot Mount your TM Backup Image on Network while using Migration Assistant, well that is live.
So where is the Problem ?
And i thought this is anyway not possible for AS based Mac´s.
Migration Assistant with TM Backup or Original HD/SSD/NVME is doing a Clone in no Time.
I do not have any need for a boot clone these days.
Just did it to prove the possibility to boot and work from a Acasis TB3/4 with WD SN770 2TB for a possible MacMini M4 Base.
Installed the System from my internal booted external migrated from internal bam-> Clone.
Could do it from the TM Backup also.
Did this when changed to MBA M2 just used Migration Assistant and imported TM Backup, bam-> Clone.
Doing this on my Hackintosh, install Beta on second NVME and import with Migration Assistant from the non Beta Internal, bam-> Clone.
There is no way to do this for Windows. You have to Clone to get a Clone.
When you cannot Mount your TM Backup Image on Network while using Migration Assistant, well that is live.
So where is the Problem ?
And i thought this is anyway not possible for AS based Mac´s.