@ITH said in 6100 Fails to come back up after power outage without manual reboot:
It has power on when the power is restored but does not function until manually rebooted again. It is "on" but unresponsive.
pfSense, is like a PC or Mac.
Ripping out the power, not using the Windows => Start menu => and select "Power down", is 'prohibited' by Microsoft. As this might mess up the file system.
pfSense can behave the same. It's rare, because very resilent file system are used, but issues can happen if the SSD was just writing something somewhere ...
pfSense isn't a device you shut down when stopping visiting the Internet (something you would do with your PC : you'll put it in sleep mode at and now it won't use the drive anymore so its safe).
This is the reason why you would equip your NAS (always on - will contain all your valuable data) and your local network with an UPS.
An UPS isn't mandatory, of course, but in that case, do shut down your stuff before the power loss happens.
[ I know, this is impossible - that's why UPS's are made possible ^^]
You can however know what happened - as it can happen again. So lets go looking for the issue.
First, make a backup of your pfSense config.
That out of the way, hook yourself up to the most important interface of your 6100 : the console access.
Login to it.
Now, rip out the 6100 power.
Wait a while - like 60 seconds.
Put it back in.
Here comes my question, and your question : what did you see ? What does it say ? What happens ?
Btw : whatever you see, there are other scenarios to test.
The WAN NIC is connected to what ? Was the other end of the WAN cable also powered down ?
Who starts up faster, pfSense or the other device on the other side of the WAN ? Cable modem are notorious if you "boot stuff out of sequence".
Etc etc.