Jump to content

For Clover Experts: old Mobo with Bios & Clover with multiple disk: do not boot

pctmac

By pctmac,
in OSx86 10.11 (El Capitan)

 Share
10 posts in this topic

Recommended Posts

pctmac
pctmac
Posted
Posted

Hi
 

I am facing issue on booting my El Capitan install with my old GA-H67MA-USB3-B3 mobo which has a Bios F8 (so NO UEFI) and 4 disks.

 

My disks are used as follow:

/dev/disk0 : SSD, MBR, 1 partition active, NTFS and bootable with Windows 64: my default boot disk in my Bios.

/dev/disk1 : GUID, NTFS, 1 partiton, not bootable, used to store my Windows Data

/dev/disk2 : SSD, GUID, HFS, 1 partition, bootable with Chimera and Mavericks

/dev/disk3 : GUID, HFS, 3 partitions, try to boot with Clover, Mavericks (backup) and El Capitan (test) + Mac Data

I boot Windows by default and hit F12 to boot from disk2 when I want to use MacOS.

 

I have succesfully installed El Capitan on second partition of disk3, installed Clover on this and when I boot with Clover by hitting F12 and selecting disk3: it hangs !

 

Here is what I have done :

I have installed El Capitan on partition 3 of my disk3 following this guide: #####: Install OS X El Capitan on Any Supported Intel-based PC

I then created a USB Clover test drive in legacy mode and I am able to boot from this stick, then choose El Capitan on disk3 who boot and run properly from this USB: I know have a proper Clover config (DSDT, config.plist, kexts, etc) which demonstrate I can boot El Capitan with clover on my PC. It also provides the files I am copying on the clover install on the disk.

I then installed Clover on my disk3 in the EFI partition (installed in ESP) using legacy mode, as for the USB stick above, and copied the config from the working USB stick. When I boot and hit F12 to choose my disk3, I just have the "Loading Operating System" message and then a black screen: no quick boot0af line message I have when booting from the USB, nothing. It's stuck, I have to power down to reboot.

Reading the Clover WIKI, I am in Option A, using legacy bios, the sequence will be:
Option A: BIOS-based PC (old motherboards)
BIOS>MBR>PBR>boot>CLOVERX64.efi>OSLoader

According to this I should install «boot» in MBR sector:

  • boot0 - searches for an active partition in the MBR and passes control to its PBR sector. Hybrid GPT/MBR layout is possible.

However if the filesystem is pure GPT, boot0 passes control to the EFI partition, further referred to as boot0af (active first).

  • Then in the PBR Sector of the EFI partition: Partition Boot Record (PBR) is a boot sector located in the beginning of each partition on a storage device. The phase two loader is stored here. PBR has the information of its partition's file system and may find and load the boot file and pass the control to it.

So I should install «boot1f32» - supports FAT32. This file system is able to be written at the booting stage thus very well suited for boot loader installation. It is possible to use it as a EFI partition or on a USB flash drive (USB sticks are usually sold pre-formatted in FAT32).

 

If I look at the Clover_Install_Log.txt file (see below), I have boot0af installed on MBR and boot1f32 installed on PBR of the EFi one, so everything should be fine !

What I do not understand is where does it hangs: at MBR or PBR level ?

 

Here my Clover Install log file:

