From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 18:43:49 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BDFC177B for ; Thu, 3 Apr 2014 18:43:49 +0000 (UTC) Received: from mail.lifanov.com (mail.lifanov.com [206.125.175.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A2D17FCA for ; Thu, 3 Apr 2014 18:43:49 +0000 (UTC) Received: by mail.lifanov.com (Postfix, from userid 58) id 4DD001AF7F8; Thu, 3 Apr 2014 14:43:49 -0400 (EDT) Received: from [10.1.3.5] (cnet520-windstream.mcclatchyinteractive.com [166.108.16.2]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.lifanov.com (Postfix) with ESMTPSA id 6AB4E1A0071; Thu, 3 Apr 2014 14:43:48 -0400 (EDT) Message-ID: <533DABE2.7080705@mail.lifanov.com> Date: Thu, 03 Apr 2014 14:43:46 -0400 From: Nikolai Lifanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Ryan Stone , Benjamin Kaduk Subject: Re: Boot fails @r264070 References: <20140403160031.GD30431@albert.catwhisker.org> <20140403162127.GE30431@albert.catwhisker.org> <533DA790.5050802@mail.lifanov.com> In-Reply-To: <533DA790.5050802@mail.lifanov.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Thu, 03 Apr 2014 18:43:49 -0000 On 04/03/14 14:25, Nikolai Lifanov wrote: > On 04/03/14 14:05, Ryan Stone wrote: >> Can somebody please confirm whether setting hw.pci.enable_ari=0 in the >> loader fixes the issue or not. That will help me to figure out if the >> issue is with ARI or if I have somehow broken PCI enumeration in >> general (I suspect the later). >> __________________ > > I already tried it. > I can confirm that it does not help. > > - Nikolai Lifanov > In fact, here is what it looks like: the disk discovery skips the first 2 and enumerates the rest. Thankfully, this isn't my boot pool and rebooting without ARI changes discovers every disk and imports it correctly. $ sysctl hw.pci.enable_ari hw.pci.enable_ari: 0 $ zpool status data pool: data state: UNAVAIL status: One or more devices could not be opened. There are insufficient replicas for the pool to continue functioning. action: Attach the missing device and online it using 'zpool online'. see: http://illumos.org/msg/ZFS-8000-3C scan: none requested config: NAME STATE READ WRITE CKSUM data UNAVAIL 0 0 0 mirror-0 UNAVAIL 0 0 0 820204606399244410 UNAVAIL 0 0 0 was /dev/ada0 7129954888383586426 UNAVAIL 0 0 0 was /dev/ada1 mirror-1 ONLINE 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 - Nikolai Lifanov