24.03 beta to 24.03 RC upgrade failed

mikkom

Hello,

I'm currently running into upgrade failure with my PFSense installation with following error, any advice how to solve the upgrade problem?

>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 5 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
pfSense repository update completed. 736 packages processed.
All repositories are up to date.
>>> Renaming current boot environment from default to default_20240411152414...done.
>>> Cloning current boot environment default_20240411152414...done.
>>> Removing vital flag from php83...done.
>>> Upgrading packages in cloned boot environment default...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking for upgrades (7 candidates): ....... done
Processing candidates (7 candidates): ....... done
The following 7 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	icu: 74.2,1 -> 74.2_1,1 [pfSense]
	pfSense: 24.03.b.20240322.1708 -> 24.03.r.20240410.1729 [pfSense]
	pfSense-base: 24.03.b.20240322.1708 -> 24.03.r.20240410.1729 [pfSense-core]
	pfSense-boot: 24.03.b.20240322.1708 -> 24.03.r.20240410.1729 [pfSense-core]
	pfSense-default-config: 24.03.b.20240322.1708 -> 24.03.r.20240410.1729 [pfSense]
	pfSense-kernel-pfSense: 24.03.b.20240322.1708 -> 24.03.r.20240410.1729 [pfSense-core]
	pfSense-repo: 24.03.b.20240322.1708 -> 24.03.r.20240410.1729 [pfSense]

Number of packages to be upgraded: 7

170 MiB to be downloaded.
[1/7] Fetching pfSense-base-24.03.r.20240410.1729.pkg: .......... done
[2/7] Fetching icu-74.2_1,1.pkg: .......... done
[3/7] Fetching pfSense-default-config-24.03.r.20240410.1729.pkg: . done
[4/7] Fetching pfSense-24.03.r.20240410.1729.pkg: .......... done
[5/7] Fetching pfSense-boot-24.03.r.20240410.1729.pkg: .......... done
[6/7] Fetching pfSense-repo-24.03.r.20240410.1729.pkg: . done
[7/7] Fetching pfSense-kernel-pfSense-24.03.r.20240410.1729.pkg: .......... done
Checking integrity... done (0 conflicting)
[1/7] Upgrading icu from 74.2,1 to 74.2_1,1...
[1/7] Extracting icu-74.2_1,1: .......... done
[2/7] Upgrading pfSense-boot from 24.03.b.20240322.1708 to 24.03.r.20240410.1729...
[2/7] Extracting pfSense-boot-24.03.r.20240410.1729: .......... done
[3/7] Upgrading pfSense-repo from 24.03.b.20240322.1708 to 24.03.r.20240410.1729...
[3/7] Extracting pfSense-repo-24.03.r.20240410.1729: .......... done
[4/7] Upgrading pfSense-base from 24.03.b.20240322.1708 to 24.03.r.20240410.1729...
[4/7] Extracting pfSense-base-24.03.r.20240410.1729: ... done
===> Keeping a copy of current version mtree
===> Removing schg flag from base files
===> Extracting new base tarball
===> Removing static obsoleted files
[5/7] Upgrading pfSense-default-config from 24.03.b.20240322.1708 to 24.03.r.20240410.1729...
[5/7] Extracting pfSense-default-config-24.03.r.20240410.1729: .... done
[6/7] Upgrading pfSense from 24.03.b.20240322.1708 to 24.03.r.20240410.1729...
[6/7] Extracting pfSense-24.03.r.20240410.1729: .......... done
[7/7] Upgrading pfSense-kernel-pfSense from 24.03.b.20240322.1708 to 24.03.r.20240410.1729...
[7/7] Extracting pfSense-kernel-pfSense-24.03.r.20240410.1729: .......... done
>>> Removing unnecessary packages...done.
>>> Cleanup pkg cache...done.
>>> Deferring package installation scripts...done.
>>> Upgrading boot code...
System Configuration

Architecture: amd64
Boot Devices: /dev/ada0
 Boot Method: uefi
  Filesystem: zfs
    Platform: unknown hardware


Updating boot code...

