From owner-freebsd-current@FreeBSD.ORG Wed Feb 20 16:17:47 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 42F17CA6 for ; Wed, 20 Feb 2013 16:17:47 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qa0-f42.google.com (mail-qa0-f42.google.com [209.85.216.42]) by mx1.freebsd.org (Postfix) with ESMTP id 029D4EFA for ; Wed, 20 Feb 2013 16:17:46 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id cr7so2492962qab.15 for ; Wed, 20 Feb 2013 08:17:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=SBniiXiv0h9ogd9ac10alTP+O3O+P0OBI95XmKRb3dA=; b=kJsnhMSz6kjfgJwzpoAGvsVpv5KCM6CHhzIn+P8w2bt8+179zotiSlvFMCWXvWKc+u j+EdvJIRH5WneqhzSlflmKB/kYpQqdItOFXkLPgjbV0j42z22g8zbNqXmkKSlYseuCom kHf30q0SQamgyXUcLv5MXZXVA4l5qkjofCNR6m0uxthMbr6eUzGm0Anav1PKUSbfNr1s uSYLYBRrbOvDhR2u1T7d/gbRdAce6peMNZBBPcLloXMyslzamfDdQqwb2njX1r0hRvhU g+fvwFySdozu+dghLf0ZU9gy514AMcrwUL8lsShOf6WWFg1EBC8a31H0EqGBCWrGenA1 inhQ== MIME-Version: 1.0 X-Received: by 10.49.108.9 with SMTP id hg9mr9788090qeb.34.1361377066230; Wed, 20 Feb 2013 08:17:46 -0800 (PST) Received: by 10.49.106.233 with HTTP; Wed, 20 Feb 2013 08:17:46 -0800 (PST) In-Reply-To: <5124E646.3060304@zedat.fu-berlin.de> References: <5124E646.3060304@zedat.fu-berlin.de> Date: Wed, 20 Feb 2013 08:17:46 -0800 Message-ID: Subject: Re: No ZFS when loading modules from loeader prompt From: Freddie Cash To: "O. Hartmann" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Current FreeBSD 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 16:17:47 -0000 Sounds like a perfect use case for Boot Environments. Create a new BE, install the new kernel into it, set it as the default, reboot. If it fails, you manually set the previous BE as the default, and reboot. That way, your "known-good", working environment is never affected. beadm should be part of 10-CURRENT. If not, there should be a port for it. On Wed, Feb 20, 2013 at 7:05 AM, O. Hartmann wrote: > 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="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 > > -- Freddie Cash fjwcash@gmail.com