Error Disk Event 11
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 09 Oct 2016 19:14:20 GMT by s_ac5 (squid/3.5.20)
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom
Event Id 11 Custom Dynamic Link Libraries
views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view
Event Id 11 Disk Device Harddisk1 Dr1
for all logs Free for subscribers Event ID: 11 Source: Disk Source: Disk Type: Error Description:The event id 11 kdc duplicate names driver detected a controller error on \Device\Harddisk0\DR0 English: This information is only available to subscribers. An example of English, please! Comments: Sf4000 We had it due to failing http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/event-id-11-disk-the-driver-detected-a-controller/fb0e7207-2bde-4fcd-b1b8-643a9f20196a battery on PERC 6/i. Changed Write Policy from Write Back to Write Through - the event stopped popping up. P.S. The Write Through Policy was a temporary solution till the new controller battery has arrived. x 233 Anonymous I've had three of these errors pop up on our Level Platforms alerts. One of them I was able http://www.eventid.net/display-eventid-11-source-Disk-eventno-616-phase-1.htm to find the cause by simply installing Dell OpenManager Server Administrator and taking a look at the storage.The firmware driver was out of date. That would be a good first place to start. The other two alerts did not have a similar find. x 309 W4tch3r ‹•ż•› I am getting this error using multiple drives in a Shintaro USB3 drive caddy. After lots of drive and cable swapping I have discovered it happens because I have the drive caddy plugged into a Noontec USB3 hub. When I bypass the hub and go straight to the PC it does not happen. I do not know yet if the problem is with the Noontec hub or the Shintaro drive dock. x 315 Alexander Freudenberg In certain conditions, this error message is related to the S.M.A.R.T attribute 187 (Reported uncorrectable errors). When a physical sector of the disk is read by an application (e.g. a SMART test tool or a simple copy command) and a sector is "unstable", meaning th
Follow 5147 Mentions744 Products Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Microsoft 491342 Followers Follow Microsoft Windows Server Microsoft Windows Server https://community.spiceworks.com/topic/304581-driver-detected-a-controller-error-which-hdd-is-device-harddisk2-dr2 2012 Join the Community! Creating your account only takes a few minutes. Join https://www.experts-exchange.com/questions/26299634/We-occasionally-get-a-driver-controller-error-event-ID-11-but-drives-check-out-ok-Cause-for-concern.html Now Am seeing 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 on \Device\Harddisk2\DR2. On this server I have internal RAID volumes, an external iSCSI event id 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 click start, right event id 11 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 provifor 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 Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > We occasionally get a driver controller error (event ID) 11, but drives check out ok. Cause for concern? Want to Advertise Here? Solved We occasionally get a driver controller error (event ID) 11, but drives check out ok. Cause for concern? Posted on 2010-06-30 Storage Hardware Windows 7 Hardware 2 Verified Solutions 58 Comments 5,692 Views 1 Ratings Last Modified: 2012-05-09 Hi Experts, we run three different external hard drives on our main system for keeping copies of important data. These drives are used regularly. They are all fairly new and so is the system. The system itself is a brand new install of Windows 7, and the diagnostics have been run on the system and it seems to be running flawlessly and with the latest drivers. However, we occasioanlly get the following error in the system log "The driver detected a controller error on \Device\Harddisk1\DR5." It's USUALLY when the drive is first plugged in for the day, however, not necessarily. Sometimes it occurs sporadically once or twice throughout the day. It is NOT when the drive is being used. Full backups are sent to these drives regularly and it never seems to throw these events then. Backups complete fine and verify fine. The drives are all Seagate (purchased within a week or two of each other) and Seatools has been run on all of them, says they are all good. Also, it seems to happen with all three drives. Anyone have any input on the error? Than