/usr/local/sbin/../libexec/install-boot.sh -b auto -d /tmp/be_mount.2l32 -f zfs -s gpt -u ada0
gpart bootcode -b /tmp/be_mount.2l32/boot/pmbr -p /tmp/be_mount.2l32/boot/gptzfsboot -i 2 ada0
partcode written to ada0p2
bootcode written to ada0
ESP /dev/ada0p1 mounted on /tmp/stand-test.kupbB8
264128KB space remaining on ESP: renaming old loader.efi file /etc/freebsd/loader.efi /etc/freebsd/loader-old.efi
Copying loader.efi to /EFI/freebsd on ESP
efibootmgr: efi_get_variable: Bad address
Creating UEFI boot entry for FreeBSD
efibootmgr: efi_get_variable: Bad address
Failed to create new boot entry
Unable to update boot code on /dev/ada0
Failed

mikey_s

I've got errors upgrading too, have just shut my test box down, so will get a full export later.

Going from 23.09.1

efibootmgr: efi variables not supported on this system. root? kldload efirt?

stephenw10

@mikey_s said in 24.03 beta to 24.03 RC upgrade failed:

efibootmgr: efi variables not supported on this system. root? kldload efirt?

That is probably this: https://redmine.pfsense.org/issues/15395

stephenw10

That might also apply to the first failure here though that error is slightly different.

Is that a UEFI device?

What do you see if you run efibootmgr manually?

mikey_s

@stephenw10

Yes it’s an UEFI device.

Planning on doing a check and fresh install of 2.7, then update to 23.09.1 and testing again.

Will highlight what I find and such.

It is my spare XG230 Rev2, I have my main Plus install on a XG135 Rev2.

stephenw10

Run: sysctl machdep.bootmethod

That will show you what it's actually booted.

stephenw10

@mikkom

What hardware is that?

Can you try running efibootmgr at the CLI and see what error it shows?

mikey_s

@stephenw10

efibootmgr: efi variables not supported on this system. root? kldload efirt?

XG230 Rev2 is a 1U Sophos appliance made by caswell. My unit is based on a Haswell CPU - i3-6100T as I swapped the CPU from a G4400.

mikey_s

@stephenw10

machdep.bootmethod: BIOS

Interesting, a re-checked the BIOS and it was UEFI and BIOS, so I'm going to re-install and then upgrade and again.

stephenw10

Ah, Ok. Yes you're hitting that bug directly then. If you install as both but then boot legacy that's when you will hit it. There's a fix for that incoming.

If you switch the BIOS to boot uefi it will pass that. Or install legacy only.

mikey_s

@stephenw10

I switched to UEFi in the BIOS and still issue, so will do a fresh install and re-test.

stephenw10

Is it actually booting uefi? The sysctl command show it is?

If so try running efibootmgr at the CLI and see what it returns.

You may have an interesting edge case.

mikey_s

@stephenw10

In process of rebuilt, so fresh 2.7.2 and upgrading to 23.09.1 atm and then I'll go to the RC and feedback.

mikey_s

Rebuilt and now updated

Boot to FW : false
BootCurrent: 0000
Timeout : 3 seconds
BootOrder : 0000, 0004, 0003
+Boot0000* FreeBSD
Boot0004* UEFI OS
Boot0003 UEFI: Built-in EFI Shell

machdep.bootmethod: UEFI

Now to deceide if I use a Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz or a Intel(R) Atom(TM) CPU C3558 @ 2.20GHz with QAT.

The XG 135 Rev3 with Intel(R) Atom(TM) CPU C3558 @ 2.20GHz is my prod system, the above is my testing system.

stephenw10

Ok well that won't hit the issue now.

mikey_s

@stephenw10 said in 24.03 beta to 24.03 RC upgrade failed:

Ok well that won't hit the issue now.

Many thanks

Happy to build it back to how it was if you want a system in BIOS mode, but I expect you're all already on the case and don't need my minimal input.

stephenw10

If you have some special edge case it could be useful. The OP here has unexpected output from efibootmgr for example.

It usually either fails entirely like you originally saw or returns the list of boot entries without error. Anything other than that would be useful to test on.