From owner-freebsd-current@FreeBSD.ORG Fri Feb 22 00:38:36 2013 Return-Path: Delivered-To: freebsd-current@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 C513A1BD for ; Fri, 22 Feb 2013 00:38:36 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id 1776A947 for ; Fri, 22 Feb 2013 00:38:35 +0000 (UTC) Received: from server.rulingia.com (c220-239-237-213.belrs5.nsw.optusnet.com.au [220.239.237.213]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id r1M0cWoZ082995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 22 Feb 2013 11:38:32 +1100 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id r1M0cR3x018765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 22 Feb 2013 11:38:27 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id r1M0cRYe018764 for freebsd-current@freebsd.org; Fri, 22 Feb 2013 11:38:27 +1100 (EST) (envelope-from peter) Date: Fri, 22 Feb 2013 11:38:27 +1100 From: Peter Jeremy To: Current FreeBSD Subject: Re: No ZFS when loading modules from loeader prompt Message-ID: <20130222003827.GA15631@server.rulingia.com> References: <5124E646.3060304@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Fri, 22 Feb 2013 00:38:36 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 20, 2013 at 7:05 AM, O. Hartmann = wrote: > At the loader prompt, I need to unload the buggy kernel and load the old > working one via > > load /boot/kernel.old/kernel > > Then I load also the ZFS related modules > > load /boot/kernel.old/opensolaris.ko > load /boot/kernel.old/zfs.ko > > Issuing boot at the end of that stage boots the kernel - the old one > -successfully - but there is no working ZFS and no ZFS volume gets > mounted although the rc.conf is executed correctly. > > What am I doing wrong at that point? Why isn't ZFS run and mount properly? Last time I ran into this problem, the issue was that "unload" also unloaded the zpool.cache file and the ZFS code relied on that to find the kernel. I don't recall what the workaround was. On 2013-Feb-20 08:17:46 -0800, Freddie Cash wrote: >Sounds like a perfect use case for Boot Environments. Create a new BE, >install the new kernel into it, set it as the default, reboot. If it >fails, you manually set the previous BE as the default, and reboot. That >way, your "known-good", working environment is never affected. How do you change your BE in the loader? Or how do you change your BE when you can't boot? --=20 Peter Jeremy --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEmvgMACgkQ/opHv/APuIf+5gCfW4aeRzU9NZAjduzYq07qqgD3 2oAAoIO16Jgv6cAY/rL/kITdCI7sj2qx =Z2yS -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c--