Recent content by Adam1203

I wish there was a betting pool.

In all seriousness, I would put money on macOS Mojave

macOS San Andreas

Try selecting your USB drive using the BIOS boot options (usually F12).

Yes. My mistake. I’ll update it.

Obviously, I'm not responsible for any data loss or issues with booting your hack. Perform the following while in your Fusion Drive: - Download Carbon Copy Cloner (CCC) - Clone your current Fusion Drive to an external HDD - Copy all of your system required KEXTs from your Fusion Drive's...

I'm willing to bet that's your problem, as it was mine. I have disk0s1 with my EFI/Clover, and had disk0s3 as BOOT OS X. That caused the updater to freak out on reboot. Once I redid it and had the Recover HD on disk0s3, I haven't had a problem.

I had the same issue, even after updating Clover. It turned out that the issue was due to my boot EFI and Recovery HD being on separate physical drives. I had to backup my Fusion Drive (with Carbon Copy Cloner), blow away the CoreStorage volume and redo it. This time I put the Recovery HD on my...

Handoff doesn't work correctly with the BCM94352Z. Airdrop does though.

I had some big issues during the update. I ended up redoing my Fusion drive. This time, I put the Recovery HD on the SSD, which is also my EFI boot drive. This seems to have fixed the issue where Clover was still trying to boot to the "wrong" drive during the update. Also make sure you have a...

If I remember correctly, handoff does not work properly with the BCM94352Z, unless something has changed recently.

This worked perfectly! I'm going to try to script some of this, so we can maybe run it from the terminal. Thank you for the guide!

So with all of this info, do you guys think this is a clover issue, or an issue with the way macOS performs its updates/installs on Fusion drives?

I've setup a Fusion drive in my macOS VMWare VM. I'm going to test this now and will update to see if this will successfully work during the initial installation. :)

I'm in the same boat. I'm just waiting until the HS update comes out that support APFS on Fusion Drives. I tried doing the install, but got the same error as the OP. I was able to fix it by doing a reinstall of Sierra.