Note: Updated the topic to include the fact that the issue was occurring during stage 2 of the upgrade.

Hmm, interesting if it's really disabled in the BIOS pfSense shouldn't see it at all. Something not working right there.

You can also just install 2.7.2 and upgrade to 2.8 if your WAN doesn't allow using the current net installer. The upcoming net installer does allow a lot more options there.

That message implies the device is not eligible for Plus. Send me your NDI in chat and I'll check it.

...well, after some false starts (like loading 2.7.2 and running into different interface names on the new hardware (i,e. igc0 vs igb0, etc..) which did not allow th eloading of my VLANS etc... I ended up editing the backup config file, replacing "igb" for "igc", and loading 2.8.0... all is working great now on the new hardware.... I will wait until I can upgrade from 2.8.0 to Plus... reason to go to Plus is to contribute $ to the project, as I have been using pfSense for free for years now... am recently retired and delving into IT and learning as I go... Thanks for all the replies and suggestions !

Ok send me your NDI in chat and I'll check it.

@lansmurf said in Upgrade from 2.7.2 to 2.80 failed, unable to boot:

You are right it is an image file of the installer...

Ah, OK, thanks!

We were able to finally figure out all of the URLs that the pfSense box was sending requests too and we now have a working squid proxy.

Thank you.

@fireodo said in php error with suricata after updating to 2.8:

@bmeeks said in php error with suricata after updating to 2.8:

Part of the install/update process for the package rebuilds the enabled rules.

Maybe to much rules too?

A possibility for sure, but the rules rebuild was apparently working under the previous pfSense version if I am understanding the OP correctly.

He also has pfBlockerNG installed and it will use a lot of PHP memory for some tasks.

@NetworkNerd In the Netgate Installer you configure WAN so it provides its own Internet connection.

In the GUI you can set how many log lines to display. Or in shell look in /var/log.

@patient0 : Thanks !!

Well we should have new installer version available quite soon so you could try that on it.

You should really use: `setenv bootcmd 'setLED; run mmcboot;'

Otherwise you won't see the expected LED sequence at boot.Though it would still boot fine.

@dws I don't have a direct answer but if you spend much time on fixing it, it's probably easier to just format+reinstall and restore from backup (which can be done during the install).