Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 9 Mar 2000 20:38:47 -0800 (PST)
From:      Doug White <dwhite@resnet.uoregon.edu>
To:        =?iso-8859-1?Q?Jos=E9_Monteiro?= <jm@sindigit.pt>
Cc:        freebsd-hackers@FreeBSD.ORG
Subject:   Re: ahc0 errors
Message-ID:  <Pine.BSF.4.21.0003092037530.48297-100000@resnet.uoregon.edu>
In-Reply-To: <20000309141136.A23000@sindigit.pt>

next in thread | previous in thread | raw e-mail | index | archive | help
Reply below .. saving detail

On Thu, 9 Mar 2000, [iso-8859-1] José Monteiro wrote:

> i've been experiencing several problems with an adaptec 2940u2w.
> 
> the disk and controller are detected as:
> 
> ahc0: <Adaptec 2940 Ultra2 SCSI adapter> rev 0x00 int a irq 11 on pci0.17.0
> ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs
> da1 at ahc0 bus 0 target 3 lun 0
> da1: <QUANTUM ATLAS IV 9 WLS 0A0A> Fixed Direct Access SCSI-3 device 
> da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled
> da1: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C)
> 
> the kernel messages invariably are:
> 
> proxy /kernel: ahc0: Data Parity Error Detected during address or write data phase
> proxy /kernel: ahc0: Received a Master Abort
> proxy /kernel: swap_pager: indefinite wait buffer: device: 0x20409, blkno: 7488, size: 4096
> proxy /kernel: swap_pager: indefinite wait buffer: device: 0x20409, blkno: 7488, size: 4096
> proxy /kernel: (da1:ahc0:0:3:0): SCB 0x1d - timed out in dataout phase, SEQADDR == 0x5d
> proxy /kernel: (da1:ahc0:0:3:0): BDR message in message buffer
> proxy /kernel: (da1:ahc0:0:3:0): no longer in timeout, status = 353
> proxy /kernel: Unexpected busfree.  LASTPHASE == 0xa0
> proxy /kernel: SEQADDR == 0x163
> 
> i already tried:
> 
> - added extra fan near the drive
> - shortened the cable distance between the disk and the controller,
>   trying to avoid near sources of elecromagnetic interference
> - lowered the transfer rate on the u2w bus to 40 and 20MB/s
> - connected the disk to the uw bus and forced the bus termination on the
>   disk itself
> 
> my crash test has been cp'ing a 200M file to another dir in the same
> filesystem, although these errors usually appear randomly a couple of times per
> hour.

These stills smell like bad termination.  Triple check it against the
manuals and the drive jumper settings, and try replacing the cable if you
haven't already.  

It may be a bum drive.  

Doug White                    |  FreeBSD: The Power to Serve
dwhite@resnet.uoregon.edu     |  www.FreeBSD.org



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




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