mrjayviper Posted June 4, 2018 Share Posted June 4, 2018 during installation, I opened up disk utility to: 1. format my single SSD to HFS+ 2. create an array using 4x 1TB drive (striped) Installer then copied the files into the SSD and rebooting. Clover cannot get to the disk selection screen. I've tried this process several times and it always boot loops at this point. As a test, I zeroed out the 4x HDDs (sudo dd if=/dev/zero of=/dev/sdX bs=1M count=100) using a Linux USB installer and I was able to get to the disk selection screen again. some info: 1. I'm using clover 4509 2. the 4x 1TB used to be a Windows10 striped software array and Clover had no issues with those. 3. if I insert a bootable USB (Windows or Linux or a OSX+clover for example) into any of the Intel USB2 slots, the motherboard will boot from it automatically. I've set on the bios (or is it UEFI?) to automatically add bootable USB into the boot options. 4. When I installed clover into my USB installer, I installed all drivers64 and drivers64UEFI drivers. Any suggestion on how to fix this? Thanks! Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted June 4, 2018 Administrators Share Posted June 4, 2018 if the os on theSSD was installed with APFS file system you have to add that to your clover drivers folder. 1 Link to comment Share on other sites More sharing options...
mrjayviper Posted June 5, 2018 Author Share Posted June 5, 2018 " add that to your clover drivers folder" I assumed when you said "that", you meant apfs.efi? If yes then I already have apfs.inside drivers64 and drivers64UEFI. But it shouldn't matter in my situation since I formatted the SSD as HFS+ (in original post). --------------- As a test last night, I again wiped the partition table of the HDDs used in the array using a Linux USB installer (sudo dd if=/dev/zero of=/dev/sdX bs=1M count=100) and clover started working again. I can also see the SSD and it's one of the bootable options (installation not finished yet). Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted June 5, 2018 Administrators Share Posted June 5, 2018 maybe the installer made a corestorage partition which did not allow for the hdd to be seen. Link to comment Share on other sites More sharing options...
Recommended Posts