This is terrible.

'Early last week we discovered an APFS filesystem bug in a beta of macOS 10.15.5. The technical details of the bug are laid out below, but the short version is that we're no longer able to use our own file copier to establish an initial bootable backup of a macOS Catalina System volume.'

[bombich.com]

[9to5mac.com]

EDIT: Workaround is included now in the top link.



Edited 2 time(s). Last edit at 05/28/2020 04:32PM by sekker.

worthy of a double headline!

Quote
hal
worthy of a double headline!

Indeed! I was collecting links and the quote while you were busy posting...

“ I was collecting links and the quote while you were busy posting...”


I hate it when that happens!

Quote
sekker
MacOS 15.5 Catalina blocks CCC from making bootable backups

Not quite, sekker.

I think Mike said that they can't continue to use their existing method but they have found a workaround. Also, only new bootable backups are affected.

Can you fix your headline? I've had it with misleading and false statements from 45 in the general media; I come here hoping to get away from that stuff…

Quote
Article Accelerator

Quote
sekker
MacOS 15.5 Catalina blocks CCC from making bootable backups

Not quite, sekker.

I think Mike said that they can't continue to use their existing method but they have found a workaround. Also, only new bootable backups are affected.

Can you fix your headline? I've had it with misleading and false statements from 45 in the general media; I come here hoping to get away from that stuff…

I will update, the headline WAS accurate at the time I posted. The question was whether it was intentional or an Apple bug; and CCC did not have a solution at the time I posted.

Glad this is being resolved.

Hi everyone,

Is it reasonable to assume this only impacts people who have moved to OS 10.15 Catalina and doesn't affect those of us who remain on OS X 10.14 Mojave and earlier?

Robert

It only affects those on 10.15.5 and nothing previously.

"Never update" --Chopper

Of note: Just ran a CCC backup today after upgrading a Mac from 10.15.2 to 10.15.5.

Apparently, the update added/modded some firmlinks because it triggered the CCC notification that I needed to use Apple Software Restore and that this would wipe the volume. Incremental backup was not an option.

So, the impact is NOT limited to the initial creation of a bootable backup, but can also affect making clones from volumes that have jumped a few updates via the combo updater.

I'm guessing that they haven't had the chance to test the workflow under sufficient circumstances to have nailed this one down.

...Also, ASR failed, leaving an empty volume. I erased this with DU and was then able to complete the ASR copy.

---