Okay, I instead updated to the deprecated 2.4.5-RELEASE-p1, and that went fine. I then updated from that to 21.02_1, which also went fine. Problem solved. Sorry for the noise.

@jimp In case it's helpful or necessary, here is the ipsec portion of my config file. (Don't have any actual ipsec tunnels configured.) <ipsec> <phase1>i</phase1> <logging> <dmn>1</dmn> <mgr>1</mgr> <ike>1</ike> <chd>1</chd> <job>1</job> <cfg>1</cfg> <knl>1</knl> <net>1</net> <asn>1</asn> <enc>1</enc> <imc>1</imc> <imv>1</imv> <pts>1</pts> <tls>1</tls> <esp>1</esp> <lib>1</lib> </logging> </ipsec>

If you contact support at https://go.netgate.com they can look up your info in other ways and get you the installation image for Plus on your Netgate hardware.

@danielduarte 2.4.4 is out of service it has been removed you need to upgrade to 2.5.0

@jimp At this point, I might as well wait for 2.5.1 and probably a couple of weeks after that to see the experience from other users. I'll post back once I've actually attempted to upgrade.

@jdeloach Great to know! and thank you!

@steveits Thanks. Just did that and was able to reinstall and load my config file and am now sorted.

Finally, I managed the setup and my old config.xml hast been recognized and everything ist working again with 2.5.0 During the setup process I have choose the wrong console. With ANSI I was mit able to select any options. With VT100 everything went very smoothly in about 15 min. Kind regards Alex

@daniellltorres Seems to be an issue with the LSI Raid chip. Maybe a BIOS or firmware update can solve it. Or you can deactivate / pull out the LSI and use the other disc controller if available.

@vargr Just a quick follow-up and officially closing down this thread: The problem is solved! Gertjan was right and a new firmware was required. It was very easy to obtain and following the link above easy to install (but I always feel nervous when updating firmware). Remember, that pfsense resets its IP-address to 192.168.1.1 as well as its admin password. Thank you again to Gertjan!

@fresnoboy Have a look here , a way to "fallback" https://forum.netgate.com/post/965219 /Bingo

This issue is resolved. I opened a support ticket, and they had me reimage the device with the 21.02_1 image (they linked me the correct image to use). There was an option to recover an existing config before install, and using that I was able to recover my old config. System is back up now and working ok, original config intact, so it was an easy recovery. I have also learned about the free online config backup service PFsence provides. I will be using that from now on, incase this happens again. Thank you.

@n8lbv Don't shoot the messenger? Yes, 6 patches, bugs do happen, to err is human. You may not like it, but Patches are an easy solution, better than waiting for a next release, and faster than doing a fresh install IMHO. (don't need to drive onsite + you get to keep the updated BSD. How's that for a win-win )

@webdawg said in 2.4.5_1 to 21.02_1 Not Working - SG-2440: And then still have a problem. You won't need it with the new stuff.... Cross your fingers and hope for the best You hope,.... you can implement your entire configuration from config -......... anything.xml

@fireodo said in pfSense-upgrade 0.94 -> 0.95: It is fixed since this morning 0.95 -> 0.96 Solved. Thanks!!

@perphide No idea if there is any (known) password during setup

I'd go exactly as you described. Crate a new VM and install 2.5.0 Take a pfSense Backup from the existing 2.4.4 VM Shut down 2.4.4 and restore the config into 2.5.0 If anything goes wrong you can just power on the 2.4.4 VM again. -Rico