The reset button on the 1100 only resets the power. It doesn't reset the config. So it will still be running whatever it was last configured as.

@stephenw10 I turned on https and now my laptop works.

@TheGushi LOL that is a wonderful analogy.

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.

@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.

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.

I just ran the update to 23.09.1 and that has solved the issue to see 24.03

@rbojorquez https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/reinstall-pfsense.html

Ideally, connect to the console and see what it says before powering off.

https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/connect-to-console.html

Best of luck!

I would reinstall anyway from that situation. If the bootloader is missing you can't really be sure other files are not also missing.

Hmm, well it's unsupported. I expect that to fail.

Yes you will need to reinstall clean because that is the last 32bit version. That hardware supports 64bit though and will run the current version. It's not the fastest but if it's working currently it should still be good. It will pass 250Mbps easily.

You should be able to backup the config, reinstall 2.7.2, then restore the config into it.