Contribute
Register

Strange Legacy Sata Drives issue

Status
Not open for further replies.
Joined
Aug 20, 2013
Messages
8
Motherboard
Gigabyte GA-Z77-DS3H ver 1.1
CPU
i5-3450
Graphics
GT 710
Mac
  1. iMac
Edited:
I've worked out the issue. Nothing to do with Sata drives.
Simply my older motherboard although Uefi and Legacy will only boot MBR with MacOs.
It will boot GPT with Windows.
I've always created mac installs with MBR on this PC and thought this Catalina install with APFS had somehow resolved the issue not realising that the old MBR hard drive left in the PC helped the boot.
I discovered the solution when creating a Clover USB boot drive with a micro USB and formatted it GPT and it would not boot.
When I compared it with the Clover USB drive I had tested earlier I realised it was MBR.


Hi Guys, I've just installed Catalina on a HPE 590UK cleveland gl8 motherboard (my main pc these days) with a i7 and GTX 660.
I already had El Capitan installed on the pc in MBR on a separate hard drive.
I have two other hard drives two with windows on.

I have a strange issue that's complicated to explain, but I'll try.

I followed the Catalina install guide here and unbelievably on this old pc I have Catalina working great, sound, graphics, everything and on a APFS SSD drive.

During the install I left the El Capitan disk in the pc as I had access to files and intend on keeping it as storage as its 1TB

This issue I have is that if I remove the El Capitan drive I get No bootable disk when booting the Catalina Drive.
Multibeast has definitely installed the boot loader to the Catalina disk.

I've even tried a Mojave drive in place of the El Capitan disk and Catalina boots fine then.

It boots fine also if I boot from a Clover USB.

Any changes that I make via Clover configurator to the Catalina config.plist work so I know it's using the correct bootloader.

It seems that I need a Clover installed disk attached to the 4th drive in my pc for Catalina to work and then it boots fine with correct version of clover?

I'm wondering wether to do the whole install again with the El Capitan disk already removed or could they be a quicker fix.

I forgot to add that I have tried running Multibeast again without the El Capitan hard drive attached and it still won't boot with a clover mac disk attached.


Cheers Al
 
Last edited:
When you removed the ELCap drive did you boot to BIOS and reset the BBS boot order to make the Catalina drive first in BBS boot order? This is likely your problem - you removed the designated boot drive and failed to tell your system which drive to use instead.
 
Status
Not open for further replies.
Back
Top