23.09.1 -> 24.03a seems fail
-
After the upgrade is performed the new BE is marked temporary for the next boot so that if boot verification fails, the system automatically reboots back into the old BE.
-
This post is deleted! -
Okay, but it doesn't make sense for this alert to appear... the system is running with the snapshot default_previous_20240302092838_20240305095307, the next is default_previous_20240302092838_20240305095307 (correctly, because it is the default) and the alert says... "this is a temporary boot", look the next from which the system will be rebooted is : default_previous_20240302092838_20240305095307 (that is what is now running).
-
-
@cmcdonald
BE Active Mountpoint Space Created
auto-default-20231208173430 - - 637M 2023-12-08 17:34
default_previous_20240302092838 - - 1.45G 2024-03-05 09:53
default_previous_20240302092838_20240305095307 NRT / 3.67G 2024-03-05 10:13
default_previous_20240302092838_20240305095307_20240305101257 - - 3.66M 2018-05-15 09:40 -
I've just upgrade to 24.03.b.20240306.0600
And the system reboot on a different snapshot, the upgrade is not completed
-
I've just upgrade (again).
PfSense reboot on 24.03b.20240306.0600
Is set "temporary BE" on 24.03b.20240307.0536 but is fully ignored
-
S stephenw10 moved this topic from Problems Installing or Upgrading pfSense Software on
