Driver Detected A Controller Error On Device Scsi Adpu3202
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : The driver detected a controller error on \Device\... VOX : Backup and Recovery : Backup Exec : The driver detected a controller error on \Device\... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page The driver detected a controller error on \Device\Scsi\adpu3202. quadra N/A 11-01-2007 11:25 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I have a problem in that in the Backup Exec alerts I am getting the following message:The driver detected a controller error on \Device\Scsi\adpu3202.This error can occur up to 2000 times in a minute, adding to the log and slowing the server down.Everything was OK from initial installation, then after about 2 weeks the above error started.I have reinstalled Backup Exec, replaced SCSI card, but nothing.The system is an SBS2003 server with a Adaptec 29320 PCI Express card and a HP DAT72X6 auto loaderAny help is mostly appreciated, I have looked at most things on the internet, and nothingThank in advanceDave Labels: 11.x and Earlier Backup and Recovery Backup Exec 0 Kudos Reply 1 Reply Re: The driver detected a controller error on \Device\Scsi\adpu3202. Jackie_Liu Level 3 Employee Accredited Certified 11-02-2007 03:41 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Just a suggestion, maybe you should check MSKB http://support.microsoft.com/kb/154690/first. 0 Kudos Reply Contact Privacy Policy Terms & Conditions
Links Notable Members Current Visitors Recent Activity New Profile Posts Search Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads More... Recent Posts Menu Log in or Sign up [H]ard|Forum Forums > [H]ard|Ware > SSDs & Data Storage > The driver detected a controller error on \Device\Scsi\adpu3201 Discussion in 'SSDs & Data Storage' started by gimp, Oct 23, 2009. Oct 23, 2009 #1 gimp [H]ardForum Junkie Messages: 9,165 Joined: Jul 25, 2008 Server 2003. Has the onboard Dell Perc 5/i for harddrives. an add-in Adaptec U320 https://vox.veritas.com/t5/Backup-Exec/The-driver-detected-a-controller-error-on-Device-Scsi-adpu3202/td-p/162799 SCSI PCI-X card. Only a Quantum LTO 2 tape drive is hooked up to the Adaptec. This error started popping up around June. June 2, to be exact, and is logged every day. The last 2 people that administered this server are no longer around. I'm not exactly sure when the tape drive was installed. But on June 2: Installation Successful: Windows successfully installed the following update: Quantum Corporation https://hardforum.com/threads/the-driver-detected-a-controller-error-on-device-scsi-adpu3201.1462654/ - Storage - Quantum LTO 2 Tape DriveClick to expand... the problem is, I cannot roll back the driver, because no previous driver exists. I also downloaded the latest driver from Quantum, which is the same exact one. If I disable the port with the tape drive, the error doesn't seem to appear. Could this be caused if the SCSI isn't terminated? This is an off-site server, but not currently doing any backups so it's not a hugely important issue, but something I would like to get cleared up. gimp, Oct 23, 2009 gimp, Oct 23, 2009 #1 Oct 26, 2009 #2 gimp [H]ardForum Junkie Messages: 9,165 Joined: Jul 25, 2008 Bueller? Bueller? I'm not all that familiar with SCSI, as I've never messed with it before... gimp, Oct 26, 2009 gimp, Oct 26, 2009 #2 Nov 20, 2009 #3 gimp [H]ardForum Junkie Messages: 9,165 Joined: Jul 25, 2008 well I haven't had any success with this yet. the SCSI cable already had a terminator, but I went ahead and set the jumper on the tape drive to enable termination at the device. still logging this error. Not sure what it could be? gimp, Nov 20, 2009 gimp, Nov 20, 2009
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs Free for subscribers http://www.eventid.net/display-eventid-11-source-adpu160m-eventno-716-phase-1.htm Event ID: 11 Source: adpu160m Source: adpu160m Type: Error Description:The driver detected a controller error on \Device\Scsi\adpu160m1 English: This information is only available to subscribers. An example of English, please! Comments: S² This event might especially occur under the following conditions: A SCSI harddisk installed using an SCA-Adapter. The harddisc is located on rubber attenuators to uncouple the harddisc to silence the drive. The SCSI Bus is set to LVD Mode Reason: No driver detected connection between the harddisk and the case so there''s no ground connection. Solution: Simply ground the harddisc enclosure by connecting it with a small wire to the case (or anything else grounded). x 20 Dana Racine This error can occur when running the HP/Compaq Tape and Library tools to upgrade firmware on an HP/Compaq server. When the hardware device scan occurs, the tool generates these errors in the event log. If you see driver detected a the EventID error (along with an EventID 117 and EventID 9 from adpu160m) generated only when you run the HP Tape and Library tool then you can safely ignore it. x 11 ASI_Tech Error messages generated by the adpu160m.sys driver can be viewed by opening the Windows NT Event Viewer error logs. To view events generated by the driver, follow these steps: Double-click the Event Viewer icon in the Administrative Tools program group. Error messages generated by the driver show up as Event ID 11. Error messages generated by the SCSI port show up as Event ID 9. To view event details, select System from the Log menu. Double-click the adpu160m.sys driver event that has an Event ID of 11. (There may be none or multiple driver events.) The top portion of the Event Detail dialog box displays information such as the time that the event was generated, the computer on which the event occurred (in case of remote monitoring) and the description of the event. The Data section of the Event Details dialog box displays the error messages generated. Click the Words radio button. In the Data section of the dialog box, the entry in the second row and second column (to the right of the 0010: entry) lists the error message generated by the driver. The com