From owner-freebsd-hardware@FreeBSD.ORG  Thu Jun 28 07:06:02 2007
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: freebsd-hardware@freebsd.org
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id F41E116A46B
	for <freebsd-hardware@freebsd.org>;
	Thu, 28 Jun 2007 07:06:01 +0000 (UTC)
	(envelope-from patpro@patpro.net)
Received: from smtp.univ-lyon2.fr (smtp.univ-lyon2.fr [159.84.143.102])
	by mx1.freebsd.org (Postfix) with ESMTP id B5E7D13C45D
	for <freebsd-hardware@freebsd.org>;
	Thu, 28 Jun 2007 07:06:01 +0000 (UTC)
	(envelope-from patpro@patpro.net)
Received: from localhost (localhost [127.0.0.1])
	by smtp.univ-lyon2.fr (Postfix) with ESMTP
	id 18D543A720CC; Thu, 28 Jun 2007 08:44:26 +0200 (CEST)
X-Virus-Scanned: amavisd-new at univ-lyon2.fr
Received: from smtp.univ-lyon2.fr ([127.0.0.1])
	by localhost (smtp.univ-lyon2.fr [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GYfQ0jPtlsmU; Thu, 28 Jun 2007 08:44:24 +0200 (CEST)
Received: from [159.84.148.60] (patpro.univ-lyon2.fr [159.84.148.60])
	by smtp.univ-lyon2.fr (Postfix) with ESMTP
	id ACE473A720C5; Thu, 28 Jun 2007 08:44:24 +0200 (CEST)
In-Reply-To: <20070627214300.319cbe41@soralx>
References: <7D3EA7E7-CF83-4385-A8FC-611B886CC7E3@patpro.net>
	<20070627214300.319cbe41@soralx>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5F2FFD72-768A-44E0-933B-87E725491E79@patpro.net>
Content-Transfer-Encoding: 7bit
From: Patrick Proniewski <patpro@patpro.net>
Date: Thu, 28 Jun 2007 07:38:05 +0200
To: freebsd-hardware@freebsd.org
X-Mailer: Apple Mail (2.752.2)
Cc: 
Subject: Re: hardware/driver incompatibility ?
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: General discussion of FreeBSD hardware <freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2007 07:06:02 -0000


On 28 juin 07, at 06:43, <soralx@cydem.org> wrote:

>> Is there any way I could test my HD to detect/prevent failure ?
>
> install smartmontools from ports
> then: smarctl -t long /dev/ad4
> after a couple hours check status: smartctl -a /dev/ad4

I've tested the disk after the crash with smartmontools (long,  
short, ...), but nothing, no error. But I know a passed SMART test  
does not mean anything.


> Western Digital harddisks are notoriously unreliable (I just had 2
> WD5000YS fail recently, at about the same time; one had ~200 hrs on  
> it,
> the other ~1700h), especially the YS models. Also, WDC won't replace
> them... Beware.

argh, crap. Too bad Maxtor Maxline III drives where not available at  
the time I bought all this hardware.

thanks,
patpro