Contribute
Register

Booting Clover drive hangs at "scan entries"

Status
Not open for further replies.
Joined
May 14, 2012
Messages
5
Motherboard
Gigabyte Z77x-UP5-TH
CPU
Intel Core i7 3770k
Graphics
Intel HD 4000 Graphics
Mac
  1. MacBook Pro
Classic Mac
  1. 0
Mobile Phone
  1. Android
Hey guys,

I've been trying to update to El Capitan with UniBeast. Upon booting the drive, I get this:


Welcome to Clover 3270
******* scan entries ***

I've been letting it sit for a while now and nothing has changed. Any ideas?

Had Ozmosis installed previously, which worked great for the most part. Previous to that, I've always had some sort of issue. My Oz setup was the only one that worked well enough to use. I have obviously installed a stock BIOS prior to attempting this install. I can provide any information you need, just ask :)
 
For those who are still stuck, or if the problem appeared suddenly on a perfectly working setup, I had the same problem, but after a while I could identify the culprit in my case : my shared Exfat partition !

I use one internal storage HDD to share between Yosemite and Windows 10, and it keeps getting corrupted. I often have to use disk repair ( doing it from OSX or Windows works the same ) to be able to mount it again on either OS, without boot problems, so I don't really get what was different this time.

The other strange thing is that my older Clover on my install USB could boot internal OSX without being disturbed by the corrupted partition, so from there I could repair it and voilà ! everything is back on track.


If anybody has a hint on why the partition would sometimes get corrupted enough to disturb the boot, i'd be glad to know.

Is there a way to configure Clover to ignore that partition, or even the whole disk ?

Thanks folks.
 
If anybody has a hint on why the partition would sometimes get corrupted enough to disturb the boot, i'd be glad to know

exFAT (Extended File Allocation Table) is a Microsoft file system optimized for flash drives.
It has very little resilience and the slightest error can lead to corruption / loss of data.
Sharing exFAT portions between different operating systems increases the risk of corruption.
 
I have the same issue only when I have a USB stick connected. My USB stick is FAT32, so I don't understand why clover has issues scanning my stick. If I disconnect my USB stick, clover will boot without any problem. I have three hard drives and an external hdd on usb 2 and I use windows 10, el capitan and 3 linux flavors on different partitions without any issue. Clovers stucks only when a USB stick is connected... :crazy:
 
Is there a way to configure Clover to ignore that partition, or even the whole disk ?

Thanks folks.

got that same thought. would be nice to know how. got a 3x500 gb ssd raid (raid0) called edit disk. in windows 10 i use macdrive 10 pro to acces the hfs+ raid. today i was tranferring alot of files away from the edit disk while beeing in windows and then when rebooting i met the clover boot 'scan entries' ****. i dont even think there is a corruption on my edit disk, i think its just because clover can smell that an alien O.S has got its dirty hands on the data recently... now i can only boot by disabling those 3 sata ports. i did Update to capitan few days ago. before in yose there was no problem when accessing hfs+ from windows for 1 year.
 
hello, i have the same problem, is there a workaround to solve this?
 
This same problem suddenly developed on my system, shortly after I installed an Oculus Rift, though that is probably a coincidence. I solved it by disabling my Windows boot drive in the bios. Strangely that drive still appears when clover scans for drives, and I can boot both Win10 and Sierra 10.12.6 with no problem ... I can't understand it, but maybe the same thing will work for someone else.
 
same problem here...
 
Status
Not open for further replies.
Back
Top