From owner-freebsd-current@freebsd.org Tue Aug 21 08:30:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0671108D7F8 for ; Tue, 21 Aug 2018 08:30:19 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6C4CB791B1; Tue, 21 Aug 2018 08:30:19 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from dhcp-10-248-112-19.eduroam.wireless.private.cam.ac.uk (global-5-143.nat-2.net.cam.ac.uk [131.111.5.143]) by mail.baldwin.cx (Postfix) with ESMTPSA id 027F510AFCD; Tue, 21 Aug 2018 04:30:17 -0400 (EDT) Subject: Re: Newly upgraded -CURRENT box does not boot To: Kyle Evans , Brett Gmoser References: <80002f50-c2a7-ff39-dbef-e39576c3da51@codexterous.com> Cc: FreeBSD Current , Toomas Soome , Warner Losh From: John Baldwin Message-ID: Date: Tue, 21 Aug 2018 09:30:16 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Tue, 21 Aug 2018 04:30:18 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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: Tue, 21 Aug 2018 08:30:19 -0000 On 8/21/18 4:19 AM, Kyle Evans wrote: > On Mon, Aug 20, 2018 at 4:27 PM, Brett Gmoser > wrote: >> Hi there, >> >> I was told to e-mail these addresses with this. >> >> I did an `svn update` on /usr/src last night, build world and kernel as >> usual. This morning I installed the kernel, booted into single user, >> installed world and did mergemaster -Ui as usual. The new kernel had booted >> fine. Upon reboot, the machine will no longer boot: >> >> Startup error in /boot/lua/loader.lua: >> LUA ERROR: cannot open /boot/lua/loader.lua: no such file or directory >> >> can't load 'kernel' >> >> Many things in the bootloader do not work, including "boot kernel.old", "ls >> /boot", and various other things (most if not all just result in "Command >> failed"). Interestingly, "ls /mnt" works, other directories do not. That's >> the only clue I have. >> >> I'm able to reboot in an installer image and mount the drive just fine. >> Everything is there and is as expected, including /boot/lua/loader.lua. >> >> I re-installed everything in /usr/src/stand (chroot'd on the installer >> image, and "cd /usr/src/stand && make clean all install"). This did not fix >> the problem. >> >> Does anybody happen to have any ideas? >> > > To briefly follow up and summarize the current standing here following > some more discussion/attempts to fix on IRC: > > 1.) x86 BIOS boot > 2.) Problem appears for both forthloader and lualoader > 3.) Early March loader works, recent loader does not [Only tried > loader from the past ~day] > 4.) ls / works, ls /mnt works, ls /boot and other directories fails > 5.) However, /boot is confirmed intact and populated by booting via > 11.2 install media and inspecting local disk > > We'll hopefully be having a bisect session tomorrow to figure out > where exactly this broke so that maybe Brett has a chance to upgrade > to 12.0, unless this sounds familiar to someone and the cause is > obvious. =) I would start with bisecting the changes to libi386/biosdisk.c. Also, comparing 'lsdev -v' output between old and new loaders might be a useful step before starting on the bisecting. -- John Baldwin