Date: Mon, 30 May 2022 08:06:32 -0600 From: Warner Losh <imp@bsdimp.com> To: David Wolfskill <david@catwhisker.org>, Toomas Soome <tsoome@me.com>, FreeBSD Current <current@freebsd.org>, Warner Losh <imp@bsdimp.com> Subject: Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c Message-ID: <CANCZdfqDx2rVNy=K1rcbQZu1igFDhuUwwBQN7UN9p=Ya-t3ZbA@mail.gmail.com> In-Reply-To: <YpSb5aWAn3DYZXZQ@albert.catwhisker.org> References: <YpQdK70gH%2B%2BZ9ZjA@albert.catwhisker.org> <AE2261C9-12E5-4DA2-AEA9-43C3E9C4AA2A@me.com> <YpSb5aWAn3DYZXZQ@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000006e6ed905e03b2acb Content-Type: text/plain; charset="UTF-8" On Mon, May 30, 2022 at 4:26 AM David Wolfskill <david@catwhisker.org> wrote: > On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: > > ... > > Does loader_4th have same issue? > > .... > > I don't know; I hadn't tried it. I will do so later today & report > back. > So if it's only one system, and it's only UFS, then what does fsck of that UFS system tell you? The loader can't find its UFS filesystem to read the configuration from. So either its having trouble finding the device (unlikely since that code hasn't changed in a long time), or its having heartburn with the UFS system for some reason it's being silent about (within the realm of possibilities because there might be an unknown edge case in Kirks recent UFS integrity changes). I suspect that the 4th boot loader will have the same issue, but a different error message. Others have reported issues with GELI, but that's not in play here, If I'm reading this correctly. Right? Warner --0000000000006e6ed905e03b2acb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Mon, May 30, 2022 at 4:26 AM David= Wolfskill <<a href=3D"mailto:david@catwhisker.org">david@catwhisker.org= </a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:= 0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">= On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote:<br> > ... <br> > Does loader_4th have same issue?<br> > ....<br> <br> I don't know; I hadn't tried it.=C2=A0 I will do so later today &am= p; report<br> back.<br></blockquote><div><br></div><div>So if it's only one system, a= nd it's only UFS, then what does fsck of that UFS system tell you?</div= ><div>The loader can't find its UFS filesystem to read the configuratio= n from. So either its having trouble</div><div>finding the device (unlikely= since that code hasn't changed in a long time), or its having heartbur= n</div><div>with the UFS system for some reason it's being silent about= (within the realm of possibilities because</div><div>there might be an unk= nown edge case in Kirks recent=C2=A0 UFS integrity changes). I suspect that= the 4th<br></div><div>boot loader will have the same issue, but a differen= t=C2=A0error message.</div><div><br></div><div>Others have reported issues = with GELI, but that's not in play here, If I'm reading this correct= ly. Right?</div><div><br></div><div>Warner</div></div></div> --0000000000006e6ed905e03b2acb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqDx2rVNy=K1rcbQZu1igFDhuUwwBQN7UN9p=Ya-t3ZbA>