Driver Detected A Controller Error On Device Harddisk0 Vmware
Contents |
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search
The Device Is Not Ready For Access Yet Vmware
Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website
The Driver Detected A Controller Error On \device\harddisk0
Testing Store Headlines Experts Exchange > Questions > The driver detected a controller error on \Device\Harddisk0. Want to Advertise Here? Solved The event id 15 disk not ready for access driver detected a controller error on \Device\Harddisk0. Posted on 2011-03-29 VMware Virtualization Windows Server 2003 1 Verified Solution 13 Comments 4,429 Views Last Modified: 2012-05-11 Hi I have an ESXI server with 3 virtual host on it... https://kb.vmware.com/kb/1005204%20 1 host gives a lot of errors in the event viewer mentioning the following: Error; event ID:11, The driver detected a controller error on \Device\Harddisk0. in combination with that error i get Error; Event ID: 15, The device, \Device\Scsi\symmpi1, is not ready for access yet. This error gets thrown a lot a lot of times within a minute (like 100 errors within a minute), and then the errors stop. This happens 1 time a https://www.experts-exchange.com/questions/26918549/The-driver-detected-a-controller-error-on-Device-Harddisk0.html day... My other virtual servers don't throw errors like this, so it can't be an hardware failure i think... VMwaretools is installed succesfully on this server and is up to date. What could be the reason and how can i prevent this errors from be thrown... thanks in advance kind regards 0 Question by:techneitsolutions Facebook Twitter LinkedIn Google LVL 51 Active 4 days ago Best Solution byNetman66 The Host with the Harddisk error is suggesting you may have a local drive going bad. The timeout thing could be as simple as requiring a new driver or perhaps a firmware update. Go to Solution 13 Comments LVL 16 Overall: Level 16 Windows Server 2003 5 VMware 1 Message Expert Comment by:btassure2011-03-29 Sounds like bus timeouts. What is your datastore architecture? What kind of disks are you using for storage? 0 LVL 51 Overall: Level 51 Windows Server 2003 42 VMware 4 Virtualization 2 Message Active 4 days ago Accepted Solution by:Netman662011-03-29 The Host with the Harddisk error is suggesting you may have a local drive going bad. The timeout thing could be as simple as requiring a new driver or perhaps a firmware update. 0 Message Author Comment by:techneitsolutions2011-03-29 Hi @btassure: my datastore contains of a RAID 5 Configuration with 3 HP 146GB 6G SAS 15K rpm SFF (
ordeal with this Event 11 that Windows quietly generates. It took us few weeks to fully work out why Windows suddenly started hanging, misbehaving or even crashing with blue screen. Now that I feel http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ it is fully resolved, I thought I’d share my conclusion (and the process) – hopefully it will help few others out there who are struggling with this. Ridiculously, many people are likely affected by this issue, but unless they open Event Viewer and search for this event id 11, they will not realize that hanging is not “normal” behavior, even for Windows! OS seems to silently recover from this problem 10 to 60 seconds driver detected later, which is really strange in my book – considering that user isn’t even alerted to this serious atapi error. For impatient souls among us, here are my conclusions: First thing – check the SATA/EIDE and power cable connection between your hard-drive and the motherboard. If possible, try another SATA outlet on motherboard or another SATA cable if available. If it still happens, the bad news is that this is likely a disk driver detected a controller error, which is especially problematic since nowadays disk controllers are built into the Motherboard. If you are in a budget crunch, one potential workaround is to slow down your HD to use different PIO. This may avoid hangs, but will slow overall performance, so no fun solution… Proper solution appears to be to replace motherboard, hence replacing disk controller. There are many motherboards starting at just $50 and in most cases it will improve overall performance and stability for you, even if you keep the same CPU and other components. I am pretty confident that this is the right diagnosis, as we went through a lot of trial and error investigative work, in a space of few weeks, after it started abruptly. At first, I was pretty much convinced that HD is dying. The system had two hard-drives, and the older hard-drive was seemingly working just fine, even with the same SATA cable and connected to the same slot on the Motherboard. Turns out it was using slower PIO by virtue of it being older HDD. During the troubleshooting process I reinstalled fresh Windows 7 64 Bit multiple times, on various HD drives, only to see the issue start happening almost instantly after clean install. Few days ago a fresh HDD became available (separate long story), so