(Solved) Image boot order after upgrading to 24.03 (Patch1)

Dobby_

I upgraded today to ...1722 and then to ...1709 and now to ...1738

After the last upgrade I saw this message

Netgate pfSense Plus 24.03-RELEASE (Patch 1) amd64 20240424-1738
Bootup complete

But then I found the following information

 Current Boot Environment: default_20240423231425_20240424001722_2024042420070
Next Boot Environment: default_20240423231425_20240424001722_2024042420070

There is no entry about ...1738

stephenw10

Where are you expecting to see that?

The ZFS BE names are not related to the pfSense build timestamps.

Steve

Dobby_

@stephenw10 said in Image boot order after upgrading to 24.03 (Patch1):

Where are you expecting to see that?

In the console after boot and the other one in the WebGui.

The ZFS BE names are not related to the pfSense build timestamps.

Ah, ok then all is right here, (solved) I was expecting to see now that
the actual and the next boot image will be ending with a ...1738 and
thought something went wrong.

jimp

Looks like your BE names are from a time in the 24.03 dev cycle when they had the timestamp added over and over. Once you get to a good point you should rename the current one to something like default or stable for example and then remove the others with the unnecessarily super long names

The Party of Hell No

@jimp I add sequential numbers at the end following clone_123... to denote the earliest to the latest. This helps in two ways. One, when deciding which boot environments are older and can be deleted. The other is if I have to recover using the console; choosing a boot environment from the drop-down choices is confusing when the choices are listed - they all look essentially the same. So by customizing the name makes it way more precise? to make the right choice in a time of stress.

jimp

Whatever works for you, have at it!

But <name>_timestamp1_timestamp2_timestamp3 looked more like the bug we fixed in 24.03 beta than anything someone would want deliberately.

mvikman

Before upgrading I usually make a new clone from the working BE, name it to xx.yy_upgrade, set it to default boot and boot to it before upgrade.
If all seems ok after a testing period, I rename it to xx.yy_stable