[9fans] fs SCSI errors

[9fans] fs SCSI errors

[Skip Tavakkolian]

After giving the the initial config somewhere in the initialization
the following messages appear in a continous loop:

scsi#0.0: retry 10 cmd #25
wreninit: w0 bad status -0004
scsi#0.0: test, status -4

I get that something is wrong with the first scsi disk.  Any ideas
what the problem is and what causes this?  FYI, w0 drive is a 9.1GB
Seagate Cheetah.

Re: [9fans] fs SCSI errors

[Skip Tavakkolian]

Thanks to your questions and a little more sleep, it occured to me
that this system has two SCSI controllers.  The onboard one is an
Adaptec AIC-7880 and the second (in a PCI slot) is a combo board with
a Symbios 53C875.  The kernel detected the second one and I assumed
that was the first controller.  The disks are on the Adaptec 7880
controller for which there are no drivers.  I will switch to the
second controller and see if I have better luck with w8 and w9.

> What's the configuration of your file server, in particular the filsys
> declarations?  What SCSI devices are at which target numbers?  Are
> they all turned on and spun up?  Is your SCSI bus (or buses)
> terminated correctly?  Has the disk in question been used successfully
> on any machine before?  recently?  Which SCSI host adapter are you
> using?  Has it been used successfully before?  Does your SCSI BIOS
> spin up all the drives (it's an option in the BIOS)?

filsys main cw0f{h0h1}	# only one IDE controller
filsys dump o
filsys other w1

The drives have SCSI ID 0 and 1 (both are Seagate ST39103LW)
I hear them spin up. I've also used the SCSI utilities (Adaptec
AIC-78xx SCSISelect utility) to format and verify the media.
They were both known working just before I formatted them (RH/Linux
on one and Win98/dos on the other).  All cables and the terminator
seem secure.

There are two SCSI controllers one is built into the motherboard
and the other is in a PCI slot. <...revelation, or perhaps duh...>

>
> If you're using a Mylex (Buslogic) host adapter, you can type
> control-B when its BIOS runs at boot-time, and from there scan your
> SCSI bus to see what the controller thinks is there, and you can
> interrogate the devices a little too.

Re: [9fans] fs SCSI errors

[Geoff Collyer]

What's the configuration of your file server, in particular the filsys
declarations?  What SCSI devices are at which target numbers?  Are
they all turned on and spun up?  Is your SCSI bus (or buses)
terminated correctly?  Has the disk in question been used successfully
on any machine before?  recently?  Which SCSI host adapter are you
using?  Has it been used successfully before?  Does your SCSI BIOS
spin up all the drives (it's an option in the BIOS)?

If you're using a Mylex (Buslogic) host adapter, you can type
control-B when its BIOS runs at boot-time, and from there scan your
SCSI bus to see what the controller thinks is there, and you can
interrogate the devices a little too.