From owner-freebsd-hardware@FreeBSD.ORG Wed Nov 16 10:57:10 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82E3416A41F for ; Wed, 16 Nov 2005 10:57:10 +0000 (GMT) (envelope-from jnury@wopr.ch) Received: from safemail.wopr-hosting.com (safemail.wopr-hosting.com [80.80.232.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 167BE43D45 for ; Wed, 16 Nov 2005 10:57:09 +0000 (GMT) (envelope-from jnury@wopr.ch) Received: by safemail.wopr-hosting.com (Postfix, from userid 107) id 6C56E94CDF5; Wed, 16 Nov 2005 11:55:36 +0100 (CET) Received: from safemail.wopr-hosting.com (localhost [127.0.0.1]) by safemail.wopr-hosting.com (Postfix) with ESMTP id 4B1DF94CDEA for ; Wed, 16 Nov 2005 11:55:36 +0100 (CET) Received: from Woprjnury (207.20.202.62.fix.bluewin.ch [62.202.20.207]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by safemail.wopr-hosting.com (Postfix) with ESMTP id 01F8694CDE9 for ; Wed, 16 Nov 2005 11:55:35 +0100 (CET) From: "WOPR, Julien Nury" To: Date: Wed, 16 Nov 2005 11:56:59 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 thread-index: AcXqlDEdshgVwr35ROevmqy8zKESfAAAHlWwAAHuhJA= X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-Id: <20051116105535.01F8694CDE9@safemail.wopr-hosting.com> X-Virus-Scanned: ClamAV Subject: TR: FreeBSD 6.0 and HighPoint RocketRAID 1520 (HPT372N) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 10:57:10 -0000 zparta@gmail.com wrote: >then you probably got a dying harddrive in your system Certainly not because : - It's the same with 2 other new drives - FreeBSD 5.4 works fine on this machine I think the problem commes from the HPT372 driver (may be not adapted to the HPT372N chipset) Regards Julien Nury