Yes, sorry to everyone who was waiting on that. Timing of other things just got in the way. I'm going to make another attempt at this. Hopefully it will bear fruit.

@TheGushi Sounds like you got it solved, congrats. That seems like quite a feat.

There is a feedback link on the doc pages to submit a ticket for doc changes/suggestions.

I have not actually used the installer yet but I was under the impression it is a generic one for any hardware including ARM models? Also one of the goals was to have one installer, and it can pull down one of a choice of versions, and Plus or CE. So one doesn't need to redownload it for every version of pfSense.

In general I've seen Netgate advise that if a router is more than a few versions old, to just reinstall. If nothing else that gets you ZFS now, but it also skips all the intermediate upgrade steps. FWIW the very few times I've run into a problem with an upgrade over the last 10ish years, it's been when it was more than a couple years old.

@jimp

So that cured the 4-5 high php-fpm items showing on the "top" while sitting on the dashboard and 100% CPU

The only new observation after adding the system information widget back and adding the CPU usage item (which I had removed as a test) and then refreshing the entire dashboard was that everything was responsive except the CPU usage line item. It took a good almost 2 minutes to "retrieve" the value. which is now only a couple of points off (higher) where it would normally be which is <20% (really hard to tell when widgets are actually in the process of updating their data)
Removing / adding and saving widgets is back to normal. back to 10-15 seconds instead of minutes+.

Once it got past that initial retrieve of the CPU usage it seems to be updating in less time but hard to tell how long. I see no other dashboard issues, everything seems near "normal" php-fpm is no longer locked at the top of top and certainly not 4-5 copies of it. When it is running it is only on top briefly.
There is really nothing stuck on top anymore it varies as normal. user is bouncing between 1 and 20% system between 3 and 10%. which seems more "normal" on this system

Thanks for all the work you guys have put into this.

@stephenw10

We spoke last week - still awaiting cabling from monoprice to rewire and utilize the new interfaces, and remove the old interfaces. In regards to the pfSense-repoc -D line, here's what I get:

[23.09.1-RELEASE][admin@efreet.warfaresdl.com]/root: pfSense-repoc -D pfSense-repoc: no package 'name' pfSense-repoc: no pfSense packages installed OS: FreeBSD OS Version: 14.0-CURRENT Platform: amd64 Product: Netgate pfSense Plus Version: 23.09.1-RELEASE FS type: ufs Language: en_US Model: QEMU Guest NDI: *hidden* Package prefix: pfSense-pkg- Serial: (null) Repo path: /usr/local/etc/pfSense Request query: {"platform":"QEMU Guest","os":"FreeBSD","osver":"14.0-CURRENT","prod":"Netgate pfSense Plus","ver":"23.09.1-RELEASE","ed":"Plus","fstype":"ufs","pkgs":"[]"} POST data: uid=*hidden*&language=en_US&serial=&version=%7B%22platform%22%3A%22QEMU+Guest%22%2C%22os%22%3A%22FreeBSD%22%2C%22osver%22%3A%2214.0-CURRENT%22%2C%22prod%22%3A%22Netgate+pfSense+Plus%22%2C%22ver%22%3A%2223.09.1-RELEASE%22%2C%22ed%22%3A%22Plus%22%2C%22fstype%22%3A%22ufs%22%2C%22pkgs%22%3A%22%5B%5D%22%7D&arch=amd64 Messages: Your device has not been registered for pfSense+. Please purchase a pfSense+ subscription to receive future updates. <a href="https://shop.netgate.com/products/pfsense-software-subscription" target="_blank" rel="noopener noreferrer">Netgate store</a>

In my case, it's apparently because I added a couple of new interfaces that didn't exist when I registered. I'm currently trying to transition from my old 1G ethernet to a new 10G ethernet solution with new interfaces (and I purchased pfSense+ to support the new configuration). Apparently this invalidated my NID, and will invalidate it again when I finalize my configuration by removing my old 1G interfaces.

Saw the same thing when attempting to update from 24.03 on third-party hardware via the GUI.

Connected to the console, confirmed that no other pfsense-upgrade instances were running, then upgraded via the console (Option 13). That upgrade went smoothly with no complaints about other pfsense-upgrade instances.

@marcosm
FRR its for bgp and only for advertising less than 2 prefixes and receiving 10. Def not meant for edge routing in that way.

The unit was also up for over 100 days so could it be possible there was some memory not properly released?

In either case, successful upgrade and re-adding the packages is a snap. I will be thinking a bit more carefully about what packages will get installed at a future point.

@SteveITS Free about 94Gb mirror raid

Yup I wouldn't expect any issues on a 2100. But you can roll back and test it locally.

Of course custom options are always a risk to some degree.

The installer is built on a newer FreeBSD version. So it implies that something in your hardware is not supported/recognised there. Probably the drive controller somehow.

Check the boot logs from the legacy and net installers for errors or omissions.

If there's a regression there it would be good to know about it now because that system probably won't boot in 24.03, 24.11 or 2.8.

Steve

@KKKalle77 said in Netgate Device ID change after reboot:

I just do an easy reboot, like other time.

Maybe you can compare the output of "ifconfig -a" between working and not working?

@pfcharles said in issues upgrading Netgate 4100 from 23.09.1 to 24.03:

I do get an odd popup, which disappears after a few seconds...

You will see that if you log into the webgui as soon as it becomes available but before bootup has completed. As you are seeing it should disappear when bootup completes.

The legacy installer images be found here: https://atxfiles.netgate.com/mirror/downloads/

You can ask TAC for the 23.09.1 recovery image.

I've been running 24.03 on a 3100 as my edge here since it we started tested it and it's been generally fine.

@stephenw10 excellent point. Turns out I was still on it, fixed that and the install went smoothly from there.
Thanks for the response!

Run the OS upgrade. The pkgs are re-installed at upgrade anyway.