From owner-freebsd-current@FreeBSD.ORG Wed Sep 7 03:56:58 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7CFD1065673 for ; Wed, 7 Sep 2011 03:56:58 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id B46698FC08 for ; Wed, 7 Sep 2011 03:56:58 +0000 (UTC) Received: from [192.168.135.110] (c-24-7-47-62.hsd1.ca.comcast.net [24.7.47.62]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id p873UnnA000323 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 6 Sep 2011 20:30:51 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4E66E564.4040301@feral.com> Date: Tue, 06 Sep 2011 20:30:44 -0700 From: Matthew Jacob User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <1922360058.114440.1315350266688.JavaMail.root@mail-01.cse.ucsc.edu> In-Reply-To: <1922360058.114440.1315350266688.JavaMail.root@mail-01.cse.ucsc.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Tue, 06 Sep 2011 20:30:51 -0700 (PDT) Subject: Re: RELENG_8 / mpt / zpool Errors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 03:56:59 -0000 On 9/6/2011 4:04 PM, Tim Gustafson wrote: > Hi all, > > I'm running RELENG_8: > > ---------- > ... > > So, is this an OS/driver issue? Is it a bad controller? Bad cables? Bad disks? > > As always, any help is greatly appreciated. Thanks! > > Likely some problem in the external box. Note that you get a 'POR' check condition- something reset out there. Possibly cables. Remotely possible firmware. Very unlikely to be an OS or driver issue.