Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Jul 2000 15:29:48 -0300
From:      MauricioWP <mwp@pucrs.br>
To:        "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG>, freebsd-scsi@FreeBSD.ORG
Subject:   SCSI Problem/Error
Message-ID:  <39807F9C.31D06E15@pucrs.br>

next in thread | raw e-mail | index | archive | help
Hi.

I had a *little* problem in my SCSI devices that halted my 4.0-stable
box today. The console messages follows:

(da1:ahc0:0:12:0): SCB 0x3b - timed out in Data-out phase, SEQADDR ==
0x115
(da1:ahc0:0:12:0): BDR message in message buffer
(da1:ahc0:0:12:0): SCB 0x47 - timed out in Data-out phase, SEQADDR ==
0x115

These messages were in highlight, so I think they're important messages
:).

The SCSI devices of the box follows:

ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0xb800-0xb8ff mem
0xe2000000-0xe2000fff irq 5 at device 13.0 on pci0
ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
Waiting 15 seconds for SCSI devices to settle
Mounting root from ufs:/dev/da0s1a
da1 at ahc0 bus 0 target 12 lun 0
da1: <QUANTUM ATLAS IV 9 WLS 0909> Fixed Direct Access SCSI-3 device
da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing
Enabled
da1: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C)
da0 at ahc0 bus 0 target 6 lun 0
da0: <QUANTUM FIREBALL ST4.3S 0F0C> Fixed Direct Access SCSI-2 device
da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing
Enabled
da0: 4136MB (8471232 512 byte sectors: 255H 63S/T 527C)

I also have a Sony DDS3 external tape drive, which is off at the moment.
Sometimes when I connect the tape to system some strange SCSi errors
appear in the console (I don't have any know, the tape was off in this
boot...).

What I'd like to know is what these error messages mean. I don't know
much about SCSI. A month ago this machine lost a disk (which I changed).
The two disks (da1 and da0) are in different SCSI channels (as you can
see in the informations above). Am I playing dumb and there something I
should do to not happen these errors. Or there is some evil in my
hardware? Maybe there is some evil Spirit of Bytes who is playing with
my machine (then I should call some kind of hardware exorcist).

Thanks for your help.

MaurícioWP.

PS.: answers from FreeBSD-SCSI please reply directly to my e-mail too.

------------------------------
Maurício Westendorff Pegoraro
CPD - PUCRS - Brasil
Unix & Security Team




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39807F9C.31D06E15>