Clover EFI installer log - Sun Nov 1 18:07:50 CET 2015
Installer version: v2.3k r3320 EFI bootloader
================================================== ====
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *128.0 GB disk0
1: Windows_NTFS Windows7 128.0 GB disk0s1   Volume UUID: 9EEFB5D4-2511-4929-B5CA-DFF91F9BD55B
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *3.0 TB disk1
1: Microsoft Reserved 134.2 MB disk1s1 | Disk / Partition UUID: 87B61FC4-989C-4408-BFB9-1E4AE8A9E042
2: Microsoft Basic Data Win7Data 3.0 TB disk1s2   Volume UUID: 7EE9CE0E-01FB-49AC-ABB4-C36C962FE623  | Disk / Partition UUID: 424F4DD1-0D84-478F-A9E5-5A2A57C5E5C2
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *256.1 GB disk2
1: EFI EFI 209.7 MB disk2s1 | Volume UUID: 0E239BC6-F960-3107-89CF-1C97F78BB46B | Disk / Partition UUID: ED3D07EE-A02C-48B8-9ACF-9F0AFE81BB76
2: Apple_HFS Mavericks-SSD 255.7 GB disk2s2 | Volume UUID: D758C9BA-6E45-3068-B09D-0EF5E7B879EE | Disk / Partition UUID: 233D9A3C-06E2-4B63-ABD3-66F465807069
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk3
1: EFI EFI 209.7 MB disk3s1 | Volume UUID: 9098615F-4F76-387C-94DE-60B40E333D52 | Disk / Partition UUID: C184A63F-58C6-44F4-9A6B-6F04FF06C3BF
2: Apple_HFS Mavericks 10.9.5 195.8 GB disk3s2 | Volume UUID: C4C62A5B-46C2-3A6B-8724-600077D9EA6C | Disk / Partition UUID: A96679D2-8B84-48BC-9B61-30D659332222
3: Apple_HFS El Capitan 10.11.1 195.3 GB disk3s3 | Volume UUID: 7F81B42E-0346-335B-8FA9-5341EA8417FD | Disk / Partition UUID: 82A6D379-8065-4EA8-B234-6273CD17FEDD
4: Apple_Boot Recovery HD 650.0 MB disk3s4 | Volume UUID: 0886E734-3603-362F-984E-B5FC37013F36 | Disk / Partition UUID: D1737F85-7CA5-4960-8A38-8507AA0A82A9
5: Apple_HFS MacData 1.6 TB disk3s5 | Volume UUID: 9E6E1842-C6A5-305C-8C08-60926E8CD8F8 | Disk / Partition UUID: C3AA55B4-8FFE-41A6-9962-FFF5350DFA14
================================================== ====
Backing up EFI files

Backing up stage2 file /Volumes/El Capitan 10.11.1/EFIROOTDIR/boot to /Volumes/El Capitan 10.11.1/EFI-Backups/r3292/2015-11-01-18h07/boot
Backing up /Volumes/El Capitan 10.11.1/EFIROOTDIR/EFI folder to /Volumes/El Capitan 10.11.1/EFI-Backups/r3292/2015-11-01-18h07/EFI
No Active Partition

Stage 0 - Writting boot0af to /dev/disk3
/Volumes/El Capitan 10.11.1/usr/local/bin/fdisk440 -u -f /Volumes/El Capitan 10.11.1/usr/standalone/i386/boot0af -y /dev/disk3

Stage 1 - Writting boot1f32 to /dev/rdisk3s1
dd if=/dev/rdisk3s1 count=1 bs=512 of=/tmp/origbs
boot volume format is FAT32
cp /tmp/boot1f32 /tmp/newbs
dd if=/tmp/origbs of=/tmp/newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd if=/tmp/newbs of=/dev/rdisk3s1

Stage 2 - Written boot6 (x64) to /Volumes/ESP/boot

Theme 'tonymacx86' (defined in config.plist) not found !
Using default theme 'embedded'
================================================== ====
=========== Clover EFI Installation Finish ===========
================================================== ====
 

I tried the following:

 

But I saw No change.

  • I have reformated the EFI partition on disk3 as FAT32, was not sure it was already the case or not but I did it, re-installed Clover but still no change.
  • Then I have disconnected disk0 (the one booting Windows) and Bingo, I have the attached menu !

So apparently, there is a conflict with the disk0 and the active Windows partition.

I also notice this is very very very slow before it display this menu, compared to Chimera.

I also notice that my disk2 with Chimera/mavericks did not show up in the list.

In the menu, I have:

  • Boot Windows from Legacy HD2: this is my Disk1 with Windows DATA: how can I remove this entry from the menu ?
  • Boot Clover from EFI: do not know what this is entry is. If I try, I've got 2 messages, b1F : init then b1f: error and I need to reboot
  • Boot mac OS X from Mavericks 10.9.5: not tested yet as I have to copy the kexts for 10.9 in Clover
  • Boot mac OS X from El Capitan 10.11.1: it works as from my USB stick.

