From owner-freebsd-questions@FreeBSD.ORG Sat Apr 1 01:47:56 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 633A016A401 for ; Sat, 1 Apr 2006 01:47:56 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1B7043D45 for ; Sat, 1 Apr 2006 01:47:55 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 14289 invoked from network); 1 Apr 2006 11:47:55 +1000 Received: from 210-84-32-140.dyn.iinet.net.au (HELO localhost) (210.84.32.140) by petreafellows.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Apr 2006 11:47:55 +1000 Date: Sat, 1 Apr 2006 11:47:52 +1100 From: Norberto Meijome To: "Wil Hatfield" Message-ID: <20060401114752.2cb0af14@localhost> In-Reply-To: References: <200603311834.19476.mistry.7@osu.edu> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.16; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: ATA Drive Issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Apr 2006 01:47:56 -0000 On Fri, 31 Mar 2006 15:43:35 -0800 "Wil Hatfield" wrote: > Ok I am just nervous about going to 6.x and putting these customers > through this not once more, but twice when I have to go back to 4.x. Sorry for asking the obvious, but why not try with 6 without any customers on the servers? putting new hardware/software straight into production seems to me like looking for troubles. Anyway, back to the problem at hand, just because they ARE new doesn't mean the cables/drives are NOT bad. Granted, that many drives in a bad state would be weird...but not really if they are from the same manufacturer's batch. smartmon clearing them would suggest that it's cabling issue. seriously, TRYING new good quality cables from a different provider can't be that hard/expensive? alternatively, try different BIOS version. usually a new version of the bIOS fixes problems. BUT I have a server (dual amd64 TYAN box, 2x SATA-I controllers with 4 SATA-II drives) which would simply not boot with a newer version of the bios, so I left it at the original BIOS (yes, keep backups of your BIOS upgrades! :-) . FWIW, 6 is better than 5.4, at least for me. good luck, Beto