Contribute
Register

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

Joined
Jun 20, 2019
Messages
48
Motherboard
Gigabyte z390 Designare
CPU
i9-9900K
Graphics
RX 5700 XT
Alright, this *might* be the last round of this call-and-response thing, so fingers crossed.
I've attached an ever-so-slightly tweaked version of the previous debug script to this post which might fix this issue. It would be good if you could try it out once more if you have time and report back with the terminal output.
No worries, happy to do it! The terminal results are attached below. I used the same terminal command as before but with the name of the script changed.

sudo /Library/Application\ Support/com.bombich.ccc/Scripts/EFIClone-v3-DEBUG.sh / "/Volumes/Catalina Clone - Data" 0 ""

I don't claim to understand how this works, but just to confirm, it should say .../Volumes/Catalina Clone - Data... with Catalina Clone being the destination volume?

Thanks again for working on this. I really appreciate it!
 

Attachments

  • eficlone-v3-DEBUG terminal results.rtf.zip
    1.3 KB · Views: 42
Joined
Jun 20, 2019
Messages
48
Motherboard
Gigabyte z390 Designare
CPU
i9-9900K
Graphics
RX 5700 XT
With Home and System folders separated onto different drives, we use Carbon Copy Cloner to backup the System drive. To backup the Home drive, we have several options:
  • Create a new task in Carbon Copy Cloner and backup the Home drive to another disk.
  • Use any other backup software of your choice. I personally use Acronis True Image to back up the entire computer (Home and System and EFI) to a Netgear ReadyNAS.
  • Use TimeMachine.
Thanks @CaseySJ! I'm interested in this as well. What are your restore steps if the user folder is on a separate drive?
 

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
18,025
Motherboard
Asus Z690 ProArt Creator
CPU
i7-12700K
Graphics
RX 6800 XT
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
No worries, happy to do it! The terminal results are attached below. I used the same terminal command as before but with the name of the script changed.

sudo /Library/Application\ Support/com.bombich.ccc/Scripts/EFIClone-v3-DEBUG.sh / "/Volumes/Catalina Clone - Data" 0 ""

I don't claim to understand how this works, but just to confirm, it should say .../Volumes/Catalina Clone - Data... with Catalina Clone being the destination volume?

Thanks again for working on this. I really appreciate it!
This output looks correct!
 
Joined
Mar 28, 2019
Messages
131
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
No worries, happy to do it! The terminal results are attached below. I used the same terminal command as before but with the name of the script changed.

sudo /Library/Application\ Support/com.bombich.ccc/Scripts/EFIClone-v3-DEBUG.sh / "/Volumes/Catalina Clone - Data" 0 ""

I don't claim to understand how this works, but just to confirm, it should say .../Volumes/Catalina Clone - Data... with Catalina Clone being the destination volume?

Thanks again for working on this. I really appreciate it!
As far as the path to the clone volume goes, your assumption is correct, though you could also just point it straight at "/Volumes/Catalina Clone" instead, the script can figure out the actual data location on its own (when it works). I specifically instructed you to do it this way because I want to emulate the exact arguments that CCC hands to the script, to replicate the actual situation as faithfully as possible. Hence we do it with the "- Data" suffix for now.

The output of the script looks better now, it correctly identifies the two EFI partitions without doubling up on anything, we can see that the entire process ran through without failure, which is good.
I would thus now suggest we try the original script with this slight modification (and the test switch still turned on!) and closely examine its output to determine whether everything is now fixed or whether there's still something off.

To this end I would suggest you try and run the attached modified version of the full EFIClone-v3 script (via Terminal, again) and upload:
- The terminal output
- The EFIClone log file
- The output of the command diskutil list

These three combined will allows us to assess whether everything is now kosher.
 

Attachments

  • EFIClone-v3-experimental.sh.zip
    4.2 KB · Views: 58

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
18,025
Motherboard
Asus Z690 ProArt Creator
CPU
i7-12700K
Graphics
RX 6800 XT
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
Thanks @CaseySJ! I'm interested in this as well. What are your restore steps if the user folder is on a separate drive?
The restore process can be as follows:
  • If we backed up the Home folder with Carbon Copy Cloner, we can restore it very easily by switching the Source and Destination disks.
  • If we backed up using Acronis True Image, we can restore selected disks from the Acronis backup. When Acronis backs up the entire computer, it keeps the identify of each drive in the system. Recovery, therefore, consists of choosing which drive(s) to restore.
 
Joined
Jun 20, 2019
Messages
48
Motherboard
Gigabyte z390 Designare
CPU
i9-9900K
Graphics
RX 5700 XT
The restore process can be as follows:
  • If we backed up the Home folder with Carbon Copy Cloner, we can restore it very easily by switching the Source and Destination disks.
  • If we backed up using Acronis True Image, we can restore selected disks from the Acronis backup. When Acronis backs up the entire computer, it keeps the identify of each drive in the system. Recovery, therefore, consists of choosing which drive(s) to restore.
That's great, super easy! What about when you have to do a fresh install of Mac OS but want to use your existing user folder that is on a separate drive?
 
