[3706] in linux-scsi channel archive
Re: BT-958 slow tape reliability
daemon@ATHENA.MIT.EDU (Erik H. Beck)
Thu Apr 16 21:54:55 1998
Date: Wed, 15 Apr 1998 21:24:36 -0400
From: "Erik H. Beck" <ebeck@tahoma.com>
To: lnz@dandelion.com
CC: linux-scsi@vger.rutgers.edu
Leonard N. Zubkoff wrote:
> Date: Fri, 10 Apr 1998 11:03:58 -0700
> From: Erik Beck <ebeck@tahoma.com>
>
> What is the most reliable way to attach a 50 pin SCSI-2 tape drive
> (Seagate Travan 4) to a BT-958? I am having problems getting this tape
> drive to work with my SCSI card under Linux and NT. I am currently using
> a 68 pin to 50 pin cable to make the connection. Active termination on
> the tape drive is being used, and no other devices are connected to the
> SCSI bus. The tape drive works OK under NT when using a Belkin Parallel
> to SCSI adapter, so I know the drive isn't totally kaput.
>
> What are the ypmtoms of the problems? Which firmware version is in your
> BT-958?
>
> Leonard
Until I moved the drive away from the computer and monitor, it wasn't able to
obey even a retension command correctly on either NT or LINUX. Once I moved
the tape drive away from the computer, it was able to sometimes correctly
interpret a retension command, but no read or write operations were
successful. The tape drive just hangs. The firmware version is 5.07b.
Kernel is a stock 2.0.33. The Seagate Tape Store 8000 is attached to the
external 68 pin port of the BT-958 with a 68 to 50 pin cable . A 50 pin
active terminator is attached directly to the Tape Store. There are no other
SCSI devices in use. This cabling arrangement may be part of the
problem. See email from Jeff Noxon below.
Here are the messages recorded in the log file:
Apr 4 23:35:47 puyallup kernel: scsi: ***** BusLogic SCSI Driver Version
2.0.10 of 11 August 1997 *****
Apr 4 23:35:47 puyallup kernel: scsi: Copyright 1995 by Leonard N. Zubkoff
<lnz@dandelion.com>
Apr 4 23:35:47 puyallup kernel: scsi0: Configuring BusLogic Model BT-958 PCI
Wide Ultra SCSI Host Adapter
Apr 4 23:35:47 puyallup kernel: scsi0: Firmware Version: 5.07B, I/O
Address: 0xFCFC, IRQ Channel: 10/Level
Apr 4 23:35:47 puyallup kernel: scsi0: PCI Bus: 0, Device: 14, Address:
0xFFBFF000, Host Adapter SCSI ID: 7
Apr 4 23:35:47 puyallup kernel: scsi0: Parity Checking: Enabled, Extended
Translation: Enabled
Apr 4 23:35:47 puyallup kernel: scsi0: Synchronous Negotiation:
NFFFFFF#FFFFFFFF, Wide Negotiation: NYYYYYY#YYYYYYYY
Apr 4 23:35:47 puyallup kernel: scsi0: Disconnect/Reconnect: Enabled,
Tagged Queuing: Enabled
Apr 4 23:35:47 puyallup kernel: scsi0: Scatter/Gather Limit: 128 of 8192
segments, Mailboxes: 255
Apr 4 23:35:47 puyallup kernel: scsi0: Driver Queue Depth: 255, Host
Adapter Queue Depth: 192
Apr 4 23:35:47 puyallup kernel: scsi0: Tagged Queue Depth: Automatic,
Untagged Queue Depth: 3
Apr 4 23:35:47 puyallup kernel: scsi0: Error Recovery Strategy: Default,
SCSI Bus Reset: Enabled
Apr 4 23:35:47 puyallup kernel: scsi0: SCSI Bus Termination: Both Enabled,
SCAM: Disabled
Apr 4 23:35:47 puyallup kernel: scsi0: *** BusLogic BT-958 Initialized
Successfully ***
Apr 4 23:35:47 puyallup kernel: scsi0: Target 0: Asynchronous
Apr 4 23:35:47 puyallup kernel: scsi0 : BusLogic BT-958
Apr 4 23:35:47 puyallup kernel: scsi : 1 host.
Apr 4 23:35:47 puyallup kernel: Vendor: CONNER Model: CTT8000-S
Rev: 1.17
Apr 4 23:35:47 puyallup kernel: Type: Sequential-Access
ANSI SCSI revision: 02
Apr 4 23:35:47 puyallup kernel: scsi : detected total.
Apr 5 16:58:51 puyallup kernel: scsi : aborting command due to timeout : pid
32, scsi0, channel 0, id 0, lun 0 Write (6) 01 00 00 3c 00
Apr 5 16:58:51 puyallup kernel: scsi0: Aborting CCB #47 to Target 0
Apr 5 16:58:52 puyallup kernel: SCSI host 0 abort (pid 32) timed out -
resetting
Apr 5 16:58:52 puyallup kernel: SCSI bus is being reset for host 0 channel
0.
Apr 5 16:58:52 puyallup kernel: scsi0: Sending Bus Device Reset CCB #48 to
Target 0
Apr 5 16:58:53 puyallup kernel: SCSI host 0 channel 0 reset (pid 32) timed
out - trying harder
Apr 5 16:58:53 puyallup kernel: SCSI bus is being reset for host 0 channel
0.
Apr 5 16:58:53 puyallup kernel: scsi0: Resetting BusLogic BT-958 due to
Target 0
Apr 5 16:58:53 puyallup kernel: scsi0: *** BusLogic BT-958 Initialized
Successfully ***
Apr 5 16:58:54 puyallup kernel: st0: Error with sense data: extra data not
valid Current error st09:00: sense key Unit Attention
Apr 5 16:58:54 puyallup kernel: Additional sense indicates Power on, reset,
or bus device reset occurred
Apr 5 16:58:56 puyallup kernel: st0: Error with sense data: extra data not
valid Current error st09:00: sense key Not Ready
Apr 5 16:58:56 puyallup kernel: Additional sense indicates Logical unit is
in process of becoming ready
*******************************
Date: Fri, 10 Apr 1998 14:39:20 -0400
From: Jeff Noxon <jeff@planetfall.com>
Are you using any wide devices on the same bus? If so, use a 68 pin
cable and wide active termination. If you're using a 50 pin terminator,
you're only terminating part of the bus. You can buy a 68-pin to
50-pin adapter gizmo that lets you plug any internal narrow device into
a 68-pin cable.
You didn't mention if it was internal or external.
In cases like this, it often makes sense to buy a second, cheap, narrow
SCSI controller. Special cables and terminators (or a new enclosure)
can easily get more expensive than another SCSI card.
Good luck
Jeff
*********************************
Thanks for your interest and assistance.
___________
Erik H. Beck
ebeck@tahoma.com
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
