Date: Mon, 30 May 2022 08:16:20 -0600 From: Warner Losh <imp@bsdimp.com> To: Toomas Soome <tsoome@me.com> Cc: David Wolfskill <david@catwhisker.org>, FreeBSD Current <current@freebsd.org> Subject: Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c Message-ID: <CANCZdfpqiOj595_uU=kWg4qD37GCO1zXZo6B2MUbWTokUeugHg@mail.gmail.com> In-Reply-To: <7BEE44CC-4D31-4CBC-BC12-9A327424299C@me.com> References: <YpQdK70gH%2B%2BZ9ZjA@albert.catwhisker.org> <AE2261C9-12E5-4DA2-AEA9-43C3E9C4AA2A@me.com> <YpSb5aWAn3DYZXZQ@albert.catwhisker.org> <CANCZdfqDx2rVNy=K1rcbQZu1igFDhuUwwBQN7UN9p=Ya-t3ZbA@mail.gmail.com> <7BEE44CC-4D31-4CBC-BC12-9A327424299C@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000008495bd05e03b4d42 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, May 30, 2022 at 8:14 AM Toomas Soome <tsoome@me.com> wrote: > > > On 30. May 2022, at 17:06, Warner Losh <imp@bsdimp.com> wrote: > > > > 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 tha= t > 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 > > > Ye, thats why I was asking about loader_4th. I=E2=80=99m trying to spot t= he issue > from ufs image sample. > I thought it was a good suggestion. My guess on it not working wasn't to imply it wasn't. Warner --0000000000008495bd05e03b4d42 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 8:14 AM Tooma= s Soome <<a href=3D"mailto:tsoome@me.com">tsoome@me.com</a>> wrote:<b= r></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"><div style=3D"ove= rflow-wrap: break-word;"><br><div><br><blockquote type=3D"cite"><div>On 30.= May 2022, at 17:06, Warner Losh <<a href=3D"mailto:imp@bsdimp.com" targ= et=3D"_blank">imp@bsdimp.com</a>> wrote:</div><br><div><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" target=3D"_blank">david@catwhisker.or= g</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> </div></blockquote></div><br><div>Ye, thats why I was asking about loader_4= th. I=E2=80=99m trying to spot the issue from ufs image sample.=C2=A0</div>= </div></blockquote><div><br></div><div>I thought it was a good suggestion. = My guess on it not working wasn't to imply it wasn't.</div><div><br= ></div><div>Warner=C2=A0</div></div></div> --0000000000008495bd05e03b4d42--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpqiOj595_uU=kWg4qD37GCO1zXZo6B2MUbWTokUeugHg>