Re: unable to boot latest 14-stable

From: Mark Millard <marklmi_at_yahoo.com>
Date: Wed, 11 Oct 2023 12:46:16 UTC 
On Oct 11, 2023, at 01:55, void <void@f-m.fm> wrote:

> On Tue, Oct 10, 2023 at 07:30:37PM -0700, Mark Millard wrote:
> 
>> When you upgrade, do you also update the FreeBSD UEFI loader
>> that is in the msdosfs file system? (Or: the analogous
>> question(s) for your type of loader.)
> 
> No, I didn't upgrade the UEFI as there was nothing in UPDATING suggesting
> that was required in the timeframe of the upgrade (30th Sept <> 10th Oct)
> and it was working prior to that. I was expecting the upgrade to be
> straightforward as it was only updating 14-stable to a slightly later 14-stable.

Note: I do not have 14.0 so the following is based on 15:

Updating has a section reporting:

        ZFS notes
        ---------
        When upgrading the boot ZFS pool to a new version (via zpool upgrade),
        always follow these three steps:

        1) recompile and reinstall the ZFS boot loader and boot block
        (this is part of "make buildworld" and "make installworld")

        2) update the ZFS boot block on your boot drive (only required when
        doing a zpool upgrade):

        When booting on x86 via BIOS, use the following to update the ZFS boot
        block on the freebsd-boot partition of a GPT partitioned drive ada0:
                gpart bootcode -p /boot/gptzfsboot -i $N ada0
        The value $N will typically be 1.  For EFI booting, see EFI notes.

        3) zpool upgrade the root pool. New bootblocks will work with old
        pools, but not vice versa, so they need to be updated before any
        zpool upgrade.

        Non-boot pools do not need these updates.

It is followed by a section about EFI as reference in (2).

[(1) does not read well for a EFI context, unfortunately.]

> The last zpool upgrade happened on the 30th Sept. The zpool prior to
> the attempted upgrade of yesterday didn't warn of missing features immediately prior.
> 
> I'm not sure it uses UEFI.

The FreeBSD-standard U-Boot used is a UEFI/DeviceTree U-boot and the msdosfs
EFI/boot/bootaa64.efi is used for aarch64.

> The rpi4 runs headless. It has a serial connection for the console going into a rpi2b. I ssh into the rpi2b and access the rpi4's console wrapped in screen(8). From there I can enter the GELI password.
> This is before the daemon boot screen, which shows as ascii graphics.
> It's not getting to the daemon boot screen at present.




===
Mark Millard
marklmi at yahoo.com