From owner-freebsd-current Mon Apr 3 11:50:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 9E51137BE8E for ; Mon, 3 Apr 2000 11:50:02 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA21201; Mon, 3 Apr 2000 20:49:46 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004031849.UAA21201@freebsd.dk> Subject: Re: HighPoint UDMA66 ICRC READ ERROR In-Reply-To: <38E8DF04.7BCC5EBE@usishealth.com> from Erik de Zeeuw at "Apr 3, 2000 01:12:20 pm" To: erik@usishealth.com (Erik de Zeeuw) Date: Mon, 3 Apr 2000 20:49:46 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Erik de Zeeuw wrote: > atapci1: port \ > 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 \ > irq 11 at device 19.0 on pci0 > ata2: at 0xb000 on atapci1 > atapci2: port \ > 0xc400-0xc4ff,0xc000-0xc003,0xbc00-0xbc07 \ > irq 11 at device 19.1 on pci0 > ... > ad4: 19574MB [39770/16/63] at ata2-master using UDMA66 > > gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39566319 retrying > gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39627167 retrying > gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39628463 retrying This means that the system has problems getting data correctly over the interface from disk to controller, in most cases its a cable problem. Are you using the right 80pin ata66 cable for this ? is it at max 18" long ? Another thing is that if you have the cable running close to something like the PSU coils on most modern motherboards, that might cause trouble too... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message