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

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

Steve

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.

@stephenw10 Thank you for your help. Successfully upgraded to 24.03

Well I would try several times at least. And I would try using several USB sticks.

When it fails like that you can drop to the shell and check what the exact errors are.

I would start by just running: dmesg

If it's a drive issue you will see a bunch of errors show there.