@jimp I ran 'pfSens-upgrade' from the Shell and the world is now safe! Other than something in item #1, none of the other issues should have been a problem on my system. Here is what I have installed. [image: 1656589707610-b15b044b-06b8-4008-8a2a-22786ca6a1e2-image.png]

You might try switching the branch back to 22.01 and then back 22.05 which should pull in the updated repo pkg again. Otherwise try running at tyhe command line: pkg-static -d update The errors that returns should tell you what's happening. Steve

@jimp I appreciate the help. Had contacted TAC, I think they thought as you did. I couldn't zero out mmdc0 while booted, and in the haze of the moment, it didn't occur to me to boot off the install media to get to a shell that I could zero it out in (duh!). Ah well. Before that, I did zero out the larger ssd (btw, it's far faster and more descriptive if you run that dd command with "bs=1024k status=progress") without any improvement, so it was definitely something in the mmdc0, because everything went smoothly after zero'ing out that drive. Thanks!

@rajbps Backup the configuration on the old hardware to your PC. Install pfsense on your new hardware. During installation of pfsense provide the configuration (by copying it onto the target disk or supplying it during the install), or I find it easier to skip that and during the first boot of pfsense cancel out of the wizard and restore your saved configuration. During the first boot after the configuration has been restored you will need to reassign the interfaces to the new hardware NICs

@voxmagna1 The other option is to tell Firefox to accept/ignore the certificate error by clicking Advanced on that error/warning page, or adding an exception manually in Settings/Privacy and Security/Certificates. Or add the self signed cert to your browser: https://forum.netgate.com/topic/154187/how-to-accept-self-signed-certificates-from-pfsense-in-firefox That may get around your a/v warning. HTTPS with a self signed cert is more secure than HTTP. I've actually had it the other way where a/v blocks logins on HTTP sites.

The mouse wouldn't work there, nor would typing the letter. There is more than one entry on the screen so pressing the letter only highlights the entry. Select the menu entry with the up/down arrow and then press Enter.

I didn't manage to solve the upgrade issue, but I did manage to get to the device with a small portable screen and keyboard. So in the end, I did a clean install (using the existing config.xml to restore) and upgraded that way. With a screen, keyboard and 2.6-loaded thumb drive, the install was a piece of cake.

@ex1580 mine has also returned with a snort update I just installed. YEAH

No ideas?

It would be root in the installer and not admin. If you do passwd or maybe passwd root it should set the password and let to go from there, or it did last I tried it. I haven't tried it lately, but it hasn't been that long ago.

FYI: https://forum.netgate.com/topic/172697/pfsense-plus-software-version-22-05-release-candidate-is-now-available-for-testing

@cclcyber I'm having the same issue. Did you ever find an answer?

@havastamas Okay, the server might have been down, thanks.

@jimp Thank you the explanation; much appreciated! Once 22.05 comes out, I will update to that and then take a backup config once again and then as you mentioned hopefully by 22.09, when I update to that - I will take a new backup and then also would be able to save the installer for my non-Netgate hardware to save some steps for future rebuilds. One more additional question; Do you foresee Netgate getting rid of CE? Or Netgate start charging for Home/Lab use? I am trying to make the decision if I made the right call to move away from CE to Plus for my Home use router/firewall.

@nasheayahu It's not really designed to upgrade pfSense via USB. You can kind of do it though, for instance, to convert to ZFS. This process allows pulling the config file during installation: https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#recover-config-xml-from-existing-installation I would definitely make sure you have your own backup though. Always a good idea. Since you have a 2100 you want the Plus software so you can open a free ticket. CE is the free, AMD64 software.

That kind of segfault in pkg can also happen if you have a package installed that is not present in the current release. The most common one is an older Zabbix version. You should be able to uninstall that package and then upgrade as normal.

@bingo600 GOOD NEWS. Solved it, and it IS due to a bug of RAM disk + ZFS. See here.

@someone464 I tried the exact same progress as yesterday today, it magically works now, very weird.