Event id 11 the driver detected a controller error on device harddisk2 dr4

 · Every disk will have a device controlling the Raw Physical drive (DR identifier) and a device per each partition, controlling the partition (DP instance) For .  · Event ID iScsiPRT CHAP Response given by the target did not match the expected one. Event ID iScsiPRT Login request failed. Event ID MSiSCSI Timeout waiting for iSCSI persistently bound volumes.  · The source may be the controller or (more probably) a device (harddisk 2) that is attached to the controller. The hardware problem can be poor cabling, incorrect termination or transfer rate settings, a faulty device, or in rare cases, a poorly written device driver. Run the troubleshooter.

Event ID iScsiPRT CHAP Response given by the target did not match the expected one. Event ID iScsiPRT Login request failed. Event ID MSiSCSI Timeout waiting for iSCSI persistently bound volumes. The error “The driver detected a controller error ” could be cabling defect, try different cables (shorter better quality). Make sure the cable you use is rated for the hard disk speed you have, such as 6gbps (SATA 6 versus 3). The source may be the controller or (more probably) a device (harddisk 2) that is attached to the controller. The hardware problem can be poor cabling, incorrect termination or transfer rate settings, a faulty device, or in rare cases, a poorly written device driver. Run the troubleshooter.

but 2 of them in particular are generating a ton of Event ID 11 ("The driver detected a controller error on \Device\Harddisk#\DR#. All Fixes for: The driver detected a controller error on \Device\Harddisk2\DR2. Drive controller errors may show up in the Event Viewer as: The driver detected. 7 Okt How can i identify what is the drive with the code Harddisk3\DR3? If it is the usb stick i don't care that much, but if it is one of my internal drives i need.