Upgraded to 2.4.4_3 - system now unstable
-
I would see if a different OS has the same issue on a liveboot, for that matter try live booting the pfSense installer, if it still hangs you have a hard ware issue.
-
@dmurphynj said in Upgraded to 2.4.4_3 - system now unstable:
Edit to add: Upgraded to 2.4.4_3 a few days ago, and everything seemed OK initially.
Upgraded from what?
-
Thanks guys. I think the C2000 bug has gotten to us... now it won't power back up at all. I ran a memtest86+ and it passed. Powered down, and now won't power back on at all.
Previously was on 2.4.4_2 - so not much of a change there.
Looks like cooked hardware - just opened a case with Supermicro. But it was bizarre that the problem only appeared under load at first - booting single-user mode or even multi-user mode without network cables attached, the system stabilized. Once I put a load on it, that's when it hung. Now we're just dead as a doornail.
Dang Atoms.... should've chosen a different CPU.
-
Everything works until it breaks, and coincidence is the mortal enemy of troubleshooting.
-
@KOM FOR SURE ...
I didn't think it was really the upgrade, but wanted to see if anyone else has run into a hard fault scenario like this.
If it were really pfSense, I'd expect at least a kernel panic. Just was curious if anyone could see a scenario where the software would hard-stop the CPU without a panic. I haven't seen that kind of hard fault in years ...
Love ya, Intel. Really.
-
unstable is a small word. i had a completely unusable box. Hoperfully my installation was a virtualized one and did restore the whole image. I dont know what happened but if somebody needs the image with the issues i will provide so sombody with deep knowledge of pfsense can understand why it just broke
-
@albgen said in Upgraded to 2.4.4_3 - system now unstable:
unstable is a small word. i had a completely unusable box. Hoperfully my installation was a virtualized one and did restore the whole image. I dont know what happened but if somebody needs the image with the issues i will provide so sombody with deep knowledge of pfsense can understand why it just broke
Spouting things in a thread that resolved around a hardware issue and has nothing to do with yours is bad manners. I understand frustration after an update gone wrong. I don't understand spreading FUD without necessary debugging myself. Standing around and shouting "I won't upgrade anymore, do it yourself if you want" is nothing that helps either you or anyone else.
-
@JeGr
ok your thought.let me write again what i did wrote on the other discussion:
This instance of pfSense is installed on january 2018. After that i did the regular updates from the UI. Thats it. Arrived today and i had a dead box. What happened? well i don't know, it seem this version(2.4.4_3) is braking something.
Never happened since using monowall and pfsense. First time!
Let me point out also that i'm the only one that can manage this box so the chance somebody has done something on the box else is zero! The web interface and the ssh is not even exposed on the wan interface. -
You're hijacking another thread for your topic, that has clearly nothing to do with it. Just stop that, please.
-
@albgen said in Upgraded to 2.4.4_3 - system now unstable:
Arrived today and i had a dead box.
'Dead box' is not a helpful term for debugging. Was it powered off with no LEDs? Was it totally unresponsive via console? Was it showing any errors? Did you reboot it? etc etc
What happened? well i don't know, it seem this version(2.4.4_3) is braking something.
And what have you seen that makes you believe this? I've been here for many years, and if I had a dollar for every user who complained about pfSense - only for the real fault to be bad hardware - then I could retire already.
Never happened since using monowall and pfsense. First time!
Like I said earlier, everything works until it breaks.
As JeGr said, if you have a problem then post a new thread.
