[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[EliM]

There might be a serious problem.

• Please check whether your files on all the disks are still present.

I hope you ran the script with TEST_SWITCH set to Y. We must always do this the first time -- to check what files the script will copy and what files it will delete. The script should only copy files from source EFI to destination EFI. It should not touch any other files.

The fact that your log is 900MB tells me that the script has FAILED.

Are any of your disks partitioned -- in other words, did you manually create partitions on any of your disks?

Yes, all files are present and the source and destination disks are still bootable. I downloaded the EFIClone-v3.sh script today and didn't modify it so I believe that means it is set to test.

I do have one disk that is manually partitioned. But neither the source or destination partition is on that disk.

Is the script just meant to copy the efi partition?

 

[CaseySJ]

Yes, all files are present and the source and destination disks are still bootable. I downloaded the EFIClone-v3.sh script today and didn't modify it so I believe that means it is set to test.

I do have one disk that is manually partitioned. But neither the source or destination partition is on that disk.

Is the script just meant to copy the efi partition?

Yes the script is only meant to copy the EFI Partition, but it might get confused by the presence of any disk containing a manually-created partition. If you can post the first 40 or 50 lines of EFIClone.log, it might help us understand the problem.

 

[CaseySJ]

Ah, I see – it's only for Z390 boards, I have a Z370.
Any chances this alternative will be suitable for Z370 systems in the future?
TIA

I believe it's easier to do this on a Z370 board. Please try this:

• Make sure you have a USB flash disk (formatted as scheme = GUID Partition Map) that contains a copy of the current EFI Folder in its EFI Partition.
• You can make the changes below to the EFI partition of this USB flash disk (and thus avoid any damage to the main macOS disk).
  • Move AptioMemoryFix.efi to your Documents or Downloads folder and delete it from the CLOVER drivers folder.
  • Copy all 3 files in OcQuirks-for-Z370.zip to the same CLOVER drivers folder and reboot.
  • Press F12 (or the function key needed for your board to open the Boot Menu) at the BIOS splash screen and select the USB flash disk to boot from.
  • Does it work?
  • If not, delete those 3 files and copy the 3 files in OcQuirks-for-Z390.zip to the CLOVER drivers folder and reboot.
  • Press F12 (or the function key needed for your board to open the Boot Menu) at the BIOS splash screen and select the USB flash disk to boot from.
  • Does it work?

 

[EliM]

Yes the script is only meant to copy the EFI Partition, but it might get confused by the presence of any disk containing a manually-created partition. If you can post the first 40 or 50 lines of EFIClone.log, it might help us understand the problem.

Thanks for looking into this @CaseySJ. Much appreciated! The first part of the log is below. I'm also attaching a screenshot from disk utility if that helps make sense of the disks and partitions.

[Tue Jan 14 12:00:59 PST 2020] - ***** EFI Clone Script start
[Tue Jan 14 12:00:59 PST 2020] - working directory = /System/Volumes/Data/Users/Shared
[Tue Jan 14 12:00:59 PST 2020] - Running /Library/Application Support/com.bombich.ccc/Scripts/EFIClone-v3.sh
[Tue Jan 14 12:00:59 PST 2020] - The operating system is Catalina
[Tue Jan 14 12:00:59 PST 2020] - Called From Carbon Copy Cloner
[Tue Jan 14 12:00:59 PST 2020] - 1: Source Path = /private/tmp/16777238@200114120009 but changing it to /
[Tue Jan 14 12:00:59 PST 2020] - 2: Destination Path = /Volumes/Catalina Clone - Data
[Tue Jan 14 12:00:59 PST 2020] - 3: CCC Exit Status = 0
[Tue Jan 14 12:00:59 PST 2020] - 4: Disk image file path =
[Tue Jan 14 12:00:59 PST 2020] - CCC completed with success, the EFI Clone Script will run
[Tue Jan 14 12:00:59 PST 2020] - CCC clone was not to a disk image. the EFI Clone Script will run
[Tue Jan 14 12:00:59 PST 2020] - Catalina : destinationVolume name has been renamed to /Volumes/Catalina Clone
[Tue Jan 14 12:00:59 PST 2020] - sourceVolume = /
[Tue Jan 14 12:00:59 PST 2020] - sourceVolumeDisk = disk6
[Tue Jan 14 12:00:59 PST 2020] - destinationVolume = /Volumes/Catalina Clone
[Tue Jan 14 12:01:00 PST 2020] - destinationVolumeDisk = disk3
[Tue Jan 14 12:01:01 PST 2020] - sourceEFIPartition = disk1s1 disk13s2 disk14s1
[Tue Jan 14 12:01:02 PST 2020] - destinationEFIPartition = disk0s1
[Tue Jan 14 12:01:02 PST 2020] - efiBootPartitionUUID =
[Tue Jan 14 12:01:02 PST 2020] - efiBootPartitionDisk =
[Tue Jan 14 12:01:02 PST 2020] - drives Mounted
[Tue Jan 14 12:01:02 PST 2020] - sourceEFIMountPoint =
[Tue Jan 14 12:01:03 PST 2020] - destinationEFIMountPoint = /Volumes/EFI 1
[Tue Jan 14 12:01:03 PST 2020] - ********* Test simulation - file delete/copy would happen here.
[Tue Jan 14 12:01:03 PST 2020] - rsync command will be executed with the --dry-run option
[Tue Jan 14 12:01:03 PST 2020] - rsync command calculated is...
[Tue Jan 14 12:01:03 PST 2020] - rsync -av --exclude='.*'' / /Volumes/EFI 1/
[Tue Jan 14 12:01:03 PST 2020] - THE BELOW OUTPUT IS FROM AN RSYNC DRY RUN! NO DATA HAS BEEN MODIFIED!
building file list ... done
IO error encountered -- skipping file deletion
./
etc -> private/etc
home -> /System/Volumes/Data/home
tmp -> private/tmp
var -> private/var
Applications/
Applications/BetterTouchTool.app/
Applications/BetterTouchTool.app/Contents/
Applications/BetterTouchTool.app/Contents/CodeResources
Applications/BetterTouchTool.app/Contents/Info.plist
Applications/BetterTouchTool.app/Contents/PkgInfo
Applications/BetterTouchTool.app/Contents/embedded.provisionprofile
Applications/BetterTouchTool.app/Contents/Frameworks/
Applications/BetterTouchTool.app/Contents/Frameworks/BTTPluginSupport.framework/
Applications/BetterTouchTool.app/Contents/Frameworks/BTTPluginSupport.framework/BTTPluginSupport -> Versions/Current/BTTPluginSupport
Applications/BetterTouchTool.app/Contents/Frameworks/BTTPluginSupport.framework/Resources -> Versions/Current/Resources

 

[CaseySJ]

Thanks for looking into this @CaseySJ. Much appreciated! The first part of the log is below. I'm also attaching a screenshot from disk utility if that helps make sense of the disks and partitions.

[Tue Jan 14 12:00:59 PST 2020] - ***** EFI Clone Script start
[Tue Jan 14 12:00:59 PST 2020] - working directory = /System/Volumes/Data/Users/Shared
[Tue Jan 14 12:00:59 PST 2020] - Running /Library/Application Support/com.bombich.ccc/Scripts/EFIClone-v3.sh
[Tue Jan 14 12:00:59 PST 2020] - The operating system is Catalina
[Tue Jan 14 12:00:59 PST 2020] - Called From Carbon Copy Cloner
[Tue Jan 14 12:00:59 PST 2020] - 1: Source Path = /private/tmp/16777238@200114120009 but changing it to /
[Tue Jan 14 12:00:59 PST 2020] - 2: Destination Path = /Volumes/Catalina Clone - Data
[Tue Jan 14 12:00:59 PST 2020] - 3: CCC Exit Status = 0
[Tue Jan 14 12:00:59 PST 2020] - 4: Disk image file path =
[Tue Jan 14 12:00:59 PST 2020] - CCC completed with success, the EFI Clone Script will run
[Tue Jan 14 12:00:59 PST 2020] - CCC clone was not to a disk image. the EFI Clone Script will run
[Tue Jan 14 12:00:59 PST 2020] - Catalina : destinationVolume name has been renamed to /Volumes/Catalina Clone
[Tue Jan 14 12:00:59 PST 2020] - sourceVolume = /
[Tue Jan 14 12:00:59 PST 2020] - sourceVolumeDisk = disk6
[Tue Jan 14 12:00:59 PST 2020] - destinationVolume = /Volumes/Catalina Clone
[Tue Jan 14 12:01:00 PST 2020] - destinationVolumeDisk = disk3
[Tue Jan 14 12:01:01 PST 2020] - sourceEFIPartition = disk1s1 disk13s2 disk14s1
[Tue Jan 14 12:01:02 PST 2020] - destinationEFIPartition = disk0s1
[Tue Jan 14 12:01:02 PST 2020] - efiBootPartitionUUID =
[Tue Jan 14 12:01:02 PST 2020] - efiBootPartitionDisk =
[Tue Jan 14 12:01:02 PST 2020] - drives Mounted
[Tue Jan 14 12:01:02 PST 2020] - sourceEFIMountPoint =
[Tue Jan 14 12:01:03 PST 2020] - destinationEFIMountPoint = /Volumes/EFI 1
[Tue Jan 14 12:01:03 PST 2020] - ********* Test simulation - file delete/copy would happen here.
[Tue Jan 14 12:01:03 PST 2020] - rsync command will be executed with the --dry-run option
[Tue Jan 14 12:01:03 PST 2020] - rsync command calculated is...
[Tue Jan 14 12:01:03 PST 2020] - rsync -av --exclude='.*'' / /Volumes/EFI 1/
[Tue Jan 14 12:01:03 PST 2020] - THE BELOW OUTPUT IS FROM AN RSYNC DRY RUN! NO DATA HAS BEEN MODIFIED!
building file list ... done
IO error encountered -- skipping file deletion
./
etc -> private/etc
home -> /System/Volumes/Data/home
tmp -> private/tmp
var -> private/var
Applications/
Applications/BetterTouchTool.app/
Applications/BetterTouchTool.app/Contents/
Applications/BetterTouchTool.app/Contents/CodeResources
Applications/BetterTouchTool.app/Contents/Info.plist
Applications/BetterTouchTool.app/Contents/PkgInfo
Applications/BetterTouchTool.app/Contents/embedded.provisionprofile
Applications/BetterTouchTool.app/Contents/Frameworks/
Applications/BetterTouchTool.app/Contents/Frameworks/BTTPluginSupport.framework/
Applications/BetterTouchTool.app/Contents/Frameworks/BTTPluginSupport.framework/BTTPluginSupport -> Versions/Current/BTTPluginSupport
Applications/BetterTouchTool.app/Contents/Frameworks/BTTPluginSupport.framework/Resources -> Versions/Current/Resources


View attachment 445022

The screenshot helps. Please also post the output from this command in Terminal: diskutil list

There is a very suspicious line in the log:
[Tue Jan 14 12:01:01 PST 2020] - sourceEFIPartition = disk1s1 disk13s2 disk14s1

sourceEFIPartition should be only one disk, not three. I want to understand where disk13s2 and disk14s1 are coming from, hence the diskutil command above.

And this line in the log shows the problem:
[Tue Jan 14 12:01:03 PST 2020] - rsync -av --exclude='.*'' / /Volumes/EFI 1/

It should read something like this:
rsync -av --exclude='.*" /Volumes/EFI/ /Volumes/EFI 1/

• /Volumes/EFI/ <--- this is the source EFI mount point
• /Volumes/EFI 1/ <--- this is the destination EFI mount point

The fact that the source EFI mount point is simply "/" in the log, it means something went terribly wrong.

 

[EliM]

Thanks @CaseySJ. Here's the diskutil list. I had to do it as screenshots because when I copy and pasted the text it was very difficult to read. I can put it in a .txt file if you prefer.

 

[Ploddles]

I believe it's easier to do this on a Z370 board. Please try this:

• Make sure you have a USB flash disk (formatted as scheme = GUID Partition Map) that contains a copy of the current EFI Folder in its EFI Partition.
• You can make the changes below to the EFI partition of this USB flash disk (and thus avoid any damage to the main macOS disk).
  • Move AptioMemoryFix.efi to your Documents or Downloads folder and delete it from the CLOVER drivers folder.
  • Copy all 3 files in OcQuirks-for-Z370.zip to the same CLOVER drivers folder and reboot.
  • Press F12 (or the function key needed for your board to open the Boot Menu) at the BIOS splash screen and select the USB flash disk to boot from.
  • Does it work?
  • If not, delete those 3 files and copy the 3 files in OcQuirks-for-Z390.zip to the CLOVER drivers folder and reboot.
  • Press F12 (or the function key needed for your board to open the Boot Menu) at the BIOS splash screen and select the USB flash disk to boot from.
  • Does it work?

A couple of weeks ago I tried OcQuirks-4 with both my Z390 and Z370 based systems and both worked fine. Since then I updated the Z390 board system to the OcQuirks.efi in combination with OcQuirks.plist version. That one runs fine but I haven't got round to trying it with the Z370 system.
What is the difference between the Z390 and Z370 files above, ie should I hold off updating to the .plist version for the time being?

 

[byteminer]

Thanks @CaseySJ. Here's the diskutil list. I had to do it as screenshots because when I copy and pasted the text it was very difficult to read. I can put it in a .txt file if you prefer.

View attachment 445023View attachment 445024

Could you additionally also upload the output of:

diskutil apfs list

I strongly suspect this is the part where things go awry, so that information would be very beneficial in figuring this out.

As an extra, it would be greatly beneficial if you could post this and the previous one as text documents, which would allow me to more easily emulate your setup for local testing.

 

[EliM]

The screenshot helps. Please also post the output from this command in Terminal: diskutil list

There is a very suspicious line in the log:
[Tue Jan 14 12:01:01 PST 2020] - sourceEFIPartition = disk1s1 disk13s2 disk14s1

sourceEFIPartition should be only one disk, not three. I want to understand where disk13s2 and disk14s1 are coming from, hence the diskutil command above.

And this line in the log shows the problem:
[Tue Jan 14 12:01:03 PST 2020] - rsync -av --exclude='.*'' / /Volumes/EFI 1/

It should read something like this:
rsync -av --exclude='.*" /Volumes/EFI/ /Volumes/EFI 1/

• /Volumes/EFI/ <--- this is the source EFI mount point
• /Volumes/EFI 1/ <--- this is the destination EFI mount point

The fact that the source EFI mount point is simply "/" in the log, it means something went terribly wrong.

@CaseySJ, you probably already realized this, but disk13s2 and disk14s1 are on the drive that was manually partitioned. disk13s2 is the efi for my windows backup and disk14s1 is the efi for my baseline clone (my baseline clone is not the source or destination for the ccc task).

 

[EliM]

Could you additionally also upload the output of:

diskutil apfs list

I strongly suspect this is the part where things go awry, so that information would be very beneficial in figuring this out.

As an extra, it would be greatly beneficial if you could post this and the previous one as text documents, which would allow me to more easily emulate your setup for local testing.

You got it. Files attached. Had to compress them as it wouldn't let me upload .rtf files