From owner-freebsd-scsi Wed May 26 16: 3: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from proteus.idirect.com (proteus.idirect.com [207.136.80.19]) by hub.freebsd.org (Postfix) with ESMTP id 09A0314DE8 for ; Wed, 26 May 1999 16:02:47 -0700 (PDT) (envelope-from fehr@idirect.com) Received: from localhost (fehr@localhost) by proteus.idirect.com (8.9.3/8.9.3) with ESMTP id TAA63340; Wed, 26 May 1999 19:02:41 -0400 (EDT) Date: Wed, 26 May 1999 19:02:41 -0400 (EDT) From: "Eric D. Fehr" To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 In-Reply-To: <199905262242.QAA03657@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After switching the drives from the Ultra2 channel to an Ultra channel (to force them to run at 40/20), they are giving errors related to dscheck. What exactly is a negative b_blkno? I've found the section of code in the kernel that this is generated by, but it isn't extremely obvious to me what exactly causes it. dsckeck: negative b_blkno -1873515648 I'll give Quantum a call and see what they have to say, as this has happened on at least 4 drives of the same model number, with two different firware versions. Thanks, Eric On Wed, 26 May 1999, Justin T. Gibbs wrote: > In article you wrote: > > Has anyone else experienced ongoing hardware read errors with this > > configuration? > > > > We're getting it with four different drives (same model), 3 different SCSI > > cables (running at 80MB/second), 3 different motherboards (Gigabyte and > > ASUS, Adaptec 7890 controller), 3 different terminators (active), and it > > is really starting to annoy me: > > > > (da1:ahc0:0:1:0): READ(10). CDB: 28 0 1 b8 11 f 0 0 80 0 > > (da1:ahc0:0:1:0): MEDIUM ERROR info:1b8117c csi:18,21,58,1d asc:11,0 > > (da1:ahc0:0:1:0): Unrecovered read error sks:80,98 > > CAM is only reporting what the drive has told us. This is not > a cable or termination or problem, but I suppose it could be a > drive firmware bug. There's very little anyone but the device > can do about reading the physical media and that is what the > complaint is about. > > Call Quantum tech support and give them the asc/ascq pair for the > error (11, 0) that the drive is reporting. New devices should not > be constanly reporting read errors unless you have a heat or other > environment problem. > > -- > Justin > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message