Driver Detected A Controller Error On Device Harddisk1 Dr3
Contents |
Follow 5147 Mentions744 Products Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS Apprenticeship Apprenticeship Passed both A+ exams and Windows exams - Networking and Windows 7. Eidsiva energi Hun skal få et system Install printer to non-domain driver detected a controller error on device harddisk1 dr1 computer Install network printer to non-domain joined computer TECHNOLOGY IN THIS DISCUSSION Microsoft 491162 Followers Follow
Driver Detected A Controller Error On Device Harddisk1 Dr2
Microsoft Windows Server Microsoft Windows Server 2012 Join the Community! Creating your account only takes a few minutes. Join Now Am seeing
The Driver Detected A Controller Error On Device Harddisk1 Dr6
the following in my 2008R2 Event Viewer: * Event Time: 19 Feb 2013 02:42:19 AM * Source: Disk * Event Log: System * Type: Error * Event ID: 11 * Event User: N/A * The driver detected a controller error
The Driver Detected A Controller Error On Device Harddisk1 D
on \Device\Harddisk2\DR2. On this server I have internal RAID volumes, an external iSCSI drive (DroboPro), and several USB 2.0 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 the driver detected a controller error on device harddisk1 dr2 windows 7 click start, right click computer and select manage. Expand storage 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 seem to validate that the disk in question is "Disk 2" that in Disk Management shows is an external 2TB USB Seagate GoFlexhere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings the driver detected a controller error on device harddisk1 dr9 and policies of this site About Us Learn more about Stack Overflow the the driver detected a controller error on device harddisk1 dr1. usb company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges the driver detected a controller error on device harddisk1 dr11 Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: https://community.spiceworks.com/topic/304581-driver-detected-a-controller-error-which-hdd-is-device-harddisk2-dr2 Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top The driver detected a controller error on \Device\Harddisk1\DR3: which disk corresponds in Computer Management? up vote 0 down vote favorite In Windows 10 64-bit, I went to Event Viewer saw this error: The driver detected a controller error on \Device\Harddisk1\DR3 I looked http://superuser.com/questions/1082162/the-driver-detected-a-controller-error-on-device-harddisk1-dr3-which-disk-corr in Computer Management > Disk Management, but not sure which drive the error message refers to. I would run a chkdsk /r on all the drives, but this 5TB drive would take over 3 days to complete a chkdsk /r. If indeed this external caused the error message, I want to make sure. hard-drive ssd hardware-failure chkdsk external-drive share|improve this question asked May 29 at 14:35 Sun 3,42721332 It clearly says which disk it is. \Device\Harddisk 1 \DR3, so it is referring to Disk 1. –LPChip May 29 at 14:40 What is dr3 for then? So it is my 931GB drive? –Sun May 29 at 14:44 Its somekind of identification to which partition it is referring. And yes, it appears to be your 931GB drive. A controller error is not like bad sectors though. Chkdsk may make the drive become permanently unavailable. you should take this warning and start doing backups. –LPChip May 29 at 14:59 Make your comment into answer –Sun May 29 at 16:59 3 Possible duplicate of Which drive is
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 http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ with blue screen. Now that I feel 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, driver detected 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 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 driver detected a 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 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 o