@jrey 23.09 to 23.09.1 on 2100 went smooth without a hitch

@etick Per https://forum.netgate.com/topic/184661/unable-to-upgrade-from-2-7-1-to-2-7-2-unmounting-boot-efi-done-failed there is a process but the safer way is to reinstall. https://redmine.pfsense.org/issues/15081

@Gertjan I did however just fix it :) I stopped panicing for a second and started thinking laterally. I noticed that /cf/conf is actually a zfs filesystem. So I said zfs mount /pfSense/cf/conf and it insisted it was mounted. No conf directory there, so something amiss. I have nothing to lose at this point staring at a reinstall with a 4 month old backup. I simply unmounted it and remounted it, and I have my configuration back, the GUI is working and I have saved the current configuration to many places :) Thanks for the suggestions, much appreciated :)

@LoGman said in Upgrade pfsense Netgate 6100, 23.05.1 > 23.09.1: Do I need to worry about these error messages? No, none of those look concerning. They look like old efi variables.

The root cause of this issue is fixed in 2.7.1/23.09. Going forward the selected repo branch is not switched when new releases are available. Updates are shown on the dashboard but the user will be required to select the new branch to upgrade.

@reynold yes as I recall it is. But as noted the default is to keep all settings during uninstall.

Where it asks you about VLANs is the interfaces assign prompt. You should complete that and assign WAN and LAN. When boot completes you will see the console menu like: *** Welcome to pfSense 2.7.2-RELEASE (amd64) on t70 *** WAN (wan) -> igb0 -> v4/DHCP4: 172.21.16.226/24 LAN (lan) -> igb1 -> v4: 192.168.226.1/24 0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option: Enter option 8 there to reach the command line. Then run the command there.

@IT_Luke Yes, I didn't reboot the system before applying the upgrade.

issues are fixed for me as well, thanks!

Yup it uses significant memory to run the upgrade. That will be freed eventually or if needed but as you found a reboot after upgrade will also free it. Steve

I upgraded yesterday via option 13 in SSH console. However I waited for more than 10 mins, it didn't reboot by itself and stayed at 2.7.1. After I manually rebooted the box,it shows now 2.7.2. Just wonder why reboot was not triggered.

Thanks, I opened a ticket, and the NDI is now in the system. I will try the available updates tonight.

@SteveITS Resolved - thank you

@boxcar2309 good choice. glad the redirect helped you out. Have a great day!

Locked out in the sense that the firewall issues no dhcp IP addresses with that no GUI access. I can access a putty session and it appears fine nothing shows any faults. I just get the white screen that has nothing on the browser not even the log in window. The apple said it can't get an IP has the whole ! Mark thing. My smartphone also and windows 10-11 it appears to not issue IP addresses. The only change I have done from last attempt was to remove all static mappings any only have the NAS and the MFP mapped before all my devices has static arp mappings ( ie the check marks in DHCP server area) [image: 1702148433114-screenshot_20231209-105906.png] I left the Mac address so I get the same IP could that be it? I should try to set them all back to static again. Originally the update worked it was just slower and showed a dual console message never seen before. [image: 1702148673135-1700616924030-screenshot_20231121-173033.png] after update shows dual 23.09 this is where logs stop with this like a bad driver loaded [image: 1702148708182-screenshot_20231209-105143.png] 2100 has no dual Display hardware options 23.05 never had the log above on this version

Either at the serial console directly or via SSH. Not using the webgui 'command prompt' because it only returns when a commmand completes and shows nothing if it hangs.

Update: Upgrade did not work. A lot of errors when i listed the packages. Reinstalled worked. Recover config did not work what it looked like but i had config saved so restored config and it worked. Thank you for the help.

@stephenw10 Looks Like that fixed it, Thank you so much! Hopefully this helps others who have the same issue!

[23.09.1-RELEASE][admin@6100.stevew.lan]/root: pkg which /usr/local/pfSense/include/vendor/autoload.php /usr/local/pfSense/include/vendor/autoload.php was installed by package pfSense-composer-deps-0.1 [23.09.1-RELEASE][admin@6100.stevew.lan]/root: pkg which /usr/local/pfSense/include/vendor/composer/autoload_real.php /usr/local/pfSense/include/vendor/composer/autoload_real.php was installed by package pfSense-composer-deps-0.1 So try installing or reinstalling pfSense-composer-deps-0.1: pkg-static install -f pfSense-composer-deps-0.1