Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Aug 2001 02:03:25 -0400 (EDT)
From:      Joe Clarke <marcus@marcuscom.com>
To:        Dan Larsson <dl@tyfon.net>
Cc:        Ted Mittelstaedt <tedm@toybox.placo.com>, FreeBSD Questions List <questions@FreeBSD.ORG>
Subject:   RE: What does these SCSI error messages mean?
Message-ID:  <20010824020133.V14558-100000@shumai.marcuscom.com>
In-Reply-To: <20010824073307.T5765-100000@hq1.tyfon.net>

next in thread | previous in thread | raw e-mail | index | archive | help
I'm not sure I have a good answer, but a parity error usually means
something bad happened between the disk and the controller.  The cheapest
solution would be to replace the cable, and see if the problem persists.
You may also want to search the -stable and -questions archive for more on
what others have done with this type of error.  Recently, I had a friend
run into this problem.  He fixed it by moving his ethernet card off the
IRQ that SCSI controller held.

Joe Clarke

On Fri, 24 Aug 2001, Dan Larsson wrote:

> On Thu, 23 Aug 2001, Ted Mittelstaedt wrote:
> | >What does these errors mean?
> | >
> | >Aug 23 20:20:29 dmx03 /kernel: (da0:ahc0:0:0:0): parity error detected in\
> |
> | I think it means you have a parity error.
> |
> | >  Data-in phase. SEQADDR(0x1ac) SCSIRATE(0x95)
> | >Aug 23 20:20:29 dmx03 /kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 73\
> | >  ca 16 0 0 2 0
> | >Aug 23 20:20:29 dmx03 /kernel: (da0:ahc0:0:0:0): ABORTED COMMAND\
> | >  csi:ff,ff,ff,ff asc:48,0
> | >Aug 23 20:20:29 dmx03 /kernel: (da0:ahc0:0:0:0): Initiator detected error\
> | >  message received
> | >[... this repeats itself about ten times ...]
> | >[... all messages within a one second timeframe ...]
> | >
> |
> | You have a problem in the SCSI subsystem.  Possible causes are bad
> | termination,
> | bad cabling, too long cabling, a failing device, incompatible SCSI devices.
> | If you would provide hardware info we might be able to assist.
>
> ahc0: <Adaptec 2940 Ultra2 SCSI adapter (OEM)> port 0xd800-0xd8ff mem\
>   0xf9000000-0xf9000fff irq 11 at device 10.0 on pci0
> da0 at ahc0 bus 0 target 0 lun 0
> da0: <WDIGTL ENTERPRISE 1.91> Fixed Direct Access SCSI-2 device
> da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit)
> da0: 4157MB (8515173 512 byte sectors: 255H 63S/T 530C)
>
> |
>
> I'm inclined to think it's not a SCSI cabling/termination or any kind of
> incompatibility issue since the box has been running flawlessly since
> FreeBSD-3.4 was released (it's now running FreeBSD-4.3 STABLE).
>
> Let's say it is a failing device. Is it the SCSI controller (ahc device)
> or the SCSI disk (da device) giving up on me? Or if that's unclear from
> the messages how can I find that out before it totally dies?
>
>
> Regards
> +------
> Dan Larsson  -+- Tyfon Svenska AB -+-  DL1999-RIPE
> 2AA5 90AE 5185 5924 1E0B  1A99 EC8A EA84 406B 06B9
>
>
>
>
>


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010824020133.V14558-100000>