@chrcoluk Thank you for the kind reply. I'm wondering if the developers could write in their pfSense updates a way to check to see if what's installed is actually correct, and if not, automagically correct it? I would imagine this would make things easier for the user. Any ideas if this can be done or who to ask if this can be done? Thanks.

@stephenw10 said in v2.6.0 to Plus. No address record.: Ah, so you registered and were able to upgrade OK? That is correct. Thanks you, Onecut

@johnpoz said in System Update to 22.10: There is no 22.10, the next release of 22 is scheduled to be 22.09 It's actually going to be 22.11 but we haven't updated the snapshots yet to reflect that. It's already that way in Redmine, though.

@kuschi Open a ticket with TAC, include your Netgate Device ID and these screen shots.

@johnpoz always humbling when a bit more research would've showed me a solution, right on this forum!! You are correct, it is an SG-1100. I don't know how to test for the certificate verification failure now that I've upgraded the package. But the first thing I'll try when the error comes back is do a power cycle! Thanks for the quick reply and have a nice weekend.

@peterg said in Reinstall pfsense+ on a whitebox to get ZFS: Thanks @bingo600 , I didn't realise CE 2.6.0 had ZFS. I've got backups for everything so it should be straightforward. Yup ... ZFS was introduced in 2.4.x , but it still used UFS as default. When you pull your hair , and it says no disk selected during ZFS install , just goto that menu and select the disk w. space , it will show an asterisk. Don't select the usb stick ... /Bingo

You absolutely cannot go from 2.7 to 2.6 "just fine". No downgrade path has ever been viable. There may be ways to force it, but it is not supported.

@doug-butte Check out https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide-versions.html#upgrading-from-versions-older-than-pfsense-2-5-0 Also follow the URL in my signature to get the latest install as an image file and restore a backup config afterwards.

It does a check before running that is calculated by pkg and it will not proceed if it sees that it would consume too much. Problem is that isn't always 100% accurate for various reasons though it's usually close enough that it gets it right. That's the only real source of data it has on how much more space the upgrade will take, so it's the most accurate method we have. Usually it would still come back up but maybe not have upgraded all the component packages, but not always (As you are seeing). It's also one of many reasons we suggest removing all packages before doing an upgrade, as that will also increase the available disk space as well as reduce the amount of things changed on disk during the upgrade.

[image: 1657018101590-image001-2.png] I just tried again from cli using pfSense-upgrade -4 and got the same error.

@jimp thanks.

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