From owner-freebsd-questions@FreeBSD.ORG Mon Mar 1 12:06:40 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 8275816A4CE for ; Mon, 1 Mar 2004 12:06:40 -0800 (PST) Received: from mail.discoveringmontana.com (unknown [206.127.77.211]) by mx1.FreeBSD.org (Postfix) with SMTP id CDCDA43D2D for ; Mon, 1 Mar 2004 12:06:39 -0800 (PST) (envelope-from benny@discoveringmontana.com) Received: (qmail 18177 invoked from network); 1 Mar 2004 20:05:19 -0000 Received: from unknown (HELO powder.discoveringmontana.com) (10.0.20.62) by 0 with SMTP; 1 Mar 2004 20:05:19 -0000 From: Benny Helms Organization: Montana Interactive To: freebsd-questions@freebsd.org Date: Mon, 1 Mar 2004 13:06:35 -0700 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403011306.35364.benny@discoveringmontana.com> Subject: ahc0: Data Parity Error Detected during address or write data phase 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, 01 Mar 2004 20:06:40 -0000 3 days ago, my VA Linux server running FreeBSD 4.4-RELEASE began filling my logs with the following messages: ahc0: Data Parity Error Detected during address or write data phase ahc1: PCI error Interrupt at seqaddr = 0x9 ahc1: Data Parity Error Detected during address or write data phase ahc1: PCI error Interrupt at seqaddr = 0x9 A google search shows a lot of questions, but no real answers. At one point, during a reboot, one of the three SCSI drives that are RAID-5 showed a red light, which went away after shutting the server back down, taking canned air to any dust in the machine (including pulling out the hard drives, blowing out their slots, and reseating them). Because of that red light, I decided to put my spare drive into play where the suspect drive had resided. Took over an hour for the raid software to rebuild the new drive, and when it rebooted, the error messages resumed immediately. Does anybody know what this error is indicating? I'd really like to fix this. Thanks! Xitron