From owner-freebsd-stable@FreeBSD.ORG Wed Jun 25 16:45:27 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19FC437B401 for ; Wed, 25 Jun 2003 16:45:27 -0700 (PDT) Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.136.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CCDE4401E for ; Wed, 25 Jun 2003 16:45:26 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from rushlight (allbery@allbery.dsl.telerama.com [205.201.8.182]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h5PNjB418930; Wed, 25 Jun 2003 19:45:11 -0400 (EDT) From: "Brandon S. Allbery " KF8NH To: "Julian C. Dunn - Lists" In-Reply-To: <1056584104.2749.333.camel@jupiter.acf.aquezada.com> References: <87wufbq5m4.fsf@inf.enst.fr> <20030624094553.GA26124@rot13.obsecurity.org> <001d01c33b64$5cede9d0$0301a8c0@mrwinslows> <1056584104.2749.333.camel@jupiter.acf.aquezada.com> Content-Type: text/plain Organization: Message-Id: <1056584715.49075.4.camel@rushlight.kf8nh.apk.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 25 Jun 2003 19:45:15 -0400 Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: ICRC error? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2003 23:45:27 -0000 On Wed, 2003-06-25 at 19:35, Julian C. Dunn - Lists wrote: > > Now what does this mean? > > I also wonder why it says that it found ad2 as UDMA100 since it is actually > > an UDMA33 disk? > > Euh... which one is your new disk? It would seem to me that the 60GB > drive i.e. ad0 is the newer one? Unless you're in the habit of buying > disks that are smaller than your existing setup. In any case, according > to Seagate > (http://www.seagate.com/support/disc/specs/ata/st340016a.html) your ad2 > drive *IS* UDMA100. > > But it sounds like the disk is bad. I usually get these errors when the > drive is dying. ICRC is "interface CRC", as opposed to data CRC; if you're getting only ICRC errors and not data CRC errors, it usually points to bad cabling, *not* to a bad disk. I suggest you make sure you're using an ATA100-rated cable and that the total cable length is within ATA100 limits. -- brandon s allbery [openafs/solaris/japh/freebsd] allbery@kf8nh.apk.net system administrator [linux/heimdal/too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university [better check the oblivious first -ke6sls]