2.6 install: didn't reboot when asked, and std instructions fail :(

MrPete

I. No reboot

Below is a screen capture from the tail end of BOTH of my installs (carp primary/secondary). In both cases, when it was time to reboot, pfSense got close-but-not-quite to shutting down.

After waiting some time, I intervened with an external forced shutdown. On boot, all was well.

pfsense 2.6 upgrade first reboot fails to shut down.jpg

(I also note that the time is incorrect during install... probably a minor nit.)

II. Standard Instructions Fail

Feels like a catch-22, when reinstalling on HA/CARP:

Do backups (of course)
First reinstall on secondary machine
Let it reconfigure and reinstall packages...

...but that's a FAIL.

The secondary machine doesn't have Internet access. It can't reinstall anything. I had to put primary in maintenance mode so secondary could get a route to the Internet.

(I did a LOT of searching and see no solution for this. How does one set a default route on secondary, when CARP keeps its interface locked down?)

UPDATE on #2 -- I solved my secondary-connect issue at least temporarily. This seems soooo obvious in retrospect. Seems it could be made a "standard thing" and auto-enabled. More discussion in separate CARP thread.

Gertjan

@mrpete said in 2.6 install: didn't reboot when asked, and std instructions fail :(:

pfSense got close-but-not-quite to shutting down.

Like : Halting and Powering Off the Firewall :

After the operating system halts, the device power will also be turned off if that feature is supported by the hardware.

At the end of the 'halt' sequence, "a bit in some a register" is set, and this will instruct the power supply to go down. The system stops.
This isn't possible if you use a an external power brick : in that case, after you see "All buffers are synced" the file system is save, and that's all that matters !!

See also pfSense "Halt System" results in Reboot"

MrPete

@gertjan Sorry, that was a typo. It's about reboot, not shutdown.

AFAIK, at the end of install, when it asks about "reboot", that's what it intends to do.

The reboot does not complete. Instead it gets as far as I showed, and stops. I had to manually finish.

UPDATE: I have found it never reboots. Separate topic...