Just a heads up, the latest Public Beta of Sierra breaks all EFI mounting scripts, including CLOVER's own installer. CLOVER therefore installs to the OS drive under /EFI/, and not on the ESP regardless if you choose "Install to ESP".
Apparently Sierra now creates a dedicated logical volume that seems to symlink to the OS drive. In my case my OS disk is /dev/disk0, and therefore the logical volume is /dev/disk1. So, when any of the EFI mounting scripts from the repo or from CLOVER attempt to mount the EFI using the root directory as a base, it will fail as there is no EFI partition on the logical volume. I have therefore had to modify all the scripts on my local stash to point to /dev/disk0 directly instead of using the main OS drive's root directory as a base, and it allows me to mount my EFI and install if necessary.
This though does not fix CLOVER as its installer tries to mount from the OS partition's root directory forcefully and doesn't even attempt to look that EFI is already mounted. I haven't attempted it but copying the contents of the /EFI directory directly to the ESP could possibly work, but not willing to test this out atm.
*ADDENDUM*
I have found that there is a simpler way of fixing this. If you run into problems mounting your EFI partition you can check to see if you have a logical volume (CoreStorage) running and revert it back, by running these two commands under Terminal:
- diskutil cs list
- diskutil coreStorage revert lvUUID
(lvUUID would be the last logical volume id string reported by the Terminal command above)
Process of reverting the CoreStorage mounting and reverting it was found
here.
