From owner-freebsd-stable@FreeBSD.ORG Sun May 25 07:50:50 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 0BD2D37B401 for ; Sun, 25 May 2003 07:50:50 -0700 (PDT) Received: from simmts3-srv.bellnexxia.net (simmts3-srv.bellnexxia.net [206.47.199.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC64C43F85 for ; Sun, 25 May 2003 07:50:48 -0700 (PDT) (envelope-from ellen.macisaac@ns.sympatico.ca) Received: from ns.sympatico.ca ([142.177.83.92]) by simmts8-srv.bellnexxia.netESMTP <20030525144849.MRPL5222.simmts8-srv.bellnexxia.net@ns.sympatico.ca> for ; Sun, 25 May 2003 10:48:49 -0400 Message-ID: <3ED0E77A.8060605@ns.sympatico.ca> Date: Sun, 25 May 2003 11:55:38 -0400 From: Zer0 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.74.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: UDMA 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: Sun, 25 May 2003 14:50:50 -0000 Hernani Marques Madeira wrote: > Hi@all > On Sunday 25 May 2003 09:15, David A Bestor wrote: > > >> I hit this 2 weeks ago when moving an 8gig to a 60 gig... >> I had the errors on the new 60gig. The errors went away >> when I changed the cable. It was connected on the IDE100 >> slot. I changed the cable to the proper cable for that >> slot and that fixed it. I found the answer in a google >> search. >> > > > Yes, i can confirm that. I also changed the cables & found the answer > on groups.google.com, too > If you've bought a built pc-system it often happens that the cables > are of poor quality what would result in a falling back to PIO mode. > This seems to be the effect of the low data integrity that is reached > in conjunction with those cables. > > Hernani > > Cable swapping did nothing to resolve my problem (that was the first thing I tried) I also tried setting the DMA mode manully in the BIOS ...no dice.