System reboots to original version after update
-
@cmcdonald Is there anything I can provide to help troubleshoot with my issue?
-
Not at this time, besides trying the next build :)
Btw, what platform are you having issues on?
-
Running on firewall appliance similar to a protectli
-
@cmcdonald Still can't get the latest snapshot to boot.
BE Active Mountpoint Space Created auto-default-20230602115934 - - 951M 2023-06-02 11:59 auto-default-20230702153529 - - 861M 2023-07-02 15:35 auto-default-20231106122501 - - 807M 2023-11-06 12:25 auto-default-20231226102200 - - 676M 2023-12-26 10:22 auto-default-20231226103555 - - 576M 2023-12-26 10:35 auto-default-20240129152546 - - 487M 2024-01-29 15:25 auto-default-20240131113103 - - 466M 2024-01-31 11:31 auto-default-20240201124653 - - 467M 2024-02-01 12:46 auto-default-20240206073737 - - 473M 2024-02-06 07:37 auto-default-20240207120306 - - 75.7M 2024-02-07 12:03 auto-default-20240212104406 - - 75.8M 2024-02-12 10:44 auto-default-20240213090524 - - 1.26M 2024-02-13 09:05 auto-default-20240213091340 - - 1.23M 2024-02-13 09:13 default - - 656M 2024-02-29 12:09 default_previous - - 688M 2024-03-03 13:04 default_previous_20240303130421 RT - 12.9G 2024-03-11 12:25 default_previous_20240303130421_20240311122539 N / 5.61M 2023-06-02 10:23 upgrade-default-20240226145932 - - 1.04M 2024-02-26 14:59 upgrade-default-20240226150339 - - 608M 2024-02-26 15:03 upgrade-default-20240226150843 - - 1.25M 2024-02-26 15:08 Execute Shell Command
-
@Lurick Are you still having the same issues?
-
His issue was fixed by updating the boot loader.
I assume you're also on a BIOS system (not UEFI) ?
-
@cmcdonald Yes
Tried to force it to use the new snapshot and it's hanging.
-
-
-
@cmcdonald Unfortunately can't get back into the working snapshot after I set the updated snapshot to permanent.
-
@hypnosis4u2nv Use option 8 at the boot loader menu to select an alt boot environment
-
@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?
-
bectl mount default
will return a path in the form of/tmp/be_mount.XXXX
replace the references in the subsequent commands accordingly -
@cmcdonald Thx, Where would I find the defer reboot option?
-
@hypnosis4u2nv You'll have to manually add
<pfsense> <system> <firmware> <bedeferreboot></bedeferreboot> </firmware> </system> </pfsense>
-
@cmcdonald I'm adding that to the config.xml and rebooting?
-
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.
-
@stephenw10 @cmcdonald Thanks for your help. Gonna give this a go tomorrow morning and report back.
-
@stephenw10 Still don't see anything in the update settings after applying this and rebooting.
-
You won't see it in the UI. But pfSense upgrader will honor it. The UI bits are in 24.03