Errors since upgrading from SDLT600 to DLT-S4

Also see this warning in the event log, prior to the Event ID 15

The description for Event ID ( 129 ) in Source ( Lsi_scsi ) 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\RaidPort0.

I suspect that this could be indeed a Hardware issue. You can check the Event viewer when the job fails. You may find any event ids. like 7, 9, 11 or 15 which corresponds to hardware problem.

Also make sure that the device drivers are latest Symantec drivers. Medium changer in the Device manager will be using the Unknown Medium Changer drivers provided by the Operating System.

In case if you are facing hardware issue then you may refer to the following technote for hardware problems.

 http://www.symantec.com/docs/TECH24414 : How to troubleshoot issues with a Robotic Library (autoloader/changer) and/or Tape Drive(s)

 To confirm that your tape drive is faulty or not please do the following steps,

1) Stop all Backup Exec services

2) Use the Manufacturer's diagnositic utility to test the tape drive.  Make sure you select the write test.

Here the issue may not be with the Tape drive but with the Connectors and cables which is cauing this issue.

Thanks,

-Sush...

Hi Sush,

I see the 11 and 15, but since restarting the BE2010 services, Catalog and Inventory were fine and I suspect it will take another 7 days to fail.

Looking at the server, no errors are reported with the SCSI ports 1, slot 3, ID-5 (S4)

As far as the Device Manager, this is not a changer but an external unit with a DLT1 and S4 installed and reported correctly in the Tape section.

Mark

Ok, updated the Server 2003 Tape driver from the Quantum website from 4.2.77.0 to 4.5.1.0

One thing at a time I guess!

Full Health test performed by Quantum Xtalk reported no issues

Hi there,

I'd recommend updating the firmware on the SCSI card and the library, and making sure that the drivers for BE are the latest.

Once done, see if this happens again.

In my case (well, 3 servers in December/January) were the result of faulty HP SCSI cards. Once these were replaced, the problem was resolved!

Laters!

Hello Marcopolo,

This problem may occur under high stress conditions. The problem occurs because of an error in the SCSIPort driver. This error generates Event ID 11 and event ID 15. Additionally, this problem may cause network timeouts if remote computers are accessing data on the drives that are using the SCSIPort driver on the Windows Server based computer.

• Event ID 11: Signifies controller errors. These errors are generally caused by hardware that is not functioning correctly. Attempting to slow the SCSI bus down and verifying that the latest SCSI drivers and firmware are loaded can sometimes resolve these issues. If these errors occur, contact the hardware manufacturer.

• Event ID 15: Signifies the device is not ready for access. These errors usually occur when the device is malfunctioning or configured incorrectly. They may also occur if the incorrect drivers are loaded, or the drivers are not up to date. If these errors occur, contact the hardware manufacturer.

Check with hardware manufacturer and make sure Event id 11 and 15 is fixed..

Sids...

Ok, I've the firmware for the HP Ultra 320 HBA, anyone care to point where the drivers are for the Library and BE2010 and how to check what version are already being used?

If you go into Device Manager, and onto your tape drive you're able to see the driver date and the version.

You can find the link to the drivers below...just filter for your version:

http://www.symantec.com/business/support/index?page=content&key=15047&channel=TECHNICAL_SOLUTION&basecat=DOWNLOADS