I am definitely avoiding any of the Cxxxx CPU's now when I am doing hardware selection.  If this same bug happened on Intel's server or desktop CPU's, yes it will definitely be a big deal.  Just look at AMD's ryzen issue, and that only effected very edge cases.

I wonder if I actually received the same hardware as what I sent in. On one of my other SG-2440 replacements, I got someone else's system w/ a different serial # and config. Granted that system had no functional issues after a config reset.  May be it was luck to have gotten someone else's box??

@internetservices:

Solution:
disable 'Monitor M-Wait' in bios
Could be under Features tab > CPU Configuration

I cant seem to find this feature in my bios http://asrock.com/mb/Intel/J3455-ITX/

Any suggestions?

Are you able to press the key during that count time and perform a run recovery?
You will need the sg-3100 arm firmware found at the gold member`s page and a pendrive.

You can find the procedure to perform this recovery at: https://www.netgate.com/docs

Hope it helps you.

Edit:

You will have to configure everything again if you do the procedure above ok?
All configuration will be lost !!

Ive got several boxes that are working fine..  Try pressing your F-5 key..

Seems to be good now. Perhaps the lock was something temporary. I dunno. I upgraded. Thanks.

It should be on by default but you can check yourself after installation.

Depending on the filesystem used:

UFS - run this on the command prompt:

tunefs -p /dev/ufsid/

Where <identifier>is the UFSID for the root filesystem, you can get that from /etc/fstab from the line that has "/" as the mountpoint (second column).

ZFS - run this:

sysctl vfs.zfs.trim.enabled

If it reports value of 1 then your system is using TRIM.</identifier>

OK I think I've resolved the issue by forcing a reinstall of all the pfsense packages.

While ssh'd in to the box and in a shell, I ran pkg info | less to look at the names of all installed packages.

I ran pkg clean -ay to clean the archives.

I ran the following to force a reinstall of all.

pkg install -fy pfSense-2.4.2 pfSense-Status_Monitoring-1.7.5 pfSense-base-2.4.2 pfSense-default-config-2.4.2 pfSense-kernel-pfSense-2.4.2 pfSense-rc-2.4.2 pfSense-repo-2.4.2_1 pfSense-upgrade-0.40

And now the web UI reports

2.4.2-RELEASE (amd64) built on Mon Nov 20 08:12:56 CST 2017 FreeBSD 11.1-RELEASE-p4

@blueadept:

I have the vpn issue also. I found that after I restart the firewall, I have to log back in and restart the openvpn. That seems to fix the issue for me.
Everything seems to be working and it shows the vpn up. The vpn users can connect but cant go anywhere. After I restart the service, it seems to work.

Restarted firewall few times and also tried to disconnect and connect the VPNs. But still having the same issue. It shows that its connected just cant connect to them.

Thanks for that, I was really hoping it would just be that simple to fix. But unfortunately that did not help.

@jimp:

2.3.5 is listed in the GUI for updates if you have the correct update branch selected, but 2.3.6 isn't that different from 2.3.5 at the moment (or 2.3.5-p1 when that happens). You may as well just stay there for the time being.

Hmm, it wasn't appearing, it was showing 2.3.4 as the latest version until I switched to the dev branch. I'll keep an eye out, and will try on IE instead of Chrome when the next release comes around. Thanks for the help.

@Grimson: you got a valid point!
I reinstalled my pfsense and now my OpenVPN Tunnel is working again :)

@mais_um:

Hi

Have you wait to package be reinstalled? Manually reinstall packages?

I tried the Reinstall alternative from the GUI but that did not work (yes it finished successfully).

However i just tried to first remove the package completely and than re-installing it and that worked! It even kept my settings for AutoConfigBackup.

This topic can be locked, thanks!

Up ? :)

Connect to the console or ssh and run option 13, or go to a shell prompt (console or ssh option 8) and run this:

pfSense-upgrade -d

If that produces any errors, post them here.

Yes, those packages are fine. Keep a backup, as always, just to be safe.

Reporting in…

My standalone SG2440 upgrade failed, too. The GUI said upgrade failed and the box became unresponsive. After digging up a console cable and driver, I bounced it to see a bunch of PHP library errors. I was up and running in a little less than an hour, after burning a stick with the latest release.

I've got a bunch of other boxen to upgrade. How do I tell what broke? I've got the uprade_log.txt, but nothing's obvious so far.

Console access is nice to have for an initial setup. Did that last decade. A minimal 640 x 400 will do just fine for that purpose.
Now i use the SSH access, and a tool like Putty. Their is no limit for a "screen size" - and very easy to 'setup'  :)