From owner-freebsd-questions Mon May 12 01:33:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA06416 for questions-outgoing; Mon, 12 May 1997 01:33:34 -0700 (PDT) Received: from krondor.cpn.org.au (slip3.tas.gov.au [147.109.237.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA06411 for ; Mon, 12 May 1997 01:33:27 -0700 (PDT) Received: from krondor.cpn.org.au (krondor.cpn.org.au [172.16.1.1]) by krondor.cpn.org.au (8.8.3/8.8.3) with SMTP id SAA17798 for ; Mon, 12 May 1997 18:32:32 GMT Date: Mon, 12 May 1997 18:32:32 +0000 () From: Carey Nairn X-Sender: cpn@krondor.cpn.org.au To: questions@FreeBSD.ORG Subject: Re: Western Digital Enterprise SCSC drive problems In-Reply-To: <3.0.32.19970512170945.007640f0@falcon.pacit.tas.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 12 May 1997, Carey Nairn wrote: > greetings all, > > I have a small problem with som WD SCSI drives and was wondering if there > are any known problems with them or any advice you could give me. > > I have 3 of these drives connected to an Adaptec 2940AU controller and > trying to install 2.2.1R. During the boot sequence the SCSI BIOS gets the > drives OK but when the FreeBSD probes start I get the following errors... > > ahc0 rev 1 int a irq 10 on pci0:16 > ahc0: aic7860 Single channel, SCSI Id-7, 3 SCBs > ahc0 board is not responding > (ahc0:0:0): SCB 0x0 - timedout in datain phase, SCSISIGI==0x46 > SEQADDR==0x12c > (ahc0:0:0): abort message in message buffer > ahc0 board is not responding > (ahc0:0:0): SCB 0x2 - timedout while recovery in progress > (ahc0:0:0): "unknown unknown ????" type 13 fixed SCSI 0 > uk0 unknown device > ..... > > Do I have 3 dodgy drives ?? > any clues, help or otherwise would be appreciated. > Thanks in advance > > cheers, > Carey Nairn > I should also have mentioned... I tested the setup with a known good drive (one that already had 2.2.1R installed) and everything worked fine. This really points at the drive IMHO. I have also tried varios jumper settings on the WD drives to no avail. thanks again Carey Nairn