From owner-freebsd-questions@FreeBSD.ORG Mon Nov 8 12:57:54 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68A6616A4CE for ; Mon, 8 Nov 2004 12:57:54 +0000 (GMT) Received: from moghedien.mukappabeta.net (moghedien.mukappabeta.net [194.145.150.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 170CC43D46 for ; Mon, 8 Nov 2004 12:57:54 +0000 (GMT) (envelope-from mkb@mukappabeta.de) Received: from [192.168.2.11] (pD95421C9.dip.t-dialin.net [217.84.33.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by moghedien.mukappabeta.net (Postfix) with ESMTP id 237982D72; Mon, 8 Nov 2004 13:53:32 +0100 (CET) Message-ID: <418F6D6E.5040102@mukappabeta.de> Date: Mon, 08 Nov 2004 13:58:22 +0100 From: Matthias Buelow User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.7.3) Gecko/20041022 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: craig@small-pla.net References: <002301c4c57f$ec9e43d0$6500a8c0@jupiter> In-Reply-To: <002301c4c57f$ec9e43d0$6500a8c0@jupiter> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: error installing 5.3-stable - WRITE_DMA X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 12:57:54 -0000 craig wrote: > out of desperation, i'm going to install a linux distro that i happen to > have found laying about (as only linux disks can...) > if it installs fine, then i would assume that the *hardware* is fine and > that the problem must lie with fBSD. > is that a fair assumption? have a look at dmesg when linux has booted. I've had a similar condition when the freebsd sysinstall would abort with the ICRC error, and linux booted, but when I looked into dmesg linux noted the exact same error, only didn't consider it fatal. it only occured once at boot anyways. nevertheless, I'd first check the UDMA cable (is it a proper 80-conductor one?) and the disk's power cable (loose contact?) -- Matthias Buelow; mkb@{mukappabeta,informatik.uni-wuerzburg}.de