Non-zero state

[etyel]

Hi,

I'm using Mojave 10.4.6. I hadn't touched the system, Clover or Carbon Copy Cloner or the script when the script stopped working normally
I'm here for help with CCC because I can't find a solution elsewhere. I've always used CCC to make my backups with a post-run shell script found here, everything worked fine until recently. Without having updated the Hack, nor CCC, nor touched the script, CCC started to derail by telling me that the script "stopped with a non-zero state" and telling me to add exit 0 at the end of the script. Well, I don't know anything about scripting, but I try to put this famous exit 0 at the very end of the script, by skipping a line, without any result. I contacted the CCC help, they told me to update CCC, which I do, no better. On my side, I tell myself that the files may have been corrupted, so I replace these scripts by backups, nothing to do. Redownloaded it, nothing.
Only one thing has changed, or I'm missing something huge but I don't see what, I'm temporarily using a Dell 27 connected in HDMI instead of my nice 32 connected in Displayport, but I don't see the connection. Updated to security update 005 since but nothing change.
The EFI partition of the clone rises normally and is intact, but it is no longer updated by CCC. So, yes, I can make manual backups but it was so much easier with the script...

[aflawrence]

I have had the same issue. CCC copies drive with no issue but on running the script returns a non-zero state. An examination of the log indicates it quits when attempting to mount EFI partition. Error log shows it could not mount EFI partition.

[aflawrence]

I figured out the issue. The script will run but you must mount the EFI before running CCC. CCC does not seem to autoload the EFI (perhaps this is a new issue with Big Sur).

[etyel]

In my case, that can't be the explanation since I stayed on Mojave and hadn't done an update. The script suddenly stopped working and it's the same thing with the other version also available on Github. As nobody seems to have an explanation, I will do the EFI updates manually.