From owner-freebsd-sparc64@FreeBSD.ORG  Mon Jul  1 19:08:02 2013
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 24011E3B
 for <freebsd-sparc64@freebsd.org>; Mon,  1 Jul 2013 19:08:02 +0000 (UTC)
 (envelope-from cross+freebsd@distal.com)
Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200::ae25])
 by mx1.freebsd.org (Postfix) with ESMTP id F2ACF1C78
 for <freebsd-sparc64@freebsd.org>; Mon,  1 Jul 2013 19:08:01 +0000 (UTC)
Received: from zalamar.mm-corp.net (static-66-16-13-46.dsl.cavtel.net
 [66.16.13.46]) (authenticated bits=0)
 by mail.distal.com (8.14.3/8.14.3) with ESMTP id r61J80Xr015553
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
 Mon, 1 Jul 2013 15:08:01 -0400 (EDT)
Subject: Re: Problems booting into ZFS on recent stable/9
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Chris Ross <cross+freebsd@distal.com>
In-Reply-To: <51D1D0B4.1070307@pix.net>
Date: Mon, 1 Jul 2013 15:08:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0F658D4-9005-4848-BDB8-66E2FF159033@distal.com>
References: <951F81F6-5301-4DF4-8822-0567FDABA4DB@distal.com>
 <51D1D0B4.1070307@pix.net>
To: Kurt Lidl <lidl@pix.net>
X-Mailer: Apple Mail (2.1283)
Cc: freebsd-sparc64@freebsd.org
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-sparc64>, 
 <mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
 <mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 19:08:02 -0000


On Jul 1, 2013, at 14:55 , Kurt Lidl wrote:
> As luck would have it, I just ran into this problem on an amd64 host
> on Friday.
>=20
> You are missing the 'zfs_load=3D"YES"' from your /boot/loader.conf =
file.
>=20
> If you have access to a serial console, this is easy to fix.

  I think that isn't my problem.  I believe I have that in my =
loader.conf (is there a "cat" equivalent in the boot loader?), and I can =
see zfs.ko being loaded:

bootpath=3D"zfs:zroot:"
Loading /boot/defaults/loader.conf=20
Loading /boot/loader.conf=20
/boot/kernel/kernel data=3D0x682758+0xa9ef0 =
syms=3D[0x8+0x8bef0+0x8+0x84bfa]
/boot/kernel/zfs.ko text=3D0x220788 data=3D0x9be0+0x17e78 =
syms=3D[0x8+0x18ee8+0x8+0x139b4]
loading required module 'opensolaris'
/boot/kernel/opensolaris.ko text=3D0x30b0 data=3D0x2c8+0x2030 =
syms=3D[0x8+0xd80+0x8+0x91d]
/boot/kernel/geom_mirror.ko text=3D0x381b0 data=3D0x5a0+0x20 =
syms=3D[0x8+0x1698+0x8+0x118a]
/
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel] in 4 seconds...=20

  I think this means that I have zfs_load=3D"YES" in my loader config, =
already, along with the vfs.root.mountfrom=3D"zfs:zroot"

  That all seem right?

      - Chris