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

Strangely enough, the output appears to be correct.
This leads me to believe that there may be something wrong with the actual script you've been using thus far.
As Casey requested before, please upload the EFIClone-v4.sh script you're currently using with CCC so that we may inspect it.

@manfriday pointed me to this thread on MacRumors in which user DSM2 has publicly posted a modified Thunderbolt NVM for the GC-Titan Ridge that provides full Thunderbolt Bus and Local Node support. It also provides a link speed of 40 Gbps. There is a very simple Thunderbolt SSDT that works in conjunction with the patched firmware. Both files are in Post #725 at the bottom of the linked page.

Because I own the GC-Titan Ridge and an SPI Flash ROM chip reader/programmer, I plan to flash the modified firmware onto my card over the weekend and see if I can duplicate his results.

This is not for Designare Z390, but for motherboards with a THB_C header. [Correction: This might work even on Designare Z390, but it might require using SMBIOS MacPro7,1. Will do some testing over the weekend.] The firmware is specifically for GC-Titan Ridge, but I believe we can apply the changes to Designare Z390 NVM as well. But keep in mind that:

• Reading/writing to the Flash ROM chip on GC-Titan Ridge is easy.
• Reading/writing to the Flash ROM chip on Designare Z390 is very very very difficult. So the work we're doing with @Elias64Fr is still the best solution for owners of this board.

When DSM2 installed the modified GC-Titan Ridge into his 2019 Mac Pro 7,1 (yes, the $6000 machine), he got this:

Just updated my BIOS to ver. 8. Now, suddenly, I can't find the UEFI OS on my Samsung 960 EVO. Clover is definitely installed there, and my "Windows 10 Boot Manager" shows up and boot just fine.

I'm able to boot into Clover and my Catalina install using my backup drive thankfully.

Why can't I boot into Clover?
Any ideas out there?

Lensjocky said:

Just updated my BIOS to ver. 8. Now, suddenly, I can't find the UEFI OS on my Samsung 960 EVO. Clover is definitely installed there, and my "Windows 10 Boot Manager" shows up and boot just fine.

I'm able to boot into Clover and my Catalina install using my backup drive thankfully.

Why can't I boot into Clover?
Any ideas out there?

Click to expand...

If macOS is installed on the Samsung 960 EVO, then it seems the Windows boot loader is also installed there. Most UEFI firmware will prioritize the Windows boot loader.

Couple of suggestions:

• If you can boot from a backup disk, boot from it and check if the Windows disk also has an EFI partition. If so, try moving the "EFI/Windows" folder to the Windows EFI partition.
• Alternatively, try enabling CSM Support in BIOS to see if the UEFI OS boot option appears in the BIOS boot menu.

Lensjocky said:

Just updated my BIOS to ver. 8 now suddenly I can't find the UEFI OS on my Samsung 960 EVO. Clover is definitely installed there and my "Windows 10 Boot Manager" shows up and boot just fine.
I'm able to boot into Clover and my Catalina install using my backup drive thankfully.

Why can't I boot into Clover?
Any ideas out there?

Click to expand...

I had such experience. After flashing BIOS the Windows EFI partition turned out to be on my Mac disk somehow :/

As a result both systems not working. Had to reinstall Windows and restore Mac from CCC.

byteminer said:

Strangely enough, the output appears to be correct.
This leads me to believe that there may be something wrong with the actual script you've been using thus far.
As Casey requested before, please upload the EFIClone-v4.sh script you're currently using with CCC so that we may inspect it.

Click to expand...

I went and try again the CCC backup and the script worked ok this time. I went ahead and edited line 85 to leave test mode (I reinstalled the script yesterday in case there was something wrong with the one I had). I worked beautifully again. That left me wondering what's going on if I'm going bananas or what. I run the debug script you sent me and compared it to the previous output and saw a difference that might have something to do.

As you'll see on the attached image, after the output we get the Terminal's symbol, preceded by the computer name and username. As you'll see, when on the left, the computer name is just a chain of characters, when it should be hMac, could that explain in some way what's going on?
Today, I've only used Brave browser, Terminal, Disk Utility, Photoshop and the background apps, CrashPlan, Dropbox, Adobe Creative Cloud and NTFS for Mac.

Thanks again for your help.

CaseySJ said:

