- Joined
- Jan 6, 2015
- Messages
- 99
- Motherboard
- Gigabyte GA-z97x-UD3H
- CPU
- i5-4590
- Graphics
- RX 580
- Mac
- Classic Mac
- Mobile Phone
I've been having serious problems with my system, which was running fine, but then became completely unbootable. After much research and countless reboots, I've decided the problem was, and is, a corruption (or something) of Clover.
I've now got back to the stage where I can boot the system from a freshly made Sierra Unibeast USB stick. I could now try to reinstall the OS, or do a clean install onto my SSD. However, I'm certain that I need to delete the existing Clover installation, remove it completely and do a fresh install.
That sounds like it should be easy: mount the EFI partition, delete the relevant folder, and then maybe replace it with one that you know works. The thing is, I already tried that once and not only did it send me back into a spiral of an unbootable system, it also messed up my working Unibeast stick (hence the need for a fresh one).
Is there a correct way of removing Clover from an SSD / hard drive and doing a clean install of Clover?
And does that require a clean install of the OS as well? Or might I get away with a reinstall of the OS?
Sorry if this isn't the correct forum, but I couldn't find where else to raise this question.
background: I think the reason for the problems with Clover has been my attempts to duplicate a working config file and then rename it. To me, that should work. But it seems to create chaos and confusion within the whole boot regime.
I've now got back to the stage where I can boot the system from a freshly made Sierra Unibeast USB stick. I could now try to reinstall the OS, or do a clean install onto my SSD. However, I'm certain that I need to delete the existing Clover installation, remove it completely and do a fresh install.
That sounds like it should be easy: mount the EFI partition, delete the relevant folder, and then maybe replace it with one that you know works. The thing is, I already tried that once and not only did it send me back into a spiral of an unbootable system, it also messed up my working Unibeast stick (hence the need for a fresh one).
Is there a correct way of removing Clover from an SSD / hard drive and doing a clean install of Clover?
And does that require a clean install of the OS as well? Or might I get away with a reinstall of the OS?
Sorry if this isn't the correct forum, but I couldn't find where else to raise this question.
background: I think the reason for the problems with Clover has been my attempts to duplicate a working config file and then rename it. To me, that should work. But it seems to create chaos and confusion within the whole boot regime.