getting confused about my bootloaders, need advice

[yummypixza]

hello there,

just installed OS X 10.11.4 recently, and it works pretty great.

 

before I installed OS X, I also have Win10 and Linux on different HDDs,

but here the problem comes, now I can't reboot to any other system anymore.

 

so here's how my HDDs set looks like under OS X:

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *240.1 GB   disk0
   1:               Windows_NTFS SYS (Win10)             239.6 GB   disk0s1
   2:                       0x27                         477.1 MB   disk0s2
/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *2.0 TB     disk1
   1:               Windows_NTFS ETC (Win10)             703.7 GB   disk1s2
   2:               Windows_NTFS ETC2(Win10)             703.7 GB   disk1s3
   3:               Windows_NTFS (Win7)                  351.9 GB   disk1s4
   4:                      Linux /boot                   524.3 MB   disk1s5
   5:                      Linux /home                   168.5 GB   disk1s6
   6:                      Linux /                       64.0 GB    disk1s7
   7:                 Linux_Swap                         8.0 GB     disk1s8
/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS Macintosh HD            239.5 GB   disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3
   4:       Microsoft Basic Data BACKUP                  1.8 TB     disk2s4

I used boot from disk1 since I want to prevent Windows' MBR from been changed, also grub2 is better for me to manage boot entries.

now they're all gone, and Clover only can detect Windows and OS X,

so my clover screen has become this:

[Win10] [Win10 recovery] [ETC] [ETC2] [Win7] [OSX] [OSX rescue]

but only OSX and OSX rescue is bootable, any other entries will lead to black screen.

in other terms, I stuck in OS X now

 

if i want to make bootloader like this:

grub2 >> [Win10] [Win7] [Linux] [Clover]

[Clover] >> [OSX] [OSX rescue]

 

what should I do?

 

---

spec:

Intel Xeon E3 1231v3

ASUS H97M-Plus (Bios rev.2501)

GTX760

16GB DDR3 RAM

disk0: Intel SSD 520 240GB (for Win10)

disk1/2: WD Red 2TB*2 (one for Linux+Win7, another for OS X)

[Dwarfy]

press F8 in startup, then choose the OS drive for Windows, Linux or Clover bootloader. 

[yummypixza]

press F8 in startup, then choose the OS drive for Windows, Linux or Clover bootloader. 

 

sadly, I cleaned motherboard's startup select menu

just followed http://www.insanelymac.com/forum/topic/308637-how-to-remove-extra-clover-bios-boot-entries-prevent-further-problems/

and now the menu would only appears "UEFI OS (2TB)", which refers to clover, and any other UEFI entries like Linux LiveUSB I made or [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] Install stick.

boot from disk0 and disk1 (Win10's MBR and grub menu) looks not possible for me?

[yummypixza]

ok, about the startup menu "cleaned up"

after I chose to take off the power plug and put it back (cold boot I think), the menu entries are back magically.

so I get into colver UEFI console and get it normal again.

 

but still, if there's a way let me don't have to smash F8 everytime, any if it?

and the main reason is about not to see many dummy Windows entries in Colver 'cause they all can't boot

[Dwarfy]

ok, about the startup menu "cleaned up"

after I chose to take off the power plug and put it back (cold boot I think), the menu entries are back magically.

so I get into colver UEFI console and get it normal again.

 

but still, if there's a way let me don't have to smash F8 everytime, any if it?

 

I myself use OS X more, so pressing F8 is not really a pain for me. It is just to get used to it.  

[fusion71au]

 

I used boot from disk1 since I want to prevent Windows' MBR from been changed, also grub2 is better for me to manage boot entries.

now they're all gone, and Clover only can detect Windows and OS X,

so my clover screen has become this:

[Win10] [Win10 recovery] [ETC] [ETC2] [Win7] [OSX] [OSX rescue]

but only OSX and OSX rescue is bootable, any other entries will lead to black screen.

in other terms, I stuck in OS X now

 

if i want to make bootloader like this:

grub2 >> [Win10] [Win7] [Linux] [Clover]

[Clover] >> [OSX] [OSX rescue]

 

what should I do?

 

---

spec:

Intel Xeon E3 1231v3

ASUS H97M-Plus (Bios rev.2501)

GTX760

16GB DDR3 RAM

disk0: Intel SSD 520 240GB (for Win10)

disk1/2: WD Red 2TB*2 (one for Linux+Win7, another for OS X)

 

It is quite possible to boot with legacy grub and then chain load to legacy Clover installed on the MBR/PBR of disk2 when you want to boot OSX eg Using EasyBCD to Chainload Chameleon or Clover from the legacy Windows Bootloader

 

However if you don't mind starting again, the best solution would be to re-install and boot all your OS's in UEFI mode on GPT formatted drives.  This way, you can launch all your OS's directly from the Clover menu (loading bootmgfw.efi for Windows, grubx64.efi for Linux).  See

 

[Guide] Dual-boot with Windows 10 and Clover - Legacy or UEFI

post#29 for installing Linux Mint in UEFI mode

[yummypixza]

It is quite possible to boot with legacy grub and then chain load to legacy Clover installed on the MBR/PBR of disk2 when you want to boot OSX eg Using EasyBCD to Chainload Chameleon or Clover from the legacy Windows Bootloader

 

now I'm using default Clover installation, which means UEFI installs maybe

is it simply using clover installer to re-install again and select "install on MBR" to change to legacy Clover?

 

now using Clover as v2.3k_r3354.

[namvan]

if you can run Clover Configuratior (because it would be easier for you to configure your boot entries maybe ), you could hide the partitions that you don't want to see at Boot Screen in GUI section.