From owner-freebsd-current@FreeBSD.ORG Wed Feb 20 15:05:45 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E96D6AD8 for ; Wed, 20 Feb 2013 15:05:45 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 9BDB49BF for ; Wed, 20 Feb 2013 15:05:45 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@FreeBSD.org with esmtp (envelope-from ) id <1U8BEu-002dOG-KR>; Wed, 20 Feb 2013 16:05:44 +0100 Received: from e178035155.adsl.alicedsl.de ([85.178.35.155] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@FreeBSD.org with esmtpsa (envelope-from ) id <1U8BEu-003p7e-Gm>; Wed, 20 Feb 2013 16:05:44 +0100 Message-ID: <5124E646.3060304@zedat.fu-berlin.de> Date: Wed, 20 Feb 2013 16:05:42 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130131 Thunderbird/17.0.2 MIME-Version: 1.0 To: Current FreeBSD Subject: No ZFS when loading modules from loeader prompt X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig93FAB683908F0A28C25215C3" X-Originating-IP: 85.178.35.155 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: Wed, 20 Feb 2013 15:05:46 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig93FAB683908F0A28C25215C3 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable At the moment, the most recent kernel of FreeBSD 10.0-CURRENT crashes on all of the boxes I compiled the most recent kernel sources (build a world ncluding kernel, not only the kernel, so the system is "consistent"= ). 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= ? Luckily, just booting the old kernel via load /boot/kernel.old/kernel and booting it having zfs_enable=3D"YES" in /etc/rc.conf set loads the /boot/kernel/opensolaris/zfs stuff - usually those kernel modules are out of sync compared to kernel.old but in this case its just a coincidence that this works. So, what is the proper way to have ZFS mounted in an emergency case when I'm in need of loading a working kernel manually? Regards, Oliver --------------enig93FAB683908F0A28C25215C3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJRJOZHAAoJEOgBcD7A/5N85l0H/3OWpgzH+8YR9nHrXBTJnxq+ LNnhXomK0c+cNeBKrfnTAJppMmbk3g9vjPvweB83q4Lm4kcr2qKFZ7fKtqSgrFAi NtoMS8z47GFaK2+SsC7O3Y/GzSnnoFK7NrjbYKzqLpgBGEda/38qboP+SYkS2VWM gjH1DFuE6QicQTE8X+RvstCeb0HqDU94WbgNCSJV6ywZiYzdm1B4EPici8t/Rxsh S9BEYeRSLci9L9M8p9TVXzv1ZvCYx2CESR+Z5HAqB+ooMkY0ek1Z0MjFH9H1QpuI Vd4/r5m/dthCYeunvIqns0EdfEhCHWoOul28lwnS+kUpjfIYxh5XQYB04Mo5w90= =lHzk -----END PGP SIGNATURE----- --------------enig93FAB683908F0A28C25215C3--