From owner-freebsd-questions Mon Nov 12 5:47:16 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 0FEDA37B405 for ; Mon, 12 Nov 2001 05:47:11 -0800 (PST) Received: from colt.ncptiddische.net (ppp-194.wobline.de [212.68.69.205]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fACDksr05002; Mon, 12 Nov 2001 14:46:54 +0100 Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fACDlFV13682; Mon, 12 Nov 2001 14:47:15 +0100 (CET) (envelope-from nils@tisys.org) Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by jodie.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fACDlTV02501; Mon, 12 Nov 2001 14:47:30 +0100 (CET) (envelope-from nils@tisys.org) Date: Mon, 12 Nov 2001 14:47:29 +0100 (CET) From: Nils Holland To: Josh Paetzel Cc: chia an , Subject: Re: UDMA ICRC error In-Reply-To: <20011112070019.E723@twincat.vladsempire.net> Message-ID: <20011112144146.Y2393-100000@jodie.ncptiddische.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 12 Nov 2001, Josh Paetzel wrote: > On Sun, Nov 11, 2001 at 08:21:38PM -0800, chia an wrote: > > hello friend_bsd; > > 1 .i have a problem when booting my Freebsd 4.4, there > > was an error appear like this : > > > > ad0s3a : UDMA ICRC error reading fsbn 1606628 of 64-79 > > (ad0s3 bn 1606628; cn 100 tn 2 sn 2 ) retrying > > ad0s3a : UDMA ICRC error reading fsbn 1606628 of 64-79 > > (ad0s3 bn 1606628; cn 100 tn 2 sn 2 ) retrying > > ad0s3a : UDMA ICRC error reading fsbn 1606628 of 64-79 > > (ad0s3 bn 1606628; cn 100 tn 2 sn 2 ) falling back to > > PIO mode > > > > what should i do? > > This looks like you have a bad cable perhaps. Does the disk seem to > work ok after these errors come up? It could also be an indication > that your disk is dying. I'd like to add a comment about this, as I just had it happen here the other day as well. In short, I had two HDDs connected to the primary IDE port. When heavy read access took place on the slave HDD, the above error message tended to appear. It didn't seem to be connected to reading any particular file, as the error seemed to appear totally random. As a solution, I put one HDD on the secondary IDE port, and ever since then the problem has gone away. I'm pretty sure that this must be some issue with the (somewhat dated) mainboard I'm using. Generally, it should be possible to put two HDDs on the same IDE port, but bad cables, flawed mainboards and certain HDDs may cause trouble, although this probably happens only very rarely. I would recommend experimenting with the cabling as well as switching IDE ports in order to track this problem down. If it doesn't want to go away, the HDD should be tried in a different system, and if it still behaves strange, it's probably indeed about to die. In that case, make a backup as long as you still can and then try to get a new drive. Greetings Nils Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message