System reboots to original version after update

[stephenw10]

Hmm, might need some input from @cmcdonald

[Lurick]

I'm having issues with the latest 24.03.a.20240302.0116 as well coming from 23.09.01 where it just boots right back into 23.09.01 after the update but keeps creating boot environments when I try to update.

bectl list
BE                                                                  Active Mountpoint Space Created
auto-default-20230126114831                                         -      -          824M  2023-01-26 11:48
auto-default-20230215141107                                         -      -          1.29G 2023-02-15 14:11
auto-default-20230607133124                                         -      -          1.17G 2023-06-07 13:31
auto-default-20230630140819                                         -      -          956M  2023-06-30 14:08
auto-default-20230929141853                                         -      -          750M  2023-09-29 14:18
auto-default-20230930131533                                         -      -          677M  2023-09-30 13:15
auto-default-20231003140926                                         -      -          614M  2023-10-03 14:09
auto-default-20231004144319                                         -      -          589M  2023-10-04 14:43
auto-default-20231006101001                                         -      -          590M  2023-10-06 10:10
auto-default-20231012123129                                         -      -          590M  2023-10-12 12:31
auto-default-20231013104306                                         -      -          592M  2023-10-13 10:43
auto-default-20231015170222                                         -      -          590M  2023-10-15 17:02
auto-default-20231016115302                                         -      -          590M  2023-10-16 11:53
auto-default-20231017061313                                         -      -          590M  2023-10-17 06:13
auto-default-20231019063409                                         -      -          591M  2023-10-19 06:34
auto-default-20231024062917                                         -      -          590M  2023-10-24 06:29
auto-default-20231027141502                                         -      -          591M  2023-10-27 14:15
auto-default-20231106143819                                         -      -          605M  2023-11-06 14:38
auto-default-20231209063414                                         -      -          614M  2023-12-09 06:34
default                                                             -      -          1.50G 2024-03-04 15:30
default_20240304153021                                              -      -          1.50G 2024-03-04 15:40
default_20240304153021_20240304154028                               -      -          1.47G 2024-03-04 15:47
default_20240304153021_20240304154028_20240304154733                T      -          1.47G 2024-03-04 15:52
default_20240304153021_20240304154028_20240304154733_20240304155235 NR     /          19.2G 2023-01-26 11:40

[cmcdonald]

@Lurick

You are most likely hitting a bug that will be fixed in tomorrow's build.

[hypnosis4u2nv]

@cmcdonald Is there anything I can provide to help troubleshoot with my issue?

[cmcdonald]

@hypnosis4u2nv

Not at this time, besides trying the next build :)

Btw, what platform are you having issues on?

[hypnosis4u2nv]

@cmcdonald

Running on firewall appliance similar to a protectli

[hypnosis4u2nv]

@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

[hypnosis4u2nv]

@Lurick Are you still having the same issues?

[cmcdonald]

@hypnosis4u2nv

His issue was fixed by updating the boot loader.

I assume you're also on a BIOS system (not UEFI) ?

[hypnosis4u2nv]

@cmcdonald Yes

Tried to force it to use the new snapshot and it's hanging.

[hypnosis4u2nv]

@cmcdonald

[cmcdonald]

@hypnosis4u2nv

You need to update the boot code

https://forum.netgate.com/post/1156211

[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.