If I reconnect my disk0, it hangs again if I try to boot from disk3.

 

So remainging questions:

  1. I am correct when I say I must use Option A: BIOS-based PC (old motherboards) :BIOS>MBR>PBR>boot>CLOVERX64.efi>OSLoader ?
  2. is Clover able to manage 2 active MBR partition on 2 disks (disk 0 and disk 3 in my case) ? If not, how should I do?
  3. why boot is so slowwww?

 

Thanks for your help

post-682407-0-00964000-1447425933_thumb.jpg

pctmac
pctmac
Posted
  • Author
Posted

mount el capitan efi, add all the required kexts to efi partition along with config.plist and smbios.plist.(iMac)

 

hope it works

Thanks. Already done. As I have a USB Stick with clover which works well (network, sound, sleep are ok), I have copied all the config to the EFI partition on disk3.

 

To me, problem is before the loader gets to read files on EFI.

pctmac
pctmac
Posted
  • Author
Posted

boot into your windows install, get easy bcd and see what entries are there in boot loader.

post back

Detailled view:

Windows Boot Manager

--------------------

identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}

device                  partition=C:

description             Windows Boot Manager

locale                  fr-FR

inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

default                 {b7524836-2bc1-11e3-ba33-8c3f126cc8f1}

resumeobject            {b7524835-2bc1-11e3-ba33-8c3f126cc8f1}

displayorder            {b7524836-2bc1-11e3-ba33-8c3f126cc8f1}

toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}

timeout                 30

 

Windows Boot Loader

-------------------

identifier              {b7524836-2bc1-11e3-ba33-8c3f126cc8f1}

device                  partition=C:

path                    \Windows\system32\winload.exe

description             Windows 7

locale                  fr-FR

inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}

recoverysequence        {b7524837-2bc1-11e3-ba33-8c3f126cc8f1}

recoveryenabled         Yes

osdevice                partition=C:

systemroot              \Windows

resumeobject            {b7524835-2bc1-11e3-ba33-8c3f126cc8f1}

nx                      OptIn

 

Looks like it does read only my disk0

bigben1
bigben1
Posted
Posted

can you boot into your mavericks install ?? if so boot into mavericks and reinstall clover on your efi partition with config.plist. 

Slice
Slice
Posted
Posted

 

 

Theme 'tonymacx86' (defined in config.plist) not found !

Using default theme 'embedded'

Good working installer should not emit such message.

Anyway I may recommend you to choose Clover BiosBlockIO option in installer if it presents in your installer.

Be sure Clover presents only in one place. Unplug USB drive before reboot.

  • Like 1
pctmac
pctmac
Posted
  • Author
Posted

Good working installer should not emit such message.

Anyway I may recommend you to choose Clover BiosBlockIO option in installer if it presents in your installer.

Be sure Clover presents only in one place. Unplug USB drive before reboot.

 

I suspect there is a scan issue: if too many partition are active or with bootloader, Clover might be lost. So I decided to try disabling the scan features and create custom entries for the disks. i modified my config  as per attached config.plist

 

Then I booted with debug and find the attached log from the USB: I am still able to boot to El Capitan but it looks like it's still scanning all entries even if it display only the 3 entries created + the Apple Recovery (but the Legacy Windows and Clover entries are no more there.

 

EDIT: I am unauthorized to upload files. How can I do ?

pctmac
pctmac
Posted
  • Author
Posted

Other observation

I never see such message with Clover.

I guess this is a message from the Bios, not from Clover.

 

Awaiting I understand how to upload files so that you get my config.plist and the debug file recorded when booting from USB (thus you can see lot of things), I also tried to boot from my disk activating the debug: it hangs again but rebooting with my Mavericks partition and trying to access to the debug file on the disk, I saw it empty: so my guess is that it hangs before Clover boot, thus it does not start the record in the debug file.

 

Again, I do not see the text "b1f init " message, I just see the cursor moving to the end of this message, but no message and then cursor dissapear.

 

What I do not understand is why it boots from USB and not from my disk? What changes in the MBR Boot and PBR Boot between disk and USB ?

 Share
Go to topic listing
×
×
  • Create New...