You can roll-back to an earlier BE snapshots if you re using ZFS. I have tested that between 23.01 and 22.05.

Steve

I guess I'll just wait for the next upgrade or just stay in the working version since the feature I need on the captive portal was fixed on 2.5.2 version. I guess no need to fix something that is working.

For those who are still watching...the HOW of the issue is unclear but regardless, i'm just resetting the box to move on with life...

thanks @stephenw10 for the help

thread closed

@vpnguy Look into ACB: https://www.netgate.com/blog/automatic-configuration-backup and https://docs.netgate.com/pfsense/en/latest/backup/autoconfigbackup.html for more information on the service. It will probably save your tuchus once or twice.

@gwabber

2ec7a9f9-075b-4c59-81fb-a534c8d8fc8e-image.png

If that file didn't exist, I would hit the big red button called "system not to be trusted" as these files :

0b570ff5-2b1c-44a6-8704-da3a35d36e2f-image.png

are created upon system (pfSense) install.

The real question is now : **what else has not been created and or not put in place ** ?

And yes, the sshd deamon will silently fail if the basic config isn't present.
I was about to propose : make the sshd system start way more verbose by editing /etc/ssh/sshd_config by adding a line with "Verbose" (something like that).

Anyway : Succes verder.

Thanks both for the answers :)

I think I'll stick with UFS on my VM. In probably 3-4 years of pfSense usage I haven't had a single corruption of my pfSense VM, but it's on a solid hypervisor and with a good UPS and software to safely shut down VMs in case of power drainage. I replicate the VM weekly so if it was to corrupt I can spin up the other VM on another ESXi host quick smart, and the restores from backups is fairly straightforward if I need to do that.

For my standalone hardware "table top" boxes and hardware rack mount bare mental installs I quickly learned that ZFS is the right way to go after various power "incidents" at remote site. No question about it - I will only use ZFS on my hardware installs.

BTW RAM is not an issue as my VMware Hosts have plenty of it - can throw 8GB or 16GB at the VM if I need to. I think Netgate should put in some clearer documentation around when to use ZFS and when not to for virtualised firewall environments.

@kaloe28 Roger. If you want to use ZFS, however, you will need to reimage the system.

@stephenw10 said in MBT-2220 Fresh Install (22.05/2.6CE) Hangs at Mountroot>:

I agree. I'll get something added in there. Thanks

I see it! Thanks! I'll probably forget all about this and have to read it again next time I have to install.

@shshs all packages store their config in config.xml
unless you tampered with it yourself

@gertjan said in SG-5100 ERROR AFTER DIDNOT FINISH UPDATE:

@roben1000

While your client can still access the command line, let him export the /conf/config.xml

Send him a new firmware, and as per Netgate mail instructions, he should use Etcher to prepare a USB drive, and have the firmware re installed from USB.
Afterwards : import the config.xml, and all will be fine.

Btw : upgrades can fail.
People often forget to take a backup of the config, don't restart pfSense just before upgrading, etc.
Because most firewalls are some what mission critical, a USB drive should be ready with the previous firmware before any 'click' on the upgrade button.
Taken all the precautions beforehand will eliminate all chances of things going wrong. I know, this isn't scientifically proven, but we'll all agree ;)

Btw : option 4 was executed.
This option resets the config, that's just one single file, shown above - with all the pfSense settings.
It will not repair any system core files.
PHP library errors etc mean that system files are damaged, missing, or are present but do not have the correct version.
A reinstall is the 'solve it in 5 minutes' solution.

edit :
If he didn't prepared a copy of the /conf/config.xml, let him take several recent files from here /conf/backup/

Thank you for this, ill note this sir
jpe he will not messup the pfsense now hahaha

Finally, I could figure it out.

The problem was the console cable, I guess a cable break.
I just tried another one and the installer is booting fine.

Thanks for your help

@stephenw10 I tried already before I replied on this post. No success.

@lmannyr RAID would be done in a BIOS configuration for a RAID controller, There is GEOM for UFS but you can do ZFS mirroring -- all of these things require reinstallation of pfSense. You will need to back up your config before proceeding.
ZFS install: https://docs.netgate.com/pfsense/en/latest/install/install-zfs.html

@adamjonfuller said in Is there an easy way to downgrade from 22.05 to 22.01?:

I can confirm that we are having the same issue. We don't use pfblockerng though. This seems to be something else related to 22.05.

This is what fixed it for me: https://docs.netgate.com/pfsense/en/latest/recipes/nat-voip-pbx.html

NAT_1.jpg

NAT_2.jpg

Does it not respond at all? Does the number lock LED on the keyboard still work?

Does it respond to ctl+t?

Does it install if you remove/disble the Broadcom NIC?

Steve

@jimp A support incident was opened with TAC after my original post. They provided a link and instructions to reinstall firmware on the 3100. It is working again. Thank you for your input.

@bitslammer said in Unable to check for updates/ No packages available:

pkg: invalid url: /pfSense_plus-v22_05_armv7-core

Yeah, that path doesn't look good : no host name what so ever, so very invalid.

Look here for a nice story and solution.