From owner-freebsd-questions  Sun Nov 11 20:58:52 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from nyc.rr.com (nycsmtp2fb.rdc-nyc.rr.com [24.29.99.78])
	by hub.freebsd.org (Postfix) with ESMTP id 4217A37B405
	for <questions@freebsd.org>; Sun, 11 Nov 2001 20:58:50 -0800 (PST)
Received: from asa.localdomain ([24.168.25.8]) by nyc.rr.com  with Microsoft SMTPSVC(5.5.1877.357.35);
	 Sun, 11 Nov 2001 23:58:47 -0500
Date: Mon, 12 Nov 2001 00:09:20 -0500
From: Scott <scottro@nyc.rr.com>
To: chia an <alan_qc@yahoo.com>
Cc: questions@FreeBSD.ORG
Subject: Re: UDMA ICRC error
Message-Id: <20011112000920.05b35a71.scottro@nyc.rr.com>
In-Reply-To: <20011112042138.87131.qmail@web13505.mail.yahoo.com>
References: <20011109173127.X3281@roman.mobil.cz>
	<20011112042138.87131.qmail@web13505.mail.yahoo.com>
X-Mailer: Sylpheed version 0.6.2 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

On Sun, 11 Nov 2001 20:21:38 -0800 (PST)
chia an <alan_qc@yahoo.com> 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? 


I've had the same problem on different machines.  There are different solutions
1. It could mean that your hard drive is going bad.  FreeBSD seems more sensitive to this than some other O/S's to it.
2. It can sometimes be fixed by changing to a better quality IDE cable
3. It can sometimes be fixed by changing (I only know how to do this with a particular drive's vendor's downloadable utility) UDMA from 66 to 33
4. You can simply tell the machine not to try UDMA mode with sysctl.conf (though I'm not quite sure how to do this--I did a search on deja and the results were conflicting with each other.

Lastly, it can, it seems often be ignored without any real problems.
HTH a little
Scott Robbins

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message