Date: Sun, 29 May 2022 18:59:34 -0600 From: Warner Losh <imp@bsdimp.com> To: FreeBSD Current <current@freebsd.org> Subject: Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c Message-ID: <CANCZdfoPazRtaKqKTtvsgm4dOoP7QFPs2HGM9ch=X9hrDS_yhQ@mail.gmail.com> In-Reply-To: <YpP9fO4v%2BdE1pCgu@albert.catwhisker.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Sorry for top posting...
Did you upgrade your boot blocks?
Warner
On Sun, May 29, 2022, 5:11 PM David Wolfskill <david@catwhisker.org> wrote:
> -- but only on one machine (of the 3 that I use for daily tracking head
> (and stable/12 & stable/13) -- the build machine ("freebeast").
>
> Each is amd64, using ... venerable ... BIOS/MBR & UFS -- stuff that has
> generally been functionally stable for the last couple of decades.
>
> So for yesterday and today, I've moved the new loader aside and copied
> the one from Friday, which works just fine.
>
> The build machine ("freebeast") uses a GENERIC kernel; the other 2 are
> laptops, and use a kernel that includes GENERIC, then tweaks things a
> bit (e.g., dropping support for tape drives; adding IPFIREWALL and
> explicitly NOT setting IPFIREWALL_DEFAULT_TO_ACCEPT; adding sound stuff).
>
> Info on the update history & copies of stuff like most recent
> (verbosely-booted) dmesg.boot should be available at
> https://www.catwhisker.org/~david/FreeBSD/history/ (and if you can't get
> through, please send a note to dhw@freebsd.org and I'll do what I can to
> fix it).
>
> (Of the 2 laptops, I only have the one that I actuaqlly use in
> day-to-day work represented.)
>
> (I note that to recover, I boot from one the stable/* slices, move the
> "head" slice's files around, then reboot from the "head" slice.)
>
> AFAICT, there were no changes to stand/* since main-n255828-18054d0220c,
> though yesterday (main-n255828-18054d0220c -> main-n255840-9cb70cb4769),
> there were some changes to sys/ufs/ffs/ffs_subr.c (from
> main-n255835-076002f24d35:
>
> commit 076002f24d35962f0d21f44bfddd34ee4d7f015d
> Author: Kirk McKusick <mckusick@FreeBSD.org>
> Date: Fri May 27 12:21:11 2022 -0700
>
> Do comprehensive UFS/FFS superblock integrity checks when reading a
> superblock.
>
> Historically only minimal checks were made of a superblock when it
> was read in as it was assumed that fsck would have been run to...
>
> -- which doesn't seem a likely culprit to me).
>
> That said, I am powering freebeast up, and plan to run a manual
> full fsck on the "head" slice's root file system.... Maybe a few
> others, while I'm here. :-}
>
> Peace,
> david
> --
> David H. Wolfskill david@catwhisker.org
> "Putin is a paranoid dictator. Putin must go. He started a senseless war
> and is leading Russia into a ditch." - Egor Polyakov & Alexandra
> Miroshnikova
>
> See https://www.catwhisker.org/~david/publickey.gpg for my public key.
>
[-- Attachment #2 --]
<div dir="auto">Sorry for top posting...<div dir="auto"><br></div><div dir="auto">Did you upgrade your boot blocks?</div><div dir="auto"><br></div><div dir="auto">Warner </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 29, 2022, 5:11 PM David Wolfskill <<a href="mailto:david@catwhisker.org">david@catwhisker.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-- but only on one machine (of the 3 that I use for daily tracking head<br>
(and stable/12 & stable/13) -- the build machine ("freebeast").<br>
<br>
Each is amd64, using ... venerable ... BIOS/MBR & UFS -- stuff that has<br>
generally been functionally stable for the last couple of decades.<br>
<br>
So for yesterday and today, I've moved the new loader aside and copied<br>
the one from Friday, which works just fine.<br>
<br>
The build machine ("freebeast") uses a GENERIC kernel; the other 2 are<br>
laptops, and use a kernel that includes GENERIC, then tweaks things a<br>
bit (e.g., dropping support for tape drives; adding IPFIREWALL and<br>
explicitly NOT setting IPFIREWALL_DEFAULT_TO_ACCEPT; adding sound stuff).<br>
<br>
Info on the update history & copies of stuff like most recent<br>
(verbosely-booted) dmesg.boot should be available at<br>
<a href="https://www.catwhisker.org/~david/FreeBSD/history/" rel="noreferrer noreferrer" target="_blank">https://www.catwhisker.org/~david/FreeBSD/history/</a>; (and if you can't get<br>
through, please send a note to <a href="mailto:dhw@freebsd.org" target="_blank" rel="noreferrer">dhw@freebsd.org</a> and I'll do what I can to<br>
fix it).<br>
<br>
(Of the 2 laptops, I only have the one that I actuaqlly use in<br>
day-to-day work represented.)<br>
<br>
(I note that to recover, I boot from one the stable/* slices, move the<br>
"head" slice's files around, then reboot from the "head" slice.)<br>
<br>
AFAICT, there were no changes to stand/* since main-n255828-18054d0220c,<br>
though yesterday (main-n255828-18054d0220c -> main-n255840-9cb70cb4769),<br>
there were some changes to sys/ufs/ffs/ffs_subr.c (from<br>
main-n255835-076002f24d35:<br>
<br>
commit 076002f24d35962f0d21f44bfddd34ee4d7f015d<br>
Author: Kirk McKusick <mckusick@FreeBSD.org><br>
Date: Fri May 27 12:21:11 2022 -0700<br>
<br>
Do comprehensive UFS/FFS superblock integrity checks when reading a superblock.<br>
<br>
Historically only minimal checks were made of a superblock when it<br>
was read in as it was assumed that fsck would have been run to...<br>
<br>
-- which doesn't seem a likely culprit to me).<br>
<br>
That said, I am powering freebeast up, and plan to run a manual<br>
full fsck on the "head" slice's root file system.... Maybe a few<br>
others, while I'm here. :-}<br>
<br>
Peace,<br>
david<br>
-- <br>
David H. Wolfskill <a href="mailto:david@catwhisker.org" target="_blank" rel="noreferrer">david@catwhisker.org</a><br>
"Putin is a paranoid dictator. Putin must go. He started a senseless war<br>
and is leading Russia into a ditch." - Egor Polyakov & Alexandra Miroshnikova<br>
<br>
See <a href="https://www.catwhisker.org/~david/publickey.gpg" rel="noreferrer noreferrer" target="_blank">https://www.catwhisker.org/~david/publickey.gpg</a>; for my public key.<br>
</blockquote></div>
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoPazRtaKqKTtvsgm4dOoP7QFPs2HGM9ch=X9hrDS_yhQ>