From owner-freebsd-stable@FreeBSD.ORG Mon Sep 9 09:19:49 2013 Return-Path: Delivered-To: freebsd-stable@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 ESMTP id 41B56E39; Mon, 9 Sep 2013 09:19:49 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9D61C2252; Mon, 9 Sep 2013 09:19:48 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id y10so5044258wgg.0 for ; Mon, 09 Sep 2013 02:19:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/th8GnQzNiG1SinHZaXrQLTfCST+/oz5nkNb4ITGvQg=; b=IP5CwLF1zy2vo04ddXFLj97AhqkmIjcARLxf0gT4Lj+V62Z5tb/L8o2B/DFUnQDppo sINXjrLOQKkdgkAQOkTKBih/mCJGcjIi72VKrg9jP6YuG7qH6qZC55jT/iwvWjJh9jF7 sk5vJgywrtlLqmsUQqQBrICkDD/4FTWjXZO8dFAjO5f0PlK36ok91Fe5kisc1agPaQTb u+0vN4krybjDK6XQOus1WD1D4SCRHGNvF0zX/ADmUZQcZ5gVOtvYZGd+i+31SpR8HJu9 6Xf6GOGgFtE/cN/MqW1E4UPFeSDqydmnZKyX/sPxmLlckUfLEPDM+PIWICk+7vjThMTU +9hA== MIME-Version: 1.0 X-Received: by 10.194.249.97 with SMTP id yt1mr452279wjc.49.1378718387172; Mon, 09 Sep 2013 02:19:47 -0700 (PDT) Received: by 10.216.235.9 with HTTP; Mon, 9 Sep 2013 02:19:47 -0700 (PDT) In-Reply-To: References: Date: Mon, 9 Sep 2013 10:19:47 +0100 Message-ID: Subject: Re: zfs_enable vs zfs_load in loader.conf (but neither works) From: krad To: J David Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-fs@freebsd.org" , freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Sep 2013 09:19:49 -0000 once you have it all working and understood have a look at the following port ''usr/ports/sysutils/beadm'' It may make things a little easier to manage in the future. In my experience BE's on zfs rock. On 9 September 2013 02:02, J David wrote: > After setting up a new machine to boot from a ZFS root using the 9.1 > install, it worked fine, but when the kernel & world was updated to > releng/9.2, it stopped booting. The pool is called "data" and the > root partition is "data/root." > > Under 9.1 it had in loader.conf: > > zfs_load=3D"YES" > vfs.root.mountfrom=3D"zfs:data/root" > > Under 9.2-RC3, the same config results in a panic: > > Trying to mount root from zfs:data/root []=85 > init: not found in path > /sbin/init:/sbin/oinit:/sbin/init.bak:/rescue/init:/stand/sysinstall > panic: no init > > If this is changed (as many Google hits recommend) to: > > zfs_enable=3D"YES" > vfs.root.mountfrom=3D"zfs:data/root" > > It seems like ZFS doesn't get loaded, so it fails instead with: > > Trying to mount root from zfs:data/root []=85 > Mounting from zfs:data/root failed with error 2: unknown file system. > > If the "?" mountroot> option is used, 50 devices are listed, none of > which are ZFS. And the "unknown file system" response comes from > vfs_byname returning NULL for zfs. > > (If both zfs_enable and zfs_load are set to "YES" then it fails as the > zfs_load case.) > > The system is using update-to-date zpool (v5000 / feature flags), and > all the updated bootblocks from the releng/9.2 build. zpool.cache is > correct, the zpool imports fine from the 9.2-RC3 live cd. The zpool's > bootfs is set correctly, the zfs mountpoint of data/root is / . And, > of course, init is present and health in data/root. The system booted > fine until updating to 9.2. > > Which loader.conf entry is actually correct for ZFS roots on 9.2, and > what (else) needs to happen to make this system bootable again? > > Thanks for any advice! > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >