"Driver has detected a controller error" - help and info pls
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 drivers and firmware are loaded.
If these errors continue to occur, contact the hardware manufacturer.
In Windows Event Viewer I get
The description for Event ID ( 129 ) in Source ( Lsi_sas2 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\RaidPort1.
Followed by
Event ID:11
The driver detected a controller error on \Device\RaidPort1.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I can't update the drivers (as they are the latest)..... I am stuck!
The SAS cable has been changed, does this point to a fault with the controller card or tape drive????
If I do a test run it completes successfully, however when I run the backup it does 380gb successfully and then asks for another tape (the overwrite/append times are fine and have been doubled checked!). This happens every day.....
Any help or pointers would be extremely useful
Thanks
Despite the tape utility telling me there was no issue with the hardware, this turned out to be a faulty drive! IBM replaced the drive 3 days ago and we have successful backups now!
Thanks for the suggestions and help along the way!