we have to go through the whole process again to save things potentially. That's unfortunate, because it means if that one drive- or its EFI partition- gets hosed, whether by natural causes, or by tinkering with the EFI/Clover itself. Other drives with bootloaders installed results in the issue. If I'm understanding this right- I've since read a huge thing on UEFI- what this means is that we should really have only a single drive with bootloaders in the EFI partition of that drive. It's unfortunate there isn't a GUI right inside Clover itself that lets us instruct Clover to not add this stuff automatically. Now my computer is happy and stable again! Since my M.2 drive was not showing at all, I removed everything using the method described above, rebooted, and here was the result:

I went to work, after the first attempt to remove the extra entries in the BIOS (UEFI 238475MB is NOT a real hard disk), here was the result: I removed the Samsung SSD, and since I am not using it, I also removed the 2TB drive (this drive was completely blank, but it's big and noisy and I don't need it). After a few restarts, by BIOS looked like this: None of the other drives had boot loaders installed. Both drives are nearly identical, and clones of each other with bootable clover and El Capitan.

The Samsung M.2 drive was still installed at sata5. In response to a question elsewhere, I reconnected my Samsung SSD to sata1. Building a CustoMac Hackintosh: Buyer's Guide

Clover efi mac