From owner-freebsd-current Sun Jan 23 23:29:13 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 DDA5B152AD for ; Sun, 23 Jan 2000 23:29:09 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA19777; Mon, 24 Jan 2000 08:29:03 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001240729.IAA19777@freebsd.dk> Subject: Re: D?ISK I/O erros In-Reply-To: <388A3FC7.79D6B082@netquick.net> from TrouBle at "Jan 22, 2000 06:39:51 pm" To: trouble@netquick.net Date: Mon, 24 Jan 2000 08:29:03 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG (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 TrouBle wrote: > this is a brand new 10gig UDMA 66 maxtor.... is this a disk problem via > hardware, or is it a BSD issue with the new code ??? > angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 7801951 retrying The driver is telling you that the transfers CRC check are not valid and it is retrying the transfer. This can be due to many things: Bad cableing, cable too near field generating devices in the machine, bad disk, bad controller, bad driver... Mostly though this is due to one of the two first items. > ad0: ATA-5 disk at ata0 as master > ad0: 9770MB (20010816 sectors), 19852 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, UDMA33 I need a full verbose bootlog (dmesg) before I can give you any more diagnostic on this.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message