I can confirm that with 2.4.4._2, it's now showing swap space again for me, whereas it had disappeared prior. I have 32G of ram, and thought that maybe it didn't need it, and/or I was losing my mind as to why it wasn't there. I could of sworn it was there in 2.4.3. :)
The local IT has disconnected pfsense nics from vsphere
OK but then the symptom of slow web GUI and inability to access updates is to be expected. The slow GUI happens because DNS isn't working and each try must time out on all DNS servers before the GUI moves on.
I was assuming the NICs were being reconnected after the IP change.
Not sure where to go from here. The only issue I've had with changing IPs is the rebinding check not allowing the new LAN IP but I think that bug was fixed a while ago.
I was wondering if you could provide step by step how to add this as I am also at this stage and would like to be able to try this for myself. Many thanks. James
Be smart and you'll find solutions, RTFM: https://www.netgate.com/docs/pfsense/hardware/boot-troubleshooting.html#disabling-acpi and adapt it to your current needs.
I saw another post almost identical to this recently where the problem ended up being a bug in the terminal software (minicom, perhaps) where it failed to update/scroll when maximized. Restoring it to a smaller window allowed it to work.
Thanks @viragomann for the answer, When I ran the function it did fix something in the records in the fs but it did not fix the boot issue, after using Dr. Google and some keywords in the search I came across this.
TL;DR:
Same process as you but they used the following command
/sbin/fsck -y /
This seemed to have fixed the issue and got all of the machines online.
No errors in system log.
No relevant errors in resolver log (only a few failed to resolve host : new_name.internal , due to devices that are already configured on the firewall but not on the dns server. Those entries have no concern with the void tables.)
I apologize for the post earlier and believe I ended up finding the answer. I should have dug a little harder into the forum. The answer looks to be that it won't restore without modification to the XML and applicable interfaces at a minimum. Not sure about the other options in the config backup, but I'll play it safe and manually configure.