Contribute
Register

EBIOS read error: Device Timeout

Status
Not open for further replies.
Joined
Dec 28, 2010
Messages
71
Motherboard
Asus Sabertooth x79
CPU
i7 3930k OC 4.5GHZ
Graphics
Nvidia GTX 680 4GB
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Hey Guys,

This forum helped me a lot throughout my entire hackintosh experience and I gave back as much as I could with tutorials etc.

My Hackintosh was working like a charm during the last year. I was working on some very important projects when suddenly I had a Kernel Panic (Nothing new, I got some in the past year and I just did a restart) but this time after I did the restart I got the following error message: "EBIOS read error: Device Timeout" Block 0x****** etc.

Now just so you know I have an Asus P6T se with 6 Harddrives connected. I searched the entire internet but the only solutions were unplug external drives or usb, set to ahci etc but I did ALL those things. Booted with every parameter possible but I still get the error. I am really afraid that my harddrives are damaged because Windows boots normally and all the drives (except the boot drive with mac os x on it) shows that they're damaged. But it can't be! I have all my work on there (3 Harddrives with backups, all corrupt??)

Can anyone help me?

Thanks
Dave
 
If you have a DVD/CD-RW, try disconnecting it. Or remove it from the device boot list in BIOS.
 
Hey Guys,

This forum helped me a lot throughout my entire hackintosh experience and I gave back as much as I could with tutorials etc.

My Hackintosh was working like a charm during the last year. I was working on some very important projects when suddenly I had a Kernel Panic (Nothing new, I got some in the past year and I just did a restart) but this time after I did the restart I got the following error message: "EBIOS read error: Device Timeout" Block 0x****** etc.

Now just so you know I have an Asus P6T se with 6 Harddrives connected. I searched the entire internet but the only solutions were unplug external drives or usb, set to ahci etc but I did ALL those things. Booted with every parameter possible but I still get the error. I am really afraid that my harddrives are damaged because Windows boots normally and all the drives (except the boot drive with mac os x on it) shows that they're damaged. But it can't be! I have all my work on there (3 Harddrives with backups, all corrupt??)

Can anyone help me?

Thanks
Dave


DaveVegas

You may want to try the RBoot 1.2 from the downloads section and make a cd of that -
You should be able to boot up from that cd and be into a single user kernel -

On the screen you should see some text - I used to know it but I have CRS ( Cant Remember stuff)

On the screen you will be given some command prompts to enter to make the drive write enable - the default is read only
Also you should see the command to run a fschk - file system check - this should be run in read 1st then if it tells you you have errors do it in
write mode - you will have to enable that w a command.
Then run the command to do the fsck again on the boot drive - and see if you get errors - if so it will state what they are - in kriptic code no less - and then ask if you want to correct it - of course you do.

Run the fsck untill you come up clean - no errors - then do a reboot or shutdown command from the prompt ( not sure which) and see it this fix's you problem
 
DaveVegas

You may want to try the RBoot 1.2 from the downloads section and make a cd of that -
You should be able to boot up from that cd and be into a single user kernel -

On the screen you should see some text - I used to know it but I have CRS ( Cant Remember stuff)

On the screen you will be given some command prompts to enter to make the drive write enable - the default is read only
Also you should see the command to run a fschk - file system check - this should be run in read 1st then if it tells you you have errors do it in
write mode - you will have to enable that w a command.
Then run the command to do the fsck again on the boot drive - and see if you get errors - if so it will state what they are - in kriptic code no less - and then ask if you want to correct it - of course you do.

Run the fsck untill you come up clean - no errors - then do a reboot or shutdown command from the prompt ( not sure which) and see it this fix's you problem

Did this work? I have the same problem with one out of 5 drives I have.
 
I had a similar failure. My system had been up & running for more than a year w/o significant problems, when I suddenly got "EBIOS Read Error: Device Timeout" during a reboot. The system froze up on me. I restarted with a Lion rescue USB and got a little further, but it still locked up with the same error message. So I disconnected two external disk drives and repeated the process, and this time got the system started. Repaired permissions on the system disk and rebooted successfully again. Then reattached one external drive, which spun up fine, and rebooted -- all okay. Same with the 2nd external drive, except the reboot failed. I unplugged that one, booted the system, reattached it and used Disk Util Repair Disk. Then rebooted successfully. Not sure what the problem was, but I replaced that drive and have had no problems since.

Good luck.
 
I had a similar failure. My system had been up & running for more than a year w/o significant problems, when I suddenly got "EBIOS Read Error: Device Timeout" during a reboot. The system froze up on me. I restarted with a Lion rescue USB and got a little further, but it still locked up with the same error message. So I disconnected two external disk drives and repeated the process, and this time got the system started. Repaired permissions on the system disk and rebooted successfully again. Then reattached one external drive, which spun up fine, and rebooted -- all okay. Same with the 2nd external drive, except the reboot failed. I unplugged that one, booted the system, reattached it and used Disk Util Repair Disk. Then rebooted successfully. Not sure what the problem was, but I replaced that drive and have had no problems since.

Good luck.

kcannon...

Good to know ... random halts like this are a real bummer !!!!

I found this link which has similar information to what you said - but make a good read as it discovers issues w Partition Maps on HD that have gone south -
http://forum.voodooprojects.org/index.php?topic=760.0

Again it down to removing SATA cables - reboot - retest till you can get into the MAC OSX -
Also dont just think its only your Hack drives - this can be cause by NTFS volumes as well - even if its not the Windows boot disk.
 
EBIOS read error: Device Timeout [Solved]

Hello everyone,
I was also suffering from the "EBIOS read error: Device Timeout".
Finally I solved this

I had this problem due to 2 hard drives. One hard drive is for Operating Systems and another for personal datas. I used to boot either WINDOWS 7 or MAC OS only after the 4-6 minutes of waiting due to this error. As I know, this problem is due to the bad partition of hard disk.

So after the 8 nights,
I changed the following AHCI PORT SETTING.
I JUST DISABLED (Not Installed) the Hard Drive, which contain my personal files

Now I can run Windows 7/ Mac OS without waiting of EBIOS Error.
 
Hello everyone,
I was also suffering from the "EBIOS read error: Device Timeout".
Finally I solved this

I had this problem due to 2 hard drives. One hard drive is for Operating Systems and another for personal datas. I used to boot either WINDOWS 7 or MAC OS only after the 4-6 minutes of waiting due to this error. As I know, this problem is due to the bad partition of hard disk.

So after the 8 nights,
I changed the following AHCI PORT SETTING.
I JUST DISABLED (Not Installed) the Hard Drive, which contain my personal files

Now I can run Windows 7/ Mac OS without waiting of EBIOS Error.

dipenchand

If your hard drive has more that two partitions and the offending partition causing the timeout error which it appears to be - their are some Stand alone Linux distro that will check a NTFS partition and fix the issues. As for the HFS volume you could use iBoot and the Apple DVD - select disk utilities and rucn a check on that volume an well as fix permisions
 
I ran into this problem and it turns out my issue was I had the install dvd in the secondary cdrom drive instead of the primary. Once I put the DVD in the first drive, the issue went away.
 
Status
Not open for further replies.
Back
Top