Pfsense wont come back up after restart

[atafm2]

I restarted pfsense using the restart/ reboot option under diagnostics tab.
But now it wont come back up and is stuck here:
login-to-view

It stayed stuck here overnight and pressing buttons on the keyboard does nothing.
How do I fix this?
I have successfully rebooted the machine before, this is the first time i have had this issue. restarting again it gets stuck in the same spot.
Running on a Dell R730xd on bare metal
Thanks!

[atafm2]

@atafm2
it is not frozen, i can still page up and down
here are some more pictures of what it says
any of these give a clue?

login-to-view
login-to-view
login-to-view
login-to-view

[NollipfSense]

@atafm2 It looks as if you're having hardware issues...possibly a NIC is not good.

[stephenw10]

You are looking at the wrong console.

What you see there are only the messages sent to all consoles. You can see it's configured as dual console with serial as primary.
If you don't have access to the serial console you can force an alternative console at boot:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/boot-issues.html#booting-with-an-alternate-console

Steve

[Gertjan]

@atafm2

login-to-view

It can't get any better.
POST failed ... throw that in Google.

To make a long story short : you've a device to be recycled.
Or : get a POST error message card, so you'll know what type of error the PC has. As it could be a simple 'battery of clock == dead'.
Or worse.

Even it the device was booting, I would put it on the 'to be scrapped' list.

[stephenw10]

That's output from the oce(4) NIC/driver though. The card may have failed and if that was assigned it will be waiting at the interface assign prompt on the serial console.

[atafm2]

@Gertjan
oce0 is a 10gbe nic. and that nic does work. (or at least was working prior to restart)

server is fine. it is a Dell r730xd. Lifecycle controller health test shows everything is healthy and the firmware and bios are all up to date. No issues with the hardware as far as I can tell. iDrac is fine too, also reports no errors in the log

[atafm2]

@stephenw10
thanks for the reply
I will have to try that

my only question is with this:

" *Once at the loader prompt, type the following to boot with the serial console active:

set console=comconsole
boot -v* "

I have not been able to type in this console yet. the only keys on the keyboard that do anything are just page up and down. I am assuming though that getting " to a loader prompt" will allow me to type though

will update,
thanks

[Gertjan]

@atafm2 said in Pfsense wont come back up after restart:

oce0 is a 10gbe nic. and that nic does work. (or at least was working prior to restart)
server is fine. it is a Dell r730xd. Lifecycle controller health test shows everything is healthy and the firmware and bios are all up to date. No issues with the hardware as far as I can tell. iDrac is fine too, also reports no errors in the log

Can be so.
But The NIC bios is POSting ....
It is paid to do that if something (and only the NIC Bios can know what this 'something' is).

iDrac : nice, it does a lot, I know, as I'm looking at mine more then often, as I wait for my 650 Watt/hour PowerEdge T310 (13 years now) to die. I let it in place as it was a very $$$ device, and I want to make every minute out of it. It never let me down - fingers crossed.

[stephenw10]

You want to boot with the video console so at the loader prompt enter:

set console=vidconsole
boot

Steve

[atafm2]

@stephenw10
so i was able to type help, and then the first command.
but after i typed this, it got hung up and wouldnt let me type the boot -v
login-to-view

also, when i restarted, i got this message
login-to-view

something is not happy

[stephenw10]

Hmm, that second screenshot looks like a UEFI driver issue, nothing to do with pfSense.

Why did you set the console to comconsole? That's the serial console and you're not connected to that.

As I said above use:

set console=vidconsole
boot

Steve

[atafm2]

@stephenw10
that fixed it!!!
thank you!!!!

[atafm2]

now the new issue is that one of my nic's is not showing up.
the 10gbe one (oce0 and oce1)
it has the blinking lights on the back, but it does not show up as an option under interfaces -> assignments

did the network card really just spontaneously fail? or do you think it could just be a driver problem?
this is the nic that had the POST failed error in the attached screen shots up above
it was working fine before i rebooted and somehow got stuck on the wrong video

[stephenw10]

The two symptoms you see there, that error message from the OCE driver and the BIOS error message, look like a problem with the card. Though I have not seen that error before so I can only speculate. Can you test the NIC in something else? Or try booting a different OS on that hardware?

[stephenw10]

This thread looks relevant:
https://community.hpe.com/t5/proliant-servers-ml-dl-sl/hp-10g-554flr-freebsd-driver/td-p/7166313/page/3

Try booting with the 10G NICs disconnected.

[atafm2]

@stephenw10
yep that was it!
Thanks again for the help :D

That 10gbe nic i am temporarily running at 1gbe using SFP+ to RJ45 adapters.
I just had to unplug both adapters, reboot the system, and once up, i plugged back in and it works

[stephenw10]

Ah, nice! That looks like an issue with the NIC firmware then. Odd that you didn't see it before.