System reboots to original version after update

[hypnosis4u2nv]

I'm on the developer release channel. After 2/9, I can't get pfsense to boot into the updated version. Seems to be an error that causes it to boot up with the previous working ZFS image. Don't really know where to start troubleshooting.

[stephenw10]

Retest with the current snapshot. There have been several fixes there.

[hypnosis4u2nv]

@stephenw10

Maybe you can help me make some sense out of this. Updated to the latest 3/2 build. Pfsense boots back into the 2/9 build. I choose the 3/2 build snapshot and click activate and run onetime. Continues to boot into the 2/9 build.

[stephenw10]

Hmm, what does it look like after you activate default_previous for the next boot?

What does bectl list show?

[hypnosis4u2nv]

@stephenw10

[stephenw10]

Hmm, I expect it to be marked R not T there if you just activate for the next boot.

You are just clicking the 'star' in the BE GUI page to activate it?

[hypnosis4u2nv]

@stephenw10 No, I'm choosing the Play button. It should boot into that snapshot and the I could make it permanent by checking the star. Unless something changed where I have to do it manually from the boot environment. Even after updating, the logs show the new default snapshot being selected for the next boot. But it never does. I've tried going back to previous snapshots from 2/9 and they don't boot either.

[stephenw10]

That should work for a one time boot yes.

So you're unable to select any other BE to boot into? Using either one-time or permanent activation?

[hypnosis4u2nv]

@stephenw10 I can select the BEs just fine through the play button, and then I choose reboot and submit. I haven't chosen the reroot option when doing the single time boot method. I'm skeptical that using the star (permenant) option may cause a failure to boot considering it's already not booting the proper snapshot and possibly falling back on the working one which is 2/9.

[stephenw10]

Sorry I meant you cannot boot into any other BEs using the one-time button?

[hypnosis4u2nv]

@stephenw10 Yes, I can't boot into any of the other boot environments before and after the 2/9 BE. I can select them for onetime, but they never boot up.

[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) ?