From owner-freebsd-stable@FreeBSD.ORG Thu Feb 16 05:05:58 2012 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEFA61065675 for ; Thu, 16 Feb 2012 05:05:58 +0000 (UTC) (envelope-from john@theusgroup.com) Received: from theusgroup.com (theusgroup.com [64.122.243.222]) by mx1.freebsd.org (Postfix) with ESMTP id B4B498FC16 for ; Thu, 16 Feb 2012 05:05:58 +0000 (UTC) To: Jeremy Chadwick In-reply-to: <20120215191931.GA30747@icarus.home.lan> References: <20120214091909.GP2010@equilibrium.bsdes.net> <20120214100513.GA94501@icarus.home.lan> <20120214135435.GQ2010@equilibrium.bsdes.net> <20120214141601.GA98986@icarus.home.lan> <20120215181757.GX2010@equilibrium.bsdes.net> <20120215191931.GA30747@icarus.home.lan> Comments: In-reply-to Jeremy Chadwick message dated "Wed, 15 Feb 2012 11:19:31 -0800." Date: Wed, 15 Feb 2012 20:48:42 -0800 From: John Message-Id: <20120216044842.282B16B9@server.theusgroup.com> Cc: Victor Balada Diaz , stable@FreeBSD.org Subject: Re: problems with AHCI on FreeBSD 8.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2012 05:05:58 -0000 Jeremy Chadwick wrote: > > CRC errors ... > >I have no real advice for tracking this kind of problem down. The most >common response is "replace cables", which isn't necessarily the root >cause. I have no advice or tips on how to track down interference >issues, or how to truly examine a disk PCB or controller PCB for the >latter item. "Flaky traces" on a PCB could cause this sort of thing. >Folks in the EE field would know more about these issues; I am not an EE >person. > >Since the attribute increased on both drives simultaneously (I have to >assume simultaneously?), it's more likely that the problem is not with >SATA cables or the drives but the controller on the motherboard. I'd >recommend replacing the motherboard. I make no guarantees this will fix >anything however, but it is the "common point" for both of your drives. This EE agrees with your advise. I would add if replacing the motherboard fails to fix the problem, then replace the power supply. Even with extremely high end test equipment, you likely would never be able to see the failure occur for at least two reasons; the most likely failure mode is inside a single IC, and adding probes would alter the environment enough to change the failure mode. John Theus TheUs Group TheUsGroup.com