From owner-freebsd-fs@FreeBSD.ORG Wed May 25 09:00:25 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 736E71065679 for ; Wed, 25 May 2011 09:00:25 +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 6412A8FC08 for ; Wed, 25 May 2011 09:00:25 +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 p4P90OTX041093 for ; Wed, 25 May 2011 09:00:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4P90OJO041088; Wed, 25 May 2011 09:00:24 GMT (envelope-from gnats) Date: Wed, 25 May 2011 09:00:24 GMT Message-Id: <201105250900.p4P90OJO041088@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Pan Tsu 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: Pan Tsu List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2011 09:00:25 -0000 The following reply was made to PR kern/153804; it has been noted by GNATS. From: Pan Tsu To: Andriy Gapon Cc: bug-followup@FreeBSD.org, Nick Sayer Subject: Re: kern/153804: boot from zfs kernel.old recovery undocumented/impossible Date: Wed, 25 May 2011 12:52:38 +0400 Andriy Gapon writes: > Try the following options: > > 1) > unload > set kernel=kernel.old > boot > > 2) > unload > load /boot/kernel.old/kernel > load -t /boot/zfs/zpool.cache /boot/zfs/zpool.cache zpool_cache_type can be anything. loader(8) unlike grub2 doesn't enforce type to be "/boot/zfs/zpool.cache". > boot Whatever happened to just typing following? boot kernel.old It assumes zpool.cache was already preloaded by failed attempt to boot default kernel. No need to `unload' the kernel, `boot' replaces it. > My expectation is that both should do what you want.