Now Available: pfSense Plus 26.03.1

[Gertjan]

@lohphat said in Now Available: pfSense Plus 26.03.1:

G-3100 needed a reboot

After a kernel (call that the core OS) update, an reboot is always necessary. The now older kernel needs to be replaced by the newer one.

[stephenw10]

Yes it always has to reboot at firmware upgrade. You mean it didn't reboot by itself?

[lohphat]

@stephenw10 It did to do the update, but then after it came up on the nerw version the web UI didn't work, everything else was working. Another reboot brought the web UI back.

[stephenw10]

Hmm, odd. Any errors logged at that time?

[lohphat]

@Gertjan Obviously, but after the reboot, the web UI was unresponsive even after restarting the process from the CLI. Another reboot fixed it.

[lohphat]

@stephenw10 There's always errors in the logs relating to interface issues on reboot. What should I be looking for?

[stephenw10]

Errors showing the nginx process failing to start for example or php processes crashing out.

What sort of interface errors are you seeing?

[SteveITS]

@jkline said in Now Available: pfSense Plus 26.03.1:

Once again, I have no LEDs after updating.

Your router functions, though?

I just updated my 2100 and it didn't return...no LEDs and the console was stuck at (after I pressed Enter) a ">" prompt:

Powering off worked, and I did one more soft reboot from the console which also went fine. Seems fine now...? Upgrade log looks fine to me, ending with:

...
>>> Removing unnecessary packages...done.
>>> Cleanup pkg cache...done.
>>> Deferring package installation scripts...done.
>>> Upgrading boot code...
System Configuration

Architecture: arm64
Boot Devices: /dev/mmcsd0
 Boot Method: uefi
  Filesystem: zfs
    Platform: Netgate 2100


Updating boot code...

/usr/local/sbin/../libexec/install-boot.sh -b uefi -d /tmp/be_mount.z8uf -f zfs -s mbr mmcsd0
ESP /dev/mmcsd0s1 mounted on /tmp/stand-test.P2CDHs
201320KB space remaining on ESP: renaming old bootaa64.efi file /efi/boot/bootaa64.efi /efi/boot/bootaa64-old.efi
201320KB 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
Copying bootaa64.efi to /efi/boot on ESP
Unmounting and cleaning up temporary mount point
Finished updating ESP

Done.
>>> Copying upgrade log...

[stephenw10]

Hmm, that's weird. That's very low level. The chipset drops to that prompt if it can't load uboot. But uboot is still there since it did boot after power cycling.

Some electrical surge interrupted it?

[SteveITS]

@stephenw10 yeah I’ve not seen that ever. It has a UPS though.