From owner-freebsd-questions Fri Feb 14 10:20:22 2003 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 4078637B401 for ; Fri, 14 Feb 2003 10:20:21 -0800 (PST) Received: from mailhost.det2.ameritech.net (mailhost1-sfldmi.sfldmi.ameritech.net [206.141.193.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AF9743FDD for ; Fri, 14 Feb 2003 10:20:20 -0800 (PST) (envelope-from dbailey27@ameritech.net) Received: from ameritech.net ([67.38.15.139]) by mailhost.det2.ameritech.net (InterMail vM.4.01.02.17 201-229-119) with ESMTP id <20030214182019.NGXT8853.mailhost.det2.ameritech.net@ameritech.net>; Fri, 14 Feb 2003 13:20:19 -0500 Message-ID: <3E4D333B.5070705@ameritech.net> Date: Fri, 14 Feb 2003 13:19:39 -0500 From: northern snowfall User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: Bill Moran Cc: Henrik W Lund , freebsd-questions@FreeBSD.ORG Subject: Re: Hard error?? References: <3E4D316C.5040706@potentialtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I used to get this error on a FreeBSD while using a perfectly stable harddrive. That harddrive is managed via Solaris now, but, I determined the issue during its FreeBSD usage was DMA. If you are running two disks on the same ATA channel with different DMA capabilities, the capabilities may be causing scrambles in the negotiation of I/O on the line. The solution is to put ATA drives that use _only_ the same DMA caps on the same ATA channel. If you only have two drives, simply put ATA0.1 on ATA1.0. This stopped my "falling back to PIO" messages and probably saved the disk from hard failure caused by misuse. Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message