Joined
Jun 20, 2019
Messages
48
Motherboard
Gigabyte z390 Designare
CPU
i9-9900K
Graphics
RX 5700 XT
As far as the path to the clone volume goes, your assumption is correct, though you could also just point it straight at "/Volumes/Catalina Clone" instead, the script can figure out the actual data location on its own (when it works). I specifically instructed you to do it this way because I want to emulate the exact arguments that CCC hands to the script, to replicate the actual situation as faithfully as possible. Hence we do it with the "- Data" suffix for now.

The output of the script looks better now, it correctly identifies the two EFI partitions without doubling up on anything, we can see that the entire process ran through without failure, which is good.
I would thus now suggest we try the original script with this slight modification (and the test switch still turned on!) and closely examine its output to determine whether everything is now fixed or whether there's still something off.

To this end I would suggest you try and run the attached modified version of the full EFIClone-v3 script (via Terminal, again) and upload:
- The terminal output
- The EFIClone log file
- The output of the command diskutil list

These three combined will allows us to assess whether everything is now kosher.
Yay! We're making progress! Here are the files.
 

Attachments

  • EFIClone-v3-experimental.sh terminal output.rtf.zip
    1.3 KB · Views: 47
  • EFIClone.log.zip
    3.6 KB · Views: 50
  • diskutil list output.rtf.zip
    2 KB · Views: 51
Joined
Nov 18, 2015
Messages
201
Motherboard
GIGABYTE Z490 Vision D
CPU
i9-10850K
Graphics
RX Vega 64
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
  • We can follow Step 1, Bullet #4 in the Catalina Mini-Guide to update Clover.
  • After the update, download the ZIP file from the same Catalina Mini-Guide and copy the kexts and drivers from the ZIP to the corresponding folders in CLOVER.
  • The SSDTs have not changed so no need to modify the ACPI/patched folder.
  • Note that we are now using:
    • OcQuirks.efi
    • OcQuirks.plist
    • FwRuntimeServices.efi
    • These 3 files will be copied into the new CLOVER/drivers/UEFI folder.
  • After making these changes, delete the old CLOVER/drivers64UEFI folder (or move it to someplace else such as your Documents or Downloads folder).

I'm assuming that I would in fact select "Install RC scripts on target volume" when following Step 1, Bullet #4 as I'm not installing to a USB drive but updating my actual boot drive. Correct?

Thanks Again CaseySJ.
 
Joined
Mar 28, 2019
Messages
131
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
Yay! We're making progress! Here are the files.

Indeed we are. So much so in fact that it appears that the problem has been solved!
The script has determined the following partitions for the backup task:
Code:
sourceEFIPartition = disk1s1
destinationEFIPartition = disk0s1

Referencing these in your diskutil list output gives us the following disks:
Code:
"disk1s1" -> belongs to "disk1" -> is container for "disk4" -> is APFS volume "Catalina"
"disk0s1" -> belongs to "disk0" -> is container for "disk3" -> is APFS volume "Catalina Clone"

As such we can now see that the two partitions were correctly found!

I'd like @CaseySJ to take a look at the results as well, just to double-check everything, but I believe this issue has thus been fixed for good.
The EFIClone-v3-experimental script is exactly the same as the current one with the fix applied, so it should be good to drop-in and replace the current one after validation.

The issue lay in the getEFIVolume method. It receives as input the disk we want to find the EFI partition for, i.e. "disk4". The problem was that it was checking for string equality in a somewhat open-ended fashion using grep "$1". Given the string "disk1" as input, it would match all disks that contained this string.
This is where we find out why this issue only affected very few people, those with a large amount of drives configured. Specifically, anyone with drives in the double digits or more.
The grep would then still try to match "disk1", but if you have, say, 16 disks (including virtual ones for APFS stuff etc), it would also match every other disk starting with "disk1", which is basically every disk above and including "disk10".
In your case, only disk13 and disk14 had an EFI partition, so that is why those two also appeared in your original output.

To fix this, we remove the open-endedness of the grep command by switching to grep "$1s". This adds an "s" to every input string, so that "disk1" becomes "disk1s". macOS distinguishes partitions using the syntax disk<num>s<partition>, so we can safely match using this method since we want to find a partition anyway. This cuts off the matching string after the actual number, preventing grep from matching anything other than the actual disk number. Thus the problem is fixed.

In typical development fashion, it all came down to a fix of literally a single character.

I would recommend we wait for Casey to take a look at the results and the proposed fix and once everything's greenlit, I think we should be good for using this script in setups with large amounts of disks safely.

I have already updated the script in my original GitHub repository with this fix as well.
 
Joined
Jul 19, 2017
Messages
121
Motherboard
Gigabyte Z390 Designare
CPU
i7-8700K
Graphics
5700 XT
  • When you put the system to sleep, it will "uncleanly" eject USB drives. To prevent this, we have two options:
    • Reduce memory speed to max 2933MHz or 2666MHz. See Post #1:
      View attachment 445002
    • Use a utility like Jettison to cleanly eject external drives prior to sleep.
I did it!! The problem its one of the USB dock. I tried a disk speed test, and in one of dock the speed is 80 Mb/s and in the other dock only 10Mb/s. After seconds in this dock, the HDD froze.

Well, thanks for your patience!!
 
Top