From owner-freebsd-questions Mon Nov 20 5:35:38 2000 Delivered-To: freebsd-questions@freebsd.org Received: from droid.nosc.mil (droid.nosc.mil [128.49.4.117]) by hub.freebsd.org (Postfix) with ESMTP id C051237B4CF for ; Mon, 20 Nov 2000 05:35:34 -0800 (PST) Received: from slartibartfast.nosc.mil (slartibartfast.nosc.mil [198.253.21.36]) by droid.nosc.mil (8.11.0/8.11.0) with ESMTP id eAKDWJp16171; Mon, 20 Nov 2000 05:32:19 -0800 (PST) Message-Id: <4.3.2.7.2.20001120082623.00b1fdf0@localhost> X-Sender: huck@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 20 Nov 2000 08:31:55 -0500 To: Andrew Gould From: Craig Huckabee Subject: Re: UDMA ICRC READ ERRORs Cc: freebsd-questions@freebsd.org In-Reply-To: <20001120125059.28047.qmail@web113.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew, I've got the same problem with 4.2-BETA and an AMD K6/2 500Mhz box, built with an ASUS P5A, and a Western Digital hard drive. I searched the mailing list archives and found this fix : /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio I added that line to /etc/rc near the top so it runs each time the system boots. Turns off UDMA mode, so performance suffers, but the errors go away (at least after /etc/rc runs they do, so a few may sneak in before that) I have two other 4.2 systems with the same hardware except they use Maxtor hard drives that don't have this problem. If anyone knows of a better solution, pass it along. I guess it is possible (or should be) to somehow to turn of UDMA in the kernel ? HTH, --Craig At 04:50 AM 11/20/00 -0800, you wrote: >Good morning all, > >I have installed FreeBSD 4.1 on an AMD K6/2 450MHz box >and keep getting the following error message when I >boot the computer: > >'ad0: UDMA ICRC READ ERROR blk# 4144087 retrying' >There are more messages where the blk# is different. > >At first I thought it might be the version of FreeBSD >or a hard drive problem; but I switched hard drives >and installed FreeBSD 4.0 without any improvement. >(The current hard drive is a Seagate 8G ATA66.) So I >installed 4.1 again. > >Last night, I ran fsck and rebooted. The problem went >away for a couple of test reboots; but is back again >this morning with different blk#'s. > >Does anyone have any advice regarding this matter? > >Thanks, > >Andrew Gould > >__________________________________________________ >Do You Yahoo!? >Yahoo! Calendar - Get organized for the holidays! >http://calendar.yahoo.com/ > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message ------------------------------------------------------- Craig Huckabee huck@spawar.navy.mil Systems Engineer, Compliance Corporation (843) 218 6459 SPAWAR Systems Center - Charleston, Charleston, SC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message