@markgca What does the system log say about those OpenVPN gateways? The 20 minute reboot indicates to me that it's hanging on something to do with interfaces. What have you found from plugging into the console port during a reboot cycle?

The -d switch there only enables debugging output. It shouldn't make any difference in itself. But I'm glad you were able to get past that anyway. Steve

@mururoa said in System update failed !: It is a know bug https://redmine.pfsense.org/issues/12796

@johnpoz I just figured that, since they are supporting pfSense+ on 3rd party hardware, we may finally be able to install onto ARM, especially those devices that are the base for their own appliances. Maybe that's just wishful thinking on my part.

I did both, and they both went without a hitch. The only reason I backed up and reinstalled was because I wanted to move to ZFS. I have one issue though. For some reason, even after a full new install and restore, I'm still not getting the option to update to 22.01. I already registered and have the activation key in my email. I even tried "pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade", and rebooted, just in case Tried to halt, unplug for 1 minute (I know it says 30 seconds, but I don't believe in "overkill"), booted back up, all to no avail. I do use an actual Qotom device for my PFsense, so your mileage may vary.

@gertjan Thanks, I just did this (as I finally made so far down the troubleshooting page... I was impatient and posted before I reached the end) and it worked. Steen

@mig39 Just to link the doc page on it: https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#segmentation-fault-in-pkg ...which is similar but mentions "SSL routines:ssl3_send_client_verify:internal error" (which is what I recall seeing, last spring) instead of "SSL routines:tls_construct_cert_verify."

@jimp With it not being a file server I figure that having the card would be fine. Didn't think about putting the drives into JBOD and doing a mirrored zpool, just always told that the dark dimension will appear if one does that on a RAID controller LOL.

@yorickbm Nope "Intel/AMD" x64 only. The only ARM install supported is Netgates own HW. /Bingo

Also please don't forget that skipping multiple versions is always a "bigger" problem/endeavour as just upgrading to the next version. Re-Installing with config-recovery in most cases is the far better alternative then simply updating and updating again. As the Plus devices got ZFS as filesystem relatively late in the game with 21.05, I'd always recommend to everyone that has the ability to be on site with the device to just take the latest stable version (21.05.2 or 22.01 if you're adventurous) and do a fresh install with config-recovery. That is available on the console prior to selecting a new install with either UFS/ZFS. Just let it find & recover the current config (or save it yourself) and do a new install with ZFS of the current CE/Plus release of your choice and afterwards watch it boot up the first time with your configuration intact and your interface setup already in place. Had no problem with that with variuos customers that "skipped a few" updates "because the system was OK and just ran..." you know the kind

Seems that this problem occurred in previous pfSense versions as well. https://forum.netgate.com/topic/106500/package-manager-unable-download-the-list-of-packages-on-new-installation

@netblues I am beginning to think that Kubuntu uses some older packages. I had tried to install a future release, but same issue. I will look at upgrading my qemu/kvm to see if this correct the issue. Or stick with OPNsense. I believe that it is build on hardenedBSD, so maybe that is why I was able to install with the current configuration. Regards

@ericatnetgate Please open a ticket at https://www.netgate.com/tac-support-request to request the current firmware!

@johnnyg_mi said in Installer fails, reboots PC, and repeat: I'm using pfSense-CE-memstick-2.5.2-RELEASE-amd64.img.gz just downloaded today. I flashed it to a USB drive, trying both Rufus AND Etcher, but I still have the same issue. After boot, I see the "Welcome to pfSense" menu and it automatically boots after 3 seconds. It starts to load but then reboots 3-4 seconds later. It simply repeats this cycle, never getting to the installer. I've installed other OSes on the same PC without this issue: CentOS Stream 8, Stream 9, and Debian 11. I have also tried downloading pfSense-CE-2.5.2-RELEASE-amd64.iso and writing/burning that to a DVD, but that has the same problem. Just before the PC reboots, I captured the errors in the attached image. I have also tried to intervene when the "Welcome to pfSense" boot menu appears; I have set "Cons: Video" (shows "Cons: Serial" by default) as well as attempting to boot in Single user mode. I have also used the Boot Options menu to set Safe Mode: On and Verbose: On, but I see the same result.[image: 1644105617095-20220205_184224-resized.jpg] See if this thread might help you out: https://forum.netgate.com/topic/161963/boot-from-install-media-results-in-can-t-find-boot-entropy. Others that have experienced this issue in the past had to change some BIOS settings to get around it. And at least one person I recall reading a post from some time back had to actually update the BIOS in his hardware device.

@pwest all in the config file. :)