[Success] GIGABYTE Z370 Gaming 7 + Intel Core i7-8700K + RX 580 + (2x) Dell P2715Q 4k @ 60Hz

[jb007]

Yep, I read that before I installed the card. I might yank the FW card if I don't get OS X going because my Digidesign 003R is not recognized in Windows, even after the last drivers from Avid. Not even compatibility mode can help here. So yeah, using the second from the bottom PCIe slot shuts out SATA3. I think the manual is often misread amongst the Firewire users. As you know, the mobo has an 6-port SATA6 block in that upper-right area by the reset and OC buttons. Populating the PCIEX1_3 slot nulls SATA connector 3 (SATA6 socket #3 from the board's block of 0,1,2,3,4,5) I was writing about the SATA1 connection which physically sits right above SATA0. -So we're still on the same page. Thanks! BTW, no M2 action going on over here. I only use the 2.5" SATA-type SSDs.

Gooday @jiffyslot, If you are using the FW card in the PCIe x 1 slot (the last small connector at the bottom of the board), then the SATA3 port 1 will not work, not the SATA3 port 3 as you have possibly misunderstood (or is it me?).

I've created a diagram for you and others to hopefully clarify the PCIe and SATA ports assignments and PCIe bus sharing. Please excuse the bright colors, but I thought it would help to highlight.

@janardan, this might help you also, if you haven't already worked it out.

@HackaShaq if you think this will help others, please feel free to put it into your build documentation.

 

[headzombie]

@northwinds

So... I am not the most technical person but have built a bunch of machines over there years, including this one. I had an issue similar to this from installing Clover instead of only the Configutator. I installed everything, MultiBeast and then Clover and rebooted. Experienced same behavior as you. Realized on boot that my Clover version was newer (Could tell by the icons) and that was probably wrong.
Reinstalled everything except Clover and everything worked and it booted off the SSD. I installed Clover again and broke again. Then realized I didn't need to install Clover, only the configuration portion.
Hopefully that makes sense, but might not be your issue?

Like a few others here my 10.13.6 install is causing me untold misery!

This is the umpteenth thread I've tried for the Gigabyte z370 in hope of working out why my new build isn't booting.

I went and bought a gigabyte z370 gaming 7 mobo and an i7 8700 along with 32GB of ram as so many posted here as to having oob successful builds with this setup.

Alas several weeks on I'm still struggling and can't get clover to boot my system ssd directly without having to go via the usb install version?

I tried a clean install - 10.13.6 - (with no convert to apfs - just in case - previously tried apfs install with similar lack of success) and then installed multibeast and clover configurator and and even removed my gt640 card so am using onboard gfx, but still I am unable to boot directly.

Please, has anyone any ideas what i need to do to fix this?

Many thanks!

Seriously, please tell me what files would help?
IOReg?
config.plist?

I'd really hoped this build would be quick and relatively pain free!

Any help greatly appreciated!

 

[jiffyslot]

Gooday @jiffyslot, If you are using the FW card in the PCIe x 1 slot (the last small connector at the bottom of the board), then the SATA3 port 1 will not work, not the SATA3 port 3 as you have possibly misunderstood (or is it me?).

I've created a diagram for you and others to hopefully clarify the PCIe and SATA ports assignments and PCIe bus sharing. Please excuse the bright colors, but I thought it would help to highlight.

@janardan, this might help you also, if you haven't already worked it out.

@HackaShaq if you think this will help others, please feel free to put it into your build documentation.

View attachment 350758

Gah! You're right. I had a second look at the manual. Why they would label the SATA 6 bus as SATA 3 is wierd. As in, "Hey that 2012 Mac Pro only runs at SATA 3, but this Mini has SATA 6..." Having an SATA3 label in front of everything makes the board lookk as though the SATA bus only runs at 3Gb/s, which I knew was wrong: That's why I must have been reading that as SATA port 3. It would have been better for them to leave the 3 off of the documentation since there's only one SATA header with 6 ports with a Z370 chipset. Thanks man! I guess I should check the SATA3_3 port instead.

Here's my PCIe setup as I've been using it:

