@bingo600 I am not seeing the "Devel" branch to upgrade from 2.7 to 2.8 for my VM...even after rebooting twice.

Screenshot 2023-06-30 at 2.40.24 PM.png

@phil214 said in The upgrade process is still broken for 23.05.1:

Our confidence in Netgate is decreasing and this is pushing us to look at other solutions for linking our office and cloud infrastructure

Be careful.
The very same 'ISO' "pfSense 23.01" has been used to init thousands of pfSense installs, and nearly all have left 23.01 to go to 23.05 or even 23.05.1 or whatever intermediate version.
So, upgrading from an identical situation, works.

And I'm of course very aware that "it doesn't work for all of us" as we all have to choice to set up our own pfSense 'as we want'.

For example : the only difference between your system and mine is : the settings.
And also : the hardware used - mine is a 4100.
The uplink can also be a factor.

What I want to say : whatever you change, you could bring the same situation with you.

What I advise you to do : do the thing that works. Go TAC Netgate. Ask for a 23.05 or even a 23.05.1 IS. Burn it to a USB drive.
Install.
DO NOT ( !!!!) import your settings : just make WAN work - that's all !! NO "enter DNS IPs" no NAT or firewall rule stuff. Just a WAN, LAN and you.
Now check that it shows upgrades.
Do so if needed.
Test basic operations.

Now, import your"23.01" saved config.
Test again.
If it is broken again : you know where to find the issue ;) Mark your saved config as 'bad - don't use'
And you know how to get rid of it.

@onetwo see if there is an error:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/firewall.html#new-rules-are-not-applied

@stephenw10 Yep. He has secure boot disabled anyway and won't run into a disk space issue, sooo... The VM in my sig is on 23.01.

Not yet. But, yes, you can easily install the most recent dev snapshot and then upgrade to RC. Or to Plus.

@mfld said in Upgrade to 23.01 results in empty firmware branches:

This brings us back to my feature request that customer should have an unregister / force re-register option or the register option should automatically unlock when token is expired + expiry date should be displayed in GUI.

I probably wrote that redmine... :)

Hmm, two issues there. One looks like a backend issue. It should not pull CE repo data or revert to it if it still exists.

Send me your NDI in chat and I'll check it.

If should still have a route to that though. Try setting 'Prefer IPv4' in Sys > Adv > Networking.

Steve

@rlinnemann The most recent attempt was in that other thread but to recap in one spot with more detail, we had two scenarios. Both 2100s had the small EFI to begin with so needed a reinstall.

May 5. Client had a short power event. We found the UPS was defective, 10 seconds runtime. The router did not boot up afterwards. On the phone they said they unplugged it. I went there with a spare 2100 and a 23.01 USB install...that image was ‎downloaded February ‎18 by the way, I looked now that I'm logged in. I didn't even try to troubleshoot it, I just reinstalled since I knew we had to. It booted up, I restored the config file in the web GUI, and then realized it didn't boot up after. Figured it was dead, and had about 15 minute left, so put in place the new 2100. I didn't really pay attention to the errors at the time.

June 6. A coworker went out to reinstall on a 2100 at a client's office to get it over with. He used the same USB I made since he didn't want to burn another. Installed, restored the config file in the web GUI, and it wouldn't boot, as above. Those were the logs and screen caps in the other thread. He reinstalled again, it failed the same way again, and he called me. Fortunately he could plug his laptop into the Comcast modem and downloaded 23.05 to burn on a spare USB. He installed that and it was fine after.

In hindsight we think 2) was the same issue as 1). This week the same tech used his USB stick to install 23.05 on the router from 1) above and it seems fine after a few reboots.

I still have the "bad" USB, it's on my desk at work. Not sure how the USB stick or its image could be a problem like this but it didn't get recycled yet.

When I reinstalled on my 2100 at home, a few months ago, I used 22.05 because I couldn't find an 8 GB stick at home. (edit: Etcher, btw, doesn't warn you about the space needed if you try to write the compressed image directly, it just fails x% of the way through)

Edit: I had found that other thread because there are very few search results for the "cannot open /boot/lua/loader.lua" error.

Upgrades from 2.7 to 23.01 were only possible if the 2.7 version was from Feb 15th or earlier.

If not it will have the wrong php version. It should be possible to recover by doing a full forced pkg reinstall against the 23.01 repo.

However CE > Plus upgrades are now using 23.05 and that's possible from any 2.7 version.

Steve

The error it shows:

Checking integrity...Child process pid=30119 terminated abnormally: Killed Failed

Should have logged something that might indicate the cause.
Check the output of dmesg or the system log after triggering it.

Indeed, that should now be fixed. Will be in 23.05.1

i don't know what happened to the text I pasted,

Proceed with upgrade? (y/N) y

Removing vital flag from php81... done.

Downloading upgrade packages...

Updating pfSense-core repository catalogue...

pfSense-core repository is up to date.

Updating pfSense repository catalogue...

pfSense repository is up to date.

All repositories are up to date.

Checking for upgrades (60 candidates): .......... done

Processing candidates (60 candidates): .......... done

Checking integrity...Child process pid=38156 terminated abnormally: Killed

@jerseymike Open a ticket at https://go.netgate.com/ and include your NDI and your Shopify Order number for the Plus token.

@daredevilbear said in Upgrading from 2.6.0 to Plus - Unable to check for updates:

Any ideas on how to fix?

Please open a ticket and include both your NDI and your Order Number

https://go.netgate.com/

For repair : pfSense-upgrade -d -c

On my brand new pfsense (my first Netgate, an 8200) it says:
"0 candidate: 100%".

23.05 branch is now available for CE. I was able to directly upgrade today from 2.6.0 > 23.05 on server 2022 hyper v. No issues.

@jimp Just tried it - took a backup of my config using the GUI, created a VHDX of 20 MB. Init as MBR. Created one partition. Formatted it as FAT (20 MB is too small for FAT32). Created a folder "config" and put the backed up configuration file into it and renamed it "config.xml".

I copied my regular VM definitions, just changed the name. So it uses the same virtual HDD as the 1st VM. Only difference is that I add the above VHDX file as a 2nd HDD in its definition.

If I really screw things up, I shutdown VM1, boot VM2 - this restores the config w/o having to set up LAN etc. Shut VM2 down once it is up and boot VM1.

So confirmed (and a big thanks) - any attached disk which is partitioned and has a partition formatted FAT/FAT32 with a folder "config" in it with a file "config.xml" will be used during all boot if present and copied, replacing your config file. After booting, it must be removed otherwise on each boot, the config.xml file on it will replace your updated.