From owner-freebsd-fs@FreeBSD.ORG Thu Apr 4 16:46:44 2013 Return-Path: Delivered-To: fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2B80BD08; Thu, 4 Apr 2013 16:46:44 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 422C7FF0; Thu, 4 Apr 2013 16:46:42 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA11146; Thu, 04 Apr 2013 19:46:40 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <515DAE70.6090502@FreeBSD.org> Date: Thu, 04 Apr 2013 19:46:40 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130313 Thunderbird/17.0.4 MIME-Version: 1.0 To: Jay Borkenhagen Subject: Re: mounting failed with error 2 References: <20825.59038.104304.161698@oz.mt.att.com> <5159F0C9.9000302@FreeBSD.org> <20825.62329.379765.344231@oz.mt.att.com> <515DA43D.7070805@FreeBSD.org> <20829.44475.910011.453770@oz.mt.att.com> In-Reply-To: <20829.44475.910011.453770@oz.mt.att.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: fs@FreeBSD.org, Niclas Zeising X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Apr 2013 16:46:44 -0000 on 04/04/2013 19:43 Jay Borkenhagen said the following: > Hi Andriy, > > Thanks for your response. > > Andriy Gapon writes: > > > > My first suggestion would be to try an image with recent stable/9 > > if you can find or produce it. > > A large part of my interest here is in helping Niclas perfect his > GPT/ZFS installation instructions, so I'll not pursue the stable/9 > approach at this time. (I have two GPT/ZFS systems running > 9.1-RELEASE based on earlier instructions from Niclas, so if I > absolutely need another such system now I do have a way to get there.) > > > > Failing that, you can set vfs.zfs.debug=1 at loader prompt before > > booting. That could shed some light on what is going wrong. The > > most likely possibility is that /boot/zfs/zpool.cache in the > > boot/root filesystem of the boot/root pool does not have an entry > > for the root pool. > > I just tried 'set vfs.zfs.debug=1' then 'boot' at the loader prompt, > and it seems I wound up at the exact same place with no further debug It's not further, it's before that. > diagnostics. I believe the important part of that error output is > this: > > =============== > Trying to mount root from zfs:zroot/ROOT []... > Mounting from zfs:zroot/ROOT failed with error 2. > > Loader variables: > vfs.root.mountfrom=zfs:zroot/ROOT > =============== > > If there's something else you'd like me to specify to the boot loader, > please let me know and I will give it a try today. > > > > Further, I believe that instructions on the Niclas' page won't > > result in a bootable pool with 9.0 or 9.1. With stable/9 they > > should work. The problem is that zpool.cache is not populated at > > all. You can try to specify cachefile property to zpool create and ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > then copy zpool.cache to boot/zfs/ on the newly created pool. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > I would be willing to attempt a re-install using Niclas' instructions > plus something to populate the zpool.cache. Can you (or Niclas) > suggest what command(s) to add to the process at which stage? I think I did? -- Andriy Gapon