2nd physical slot: PCIEX16: AMD Sapphire RX-580. -double-width fatty.

5th physical slot: PCIEX1_3: Syba Firewire 800/400 card.

6th physical slot: PCIEX4: GC Alpine Ridge Thunderbolt card.

And something just occurred to me: What if that Firewire card -just it being in the board- is the root of the problems? Because I'm pretty sure that none of those more recent iMacs have no Firewire. An unexpected non-OEM device. It could work later, but maybe not on installation of OS X. Thoughts?

 

[jb007]

Gah! You're right. I had a second look at the manual. Why they would label the SATA 6 bus as SATA 3 is wierd. As in, "Hey that 2012 Mac Pro only runs at SATA 3, but this Mini has SATA 6..." Having an SATA3 label in front of everything makes the board lookk as though the SATA bus only runs at 3Gb/s, which I knew was wrong: That's why I must have been reading that as SATA port 3. It would have been better for them to leave the 3 off of the documentation since there's only one SATA header with 6 ports with a Z370 chipset. Thanks man! I guess I should check the SATA3_3 port instead.

Here's my PCIe setup as I've been using it:

2nd physical slot: PCIEX16: AMD Sapphire RX-580. -double-width fatty.

5th physical slot: PCIEX1_3: Syba Firewire 800/400 card.

6th physical slot: PCIEX4: GC Alpine Ridge Thunderbolt card.

And something just occurred to me: What if that Firewire card -just it being in the board- is the root of the problems? Because I'm pretty sure that none of those more recent iMacs have no Firewire. An unexpected non-OEM device. It could work later, but maybe not on installation of OS X. Thoughts?

@jiffyslot glad we got that sorted, hopefully, my diagram helped.

• My thoughts regarding the Syba Firewire card. Have a look at this thread where @Inkly confirms that the SYBA PEX30009 (is that the same as yours?), works well in a Z370 Mobo, including sleep. Note that @awediohead posted in the same thread that he had kernel panics if he had the "Fix Firewire" option ticked in Clover Configurator. I don't have a modern Firewire card to test this. Edit: Also put your Firewire card in the PCIEX1_1 slot, as this does not share bandwidth with anything else on this Mobo (Same goes for the PCIEX1_2 slot, but this is usually covered up by the GPU card). This will free up your SATA3 [1] port! I use this PCIEX1_1 port for my combined WiFi/Bluetooth card.
• If you are trying to install HS again, please remove all cards except the RX 580 whilst installing the software. Once you get HS booting from the SSD, then introduce one thing at a time. This makes fault finding a lot easier for you and others. I usually (but not always) write down the steps I took as I go.
• One thing I have noted previously on another post is that I had issues booting from the SSD after I updated Clover within Clover configurator. It would not boot from my SSD boot drive after applying the later version. So I reapplied the revision 4630 from the Multibeast HS 10.4 install, which is version 4630.
• Also since you are using an AMD RX 580 and your Mobo does have NVRAM, you should use the "Clover UEFI Boot Mode" in Multibeast, not the "Emulated NVRAM" version, (you would use the late if you had a NVIDIA card though from my understanding). You can test that you do have NVRAM available, by running this test from a terminal:
  

  sudo nvram TestVar=DoIHaveNativeNVRAM

  Then reboot and run this from a terminal:
  

  sudo nvram -p | grep 'TestVar'

  If you see "TestVar DoIHaveNativeNVRAM" then you have Native NVRAM, otherwise, you will have to use "Emulated NVRAM".

Let us know how you go if you decide to go ahead with another attempt.

Jim

 

[jiffyslot]

Thank you!

I'm not going to use Firewire in this capacity, so I've pulled it before install: If I need it down the road, I'll use PCIEX1_3 because at that point, I'd have access to the BMD MultiDock via Thunderbolt, so the lack of an particular onboard SATA port is fine. So that you know, the PCIEX1_1 slot is blocked by the huge Noctua CPU Cooler; there's just enough clearance for the AMD to go into the PCIEX16 slot. The Thunderbolt card goes in at the bottom. That's where it goes for this board and that card.

