From owner-freebsd-questions@FreeBSD.ORG Sat Jan 14 23:45:29 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 1A0BA16A41F for ; Sat, 14 Jan 2006 23:45:29 +0000 (GMT) (envelope-from list@mindling.com) Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9246A43D46 for ; Sat, 14 Jan 2006 23:45:28 +0000 (GMT) (envelope-from list@mindling.com) Received: from [10.0.0.11] (64-142-39-120.dsl.static.sonic.net [64.142.39.120]) (authenticated bits=0) by a.mail.sonic.net (8.13.3/8.13.3) with ESMTP id k0ENjSGl021582 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sat, 14 Jan 2006 15:45:28 -0800 Message-ID: <43C98D1A.8030909@mindling.com> Date: Sat, 14 Jan 2006 15:45:30 -0800 From: Sebastian User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 CC: freebsd References: <43C96C73.9010904@mindling.com> <0T2rehckIn3Nv9%markus@bsd.trippelsdorf.de> <43C97BE6.5060901@mindling.com> In-Reply-To: <43C97BE6.5060901@mindling.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Getting around WRITE_DMA errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jan 2006 23:45:29 -0000 Sebastian wrote: > Markus Trippelsdorf wrote: > >> Are you sure that your hard drive is not dying? Run smartctl -a >> /dev/ad0 and see if any errors were being logged. >> (smartctl is part of the smartmontools port) >> You should also try another cable. >> >> > Thanks for the response. I'm reasonably sure, the disk is brand new, > and though it could certainly be bad, I installed Linux on the system > this morning without issue. I've tried two different UDMA cables also, > just to be sure. Under PIO4 mode in BSD (by setting hw.ata.ata_dma=0), > I can install and then write data to my heart's content without any > errors. > > I'm currently reinstalling again, because I believe a partition has > become corrupted after panicking with the disk in UDMA6 mode. > Just as a followup: Attempting to run "atacontrol mode ad0 UDMA6" resulted in WRITE_DMA48 errors and a panic. Afterwards, disk access was slow, and trying to use _any_ UDMA mode resulted in DMA errors being logged, and eventually another panic. Having briefly tested UDMA3-5 with success previously, I felt that the partitions must have been corrupted somehow, so I reinstalled FreeBSD from scratch. It's better, after booting with "hw.ata.ata_dma=0" and then running "atacontrol mode ad0 UDMA5", it's running fine using UDMA5 and copying lots of data around: # atacontrol mode ad0 current mode = UDMA100 So my question remains: How do I tell FreeBSD to use UDMA5 on this drive at boot-time? Thanks.