@pangel I don’t know but if you aren’t 100% sure there are no other problems a reinstall is probably safest.

@gertjan re-install is exactly what fixed it. Netgate got the file to me in record time. Thanks for the thoughts.

Hi, today it worked from the GUI. regards,

Probably why : http://repo00.atx.netgate.com/pkg/pfSense_plus-v22_05_aarch64-pfSense_plus_v22_05/ 404 Not Found nginx

@johnpoz The response to trying to update pkg: Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pkg-static: Repository pfSense has a wrong packagesite, need to re-create database Fetching meta.conf: . done Fetching packagesite.txz: .......... done Processing entries: pkg-static: Newer FreeBSD version for package pfSense-pkg-RRD_Summary: To ignore this error set IGNORE_OSVERSION=yes Will wait until I have cable, but hoping there is a way to remove the offending files and do a regular update.

@chrcoluk said in pfSense Plus licenses and system patches: Is it easy to get multiple home licenses, so e.g. one to test on a VM, then a second to put on the actual firewall device? Tokens are non-transferable, the same with TAC support, so once it's tied to a device it's locked to that device and you need to purchase/procure an additional license to move it. Be weary, as well, that VM NDIs will change whenever you move hosts, too.

That error during the installation process usually means it's having trouble reading the installer media. The correct image to use would be the USB memstick installer and the best way to image it is with Etcher. You might have tried multiple USB thumb drives but were they all the same brand/model? It might be that the system/BIOS/hardware doesn't get along with that particular drive type. We've seen that happen on occasion, especially with certain combinations of USB drives and USB 3.0 ports. We've also seen errors on certain hardware with high capacity USB drives where smaller drives work fine. If the target system has other USB ports you might also try using those, especially if the one you're having a problem with is USB 3 and there is a USB 2 port you can try.

I have decided against doing things this way, and will do a clean install instead.

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