Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

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 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
>
>
> Ye, thats why I was asking about loader_4th. I’m trying to spot the 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