From owner-freebsd-questions@FreeBSD.ORG Tue Jan 25 21:01:53 2005 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 6E09216A4CE for ; Tue, 25 Jan 2005 21:01:53 +0000 (GMT) Received: from smtp101.rog.mail.re2.yahoo.com (smtp101.rog.mail.re2.yahoo.com [206.190.36.79]) by mx1.FreeBSD.org (Postfix) with SMTP id D382143D31 for ; Tue, 25 Jan 2005 21:01:52 +0000 (GMT) (envelope-from derekm.nospam@rogers.com) Received: from unknown (HELO chesed.razorfever.net) (plick@rogers.com@70.25.112.61 with plain) by smtp101.rog.mail.re2.yahoo.com with SMTP; 25 Jan 2005 21:01:52 -0000 Received: from [192.168.0.201] ([192.168.0.201])j0PL1pnA045475 for ; Tue, 25 Jan 2005 16:01:51 -0500 (EST) (envelope-from derekm.nospam@rogers.com) Message-ID: <41F6B3CC.1060802@rogers.com> Date: Tue, 25 Jan 2005 16:02:04 -0500 From: Derek User-Agent: Mozilla Thunderbird 1.0 (X11/20050112) X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.70, clamav-milter version 0.70j Subject: Re: READ_DMA timed out on Promise FastTrak100 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: Tue, 25 Jan 2005 21:01:53 -0000 list@mindling.com wrote: > However, when I boot FreeBSD, the system reports READ_DMA errors on the > second drive, and the array reports a degraded state. I can still mount > it, and both drive lights flash when accessing the volume. Googling returns a lot of information relating to hardware: http://www.google.ca/search?q=%22FAILURE+-+READ_DMA%22+freebsd > I was originally running 5.3-RELEASE-p5 (SMP, dual P3). I built and > booted 5.3-STABLE SMP, and although everything else looks fine, the > READ_DMA error is unchanged. I have verified the seating of cables and > cards. > > Does anyone have any pointers? What else should I try? > Thanks in advance. My suggestions would begin with replacing your cables (obviously with UDMA100-style/80-conductor)... I know the promise cables have that nifty "PROMISE" branded ribbon that looks like one is supposed to use to remove the cable from the drive, but I've seen that thing cause some trouble (like ruining the drive connectors). Failing that, if you can take the drive out of the machine (new cable, new card, new system), and run the manufacture's _extensive_ drive tests on it, I think you'll find all is not well. Cheers, Derek