What Phil said.

Dear Master  NOYB, Thanks for yours informations…

I got the solution from here https://forums.freebsd.org/threads/56524/ I had to disable SMP. *I use a very cheat and limited motherboard with literally no configurations in the bios.

The considerations are no different than with other hardware in general, except you don't have to worry about any kind of potential hardware compatibility issues, which takes away the biggest risk there. As always, pay attention to the release notes posted on the blog. Generally fine to upgrade to latest at this point with the exception of those on 2.2.x or earlier reliant on a package that's been deprecated in 2.3.x+. The upgrade process is the same.

Turning on legacy mode en the setup goes one step further I choose single user, kernel loads And oh, boot is going one step further : Enter full path name of shell or RETURN for /bin/sh: So I press enter : system hangs.  I type /bin/sh: <enter>Then an error : init: can't exec /bin/sh: for single user : no such file or directory. So I rebooted for the (forgot how many times but this time I did choose Multiple users and what a surprise, setup continues to the "graphical" setup. So case solved. Still weird that single user setup fails.</enter>

Ok so that has killed that process. The load is still high so it must be something else. last pid: 40086;  load averages:  0.50,  0.56,  0.51 What else can i try to track down the problem service. Thanks. Edit: This is what i am seeing now. ps auwwx | grep pkg root  48874  9.0  0.5  45172 10264  -  S    1:11PM    0:00.96 /usr/sbin/pkg search –raw-format json-compact pfSense-pkg- root  48739  0.0  0.4  45172  7796  -  S    1:11PM    0:00.00 /usr/sbin/pkg search --raw-format json-compact pfSense-pkg- Seems to come and go, so still not sure if thats the real service/process taking up the cpu time.

@churchi: Hi all, Ok so i have worked out what the issue was. Since my pfsense is in VMWare running as a VM on esxi, when i installed the last patch the system must have been rebooted which is normal. I had then rebooted the system a number of times to try and fix the issue but never powered down the VM. So tonight i powered down the VM and fired it back up and the interface stats are back on the dashboard. Weird one, but thought i would post so everyone knew the fix. Case solved. Cheers. A saint among men. Thanks for posting the solution. No DenverCoder9 here.

You do understand the iso is gzipped right, did you uncompress it to get your actual iso, and did you validate your checksum was valid?

When restoring a configuration and the interfaces don't match up. It prompts for a interface mismatch. This screen says select "Apply Changes" after fixing the mismatch. There is no apply changes button. The "Apply Changes" button got lost in among changes to the way info/warning boxes are displayed in 2.3 I raised Redmine issue https://redmine.pfsense.org/issues/6460 And Pull Request https://github.com/pfsense/pfsense/pull/2996

You can do it with nano, otherwise just backup the 2.2.6 config and upgrade. If it goes south for some reason, re-install 2.2.6 and restore the config.

Just thought i'd update Ended up having to use hyperterminal to access the box, couldn't for the life of me get Putty to work. It is now up and running the latest PfSense! Now i just need to figure out how to lower the fan speeds….those dang things are LOUD!

@phil.davis: I have nothing to do with setting the policy or roadmap, I am just reporting what is happening in the GitHub repo(s). I am absolutely aware of that. Thanks!

I know this is an old thread now but I only just rebooted my box the other day after upgrading the hardware - the restore was fine but the reboot broke the VIPs again and the same errors resulted in the logs. I made the suggestions and bound the VIPs to the localhost and everything came back up okay! :) Thank you for all your help, had I have not heard that from you guys I'd have had to result to command line to fix. Cheers, Tim

push.

If you try to install on your Win10 PC the installation process will wipe out Win10….. You can install in a VM environment, if you are not confortable with VLANs, you should have 2 nics for an easy installation. This forum and youtube is full of instructions.

the right solution is here: https://forum.pfsense.org/index.php?topic=109952.msg613371#msg613371

The console has option #13 which allows an update via the console. No idea on the adapters though.