Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Mar 2004 14:48:59 -0700
From:      "Elliot Finley" <lists@efinley.com>
To:        =?iso-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk>
Cc:        freebsd-current@freebsd.org
Subject:   Re: reliable disk FAILURE
Message-ID:  <01f201c40ad7$56ee7110$32cba1cd@science1>
References:  <019001c40abb$ac2a9350$32cba1cd@science1> <4055FCB9.1040406@DeepCore.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- 
From: "Søren Schmidt" <sos@DeepCore.dk>
To: "Elliot Finley" <lists@efinley.com>
Cc: <freebsd-current@freebsd.org>
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01f201c40ad7$56ee7110$32cba1cd>