Contribute
Register

EBIOS read error: Controller or device error Block 0x0 Sectors 0

Joined
Feb 22, 2014
Messages
2
Mac
Classic Mac
Mobile Phone
This fixed my problem (caused by USB HDD left plugged in) too. Nice! Thanks.

I had this problem when rebooting my hack with usb printer turned on.. as mentioned in other posts, card readers can be the culprit and my printer has one.. I added this to my org.chameleon.boot.plist and it solved the problem :

<key>Scan Single Drive</key>
<string>Yes</string>

This is fine if you mainly boot from one partition, may not be ideal for regular dual booters (I have no need so have no real experience sorry, maybe someone else can weigh in?). If I need to boot from an installer or other drive I use the BIOS special boot menu, in my case F12 on startup. Hope this helps, as it is irksome even though the hack will boot eventually if left alone.
 
Joined
Feb 13, 2011
Messages
14
Motherboard
3x Mac & 2x Hack
CPU
3x i5, 2x core2duo
Graphics
gtx1060, gtx1050ti, gtx750ti, 9800GT, hd3000x3, gt320, gma950
Mac
MacBook Air, Mac mini
Classic Mac
128K, 512K, Classic, Color Classic, eMac, iBook, iMac, Lisa, Performa, Portable, Power Mac
Mobile Phone
Android, iOS
I've had the same problems after flashing (gigabyte mbo) to latest bios.
and yes, I have a card reader panel installed in my desktop.

to fix this:
1. go to "bios features" -> "hard disk bbs priorities"
2. disable all boot options that points to card reader slots, leaving just your hdd.

enjoy.
 
Joined
Dec 11, 2012
Messages
8
Motherboard
Gigabyte Z97M-D3H
CPU
Core i7 4790K
Graphics
EVGA GeForce GTX 950
Mac
Classic Mac
Mobile Phone
Android
I've had the same problems after flashing (gigabyte mbo) to latest bios.
and yes, I have a card reader panel installed in my desktop.

to fix this:
1. go to "bios features" -> "hard disk bbs priorities"
2. disable all boot options that points to card reader slots, leaving just your hdd.

enjoy.
This worked like a charm for me. Thanks.
 
Joined
Oct 19, 2014
Messages
9
Motherboard
Z87X-UD7 TH
CPU
4770K @ 4.2Ghz
Graphics
GTX 650Ti, GTX 780Ti
Mac
MacBook Pro
Classic Mac
Mobile Phone
I had this problem when rebooting my hack with usb printer turned on.. as mentioned in other posts, card readers can be the culprit and my printer has one.. I added this to my org.chameleon.boot.plist and it solved the problem :

<key>Scan Single Drive</key>
<string>Yes</string>

This is fine if you mainly boot from one partition, may not be ideal for regular dual booters (I have no need so have no real experience sorry, maybe someone else can weigh in?). If I need to boot from an installer or other drive I use the BIOS special boot menu, in my case F12 on startup. Hope this helps, as it is irksome even though the hack will boot eventually if left alone.
This work perfectly for me! Thanks so much!
 
Joined
Sep 24, 2011
Messages
70
Motherboard
ASUS P9X79 PRO
CPU
i7-3930K @ 3.2 GHz
Graphics
GTX 980 TI
Mac
iMac, MacBook Pro, Mac mini, Mac Pro
Classic Mac
iBook, Performa, Power Mac, PowerBook, Quadra
Mobile Phone
iOS
I had this problem when rebooting my hack with usb printer turned on.. as mentioned in other posts, card readers can be the culprit and my printer has one.. I added this to my org.chameleon.boot.plist and it solved the problem :

<key>Scan Single Drive</key>
<string>Yes</string>

This is fine if you mainly boot from one partition, may not be ideal for regular dual booters (I have no need so have no real experience sorry, maybe someone else can weigh in?). If I need to boot from an installer or other drive I use the BIOS special boot menu, in my case F12 on startup. Hope this helps, as it is irksome even though the hack will boot eventually if left alone.
Adding the boot.plist string to the top of my file made the read error go away for me. Tried disabling all possible boot options in my Asus BIOS setup, but the string was the only thing that finally worked. I've been seeing this error for years on my hackintosh and didn't notice any problems with my machine, so it was a low priority fix. Finally found a solution, nice to not see this error anymore. Thanks so much!
 
Joined
Jun 9, 2012
Messages
4
Motherboard
Ggabyte
CPU
Core 2 DUO 3G
Graphics
GT 9500
Mac
MacBook
Classic Mac
Mobile Phone
I have the same problem but suspect the old Kingston SSD drive am using for Boot.
 
Joined
Mar 2, 2011
Messages
7
Motherboard
10.6.8
CPU
Core i5
Graphics
Nvidia
Mac
iMac
Classic Mac
Mobile Phone
iOS
For anyone who has still not managed to solve an EBIOS read error, you might like to read through what happened to me (sorry for the long post but the extra info might be helpful).

I have 4 internal hard drives: 1 is my main Mac OS, 1 Win 7 (almost never used hehe), 1 emergency startup drive and 1 Time machine. The Time machine back up drive went bad a few months back so I got a new one. When I put in the new one, it worked a couple of days and went kaput so I took it back and got a replacement. That seemed to work okay for a few weeks then it started disappearing from the desktop. When I restarted the machine, it reappeared. Until a week ago when it just wouldn't come back on. Last week, my cat dislodged the cables from the computer. Normally, a power outage wouldn't present any problems but my Mac OS wouldn't boot. When I booted from my emergency startup drive, I tried to repair the main disk but it refused to unmount. I tried to restart my emergency start drive in safe mode and then I couldn't get past the Apple logo. Things were clearly weird. I used my old USB to boot but I was having trouble everywhere.

After reading through this thread, I realised that the problem was probably SCSI-related but I couldn't work out how to prove it. I couldn't believe that all the disks had gone bad at the same time – that would be too much of a coincidence. After watching a YouTube video on how to rip apart an old external back up drive that I had (that had gone down years ago) I managed to insert one of the drives and repair it fine but when I put it back inside the machine, it wouldn't boot properly. That's when I got the idea that it might be the power supply. I had ruled this out previously because it booted into Win 7 fine every time. But anyway, I bought a new one as the old one had been working continuously for nearly 4 years (and was starting to sound pretty loud). Finally, after much shifting around, everything is hunky dory and all is working perfectly as before so if you are still having problems with the EBIOS error, try to check your power supply – just because it's working, it doesn't mean that it's working perfectly.

Thanks to all the posters here for putting me on the right track.
 
Top