From owner-freebsd-fs@FreeBSD.ORG Wed May 25 14:30:16 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 658A8106564A for ; Wed, 25 May 2011 14:30:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5583E8FC13 for ; Wed, 25 May 2011 14:30:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4PEUGor044108 for ; Wed, 25 May 2011 14:30:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4PEUG2d044103; Wed, 25 May 2011 14:30:16 GMT (envelope-from gnats) Date: Wed, 25 May 2011 14:30:16 GMT Message-Id: <201105251430.p4PEUG2d044103@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Nick Sayer Cc: Subject: Re: kern/153804: boot from zfs kernel.old recovery undocumented/impossible X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Nick Sayer List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2011 14:30:16 -0000 The following reply was made to PR kern/153804; it has been noted by GNATS. From: Nick Sayer To: Pan Tsu Cc: Andriy Gapon , bug-followup@FreeBSD.org Subject: Re: kern/153804: boot from zfs kernel.old recovery undocumented/impossible Date: Wed, 25 May 2011 07:21:40 -0700 On May 25, 2011, at 1:52 AM, Pan Tsu wrote: > Andriy Gapon writes: >=20 >> Try the following options: >>=20 >> 1) >> unload >> set kernel=3Dkernel.old >> boot >>=20 >> 2) >> unload >> load /boot/kernel.old/kernel >> load -t /boot/zfs/zpool.cache /boot/zfs/zpool.cache >=20 > zpool_cache_type can be anything. loader(8) unlike grub2 doesn't = enforce > type to be "/boot/zfs/zpool.cache". >=20 >> boot >=20 > Whatever happened to just typing following? >=20 > boot kernel.old >=20 > It assumes zpool.cache was already preloaded by failed attempt to boot > default kernel. No need to `unload' the kernel, `boot' replaces it. I didn't try that. At the time I didn't think it worked that way. Back = when I was in full on panic mode, I think option number 1 was what = finally worked, but I am happier with option 2, as it offers the most = control. It just needs to be better documented. >=20 >> My expectation is that both should do what you want.