Jump to content
9 posts in this topic

Recommended Posts

Hi,

 

I have two physical discs with Clover booting El Capitan (non-uefi). Disk 1 is used kind of "productive" and disk 2 is used for "experimental" tests (like fiddling with clover settings or different kexts). I decide via BIOS boot options which disk to boot as both disks have clover installed.

However what I totally don't understand is that when I boot disk 2 (as said via Bios boot options), clover seems to load the /EFI/Clover/config.plist from the first disk!

 

(Btw. disk 2 was cloned with free superduper and clover installed afterwards on that disk. I already verified with Disk Utility that both disks have a different File system UUID, although I'm not sure whether this should make a difference)

 

Regards,

Herbert

  • 3 weeks later...

As you are using legacy Clover then the sequence is as follow:

1. BIOS started MBR zero sector from the drive you choose to boot. This is disk2. There is a boot0af boot sector written into.

2. This program boot0af search for EFI System Partition on the drive, load sector 1 from the partition and start it. There is boot1f32 boot sector written into.

3. This program boot1f32 search for a file with name boot on the partition. This is CloverEFI. It also can be Chameleon.

4. The CloverEFI make initialization of hardware and search for /EFI/CLOVER/CLOVERX64.EFI but it forgot from where it was loaded. So why it may load the file from disk0 and other files from disk0 installation.

5. The same issue if you have USB stick inserted. Clover from HDD will load USB Clover installation.

This issue is not repairable so I may just suggest you to make only way to boot.

  • Like 1

Thanks a lot for that info!

Do I have other options to recover from booting problems if e.g. I wrongly tuned my clover installation?

Would booting from USB help in such a case (as you suggested in point 5). Does USB always take precedence for /EFI/CLOVER/CLOVERX64.EFI ?

Or does it just depend on the boot order defined in my BIOS? (which I could always change should I run into problems with one clover configuration)

  • 10 months later...

I am confused with this explanation. It would mean that the boot configs for several disks are not predictable... :unsure:

I got 4-5 different disks, all with an EFI partition, one main Yosemite Disk, one Windows disk and experimental EL Capitan Disk (plus recovery HD etc..)

When in Clover boot menu I always wonder which config.plist is actually loaded and presented in the GUI for temporary modification? The config.plist from my previous boot? from my default boot HD...? When I select one HD (or USB) for booting are the temporary mods merged with the config.plist on that HD or are they ignored?

 

I browsed thru the numerous clover forum articles but I could not find any description how clover actually works..? Any hints appreciated..

 

Thanks!

 

4. The CloverEFI make initialization of hardware and search for /EFI/CLOVER/CLOVERX64.EFI but it forgot from where it was loaded. So why it may load the file from disk0 and other files from disk0 installation.

5. The same issue if you have USB stick inserted. Clover from HDD will load USB Clover installation.

This issue is not repairable so I may just suggest you to make only way to boot.

They are not merged. There will be loaded first one Clover with it config.plist.

It may depends on timeout to spin up HDDs.

  • 4 weeks later...

I am confused with this explanation. It would mean that the boot configs for several disks are not predictable... :unsure:

I got 4-5 different disks, all with an EFI partition, one main Yosemite Disk, one Windows disk and experimental EL Capitan Disk (plus recovery HD etc..)

When in Clover boot menu I always wonder which config.plist is actually loaded and presented in the GUI for temporary modification? The config.plist from my previous boot? from my default boot HD...? When I select one HD (or USB) for booting are the temporary mods merged with the config.plist on that HD or are they ignored?

 

I browsed thru the numerous clover forum articles but I could not find any description how clover actually works..? Any hints appreciated..

 

Thanks!

 

Since with the latest Clover, you can pick the config.plist from a menu, you can create fake config.plists with a reference to the disk in the filename. So that is a work around to see which disk was booted. I agree that it would be nice if Clover would just show which disk is selected.

×
×
  • Create New...