From owner-freebsd-current@FreeBSD.ORG Mon Mar 15 13:49:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9576F16A4CE for ; Mon, 15 Mar 2004 13:49:08 -0800 (PST) Received: from thunderbird.etv.net (thunderbird.etv.net [208.14.190.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EFA543D3F for ; Mon, 15 Mar 2004 13:49:08 -0800 (PST) (envelope-from lists@efinley.com) Received: from [205.161.203.50] (helo=science1) by thunderbird.etv.net with smtp (Exim 4.30; FreeBSD) id 1B2zxL-000C7V-Ud; Mon, 15 Mar 2004 14:49:07 -0700 Message-ID: <01f201c40ad7$56ee7110$32cba1cd@science1> From: "Elliot Finley" To: =?iso-8859-1?Q?S=F8ren_Schmidt?= References: <019001c40abb$ac2a9350$32cba1cd@science1> <4055FCB9.1040406@DeepCore.dk> Date: Mon, 15 Mar 2004 14:48:59 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-current@freebsd.org Subject: Re: reliable disk FAILURE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Elliot Finley List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2004 21:49:08 -0000 ----- Original Message ----- From: "Søren Schmidt" To: "Elliot Finley" Cc: Sent: Monday, March 15, 2004 11:58 AM Subject: Re: reliable disk FAILURE Elliot Finley wrote: > when doing a disk-to-disk backup using dump/restore, I reliably get a disk > failure. I don't think it's the disk because it happens on six different > machines. All six machines are using SATA drives. They all have an ASUS > P4P800 MB. > > None of the six machines had any problems until after the last security > patch to 5.2.1. After the patch, they all fail. If I remember correctly, > the last security patch only touched some TCP files, so the disk failures > don't make any sense to me. > > commands causing the failure, console output and dmesg are below. This is > on a test machine that I can take down or modify at any time, so if there is > anything further that I can do to help debug this - please let me know. - Does it also fail if you use the Promise channels instead ? There is NOT a failure if both drives are on the Promise controller. There is also NOT a failure if both drives are on the motherboard IF I turn off HyperThreading in the BIOS. The failure happens if both drives are on the motherboard and HyperThreading is on. Elliot