If macOS is installed on the Samsung 960 EVO, then it seems the Windows boot loader is also installed there. Most UEFI firmware will prioritize the Windows boot loader.

Couple of suggestions:

• If you can boot from a backup disk, boot from it and check if the Windows disk also has an EFI partition. If so, try moving the "EFI/Windows" folder to the Windows EFI partition.
• Alternatively, try enabling CSM Support in BIOS to see if the UEFI OS boot option appears in the BIOS boot menu.

Click to expand...

CaseySJ,

Thanks for the suggestions.

As soon as I temporarily moved my "EFI/Microsoft" folder into "EFI/Clover/Microsoft" the UEFI OS boot option became visible in the BIOS Boot order options and via F12 on a cold boot.

Some version of this issue has shown up on my rig before and it stems from me failing to remove my Samsung 960 EVO from my system when I installed Windows 10 on it's own SSD. My Windows 10 SSD does not have an EFI partition and Clover simply inserted that "EFI/Microsoft" folder on my Samsung 960 EVO boot drive. This normally is fine, but can cause trouble during updates and such.

I know this is a question well beyond the scope of a Hackintosh forum, but does anyone know of a way for me to correct this mess without removing all my drives and doing a clean install of Windows 10? I suppose I'd need to create an EFI Partition on the Windows 10 SSD and move the "EFI/Microsoft" folder there and point Clover to it somehow?

I know this mess is of my own making and if it can't be done I'll have to live with it.

Thanks

edunon said:

I went and try again the CCC backup and the script worked ok this time. I went ahead and edited line 85 to leave test mode (I reinstalled the script yesterday in case there was something wrong with the one I had). I worked beautifully again. That left me wondering what's going on if I'm going bananas or what. I run the debug script you sent me and compared it to the previous output and saw a difference that might have something to do.

As you'll see on the attached image, after the output we get the Terminal's symbol, preceded by the computer name and username. As you'll see, when on the left, the computer name is just a chain of characters, when it should be hMac, could that explain in some way what's going on?
Today, I've only used Brave browser, Terminal, Disk Utility, Photoshop and the background apps, CrashPlan, Dropbox, Adobe Creative Cloud and NTFS for Mac.

Thanks again for your help.

Click to expand...

The string of characters from running the actual script is likely normal. It is probably a temporary directory where one ends up because the script goes to the EFI partition, which is then unmounted when the script finishes, thus booting you into some temporary directory.

The output itself is actually identical to the debug script, and both look correct.
Currently things point to something having been screwed up with your original version of the EFIClone script. Since we can't seem to reproduce this behavior, it's going to be very difficult to figure out what went wrong.

To verify that the script produces consistent output now, I'd recommend you once again (last time, pinky promise) completely remove EFIClone-v4.sh and redownload it from Casey's CCC backup guide. Redo the entire setup procedure for it if possible. After that, reboot your PC and try running the script (with test mode still enabled!), then have a look at the log file it produced.
If that still looks kosher, then maybe there was some kind of typo in your original version of the script.

byteminer said:

The string of characters from running the actual script is likely normal. It is probably a temporary directory where one ends up because the script goes to the EFI partition, which is then unmounted when the script finishes, thus booting you into some temporary directory.

The output itself is actually identical to the debug script, and both look correct.
Currently things point to something having been screwed up with your original version of the EFIClone script. Since we can't seem to reproduce this behavior, it's going to be very difficult to figure out what went wrong.

To verify that the script produces consistent output now, I'd recommend you once again (last time, pinky promise) completely remove EFIClone-v4.sh and redownload it from Casey's CCC backup guide. Redo the entire setup procedure for it if possible. After that, reboot your PC and try running the script (with test mode still enabled!), then have a look at the log file it produced.
If that still looks kosher, then maybe there was some kind of typo in your original version of the script.

Click to expand...

Well, the bizarre events keep coming. Before doing any of what you just suggested I restarted the computer just to see if everything would work ok after. Turns out that it doesn't. Same problems, only destination EFI partition mounts.

I've run the debug script you give me and the output is different, so it's the EFIClone.log, so i'm attaching both again, hoping bring some light. Many thanks!

Lensjocky said:

... but does anyone know of a way for me to correct this mess without removing all my drives and doing a clean install of Windows 10? ...

Click to expand...

I've been meaning to check this out myself for a couple of weeks since I'm facing the same problem on one of my systems.