From owner-freebsd-stable@FreeBSD.ORG Thu Feb 9 18:37:07 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A149A106564A; Thu, 9 Feb 2012 18:37:07 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 5EFC08FC13; Thu, 9 Feb 2012 18:37:07 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.5/8.14.4) with ESMTP id q19Ib4cw067513; Thu, 9 Feb 2012 13:37:04 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4F34124F.9090808@sentex.net> Date: Thu, 09 Feb 2012 13:37:03 -0500 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Jeremy Chadwick References: <4F32E289.4080806@sentex.net> <4F32F5B0.2060203@FreeBSD.org> <20120208223819.GA27488@icarus.home.lan> <4F32FB5E.7050102@FreeBSD.org> <4F33DB75.1080202@sentex.net> <20120209152240.GA95470@icarus.home.lan> <4F33F056.6070300@sentex.net> <20120209163415.GA96451@icarus.home.lan> In-Reply-To: <20120209163415.GA96451@icarus.home.lan> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.71 on IPv6:2607:f3e0:0:1::12 Cc: Alexander Motin , freebsd-stable@FreeBSD.org Subject: Re: siisch1: Error while READ LOG EXT 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, 09 Feb 2012 18:37:07 -0000 On 2/9/2012 11:34 AM, Jeremy Chadwick wrote: > > You will probably need to "track these drives" on a regular basis. That > is to say, set up some cronjob or similar that logs the above output to > a file (appends data to it), specifically output from smartctl -A (not > -a and not -x) and smartctl -l sataphy on a per-disk basis. smartd can > track SMART attribute changes, but does not track GPLog changes. Make > sure to put timestamps in your logs. Thanks very much for having a look, and the suggestions. It think this is the way to go to see which drive my have errors incrementing. Alexander, is there a better way you can suggest ? > > As for fixing the problem: I have no idea how you would go about this. > Use of port multipliers involves additional cables, possibly of shoddy > quality, or other components which may not be decent/reliable. Possibly. Cables are one of those things I am happy to "pay extra for better quality" but how does one assess quality of such parts. > > Overall, this is just one of the many reasons why I avoid PMs, as well > as avoid eSATA (especially eSATA). Yeah, at some point it doesnt really work with too many PMs, especially if you cant query the thing to find out where things are "bad". I think for the next version of this box I will use the newer generation 3ware SAS/SATA controller ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/