Clover stuck at "scan entries"

Hi everyone!
A few weeks ago a upgraded to El Captian and clover from Mavericks.
Up until yesterday everything worked great. However now I am unable to boot OS X. It is stuck on "scan entries". I also tried to boot from the USB drive, however the same problem occurs. I did some research and found that sometimes faulty raid 0 drives can confuse clover. I tried some more things, and unplugging one of the raid 0 hard drives enables clover to boot. However, then I can't access the data on my RAID setup.

I did however find a way to do it, but it is hardly user friendly. What i did was enable "hot swap" in the BIOS, disconnect the data cable before booting to clover, after clover has successfully scanned i reconnect the hard drive and then select boot from my OSX SSD. This works, and the RAID drive show up in OSX, so I do not think anything is wrong with my drives. Disk Utility did not report any errors. So something must have happened, and I have no idea what. Below is a picture showing all partitions from the internal hard drives.



Computer info:
OS X installed on a 128 GB SSD
Windows installed on a 1 TB HDD
Two 3 TB HDD creating a 5TB raid 0 volume.
Each 3 TB drive also have one volume at around 400 GB.

Hopefully someone might know whats going on.

Sincerely Henrik

Funny. I have installed El Cap for the first time on my main edit machine today.
Previously working fine under Yosemite.

Everything with my combination of hardware is fine until I add my 3x HDD RAID 0 into the mix, when I do the machine gets stuck on a 'Welcome to Clover 3320 .....scan entries... message.

Luckily I have another mirrored external hardware RAID0 so I could delete this RAID Array and make another in El Cap, but I'd like to know how to fix it if I can.

UPDATE. I've found a thread where there's a possible fix, but I don't really understand the exact config file coding that he's done: http://www.tonymacx86.com/bootloade...g-scanning-entries-because-software-raid.html

I've gone as far as mounting my EFI partition and opening the config file in Text Edit. But I don't really want to change anything in case I kill the installation and have to start again.

There's a lot of people with this issues when I search this site, and even though it might be considered a low priority issue it's still going to be a real problem for anyone hoping to use using a software RAID in Clover.

http://sourceforge.net/p/cloverefiboot/tickets/113/

Great info you found there!
Yeah, I have a Time Machine backup of the contents of the raid so loosing the data is not that much of an issue. It is just not that fun to transfer close to 5 TB of data, even with a wired connection

I will do some testing with it tomorrow, I have a USB installed with Clover so it makes testing thing a lot easier (and safer) as you don't have to use your config file stored on your SSD or HDD.

It does indeed seem to be a quite common issue, hopefully this works.

Sincerely Henrik

Hi Henrik.

I'm used to Hackintoshes working with very little trouble, so this Clover tweaking is a bit dull.

I'm planning to use the Clover Configurator app, not sure if that'll let me adjust the config file on my USB stick... I can always go back to my Yosemite SSD if I have to, but I guess we have to learn to work with Clover from here on.

Here's another useful resource: http://clover-wiki.zetam.org/configuration/gui#gui_hide

Success!
I tried using Clover Configurator, but couldn't get it working.
So in the end I put the following into the config file:

<dict>
<key>AddArguments</key>
<string>root=UUID=2CE65124-93A0-3BCF-81E6-3290A83976FF</string>
<key>Disabled</key>
<false/>
<key>FullTitle</key>
<string>El Capitan</string>
<key>Hidden</key>
<false/>
<key>Ignore</key>
<false/>
<key>NoCaches</key>
<false/>
<key>Type</key>
<string>OSX</string>
<key>Volume</key>
<string>El Capitan</string>
</dict>

As I'd already been tinkering with Clover Configurator it had already put some new data at the right spot in the config file so I knew where it needed to go, and that the syntax spacing (or whatever it's called) was correct.

My main SSD install was called El Capitan, so I added that in relevant positions, but I got the UUID from the OSX system profiler.

I was adjusting the config on the main SSD EFI partition. So I could boot into my USB stick to tinker with the SSD rather than ruin the USB installer/boot setup.

Nice to hear!
Haven't had time to work on my hackintosh, but good that we have a solution!

Sincerely Henrik

is the uuid used the one for your boot drive?

where did you inject that bit of code in your plist file?