Red Hat Customer Portal

Skip to main content

qla2xxx scsi errors in the logs

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux (RHEL)

Issue

The following messages are seen in the logs:

Dec  8 11:56:36  kernel: st: Version 20070203, fixed bufsize 32768, s/g segs 256
Dec  8 11:56:36  kernel: st 0:0:10:0: Attached scsi tape st7
Dec  8 11:56:36  kernel: st7: try direct i/o: yes (alignment 512 B)
Dec  8 15:46:30  kernel: qla2xxx 0000:06:00.0: scsi(0:10:0): Abort command issued -- 1 10fb 2002.
Dec  8 15:46:41  kernel: qla2xxx 0000:06:00.0: scsi(0:10:0): Abort command issued -- 1 10fb 2002.
Dec  8 15:46:41  kernel: qla2xxx 0000:06:00.0: scsi(0:10:0): DEVICE RESET ISSUED.
Dec  8 15:46:41  kernel: qla2xxx 0000:06:00.0: scsi(0:10:0): DEVICE RESET SUCCEEDED.
Dec  8 15:46:52  kernel: qla2xxx 0000:06:00.0: scsi(0:10:0): Abort command issued -- 1 10fb 2002.
Dec  8 15:46:52  kernel: qla2xxx 0000:06:00.0: scsi(0:10:0): LOOP RESET ISSUED.
Dec  8 15:46:52  kernel: qla2xxx 0000:06:00.0: LOOP DOWN detected (0 0 0).
Dec  8 15:46:57  kernel: qla2xxx 0000:06:00.0: LOOP UP detected (8 Gbps).
Dec  8 15:47:18  kernel: qla2xxx 0000:06:00.0: qla2xxx_eh_bus_reset: reset succeeded
Dec  8 15:47:39  kernel: qla2xxx 0000:06:00.0: scsi(0:10:0): Abort command issued -- 1 10fb 2002.
Dec  8 15:47:39  kernel: qla2xxx 0000:06:00.0: scsi(0:10:0): ADAPTER RESET ISSUED.
Dec  8 15:47:39  kernel: qla2xxx 0000:06:00.0: Performing ISP error recovery - ha= ffff810139dd44f8.
Dec  8 15:47:45  kernel: qla2xxx 0000:06:00.0: LOOP UP detected (8 Gbps).
Dec  8 15:47:47  kernel: qla2xxx 0000:06:00.0: qla2xxx_eh_host_reset: reset succeeded
Dec  8 15:48:08  kernel: qla2xxx 0000:06:00.0: scsi(0:10:0): Abort command issued -- 1 10fb 2002.
Dec  8 15:48:08  kernel: st 0:0:10:0: scsi: Device offlined - not ready after error recovery
Dec  8 15:48:08  kernel: st 0:0:10:0: timing out command, waited 14000s
Dec  8 15:48:08  kernel: st7: Error 6080000 (sugg. bt 0x0, driver bt 0x6, host bt 0x8).

Resolution

  • Contact storage vendor for additional help to find a resolution.
  • A SAN failure occurred. One workaround for some instances of this failure has been to disable link speed autonegtiate and set the FC speed to a fixed 4Gb instead of 8Gb.
  • Also check by removing/detaching the storage devices from the server that are not being used.

Diagnostic Steps

  • These could indicate a number of issues: the HBA, SAN, or the ST tape. Check the SAN connectivity and the storage.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.