Jump to content

CloverEFI BiosBlockIO rev>4077 hangs at "Scanning entries"


romaincs
 Share

17 posts in this topic

Recommended Posts

Hello everyone,

 

 

I have an issue with the lastest clover revision that I did not had with rev. 4077 using BiosBlockIO.

Clover hangs at "Scanning entries...". To be able to boot, I must install without using BiosBlockIO but Sata instead.

 

I'd like to use BiosBlockIO as I have RocketRaid 2720SGL that is faster than my Rampage 3 Extreme ICH10 controller (the same is true with Marvell controller) and is only bootable with this option.

 

If I revert back to rev 4077, it does not hang...

 

 

Is anyone having an idea about this issue ?

 

Thanks

Link to comment
Share on other sites

Thanks for you answer chris1111 !

 

I looked at it, but sadly it won't help as the issue is before the loading of the OS... :(

 

I can't get to the Clover GUI as it hang at scanning entries if I install clover with BiosBlockIO boot file.

Link to comment
Share on other sites

Thanks for you answer chris1111 !

 

I looked at it, but sadly it won't help as the issue is before the loading of the OS... :(

 

I can't get to the Clover GUI as it hang at scanning entries if I install clover with BiosBlockIO boot file.

and without BlockIO ? Only Boot64 +boo0af

Link to comment
Share on other sites

With CloverEFI 64-bits BiosBlockIO + boot0af -> Hang at Scanning entries.

With CloverEFI 64-bits SATA + boot0af -> I get to clover GUI but my RocketRaid controller is not bootable, it would be bootable with BiosBlockIO (as I did before Clover rev. > 4077).

Link to comment
Share on other sites

Thanks for you input smolderas !

 

Is that option makes boot on first sata port ? If it is, it won't solve my problem.

 

I have to get clover looking at Bios boot entries, not SATA ones. It is the only way I'm aware of to keep raid features and boot from the RocketRaid board. :(

Link to comment
Share on other sites

@romaincs,

 

Maybe a toolchain/compilation or edk2 problem.  

 

You can try replacing your "boot" file with the attached Clover r4293 boot7 compiled with GCC53 in Linux (vs boot7 compiled with XCODE5 toolchain).

 

Worst case scenario:  keep your Clover "boot"/boot7 file from r4077 and only manually update CLOVERX64.efi and BOOTX64.efi.

boot7_GCC53.zip

boot7_XCODE5.zip

Link to comment
Share on other sites

So, no luck with this... It is a bit strange...

 

I decided to open my box, and unplugged all drives on the SAS controller, and it does not hang anymore...

 

If I only plug my system drive back, it does not hang too.

 

I'm digging into this...

 

Another strange issue, may be related, is about USB keyboard in CloverGUI: If I plug my optical sata devices onto my ICH10, keyboard won't work... If I plug them on Marvell controller, the keyboard works..

 

May be I should play flashing my bios... Any recommanded version for R3E and Clover ?

 

It start to drive nuts :rofl:

Edited by romaincs
Link to comment
Share on other sites

As soon as I plug a second HDD/SSD on the SAS, clover hang at ".... scan entries ...".

 

If I leave only OSX SSD, it works fine...

 

Again, it used to work with rev 4077 and don't with higher rev's.

 

as the boot files does not resolve this, even the 4077 one, it must be on the efi files side... or may be apfs.efi ?...

Link to comment
Share on other sites

Thanks UcaUca, I do not have UEFI on my board, but I gave it a try and.... nope... :(

 

Is there a way to get a log to know what happened before "....scan entries..." ? It could bring some light on what the issue is...

Link to comment
Share on other sites

Ok no problem. Than the solution could be easy. Try what I explained in the video. This way you disable Scanning entries entirely, but you have to tell clover by a custom entry, what drive to boot from. In the big list with the UUID, obviously you'll have to choose your boot partition (I wasn't sure thats why I was hibernating there :D)

 

For Users experiencing similar issue: This workaround does not necessarily work in conjunction with VBoxHfs-64.efi. In that case, its easier to switch to HFSPlus.efi which doesn't require the workaround at all. 

 

​Clover in general doesn't like RAIDs that much. Its not about using them as boot drives, more about passing them during boot process.

 

EDIT: A wait, you mean, you want to boot from that Rocket card? Hm... than this workaround might not work for you as its intention is to make clover not SEE it. Or... Are you booting of a RAID or a single drive? If it is a single drive, you should give it a try.

SkipScanEntries.mp4.zip

Link to comment
Share on other sites

It is a single drive (SSD) on the SAS controller. If I leave only this drive on the controller, it won't hang. But if I plug a drive, even single drive (not a raid array) it hang again...

 

I will make a clone of my boot drive to play in depth with it without breaking all my stuff.

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
 Share

×
×
  • Create New...