Date: Tue, 21 Aug 2018 09:30:16 +0100 From: John Baldwin <jhb@FreeBSD.org> To: Kyle Evans <kevans@freebsd.org>, Brett Gmoser <freebsdcurrent@codexterous.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Toomas Soome <tsoome@freebsd.org>, Warner Losh <imp@freebsd.org> Subject: Re: Newly upgraded -CURRENT box does not boot Message-ID: <f95b3e58-cc6e-f158-df5b-b137a15c00db@FreeBSD.org> In-Reply-To: <CACNAnaFvjSEVZoJm9OZE4T0mqhDncQxyUaF-c92b1oMPwt0bug@mail.gmail.com> References: <80002f50-c2a7-ff39-dbef-e39576c3da51@codexterous.com> <CACNAnaFvjSEVZoJm9OZE4T0mqhDncQxyUaF-c92b1oMPwt0bug@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/21/18 4:19 AM, Kyle Evans wrote: > On Mon, Aug 20, 2018 at 4:27 PM, Brett Gmoser > <freebsdcurrent@codexterous.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f95b3e58-cc6e-f158-df5b-b137a15c00db>