Great 2.4.5 p1 update, "Kernel not found". Its been 13 month since I was able to update.
So is this some war on Hyper-v users? 2.4.5 was useless, 1 cpu core to run everything. I did spend a lot of time after the upgrade trying to figure out what was going on... Now i hoped 2.4.5p1 would solve everything and I would finally be able to update.
SURPRISE!!! Rebooted and "Kernel not found" message in console and my pfsenses are dead. Well, as a suspicious and resourceful IT manager I had backups so disaster averted but I´d like to know what the hell is going on? I havent been able to update my Pfsenses to a new version since may 2019!!! Is this a thing towards Hyper-v users, do you want to sell more of your own hardware or are you just not testing your stuff before release?
And before you go mad at my somewhat critical writing please know Ive been a IT-pro for 30 years, used Pfsense for many years and loved it. But now I need to seriously question wether I want to continue down this path of no updates. My config is complicated, many packages and high security so I am reluctant to make any new installs. Just to complicated since the backup system misses to much and I have to fix it manually. A new product would be a pain to get up and running but if I dont see any future in this i may have to. So before I go choose another product I´d like some feedback from the devs how you are going to handle this since I bet I´m not alone???
provels last edited by provels
@154218K2 FWIW, the system in my sig works fine on 2012R2. What server ver? Tried Gen 1? Yes, I did have the 2.4.5 CPU problem, but I had checkpointed before update so rollback was no issue. I'd probably create a fresh 2.4.5-p1 Gen 1 machine and restore your backed up config, and give it the same MACs as your previous machine so limited downtime if you have to turn one off and the other on. HTH
This post is deleted!