System reboots to original version after update

[hypnosis4u2nv]

@cmcdonald Unfortunately can't get back into the working snapshot after I set the updated snapshot to permanent.

[cmcdonald]

@hypnosis4u2nv Use option 8 at the boot loader menu to select an alt boot environment

[hypnosis4u2nv]

@cmcdonald I got back in, had to get back into the GUI and set that snapshot as the default because it kept trying to reboot back into the updated default.

bectl mount default
gpart bootcode -b /tmp/be_mount.XXXX/boot/pmbr -p /tmp/be_mount.XXXX/boot/gptzfsboot -i 1 ada0
bectl unmount -f default
bectl activate -t default
shutdown -r now

What should I replace XXXX with?

[cmcdonald]

@hypnosis4u2nv

bectl mount default will return a path in the form of /tmp/be_mount.XXXX replace the references in the subsequent commands accordingly

[hypnosis4u2nv]

@cmcdonald Thx, Where would I find the defer reboot option?

[cmcdonald]

@hypnosis4u2nv You'll have to manually add

<pfsense>
    <system>
        <firmware>
            <bedeferreboot></bedeferreboot>
        </firmware>
    </system>
</pfsense>

[hypnosis4u2nv]

@cmcdonald I'm adding that to the config.xml and rebooting?

[stephenw10]

Yes. You probably don't have a <firmware> section so will have to add that but you will have a <system> section so it should be added inside that.

[hypnosis4u2nv]

@stephenw10 @cmcdonald Thanks for your help. Gonna give this a go tomorrow morning and report back.

[hypnosis4u2nv]

@stephenw10 Still don't see anything in the update settings after applying this and rebooting.

[cmcdonald]

@hypnosis4u2nv

You won't see it in the UI. But pfSense upgrader will honor it. The UI bits are in 24.03

[hypnosis4u2nv]

@cmcdonald OK thanks. I followed the instructions in the link you provided and updated to the latest snapshot. When the system booted up it was on the Feb 29th snapshot. I did a regular update to the latest snapshot and this time it booted up fine on the latest. Although it threw an error upon bootup. Appreciate everyones help to get me past that issue.

Crash report begins.  Anonymous machine information:

amd64
15.0-CURRENT
FreeBSD 15.0-CURRENT #0 plus-devel-main-n256292-447d90db3c9: Tue Mar 12 06:38:59 UTC 2024     root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/obj/amd64/PHcZzx3l/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBS

Crash report details:

PHP Errors:
[12-Mar-2024 11:14:44 America/New_York] PHP Fatal error:  Uncaught Error: Failed opening required '/usr/local/www/shortcuts.inc' (include_path='.:/etc/inc:/usr/local/pfSense/include:/usr/local/pfSense/include/www:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear:/usr/local/share/openssl_x509_crl/') in /usr/local/www/head.inc:26
Stack trace:
#0 /usr/local/www/index.php(340): include()
#1 {main}
  thrown in /usr/local/www/head.inc on line 26

[DefenderLLC]

@hypnosis4u2nv I think that's an issue with today's build. I saw something similar, but in a crash report via the GUI. First time I've ever seen one of those. I posted the details of my error here:

https://forum.netgate.com/topic/186689/pfsense-plus-crash-report

[cmcdonald]

@DefenderLLC Yes, we are discussing this internally now.

[DefenderLLC]

@cmcdonald FWIW, everything seems to be working fine from a technical perspective.