Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!sgi!shinobu!odin!anchor!olson
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: disk timeout, SCSI reset...
Message-ID: <1991Apr7.201502.1883@odin.corp.sgi.com>
Date: 7 Apr 91 20:15:02 GMT
References: <9104062100.AA28279@adcs00.fnal.gov>
Sender: news@odin.corp.sgi.com (Net News)
Organization: Silicon Graphics, Inc.  Mountain View, CA
Lines: 37

In <9104062100.AA28279@adcs00.fnal.gov> dave@ADCS00.FNAL.GOV (David Richardson) writes:
|   I think there may be more to this than just coincidence.  We have had these
| same messages show up on our machines since the upgrade to 3.3.2.  There have
| not been any obvious problems other than the annoying messages.
| Apr  4 09:05:42 adchl1 unix: sc0,1: Resetting SCSI bus: timeout after 30 sec
| Apr  4 09:05:42 adchl1 unix: dks0d1s0 (/): retrying request
| Apr  4 09:06:54 adchl1 unix: dks0d4s10: retrying request
| 
| Apr  5 16:57:09 adcs00 grcond[27111]: CIO: sc0,5: Resetting SCSI bus: timeout
| after 120 sec
| Apr  5 16:57:09 adcs00 grcond[27111]: CIO: dks0d1s0: retrying request
| Apr  5 16:57:09 adcs00 grcond[27111]: CIO: dks0d4s10: retrying request
| 
|   We did not make any changes to the hardware during or since the upgrade.
| I'm inclined to think the clue lies in the fact that both of these machines
| have Gigatape 8mm tape drives.  Our machine's without the 8mm tapes do not
| record these messages.  What's up?

What OS release were you running before the upgrade, and what hardware
do you have (cpu and SCSI devices).  The hinv output might help.

I'm beginning to sound like a broken record, but for 3rd party hardware,
your best bet is to contact the vendor.  My guess is still cabling or
termination problems.  There were some OS changes in 3.3 that affected the
average size of disk i/o for scsi drives, and that could be exposing
a problem that has always been there.

If you were running pre 3.2 software before, scsi devices didn't run in
sync mode, and that could have something to do with the problem, but
that doesn't sound likely, since the 8mm drvies weren't really
supported prior to 3.2 (there was a 3.1g maint release to support them,
but not many people had that).
--

	Dave Olson

Life would be so much easier if we could just look at the source code.