23.09.1 -> 24.03a seems fail
-
@Luca-De-Andreis You may need to check the following. If it's enabled, you must log into the console and click Verify button to confirm things are good. Otherwise, it will reboot in 300 seconds to the previous boot environment
-
-
The firewall runs 23.09.1, boot verification is not present
-
-
Let's try to collect some output of the failure. Do you have serial access to the console? If so, make sure you enable logging in your terminal emulator. If you've got display output only you will likely need to screen record.
before performing the upgrade, add the following to your config.xml. You can use Diagnostics > Edit File to do so. The path is /cf/conf/config.xml.
<system> <firmware> <bedeferreboot></bedeferreboot> </firmware> </system>This will cause the update to NOT automatically reboot after installation.
Now perform the upgrade. Please attach output here or to me directly.
Next, note the name of the new BE that was created. It should actually be the original name. Your current should name have a timestamp appended.
Go to diagnostics > command prompt and enter
bectl mount benamereplacing bename as necessary.
You should see a path returned in the form of
/tmp/be_mount.XXXXCopy this path.
Now enter
touch /tmp/be_mount.XXXX/verbose_rcFinally unmount the BE with
bectl unmount -f benameReboot.
pfSense startup is now very verbose. Send me the entire ouput.
Thanks
cmcdonald@netgate.com
-
OK I start to upgrade log :
upgrade-log.txtPlease note... this is a KVM virtual machine, not a bare metal system.
-
I think I understand
the problem lies in the incorrect (automatic) selection of the boot snapshot:I forced boot to a snapshot that was not selected. There must be some problem in the post upgrade setting ....
Now I'm in 24.03
-
Cool. I would rename you BEs to clean that up. There is new code in that makes that better moving forward.
-
-
Mhhh not good, there are still problems with snapshots ....
I have updated to 24.03.b.20240305.0455 and the boot was done with the previous release.
I try to manually force the correct boot snapshot....
-
-
Yes, KVM VM.
-
Go to Diagnostics > Command Prompt and enter
touch /verbose_rcThen do the upgrade again.
I need the console ouput during the reboot.
-
OK
-) Rollback to 23.09.1
-) Upgrade to 24.03 beta- After reboot:
OK, I've create verbose_rc file .... which log file should I give you?
-
You'll need to watch the boot at the console. I just need the end of it. Most likely what is happening is that you are actually booting into the new version but it's failing boot verification for some reason and automatically rolling back to the previous.
-
OK, I carefully repeated the whole update process.
I checked the boot sequence carefully and there is no upgrade attempt.
The post upgrade 23.09.1->24.03 Beta system seems to boot from the snapshot related to 23.09.1 without even trying to upgrade.
That is if I do not go to "play" with the BE ... if I go to force the snapshot, it starts correctly in 24.03. -
Mhhhhh something is not working
If I click, relative to the last line of this image, on... start from this snapshot (24.03b) the system restarts in 23.09.1
-
-
Why this one ?
I've just set a new default boot snapshot (change the star) .... I did not set a "one time boot mode"
-
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.
