@noloader said in Where is /conf/upgrade_log.latest.txt located?:

/conf/upgrade_log.latest.txt

^ right there

you can either

a) ssh in

or;

b) Diagnostics -> Command Prompt -> Download File

or;

c) Diagnostics -> Edit File

Option b is a good option. Will get a copy on your local system, then open it there.

@SteveITS Thank you. I ended up doing this using an image provided to me from Netgate Support 🙏

@Stewart @SteveITS

This was solved here.

Due to changes in pkg, the new version of pkg may not be able to properly locate and use the CA trust store when running on the previous version before upgrading. If the firewall is unable to load packages or check for updates after selecting the CE 2.7.1 upgrade branch, run certctl rehash from the console, a root shell prompt, or via Diagnostics > Command Prompt. This will allow pkg to utilize the system certificates until the next reboot.

This is true in 2.7.0 as well. Running the certctl rehash brought it up to be able to upgrade.

@neuf_16 said in 2.7.2 Upgrade Issue (bug):

@bmeeks Yes I am well aware that it is saying 2.7.0 in bold. That is why I created this post. You will also notice the second screenshot which says CURRENT Base System is already 2.7.2

Yes, I know that. But the very first words of your post said: I upgraded to 2.7.2.

Not trying to be nit-picky, but rather just wanted to be sure you were aware the attempted upgrade was unsuccessful. If you had said "I attempted an upgrade to 2.7.2, but it failed" or something similar to that, there would have been no ambiguity. Not all posters here use English as their native language, and I've seen some misunderstandings/miscommunications about issues in the past due to that. Just clarifying the condition, not trying to be condescending or insulting.

There are many, many posts here on the forum about similar issues. The Netgate team has been trying to make the pkg utility and upgrades in general more robust. But there are some apparent growing pains with that process.

Look through all the similar posts and you should find a workable solution. Or you can save off your config.xml file and simply reinstall with a fresh pfSense 2.7.2 CE image file and then restore/recover you config.xml to bring back your firewall configuration.

hi @SteveITS

Thank you I will try on the next allowable schedule for update

@SteveITS I solved with this https://forum.netgate.com/topic/184661/unable-to-upgrade-from-2-7-1-to-2-7-2-unmounting-boot-efi-done-failed/23

I even just tried doing an outbound NAT for the firewall and it didn't seem to help

9b709ae6-6907-4076-a1aa-6d94785d064b-image.png

same thing when I try and ping out from it, 100% packet loss.

@michmoor TNX a milion your solution works fine.
Many Many thanks! You saved me hours and hours to reinstall and reconfig everything.
I love you!

@jimp said in 23.09.1 - pfsense-boot fails to upgrade:

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

This fixed my issue thanks @jimp

@old_man_noBS Tnx ! Worked like a charm.

I would not expect it to. Ever. What you're seeing is odd.

@stephenw10 Yap, it did. Procedure was:

8GB USB flash drive, formatted FAT32 Stored my config as file "config.xml" on it Checked on the PC that the config was fine and readable in Notepad++ Plugged it into my server (Dell R720) USB Device passthrough to the pfsense VM Booted pfsense from install ISO Installer recognized the USB drive and also the config.xml, it wrote that config.xml was copied into the restore area before showing the "Reboot now" screen Acknowledged the reboot At startup it wrote that the config.xml is corrupt (0 Byte) and it died into the login screen Pulled the USB stick, checked on the PC and found the config.xml file on the stick empty with 0 Bytes length

I did that several times, always with the same result and with the 2.7.0 and the 2.7.2 install ISO.

Yes you should be able to upgrade to 23.09.1 and you should upgrade.

Apparently the good old help of attempting to document and present a decent forum post ...is what was required to solve the problem....

For the aftermath readers, the solution was:

$ pkg-static bootstrap -f

Followed by

pkg-static install -fy pkg pfSense-repo pfSense-upgrade

Then the update would roll through via GUI.

Ideas from here:
https://www.reddit.com/r/freebsd/comments/17zbznm/freebsd_140_upgrade_pkg_utility_stops_working/

If you want to keep the other disk connected you could wipe the metadata from the disk as described in the documentation:

https://docs.netgate.com/pfsense/en/latest/troubleshooting/multiple-disks.html

However, if it's not needed it's probably best to disconnect/remove it as you have done.

Yes strange because you have the resolution behaviour set to use localhost (Unbound) by default and only fall back to remote servers.

It implies Unbound is failing yet you specifically tested that and it resolved OK.

Hmm, that looks like a drive issue. Check the SMART status. Consider replacing it.

Steve

It can't find anything to boot on the drive. But it is still loading the boot loader which is on the disk so it's probably not drive failure.

I would just reinstall 2.7.2 clean and restore your config into it, assuming you have a backup.

Steve

pkg-static update only updates the available packages. The only thing that could get upgraded there is pkg itself. That can show that libssl error but not for pkg-static which is what pfSense upgrade uses.

@stephenw10 Ok thanks, have done.