roddie Posted October 5, 2017 Share Posted October 5, 2017 Sorry for the unclear title, but I'm struggling to properly define this I've been dual-booting Sierra (not High) and Windows 10 on separate SSDs for months without issue. I'm using UEFI and my Mac SSD has always been the default. On Tuesday, I booted over to Windows 10 to do some stuff and I let it get caught up on updates/patches. I shutdown and restarted, and the system booted into Windows 10 right away. I shutdown again, and went into the BIOS and didn't see any of my Mac SSD UEFI partitions as an option for booting. Since then, I've done some messing around with fdisk (from Recovery) and have tried setting various partitions to active, but I'm still unable to get my Mac SSD UEFI partitions to show up in the BIOS as a boot option. I created a Clover USB drive on another Mac, so I can now finally get into my SSD and boot into OS X, but of course, my sound drivers aren't loading (since fixed by copying my kexts/config.plist from the SSD to USB). There have been a couple of times where I do see the SSD's UEFI partitions as boot options, but they always disappear on the next boot. Is it possible that the Windows 10 updates messed with the MBR on my Mac SSD or is this unrelated, and is my SSD failing? Once I'm in the OS, everything is fine, and I haven't had any other issues on this build. Is there any reason why the BIOS would be inconsistent with what it sees as boot options? Here's how gdisk sees my current partition table on the Mac SSD Warning: Devices opened with shared lock will not have their partition table automatically reloaded! Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/disk1: 1465149168 sectors, 698.6 GiB Sector size (logical): 512 bytes Disk identifier (GUID): 59A3C714-1555-44CE-A40A-2E5005607770 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 1465149134 Partitions will be aligned on 8-sector boundaries Total free space is 13 sectors (6.5 KiB) Number Start (sector) End (sector) Size Code Name 1 40 409639 200.0 MiB EF00 EFI System Partition 2 409640 1463879591 697.8 GiB AF00 3 1463879592 1465149127 619.9 MiB AB00 Now that I can at least boot up using USB, I don't want to mess with fdisk/gdisk anymore without checking here to see if there's something obvious I'm missing. Thanks for any help! Link to comment Share on other sites More sharing options...
fusion71au Posted October 5, 2017 Share Posted October 5, 2017 How did you install Windows (legacy mode or UEFI mode)? What is the output of "diskutil list" in OS X terminal? Assuming that Windows is installed in UEFI mode on a GPT formatted disk, it's likely the Windows boot loader has given itself first boot priority after the update. You can install EasyUEFI in Windows to restore first boot priority to Clover - see "Add Clover as a UEFI Boot Option using the EasyUEFI Program" post#1. Link to comment Share on other sites More sharing options...
roddie Posted October 6, 2017 Author Share Posted October 6, 2017 How did you install Windows (legacy mode or UEFI mode)? What is the output of "diskutil list" in OS X terminal? Assuming that Windows is installed in UEFI mode on a GPT formatted disk, it's likely the Windows boot loader has given itself first boot priority after the update. You can install EasyUEFI in Windows to restore first boot priority to Clover - see "Add Clover as a UEFI Boot Option using the EasyUEFI Program" post#1. Thanks for the reply! Windows is installed in UEFI mode. "diskutil list" output (/dev/disk1 is my Mac SSD): /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *750.2 GB disk0 1: Windows Recovery 471.9 MB disk0s1 2: EFI NO NAME 104.9 MB disk0s2 3: Microsoft Reserved 16.8 MB disk0s3 4: Microsoft Basic Data 749.6 GB disk0s4 /dev/disk1 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *750.2 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS Sierra 749.3 GB disk1s2 3: Apple_Boot Recovery HD 650.0 MB disk1s3 /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *3.0 TB disk2 1: EFI EFI 209.7 MB disk2s1 2: Apple_HFS DATA 3.0 TB disk2s2 /dev/disk3 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *3.0 TB disk3 1: EFI EFI 209.7 MB disk3s1 2: Apple_HFS Backup Disk 3.0 TB disk3s2 3: Apple_Boot Recovery HD 650.0 MB disk3s3 /dev/disk4 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *64.2 GB disk4 1: EFI EFI 209.7 MB disk4s1 2: Apple_HFS MacRecover 63.8 GB disk4s2 So, I actually did try to manually add a UEFI boot entry earlier today using the Clover UEFI shell - It shows up in EasyUEFI as "hidden", however, and it still does't show up in my BIOS as a boot option, even after I moved it to the top in EasyUEFI. The "Hidden" thing is curious to me - I have a feeling that I mucked things up while trying to get the system up and running yesterday by issuing an "fdisk -u /dev/rdisk1" Based on some searching I've done, I think I might have to do something with gdisk to get things back to GPT, but I only have a limited amount of understanding of partition tables and boot record types, so I'm hesitant to try it without some proper guidance. On the bright side, I can boot into OS X via USB anytime I want and my sound is working fine now. Link to comment Share on other sites More sharing options...
roddie Posted October 6, 2017 Author Share Posted October 6, 2017 Sure enough, some magic with gdisk and I'm back and running - I haven't booted back in and out of Windows 10 yet (fear), but I can now boot Clover directly from my SSD and the UEFI option shows in my BIOS. I followed the instructions for "trying to change disk1 from hybrid MBR to protective MBR/full GPT" here: http://www.insanelymac.com/forum/topic/298027-guide-aio-guides-for-hackintosh/?p=2098111 I'm guessing the fdisk -u that I ran on Tuesday messed it up, but simply creating a new protective MBR using gdisk fixed it. Thanks again! Link to comment Share on other sites More sharing options...
Recommended Posts