From owner-freebsd-questions@FreeBSD.ORG Thu Apr 21 20:04:14 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 6361116A4CE for ; Thu, 21 Apr 2005 20:04:14 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE9F943D1F for ; Thu, 21 Apr 2005 20:04:13 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1109.wanadoo.fr (SMTP Server) with ESMTP id 8636D1C000BC for ; Thu, 21 Apr 2005 22:04:12 +0200 (CEST) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1109.wanadoo.fr (SMTP Server) with ESMTP id 62C361C000B5 for ; Thu, 21 Apr 2005 22:04:12 +0200 (CEST) X-ME-UUID: 20050421200412404.62C361C000B5@mwinf1109.wanadoo.fr Date: Thu, 21 Apr 2005 22:04:12 +0200 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <193906655.20050421220412@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: <1212701106.20050421194847@arax.md> References: <1212701106.20050421194847@arax.md> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: WRITE_DMA problem again X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 20:04:14 -0000 arax writes: > I was just wondering if there's a solution to fix the WRITE_DMA problem. I've > searched the archives but couldn't find a complete answer to this, > like why it's happening and what to do about it. I'd appreciate any help. I had the same problem (same logical device, in fact, and also on FreeBSD 5.3) and it turned out to be a bad drive. I was able to verify this by downloading the vendor's standalone test software, booting it on the server, and running exhaustive tests against the drive. On the full test, the software hung (whereas it worked fine on the other, identical drive that I had configured on the system). Since this was a bootable disk and FreeBSD wasn't even in the system, this ruled out FreeBSD. I reluctantly replaced the drive (which was only 60 days old or so) with an identical model, and I've had no problems since. > It seems that this doesn't do any harm to my system, but I'm not sure > because at this time the system is under no load at all. These errors just > appear from time to time. I would like to fix this before I move the > server into production. The problem eventually corrupted some structure on my drive, but apparently the system was able to recover most of it. The drive worked well enough to allow me to run full backups before replacing it. Fortunately, there wasn't much on it. If your disk vendor offers bootable test software, download that and test the drive exhaustively offline. If it fails or hangs, you have your answer: replace the drive. If it passes with flying colors, then you'll have to look back to FreeBSD. -- Anthony