How to resolve SCSI bus timeouts

Article:TECH5027  |  Created: 2009-01-16  |  Updated: 2014-02-27  |  Article URL http://www.symantec.com/docs/TECH5027
Article Type
Technical Solution

Product(s)

Subject

Issue



A SCSI bus timeout occurs when either the SCSI controller or the SCSI device detects that a command has not been responded to within a specific timeout period. Normally, commands are issued by the SCSI controller, which then waits for a response from the device being addressed. If no response is detected, the controller may reset the bus to reinitiate communication. While disk drives normally recover well from SCSI bus timeouts and resets, tape drives have much greater difficulty in doing so.
 


Cause



To try to detect problems such as these, the architects of the SCSI bus, and Backup Exec (tm) programmers have defined time limits for possible operations being performed by tape drives attached to the SCSI bus. Normally, these timeout values are large enough to accommodate any delay, including retries, in executing the specific command being attempted. In the event that the device does not respond in the amount of time indicated by the timeout value, a timeout occurs.

Usually, the first indication of a timeout is that the tape drive ceases activity. However, because some operations can take several hours on some tape drives, some timeout values are very long, which can make it seem as if the program itself has stopped responding, or that there is some kind of application error.
Given below are some suggested changes and checks to help resolve the SCSI timeout issue.
 


Solution



To try to detect problems such as these, the architects of the SCSI bus, and Backup Exec (tm) programmers have defined time limits for possible operations being performed by tape drives attached to the SCSI bus. Normally, these timeout values are large enough to accommodate any delay, including retries, in executing the specific command being attempted. In the event that the device does not respond in the amount of time indicated by the timeout value, a timeout occurs.

Usually, the first indication of a timeout is that the tape drive ceases activity. However, because some operations can take several hours on some tape drives, some timeout values are very long, which can make it seem as if the program itself has stopped responding, or that there is an application error of some kind.
Given below are some suggested changes and checks to help resolve the SCSI timeout issue.

First, ensure that the Backup Exec drivers are installed.
 
1. Right-click the My Computer icon on the desktop, and then select Manage.
 
2. Select Device Manager, and from the right pane, expand Tape drives, right-click the tape device and then select Properties.
 
3. Select the Driver tab; ensure a Veritas or Symantec signed driver is listed (Driver Provider).
 
4. If the driver is not signed by Veritas or Symantec, execute the Device Configuration Wizard from within the Backup Exec GUI | Tools | Wizards.
 
5. Select the Install tape device drivers and follow the wizard to install Symantec drivers for your tape device.
 
6. Reboot server and confirm a new driver is loaded.

Next, check configuration on the SCSI controller.
 
  • Set the SCSI ID of the tape drive as close as possible to the SCSI ID of the HBA controller/interface. Example: If the HBA controller ID is 7 then the tape drive should have 6 or 8, or any available ID which is closest to 7, if 6 and 8 are unavailable.
  • Avoid 0 or 1 for SCSI ID's, these are usually reserved for bootable devices
  • Set INITIATE WIDE NEGOTIATION to off for controllers with a wide bus
  • Set INITIATE SYNC NEGOTIATION for the ID of the tape drive to off
  • Set MAXIMUM SYNC TRANSFER RATE to the slowest possible setting
  • DISCONNECT must be enabled for all tape drive SCSI IDs
  • Set SCSI PARITY CHECKING to off
 
WARNING: The Parity Checking adjustment is for diagnostic use only and should never be left disabled during production backups. Symantec Corporation cannot be held liable for data corruption due to Parity Checking being disabled.
 
Hardware Issues:
 
  • Check with the controller and tape drive vendors for firmware and driver updates.
  • Use good quality cabling that follows the SCSI specification.
  • For external cables, use heavy duty shielded cables.
  • Under no circumstances should an external SCSI cable be detached from any connection while power is still applied to any device on the bus.
  • For single-ended internal cables, make sure there is at least one foot of cable between devices.
  • Also, for single-ended buses, make sure the overall cable length from termination to termination does not exceed the maximum bus length of three meters (roughly 9 to 10 feet).
  • Use active termination on both ends of the SCSI bus.
  • The last external device (if any) on the SCSI chain is terminated.
  • The last internal device (if any)) on the SCSI chain is terminated.
  • The internal termination of the SCSI host adapter is not set to Automatic, but to the appropriate setting for the hardware configuration (Refer to the Host Adapter documentation for the correct settings).
  • All external devices should be set to supply termination power.
  • Put the tape devices on a separate controller by itself or change the existing controller.
  • Replace the tape drive.
Additional errors that may be resolved by following this Tech Note:
 
  • "Device I/O" errors.
  • "Bad Block" errors.

 


Supplemental Materials

SourceEvent ID
Value9
Description

The device, \Device\ScsiPort0, did not respond within the timeout period


SourceEvent ID
Value11
Description

The driver detected a controller error on \Device\Scsi\


SourceEvent ID
Value15
Description

The device, \Device\ScsiPort1, is not ready for access yet


SourceError Code
ValueA0008442
Description

E_Engine_Out_of_Memory




Legacy ID



191158


Article URL http://www.symantec.com/docs/TECH5027


Terms of use for this information are found in Legal Notices