Driver Detected Controller Error Device Harddisk1 Vmware
Contents |
Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Microsoft 491162 Followers Follow Microsoft Windows Server Microsoft Windows Server 2012 Join the Community! Creating your the driver detected a controller error on device harddisk1 dr9 account only takes a few minutes. Join Now Am seeing the following in my the driver detected a controller error on device harddisk1 dr1. usb 2008R2 Event Viewer: * Event Time: 19 Feb 2013 02:42:19 AM * Source: Disk * Event Log: System * Type: Error
The Driver Detected A Controller Error On Device Harddisk1 Dr11
* Event ID: 11 * Event User: N/A * The driver detected a controller error on \Device\Harddisk2\DR2. On this server I have internal RAID volumes, an external iSCSI drive (DroboPro), and several USB 2.0 https://kb.vmware.com/kb/1005204%20 hard drives attached. How can I determine what hard drive / storage device is "\Device\Harddisk2\DR2"? Thanks in advance for any feedback. Cheers, Derek Reply Subscribe RELATED TOPICS: Driver detected a controller error The driver detected a controller error on \Device\Harddisk1\DR1. system Error   1 2 Next ► 28 Replies Cayenne OP murpheous Feb 19, 2013 at 2:42 UTC click start, right click computer and select manage. Expand storage https://community.spiceworks.com/topic/304581-driver-detected-a-controller-error-which-hdd-is-device-harddisk2-dr2 on the left and select disk management. That should tell you. 1 Sonora OP derektom Feb 19, 2013 at 2:56 UTC Thanks for your reply. That's the first place I looked but I'm unsure how to correlate Harddisk2\DR2 to any of those drives. Is "DR2" = "Disk 2"? Attached is a screenshot for reference. Thanks again. 0 Mace OP Rockn Feb 19, 2013 at 3:36 UTC Does diskpart give you more detailed info? 0 Mace OP LarryG. Feb 19, 2013 at 4:05 UTC Do you have any Management software installed for the RAID? That would have it's own logging and hopefully diagnostics too. 0 Jalapeno OP supasieu Feb 19, 2013 at 4:36 UTC Try this link: http://support.microsoft.com/kb/244780/en-us
0 Sonora OP derektom Feb 20, 2013 at 1:13 UTC Thanks for the feedback, Rockn, LarryG., and Fishsauce. diskpart didn't give me any helpful info beyond what the Disk Management console had already provided. I have HP RAID management software but it didn't really help either since I have so many other hard drives (USB, iSCSI) that are not on the internal RAID. Following a link off of the link Fishsauce provided (below), it does seordeal 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 it is fully resolved, I thought I’d share my http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ conclusion (and the process) – hopefully it will help few others out there who are struggling with http://backupchain.com/i/all-fixes-for-the-driver-detected-a-controller-error-on-deviceharddisk2dr2 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 later, which is really strange in my book – considering that user isn’t even alerted to this serious driver detected 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 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 driver detected a 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 I tried replacing the “dying” HD. Guess what, it being newer HD, it was instantly affected by the same issue, even though I put clean Windows there also. Thus it was concluded that controller was faulty, and I went shopping for a new motherboard. As an aside – DDR3 memory is Ridiculously Cheap. I was
Viewer as: The driver detected a controller error on \Device\Harddisk2\DR2. or: The driver detected a controller error on \device\ide\ideport1 Disk Issues and Defects The first thing to be concerned about is a disk defect, especially if the system hardware or drive configuration hasn't been changed lately. Before you head off and test the drive, it's a much better idea to back it up. The reason is simple, the drive may only have a couple minutes to live and running an elaborate deep scan on it will stress it quite a bit. Many times hard drives fail completely when put under high load, such as a whole image backup or a bad sector check. If you can copy and paste your most important data first, that would probably be best. RAID Issues In recent years the error "The driver detected a controller error on \Device\Harddisk2\DR2″ is covering up a severe disk defect within RAID systems on some servers. It's quite peculiar because the RAID utility that ships with the RAID controller fails to realize a disk is bad until the disk generally fails completely. We have had dozens of customers report this issue even on brand new servers! Hence, run a disk check after backing up your data: Running a Disk Bad Sector Check After backing up at least the most important files to another set of disks, use the command prompt as administrator and run: CHKDSK