From owner-freebsd-current@freebsd.org Mon Dec 11 22:37:20 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19331EA14FB for ; Mon, 11 Dec 2017 22:37:20 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 843F47D270 for ; Mon, 11 Dec 2017 22:37:19 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22f.google.com with SMTP id f13so20998366lff.12 for ; Mon, 11 Dec 2017 14:37:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=0HOgl/8Qg2WcuO0yDhjFf8pqP1kaGT5XRdPKjk6wnNM=; b=XHXe5E/T/WUiuCJcuA0QM8vHMgFP/IOqzyM0iv5wac0+lmKJOoBUA0LI0wQ6cSPLW3 bFnomvhDDcW3VYs7e+xq9AOF2FujMx4BnYwsdC2S7WFwC72Fi0JzgPNm1N12cXodiKsi JO8+t/NZF5rVo3p3RwZ3SYHjg4Y3OCyjt6JkKQSqk1j3q1s8okaKUf/GultXXtpp0bpL gFf5Nnwhnkkr09cxnzU0v2JZRVBH87tWxrCBa29w5Sv3jZ8YjjRcqXkpKWKPL8vI4X90 raTlE9WxDJB2fKg09rEmHyDoDkDrk1HCxVxf7bNa57tBvN3m7+Dbard58QFbI8PmfXyT VinQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=0HOgl/8Qg2WcuO0yDhjFf8pqP1kaGT5XRdPKjk6wnNM=; b=rtF2+Q2gAnjwTkPzf25/1pZwM16czK7re2FLXm9ibRjF7M0rt12Mn7t5WiO/sjFnjx WFkgsrMc06lF7LZHlkHi4FM5YrZ5bvD4WhF+EqqqI93Lt4jw1+ywcpY4+a4FNTzunlN0 D4R7zD2GYDa+nAnGU8hLrcfkS2d4P4hjjnQMspm6r4I9kHVGEiEjzRaV6qXO+72RhvVK vTpCv1GknAhkw0ZZW3X5qFt89ku5zT/xhTUC+hZa0q9gVlmqPbpoU3lJxgx+Sf3u9OFq wHStqhIGEChy5C45yAptBXH3K/za0dYoys0rfiRETyfZSpmhuk/kuOTZt0tzTwlUk+t4 Ya3w== X-Gm-Message-State: AKGB3mI36hwwADUFsP6GWyL649ec8CXCJHMtw1jZvBh515xSdp4Ni68n CYDjjyvZF2C/mFF1BwjJ6xHbvgluOe4RL+gwh5c= X-Google-Smtp-Source: ACJfBouJQqG/U4SuYUYNL281Ct4VQkI8rNrW4quCXHxCLEMJt6oMgb6Q6lpi42rnRUGPGnHVD9NZpkjsSMmU7XAa4oM= X-Received: by 10.46.88.4 with SMTP id m4mr925793ljb.15.1513031837520; Mon, 11 Dec 2017 14:37:17 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.76.19 with HTTP; Mon, 11 Dec 2017 14:37:16 -0800 (PST) In-Reply-To: References: From: Alan Somers Date: Mon, 11 Dec 2017 15:37:16 -0700 X-Google-Sender-Auth: UhonA1bzO-ch9RNeFss2oJyq-mM Message-ID: Subject: Re: don't know how to load module '/boot/loader' To: Warner Losh Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Mon, 11 Dec 2017 22:37:20 -0000 On Mon, Dec 11, 2017 at 3:30 PM, Warner Losh wrote: > > > On Mon, Dec 11, 2017 at 3:26 PM, Alan Somers wrote: > >> On Mon, Dec 11, 2017 at 3:19 PM, Warner Losh wrote: >> >>> >>> >>> On Mon, Dec 11, 2017 at 3:03 PM, Alan Somers >>> wrote: >>> >>>> I just upgraded my head machine to r326772. Now, boot2 can't find the >>>> loader. Instead, it tries to boot the kernel directly, which fails >>>> because >>>> the ZFS module isn't loaded. If I break into boot2 and type "boot >>>> /boot/loader" I get the error "don't know how to load module >>>> '/boot/loader'". I last updated on 30-Nov, so this bug must've been >>>> introduced since then. Any ideas? >>>> >>>> BTW, I can successfully boot with the following commands: >>>> unload >>>> load /boot/kernel/kernel >>>> load zfs >>>> boot >>>> >>>> http://bayimg.com/iAKmFaAgl >>> >>> >>> I'd bisect :) >>> >>> However, try to update to just before this commit: >>> >>> Author: imp >>> Date: Fri Dec 8 19:57:16 2017 +0000 >>> >>> Create interp class. >>> >>> Create an interp class. Use it to separate out the different types of >>> interpreters: forth and simple with function pointers rather than >>> via #ifdefs. >>> >>> Obtained from: lua boot loader project >>> (via https://bsdimp@github.com/bsdimp/freebsd.git >>> lua-bootloader) >>> Sponsored by: Netflix >>> >>> >>> git-svn-id: svn+ssh://svn.freebsd.org/base/head@326712 >>> ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f >>> >>> would be a good place to start. >>> >>> It's a shame we can't create zpool images with an unpriv'd user command. >>> Would help out the ZFS testing of the boot loader refinement. >>> >>> Warner >>> >> >> If I bisect this, what parts do I need to reinstall each time? A full >> buildworld would be too slow. Is it sufficient to reinstall stand? >> > > Just rebuild stand, reinstall it and reboot. > > Also, why are you trying to load /boot/loader from /boot/zfsloader? That > has me confused. The screen shot looks like it found the kernel OK and was > going to boot it, but then you interrupted it, unloaded it and tried to > load /boot/loader. Shouldn't that be /boot/kernel or /boot/kernel.old or > something like that? > > OK is /boot/loader's prompt (boot2 has no such prompt).... maybe the real > bug here is that the menu has stopped working leading to your confusion... > > Warner > It certainly could be a bug in the menu. I'm definitely confused, because this is a domain I've seldom dealt with, since it usually just works. If I'm actually in /boot/loader, then there are two problems: 1) The menu isn't working 2) The loader isn't reading /boot/loader.conf.