[3628] in linux-scsi channel archive
Re: IBM DCAS 32160 help!
daemon@ATHENA.MIT.EDU (Mike Nachlinger)
Sun Apr 5 22:30:41 1998
Date: Sun, 5 Apr 1998 19:25:15 -0700 (PDT)
From: Mike Nachlinger <mnach@northstar.apres.org>
To: Michael Firkins <michael@sa.lyppard.com.au>
cc: linux SCSI <linux-scsi@vger.rutgers.edu>
In-Reply-To: <980405.165138@sa.lyppard.com.au>
On 5 Apr 1998, Michael Firkins wrote:
> Subject: Time: 3:05
> PM
> OFFICE MEMO IBM DCAS 32160 help! Date:
> 5/4/98
> Hi.
> I am getting some nasty device timeouts and resulting scsi bus resets on
> a RedHat 4.2 (2.0.32) system.
> Here is the Picture: (This all used to work fine)
> Buslogic BT958
> IBM DCAS32160 Fast/Wide SCSI disc 2.1gb (id 0)
> Fujitsu MO removable drive (narrow) (id 1)
> Tandberg Tape drive TDC4120 1.2gig (id 3) (terminated)
> The linux system resides on a eide drive hda, the scsi is for database
> files (Pick D3 native)
>
> The system has been in use for around 8 weeks, I removed it from use
> whilst I was away overseas for a few weeks. When I tried to restore the
> Pick Data files from the Tandberg tape drive I get the following
> messages:
> >kernel : scsi : aborting command due to timeout : pid 25144, scsi0,
> channel 0, id 0 , lun 0 write (6) 1c dc ca 40 00
> >kernel : scsi0 : Aborting CCB #25157 to Target 0
> >kernel : scsi : aborting command due to timeout : pid 25153, scsi0,
> channel 0, id 0 , lun 0 write (10) 00 00 22 2d 96 00 00 f4 00
> etc etc. About a second later, I get a SCSI host 0 abort, pid 25144,
> timed out - resetting, and the scsi bus is reset.
>
> I have restored the tape on another machine in case there was some
> problem with the data, but it's fine.
> I have checked termination, cables and addresses. All seem fine.
> It seems to me that the DCAS might have gone bad, but if I write linux
> files to the spare partition on it, there is no error.
> Any advice on how to track this down and what to look for would be
> appreciated. I am going to pull the DCAS for the present and put the
> PickD3 data on a spare eide drive to get the system going. Hopefully
> that will work...... (at least it will separate the DCAS from the rest
> of the scsi bus!)
>
> Michael
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.rutgers.edu
>
I have a DCAS-34330UW with a Buslogic BT-958 doing the same thing on a Debian
1.3.1r6 2.0.33 & 2.1.92 system. It was ALOT worse with an Adaptec 2940. I built
new cables stubbed on 12" centers, turned off on board termination and applied
Granite Digital active terminators, patched the AICxxxx driver per Doug
Ledsford. The errors are less with the Buslogic but still occure every 5 days
or so generally with a reboot. Also have a raid0 & raid 5 tied to this chain
(small, experimental partitions, more of a toy right now). It drives me nuts!
I'm about ready to throw the drives away also. I think about all thats left is a
firmware bug. The good side is the drives run very cool. Killed 3 fujitsu's
before smartened up. (All of the other drives on my system are narrow). If you
figure this out I'd love to hear about it.
Regards,
Mike
+--------------------------------------------------+
| Mike Nachlinger (408) 446-9914 mnach@apres.org |
| Apres Ski Club 1-888-APRESGO www.apres.org |
+--------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
