@teamits
Oh, I am blind. I now see the other issue mentioned, apologies

@teamits

It has nothing to do with "boot".

It keeps booting up. I have a screen connected through serial port. Then I found that the operating system does not have enough memory, and can not perform the upgrade.

The IT support (support@netgate.com) was very competent, and helped me to reinstall. After 15min my Netgate device is working again.

Look there:
https://youtu.be/dbSUdDyfW0M

@sgw The other option is to use MD5 as the hash algorithm, though I would recommend against if possible to avoid. AESGCM is the ideal workaround here. Best of luck.

I'd start with Status/System Logs/System/General, Gateways, and Routing.

@teamits Yes, four-port network card. D'oh, pretty obvious ;) Thank you for clarifying, friend.

Does the wifi router itself pull an IP address from pfSense when it's connected to the SG-2100 LAN?

Steve

Everything that is done through the webgui is backed up.

Only things like custom loader files are not.

Steve

Yes, it's a known issue in 21.02/p1. https://redmine.pfsense.org/issues/11436

@ozlecz Looks like at one time is was: MTFDDAV256TBN

I couldn't guaranty we always used that drive though. I could probably see what was fitted to yours if you have an order number.

Steve

@jonathan66

Reboot using the console.
Chose option 5.
When asked, use option F = Reboot and run a filesystem check

After the reboot, the file system is checked and repaired.
Changes are these files :
/usr/local/lib/php/20190902/zlib.so
/usr/local/lib/php/20190902/xml.so

will not get repaired. Maybe even removed because invalid.
A re install is in the case the fastest way out.
Or, from the install file - extract these two files and copy them over.

What happens is that your config file can't be read, so pfSense defaults to default settings.
For WAN, this is DHCP on WAN - so it works out of the box.
For LAN it is 192.168.1.1/24 etc - but you probably changed that, so LAN does not seem to work now (tip : keep LAN to the default settings, so, in case of emergency, LAN works ^^)

Btw : tip : before you upgrade, reboot using the console and do a "sanity" file check. That way you are sure all is well. Check the GUI logs after the reboot. See for any suspect messages.

File system inconsistencies go undetected while booting from the GUI (except when the block the booting process).
They are normally introduced when there is a power failure (aka : no clean shu tdown) and very comparable what will happen with your PC when you ripe out the power.

Hi @gabacho4

Thank you for your reply.
I thought I did something not right in the setting or configuration.

Anyway, if it is due to the FreeBSD, there isn't much can be done.

Paying for 1G connection and not getting it, i am disappointed.

@stephenw10 I’d seen that one, along with another that causes a panic if there are multiple changes/saves in a short timeframe. Glad I’m not experiencing anything new. Here’s to hoping a fix comes very soon.

Yes, that is possible.

Good to hear. Odd it's required. I know some others are using pfatt in 2.5/21.02.

Steve

That is expected. the FreeBSD repo should be disabled so that pkgs are only pulled from out repo by default. Some are not the same and pulling them from FreeBSD directly can break things.

Steve

Just to confirm, that is the expected U-Boot version in the SG-1100.

You can see U-Boot report that in it's boot messages:

U-Boot 2017.03-armada-17.10.2-g6a6581a-dirty (Nov 01 2018 - 16:04:57 -0300) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU @ 1200 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR @ 750 [MHz] DRAM: 1 GiB U-Boot DT blob at : 000000003f716298 Comphy-0: USB3 5 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 6 Gbps

Steve

@welbo97 said in pkg-manager says netgate cert invalid:

Is there a way to get it working without pulling power and doing a cold reboot?

From what I've read on the forum., some chip has really to hardware reset.
This can only be done by removing the power for a while.