Re:_Loader_can't_find_/boot/ua/loader.l ua_on_UFS_after_main-n255828-18054d0220c

On 30 May 2022 8:38:27 pm AWST, David Wolfskill <david@catwhisker.org> wrote:
>On Mon, May 30, 2022 at 05:16:57AM -0700, Alastair Hogge wrote:
>> ...
>> I have not been able to use a new /boot/loader.efi (following -CURRENT)
>> since 
>> mid to late 2021, and your symptoms look the same; fortunately, I found
>> bug 
>> report 264282[0] last night, which I think is related. Yamagi has
>> already done 
>> the investigation, and found a possible cause. For the time being, in
>> the case 
>> of a GELI backed UFS mount, after GELI decrypts the mount, one has to
>> manually 
>> set currdev back to the correct disk.
>> 
>> 0: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264282
>> ....
>
>I (just) checked; after switching back to the Lua loader, the currdev
>variable is set to "disk0s4a:", which is correct for my case.
>
>Trying loader's "lsdev" command shows the expected disks, slices, and
>partitions, correctly identified as FreeBSD UFS, swap, or ZFS.
>
>Trying to (e.g.) "ls disk0s4a:" fails, saying that it can't find /.

Thanks for having a look into that mate.

-- 
Sent from a device with a tiny bloody screen and no hard keyboard; please excuse my brevity.