CarbonCopyClone Failure OSX 13.0

[swizzley]

After updating I took a backup and that backup succeeded but that backup fails to boot. It hangs on a black screen for a while and then loops back to POST. Anybody have any success using CCC with 13? I haven't tried since 13.0.1 will update after I try again.

 

[swizzley]

I was able to clone the disk using aomei backerupper from window$. I'm booted from it now running 13.0.1

Best Backup Software for PCs, Servers and iPhones | AOMEI

Your data deserves strong protection from the best Windows and iPhone backup software of AOMEI. AOMEI products enable home and business users to easily backup data, restore system image, clone hard drive and more.

www.ubackup.com

 

[Edhawk]

Carbon Copy Cloner release 6.1.3 supports macOS Ventura.

Blog | Carbon Copy Cloner | Bombich Software

bombich.com

CCC 6 Release Notes | Carbon Copy Cloner | Bombich Software

bombich.com

 

[swizzley]

I used CCC 6.1.3 and it would not boot. It shows the EFI partition in the menu but not the OS. I haven't tested CCC again since I have the clone working, but I am planning on it with next point release.

 

[c-o-pr]

Just in case it helps:

CCC doesn't handle the EFI. You have to handle that.

A CCC clone is a Mac-specific volume level copy, not a partition or block level copy. In this sense it's not a drive clone, but a system specific copy. This is akin to Windows data migration tools like get bundled with new drives and are aware of Windows specific layout details. CCC is very Mac aware, but not EFI.

By default, a clone is a Data partition only, no system.

The bootable backup assistant can copy the whole drive but requires erasing the target volume, which must be APFS to start. I believe any existing EFI contents are not touched—but I might be wrong.

In a thread from a year ago it was learned that a bootable (APFS Replicator) clone must be made while booted from the drive to be copied, or the target may not be bootable. That news was reported to come directly from Bombich. I should assume that CCC would now warn you about this... Idk There may have been a misunderstanding about the distinction between an APFS Replicator clone (Apple SW guided by CCC) and a CCC Data partition clone,

 

[swizzley]

CCC has always

Just in case it helps:

CCC doesn't handle the EFI. You have to handle that.

A CCC clone is a Mac-specific volume level copy, not a partition or block level copy. In this sense it's not a drive clone, but a system specific copy. This is akin to Windows data migration tools like get bundled with new drives and are aware of Windows specific layout details. CCC is very Mac aware, but not EFI.

By default, a clone is a Data partition only, no system.

The bootable backup assistant can copy the whole drive but requires erasing the target volume, which must be APFS to start. I believe any existing EFI contents are not touched—but I might be wrong.

In a thread from a year ago it was learned that a bootable (APFS Replicator) clone must be made while booted from the drive to be copied, or the target may not be bootable. That news was reported to come directly from Bombich. I should assume that CCC would now warn you about this... Idk There may have been a misunderstanding about the distinction between an APFS Replicator clone (Apple SW guided by CCC) and a CCC Data partition clone,

CCC has always worked for me, I have used the same EFI post script I've used since Mojave, and Ventura is the first where the backup was no longer bootable.