Re: FreeBSD 13.0-RC3 Now Available

On Sun, 21 Mar 2021 at 03:08, Glen Barber <gjb_at_freebsd.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> The third RC build of the 13.0-RELEASE release cycle is now available.
>
> === Upgrading ===
>
> The freebsd-update(8) utility supports binary upgrades of amd64, i386,
> and aarch64 systems running earlier FreeBSD releases.  Systems running
> earlier FreeBSD releases can upgrade as follows:
>
>         # freebsd-update upgrade -r 13.0-RC3
>
> During this process, freebsd-update(8) may ask the user to help by
> merging some configuration files or by confirming that the automatically
> performed merging was done correctly.
>
>         # freebsd-update install
>
> The system must be rebooted with the newly installed kernel before
> continuing.
>
>         # shutdown -r now
>
> After rebooting, freebsd-update needs to be run again to install the new
> userland components:
>
>         # freebsd-update install
>
> It is recommended to rebuild and install all applications if possible,
> especially if upgrading from an earlier FreeBSD release, for example,
> FreeBSD 11.x.  Alternatively, the user can install misc/compat11x and
> other compatibility libraries, afterwards the system must be rebooted
> into the new userland:
>
>         # shutdown -r now
>
> Finally, after rebooting, freebsd-update needs to be run again to remove
> stale files:
>
>         # freebsd-update install


Hi,

There are two edge cases where the above update instructions will not work.

1) Due to the VLAN re-write in ifconfig(8), if a user is using a host that
is fully utilising VLAN tagging, the machine will not be available on the
network until the second reboot.  The user will either need IPMI/LOM access
to the console to execute the second 'freebsd-update install' command or
have a way of it being executed and automatically rebooting prior to having
access to the host on the network again.

2) If a user has a 12.2 zpool checkpoint in play and booting via BIOS
legacy mode, the machine will hang at next reboot with 'zio_read error: 5'
'ZFS: i/o error - all block copies unavailable' 'ZFS: can not read
checkpoint data.'  The machine will have to be rebooted with a boot ISO and
the checkpoint will need to be discarded and the system will boot correctly
again (rewind has been unsuccessful).  Please note: This does not appear to
be an issue where hosts use UEFI for booting operating systems or if zpool
checkpoints are destroyed prior to the update process.

Cheers,

Jason.