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

lovely666

macrumors member
Original poster
Oct 7, 2006
45
14
Hey All,

Been using Carbon Copy Cloner for years, and had been a happy customer until I dealt with Rob in support. Must have bought 4 version of it over the past 5 years.

I've been trying to make a bootable clone of my MacPro5,1 BigSur 11.6 system, and for some reason the clones aren't bootable, I can make them bootable by using bless to create a new volume snapshot, but those clones will break straight after an update, and will need to be bless/snapshotted again to boot. After investigate the issues and not being able to find any information about what the underlying problem is, I reach out to Carbon Copy Cloner support, and was extremely disappointed with their response. This is informational for anybody else who is considering buying carbon copy cloner, especially if you run an apple unsupported system, like many of us do these days.

A "sorry we don't know how to solve that" or something to that affect would have been fine, but the corporate style we don't support your use case because it is a patched system is pretty offensive to the people who pay for your software, especially when that condition isn't any where on their website.

Their response:
macOS 11 Big Sur was last updated to version 11.6 is out of date, I would update to the current/last release of macOS 11 Big Sur (11.7.3) to see if that helps.

I am running a MacPro5,1 with opencore legacy patcher.
We cant really get into patched systems if APple does not support it.. there is not much we can add to that.

Best wishes

---
(As for the line about updating, what the hell do you think i was making a clone for, and why did i try to update that clone? because I was testing the 11.7.3 update, but don't feel 100% comfortable about doing it, if the backups aren't 100%).

My Original Support Request:
Hello,

I'm wondering if you can shed some lite on why my Big Sur 11.6 clone fails to boot. In the past i've it's worked flawlessly. However now when I make a clone it gets stuck with "rooting from the live fs of a sealed volume is not allowed on a release build" kernel error message on boot. Which I assume is something to do with it not using the seal snapshot when booting.

If i create a new snapshot, with "sudo bless --folder 850\ EVO/System/Library/CoreServices/ --bootefi --create-snapshot --verbose" it will boot, however after applying an update it get stuck again with the same rooting error, until I re-bless/snapshot it.

Ideally I would like for the clone to work without blessing/snapshotting after the clone. Just can't figure out what's wrong with my current running system that's causing the clone not to work, until it's bless/snapshoted (i assume it's snapshotting because ccc does the blessing)

I am running a MacPro5,1 with opencore legacy patcher.
I've attached my carbon copy cloner debug log.

Thankyou for your time.
 

MisterAndrew

macrumors 68030
Sep 15, 2015
2,895
2,390
Portland, Ore.
I was having the same issue with my 7,1. I had to select the option to make the backup bootable, which completely erases the destination drive and attempts to make a bootable clone of the source. I think it has more to do with the complexity of the recent macOS releases rather than the hardware.
 

mode11

macrumors 65816
Jul 14, 2015
1,452
1,172
London
Yes, you need to use CCC’s Legacy clone option. I used it to clone my 5,1’s Monterey 12.6 install to a better NVMe SSD, which obviously needed to be bootable. Didn’t have to Bless afterwards.

This has to do with the way macOS has used separate boot and data volumes in recent versions, with the former being read-only. It’s a security thing. Note that whilst you can clone, you can’t keep doing incremental backups to it like a normal backup. It may work for a bit but isn’t reliable. It’s a one and done thing.
 
Last edited:

genexx

macrumors regular
Nov 11, 2022
221
124
Legacy Patcher...........

If the Patcher is doing what Open Core does, you simply have to Mount the EFI Partition and copy the EFI Folder from the Original HD/SSD/NVME to the clone as you have to with OpenCore Systems copied via CCC.
 
Last edited:

lovely666

macrumors member
Original poster
Oct 7, 2006
45
14
Thanks @mode11, @genexx @MisterAndrew, I can confirm that I was using the bootable clone option, and that I don't need to clone the EFI Partition as I use an externall usb stick that contains opencore, which I always boot from. eg opencore boots up, and i choose the new clone as the boot drive, which is what doesn't work until to I bless/snapshot the new clone.

Open Core Legacy Patcher, is simpy a tool that installs opencore (it can setup file patching to allow unsupported hardware (nvidia) cards to work but i don't use that as i have all supported hardware except for the base system).
 

mode11

macrumors 65816
Jul 14, 2015
1,452
1,172
London
I use Martin Lo’s OC, which I keep on the EFI of a SATA SSD in bay 1. That disk is for Windows (ensures it’s not possible to boot Windows without OC running). So I didn’t do anything with OC when I cloned my disk.
 

lovely666

macrumors member
Original poster
Oct 7, 2006
45
14
I use Martin Lo’s OC, which I keep on the EFI of a SATA SSD in bay 1. That disk is for Windows (ensures it’s not possible to boot Windows without OC running). So I didn’t do anything with OC when I cloned my disk.

Very simular to how i use an external usb sticks. Additionally i have two of them which i use gdisk on to keep the partition ids the same, thus i don't need to worry about not being able to get into the firmware boot picker, nor do i need to worry about updating, just swap to the not current stick, update it and test it. if doesnt't work just swap back.
 

genexx

macrumors regular
Nov 11, 2022
221
124
Thanks @mode11, @genexx @MisterAndrew, I can confirm that I was using the bootable clone option, and that I don't need to clone the EFI Partition as I use an externall usb stick that contains opencore, which I always boot from. eg opencore boots up, and i choose the new clone as the boot drive, which is what doesn't work until to I bless/snapshot the new clone.

Open Core Legacy Patcher, is simpy a tool that installs opencore (it can setup file patching to allow unsupported hardware (nvidia) cards to work but i don't use that as i have all supported hardware except for the base system).
@lovely666

interesting, i was able to clone Monterey+Ventura and just changed the EFI for the Laptop but as it was a SMBios Model without an T2 Monterey+Ventura did not seem to care.

On the SMBios iMac20,1 clone ( same Hardware different NVME ) i never had to change anything and SecureBoot worked 02% OOB.

Never had to re bless.
 

lovely666

macrumors member
Original poster
Oct 7, 2006
45
14
@lovely666

interesting, i was able to clone Monterey+Ventura and just changed the EFI for the Laptop but as it was a SMBios Model without an T2 Monterey+Ventura did not seem to care.

On the SMBios iMac20,1 clone ( same Hardware different NVME ) i never had to change anything and SecureBoot worked 02% OOB.

Never had to re bless.

In the past it worked fine for me too, but something has changed that is forcing me to need to re-bless (blessing after ccc does it)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.