Date: Wed, 26 May 1999 16:32:55 -0700 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>, "Eric D. Fehr" <fehr@idirect.com> Cc: scsi@FreeBSD.ORG Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 Message-ID: <199905262332.QAA09141@salsa.gv.tsc.tdk.com> In-Reply-To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com> "Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2" (May 26, 4:42pm)
next in thread | previous in thread | raw e-mail | index | archive | help
On May 26, 4:42pm, "Justin T. Gibbs" wrote: } Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 } In article <Pine.BSF.4.10.9905261601550.60127-100000@proteus.idirect.com> 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. ... such as power quality or vibration. 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?199905262332.QAA09141>