@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 [image: 1703550463313-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.

@stephenw10 Yes, that was it! I have managed to upgrade it directly from 2.7.0 to 2.7.2 without any apparent issue. Thank you Stephen for you help!

@stephenw10 said in Fail upgrade but...: Yes I would reinstall 23.09.1 to be sure you have a clean system. Thanks I am not very experienced, the idea of reinstalling scares me a bit. This morning I couldn't access the administration web page, I had a 502 bad gateway. I managed to connect with the serial port, ran pkg-static info -x pfSense and saw that some packages were 23.09.1 and some 23.05.1. I upgraded with pkg-static upgrade and everything seems to be fine at the moment. Thank you very much

@SteveITS Thanks, the first was spot-on. Unfortunately, updating now fails with the EFI-space-problem - on a 500G SSD, yeah sure. However, I reinstalled all my 2.7.0 packages an the FW works again (at 2.7.0). The EFI-problem will have to wait for another day. Thanks for a non-sleepless night :).

@stephenw10 Thanks for the pointer on passing the -y flag. Prior to seeing this, I was able to install the sudo package and run the command in an SSH shell. After the "missing" packages were installed, things seem to be correct now. It is troubling that there was not an explicit notification from pfSense warning that the original upgrade had failed. This seems like a significant omission to me. When using the CLI available from the GUI (System / Command Prompt), I could not figure out a way for it to accept interactive input. I see that the documentation seems to be consistent with this behavior: "Interactive commands, such as vi will fail similarly, or may exit due to other issues with the terminal being non-interactive." Thanks again for your help!

What upgrades is it offering you? You might have to do it in several steps. If you really are running 2.4.0 though I would reinstall. Steve