Ql2300 Driver Detected A Controller Error
Contents |
a Question Ask for 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 ql2300 qlogic Freelance Project Hire for a Full Time Job Ways to Get Help
The Driver Detected A Controller Error On \device\raidport
Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Courses Vendor Services Groups Careers Store Headlines
Ql2300 Event Id 129
Website Testing Experts Exchange > Questions > QLogic ql2300 Event 11 - The driver detected a controller error Want to Advertise Here? Solved QLogic ql2300 Event 11 - The driver
Ql2300 Reset To Device Was Issued
detected a controller error Posted on 2006-01-16 Storage Software Storage 1 Verified Solution 5 Comments 36,125 Views Last Modified: 2013-11-15 Our netbackup server is running Windows 2003 which has two Qlogic 2300 Fibre cards installed. The fibre cards are attached to ADIC Scalar i2k Library which produces the following error: 1/9/2006 3:02:51 PM ql2300 Error None 11 N/A BACKUP-SRV The driver ql2300 event id 11 detected a controller error on \Device\RaidPort1. During this error, we are unable to see the library or the tape drives. Can someone provide me some insight on what this error means? Thanks, 0 Question by:simpsop Facebook Twitter LinkedIn Google LVL 22 Best Solution bydovidmichel You are having trouble for good reason, the event code does not match up to any explanations. They do not list a C level code for any of their controler or driver versions. Just in case here is the Go to Solution 5 Comments LVL 22 Overall: Level 22 Storage 19 Storage Software 16 Message Expert Comment by:dovidmichel2006-01-16 Event 11 is just a very generic event. You need to dig deeper for the details of what is really happening. Here is the link to the QLogic support page for Event 11. It has a table detailing it out. http://www.qlogic.com/support/logs/evlogV9xxx_error.asp From the above link: "The event information is viewed using the Windows Event Viewer. Events logged by the drivers are listed with the Source field set to "ql2300" and the Event ID field set to "11". Double cl
Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems qlogic 2300 Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission https://www.experts-exchange.com/questions/21698737/QLogic-ql2300-Event-11-The-driver-detected-a-controller-error.html Critical Servers Servers for Cloud Server Management All Servers Storage All-flash and Hybrid Storage Midrange and Enterprise Storage Entry Storage Systems Data Availability, Protection and Retention Software Defined Storage Management and Orchestration Storage Networking All Storage Networking Switches Routers Access Points and Controllers Wireless LAN Campus and Branch Networking Data Center Networking Wide Area Network Software Defined Networking Network https://community.hpe.com/t5/Storage-Area-Networks-SAN/ql2300-the-driver-detected-a-controller-error-device-raidport0/td-p/4214378 Functions Virtualization Network Management All Networking About UsSupportClearType to search2086159Solutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven Organization Enable Workplace Productivity Cloud Security Big Data Mobility Infrastructure Internet of Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Server Management All Servers Storage All-flash and Hybrid Storage Midrange and Enterprise Storage Entry Storage Systems Data Availability, Protection and Retention Software Defined Storage Management and Orchestration Storage Networking All Storage Networking Switches Routers Access Points and Controllers Wireless LAN Campus and Branch Networking Data Center Networking
ordeal with this Event 11 that Windows quietly generates. It took us few weeks to fully work out why Windows suddenly started hanging, misbehaving http://www.adir1.com/2012/01/solved-the-driver-detected-a-controller-error-on-deviceideideport2/ or even crashing 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 https://vox.veritas.com/t5/Backup-Exec/quot-Driver-has-detected-a-controller-error-quot-help-and-info/td-p/491841 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 driver detected 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 atapi error. For impatient souls among us, here are my conclusions: First thing – check the SATA/EIDE and power cable connection between your driver detected a 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 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 ca
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 : "Driver has detected a controller error" - help an... VOX : Backup and Recovery : Backup Exec : "Driver has detected a controller error" - help an... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution "Driver has detected a controller error" - help and info pls davewingrave Level 3 05-02-2012 02:04 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi We are running B/Up Exec 2010R3 on a IBM X3650 (Win 2003 R2 standard SP2) and the backup keeps failing. It is using an IBM ULT3580-HH5 (LTO5) tape drive with an IBM SAS controller card (actually an LSI 9212-4i4e). I am now getting hardware errors (for about 1 week) but I have the latest drivers installed for the hardware and I have updated BE with the latest hotfixes. The error i get in BE is The following event was reported on 5/1/2012 8:33:30 PM: The driver detected a controller error on \Device\RaidPort1. -------------------- This error signifies controller errors. These errors are generally caused by hardware that is not functioning correctly. To resolve these errors, try the following actions: - Slow the SCSI bus. - Verify that the latest SCSI drive