Clover stopped working after re-attaching the drive

[brofessor64]

Greetings,

 

I had a fully working 10.11 installation via Clover on an SSD along with Windows 8.1 (dual boot). Today I was having many issues with Win (nothing unusual, sod it!) so I decided to install Win10 on another SSD and because of yet another plethora of Windows-related problems, I had to unplug my main drive (the one with OS X and Clover on it) from the motherboard to make the installer work.

 

When I re-attached it, Clover did not show up. I figured it might be due to changed boot order but there is no UEFI option in the boot menu either (it's usually something like UEFI: P1 Samsung PRO 512GB, now it's without the UEFI bit). The partitions are intact and I can still boot into Windows, yet when I try to boot from the OS X partition, it does not work (normal black screen, insert media, press any key).

 

I did not change any UEFI /“BIOS”/ settings, swap the SATA port, or make any alterations to the drive whatsoever.

 

As my next step, I installed Clover on a USB drive and successfully booted into the main OS X partition on the SSD through it. I successfully mounted the EFI partition and confirmed that all files on it are intact. I then re-installed Clover to the OS X partition (the installer considered it an upgrade), but to no avail—nothing has changed after a reboot.

 

Now I'm sitting here and wondering what could have caused this and how to fix it. Unfortunately, I haven't been able to find another person with the same problem so far. Any help will be appreciated.

 

Cheers!

 

 

 

For what it's worth, the board is a GA Z97X Gaming 7 and here's a part of the Clover install log:

 

Clover EFI installer log - Sun Oct  9 21:17:51 CEST 2016

Installer version: v2.3k r3793 EFI bootloader

======================================================

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *512.1 GB   disk0

   1:                        EFI EFI                     209.7 MB   disk0s1

   2:                  Apple_HFS OSX                     255.5 GB   disk0s2

   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

   4:         Microsoft Reserved                         134.2 MB   disk0s4

   5:       Microsoft Basic Data                         255.6 GB   disk0s5

[HackerKitty]

Did you check the BIOS Boot Menu?

Sometimes installer can make changes to the EFI BIOS. 

Chech if CMS is set to Disabled (Auto also works but less stable) and OS Type is set to Other OS, not Windows.

[brofessor64]

Did you check the BIOS Boot Menu?

Sometimes installer can make changes to the EFI BIOS. 

Chech if CMS is set to Disabled (Auto also works but less stable) and OS Type is set to Other OS, not Windows.

 

Hi, thanks for the tip, but unfortunately those two options are set correctly so this doesn't appear to be the issue.

 

I was wondering: Does Clover have something like bcdboot in Windows to repair the bootloader? Perhaps it could be more effective than an update/reinstall.

 

I'm probably going to wipe out the whole disk and start anew with Sierra so I guess it's not pressing but I'd really like to know what's behind the issue in case I need to follow the same procedure in the future.

[HackerKitty]

I think the easiest way to multipleboot with Windows is thru EasyBCD.

I have been usung my other Windows/Linux dualboot machine that way with legacy boot.

But accordin to

https://neosmart.net/wiki/easybcd/system-requirements/

it claims to be EFI compatible.