I've installed HS on a 2.5" spinner to force HFS+ -I ran Multibeast 10.4, but on reboot I'm at 99.99% boot after an hour, so either it'll finish so I can CCC (clone) it to an SSD before proceeding, or I'll have to start over.

 

[jb007]

Thank you!

I'm not going to use Firewire in this capacity, so I've pulled it before install: If I need it down the road, I'll use PCIEX1_3 because at that point, I'd have access to the BMD MultiDock via Thunderbolt, so the lack of an particular onboard SATA port is fine. So that you know, the PCIEX1_1 slot is blocked by the huge Noctua CPU Cooler; there's just enough clearance for the AMD to go into the PCIEX16 slot. The Thunderbolt card goes in at the bottom. That's where it goes for this board and that card.

I've installed HS on a 2.5" spinner to force HFS+ -I ran Multibeast 10.4, but on reboot I'm at 99.99% boot after an hour, so either it'll finish so I can CCC (clone) it to an SSD before proceeding, or I'll have to start over.

Ahh, I see, big Cooler. I've got a Corsair H110i AIO, lots more room.

I'm not sure as to the time difference between me in Melbourne Australia and you, but I will check later. I've got my fingers crossed for you! 1 Hour? I guess the old 2.5" drives are slow!

 

[jiffyslot]

Slow, but the install time on a 5400 RPM 2.5 Samsung using a Unibeast installer was not much slower. It booted once very nicely and let me create an account, ran EFI mounter and MultiBeast 10.4.0 and ran the minimal patch setup. -And it failed on me again on restart. Windows 10 is working great on this machine. So this machine is now a over-spec Vienna Ensemble Pro Server. (Time-wise I'm UTC-07:00) https://www.worldtimeserver.com/

 

[jb007]

Slow, but the install time on a 5400 RPM 2.5 Samsung using a Unibeast installer was not much slower. It booted once very nicely and let me create an account, ran EFI mounter and MultiBeast 10.4.0 and ran the minimal patch setup. -And it failed on me again on restart. Windows 10 is working great on this machine. So this machine is now a over-spec Vienna Ensemble Pro Server. (Time-wise I'm UTC-07:00) https://www.worldtimeserver.com/

@jiffyslot, thanks for getting back to me. I don't know what could be wrong.

What is the error message?

Did you run Clover in verbose mode with the "halt on kernel panic" option on in the Clover boot menu, (press spacebar and tick the two options), then so as to catch the errors if any?

Also at clover boot, hit F2 to log the progress int the misc folder in your EFI, then you can see this if you can boot into the OS using your Unibeast installer. There has to be something that is not right (obviously!).

Jim

 

[jb007]

Slow, but the install time on a 5400 RPM 2.5 Samsung using a Unibeast installer was not much slower. It booted once very nicely and let me create an account, ran EFI mounter and MultiBeast 10.4.0 and ran the minimal patch setup. -And it failed on me again on restart. Windows 10 is working great on this machine. So this machine is now a over-spec Vienna Ensemble Pro Server. (Time-wise I'm UTC-07:00) https://www.worldtimeserver.com/

@jiffyslot, just another thing if you want to try it is to remove half of your 4 x 16GB RAM (32GB) or even just 1 x 16GB to see if it is a memory problem with macOS or (?). You do have more RAM than most here, so it's worth a try. Just follow this guide for the RAM slots to use eg if two modules they go in DDR4_2 & DDR4_4 slots.


Jim

 

[charlosb21]

I Just bought all the same parts except the m.2 drive and only have the CPU, RAM, and I'm using the onboard graphics for now and I cannot load into the install USB or any of my previous build hard drives with Mac OS on them or any of the clones of those. all I get is some sort of panic I'm guessing and I cannot see what's going on I took a screenshot on my phone of it but I have been building Hackintoshes for years and I have never experienced anything like this. Also, I do not know if this has to do with anything the BIOS will not update no matter what I do it's on F1 and I cannot Q-flash it or update it with window's bios update utility, and SATA 1 & and SATA5 & 6 do not work.