Great to hear. Thank you for the feedback.

And the power bill for such a server is not exactly negligible

@jimp said in Pfsense installer can't find hard drive or raid virtual disk: When you had it running on FreeBSD, which disk controller driver was it using? I don't check it further, but I know It's missing some driver that I don't know. I just know my device name not the controller. I'm on the way to my Datacenter and find some clue to answer

Sounds like the internal drive might have failed. Are you able to get an image and install again?

@jimp said in Upgrade problem 2.4.3-RELEASE-p1 to 2.4.4_p1 - Lost VGA Console: https://www.netgate.com/docs/pfsense/install/upgrade-guide.html#upgrading-from-versions-older-than-pfsense-2-4-4 Read the part about console problems near the end of that section, you might need to add kern.vty=sc into your /boot/loader.conf.local and then reboot. Thanks @jimp... That got it! I read that, but a J1900 is a Celeron not an Atom, so I didn't think this applied. So for anyone else in the same boat, this issue applies to J1900 (and maybe other Celerons as well.)

@grimson Thank you! Case closed . So it seems like it was a bug in pre 2.4.4 versions, that my previous configuration was working well, not a feature.

Thanks ! Seems to have done the trick quite nicely. All that is left are a few 10's of mtree deltas on lockdown flags on things like passwd: flags ("schg" is not "schg,uarch"). Thanks a lot !

Thanks for your big help

Ooo I might be good, the support got back to me pretty quick....

@asamat said in Upgrade - How to roll back: Hello, make a backup (Diagnostics/Backup&Restore/Download configuration as XML) download 2.4.4_p1 image and make bootable USB stick. With 2.4.4_p1 release, FAT32 partition will be created on USB stick, so you can put your XML configuration file into this partition. upgrade and check if it works if it isn't, reinstall from USB stick Thanks @asamat - Hopefully I won't need to roll back, but at least I know one way to do it. The system came back up. Only thing is the console froze with: Booting | The little spinner didn't spin and I got no boot messages. I did a second reboot and see if the issue would clear, but unfortunately it didn't. I'll post this as a separate thread.

Not a typo, it's just what it sees in its repo at the time, but once the upgrade starts it picks up the most recent version. It only needs to see something more recent than what it has to trigger the upgrade message/process.

It turns out I got into a similar situation. I've upgraded several routers, ours and clients, to 2.4.4 and 2.4.4_1 recently. Last night I tried updating a SG-3100 from 2.4.3_1 and the GUI kept showing a "failed" message during the update and/or downloading, but no actual errors were shown that I saw. I tried a couple of times, and eventually it finished, and restarted, but didn't come up. Today on site I could not ping the LAN IP showing in the console, and the console showed 2.4.4_1 installed but all sorts of PHP errors for missing libraries and so forth (I didn't document them). The short version is I ended up reinstalling from the SG-3100 "factory" image for 2.4.4_1 (https://www.netgate.com/docs/pfsense/book/install/download-installer-image.html) via USB stick and it seems fine now. A while back I seem to recall someone posting that the update could "fail" but still be processing in the background and the router restart eventually and upgrade fine...I'm wondering if something like that happened and I didn't wait for the reboot.

In a scenario tied to only console access I would not going to Update. Better skip that and update when you have more Options like the default WebGUI. 2.4.4 to 2.4.4-p1 should not be any problem but double bottom you know... ;-) If something goes terrible wrong you need local access anyway. I'd also keep some USB flash with preloaded 2.4.4-p1 handy... -Rico

Nice to hear everything worked for you, enjoy! -Rico

Jimp has applied a solution. See it here https://redmine.pfsense.org/projects/pfsense/repository/revisions/4c6e3de40f56a1bd8d978a9dd4677d0ab025b8cb

@veldthui pf will tag it in thr exact same way then. No reason not to work

Is this related to https://www.netgate.com/docs/pfsense/install/upgrade-guide.html#upgrading-from-versions-older-than-pfsense-2-4-4 : "Gateway handling changes in 2.4.4 may result in different default gateway behavior than previous releases. Nearly all cases should behave properly, but be aware that it may be necessary to re-select the default gateway after upgrade."

See here : https://forum.netgate.com/topic/138343/2-4-4-2-4-4-p1-unexpected-operator https://forum.netgate.com/topic/138330/pfsense-2-4-4-release-p1-is-now-available/12

After spending time on this that I'd rather have back, I found that the root cause could have been any one or all of the widgets on the dashboard. After removing all the widgets on the source host and then redeploying the "All" configuration on the new host, the issue went away. The crash seemed to be triggered by clicking any link on the UI while the dashboard was present.

Reinstalled 2.4.4_1 and after a 2-3 reboot, I had to restart Unbound and Dpinger to get some log in the Status / System Logs / System tab NTP was logging fine.