PfSense 2.3.3-RELEASE-p1 will not Autoboot

madmatuk

Hi guys,

I have numerous pfsense installs at different locations, but one of these installs refuses to automatically boot into pfsense and awaits a keypress ( either enter or 1 )

The hardware and install media is the same for all other installations, so i am not sure what could be wrong.

While the system is running fine when booted, i really do need it to autoboot into pfsense in case of a power cut or similar.

Contents of loader.conf
autoboot_delay="3"
comconsole_speed="115200"
hw.usb.no_pf="1"

Contents of loader.conf.local
kern.cam.boot_delay=10000

Any idea how i can fix this without reinstalling?

Regards
Mat

madmatuk

No one? :(

pwood999

probably a bios setting on that one machine. Could it be doing a "halt on xxx" and waiting for a key press?

madmatuk

Hi,

No its beyond the bios, it is within pFsense itself after the boot selection screen.

I did check bios, it is identical to my other machines of exactly the same spec.

It is quite frustrating, think i might need to reinstall :(

Regards
Mat.

pwood999

Are you using remote serial console ? If so, maybe it's waiting for something on the serial port ?

My remote pfsense is headless VGA console, where I just access using GUI & SSH.

Nischi

@madmatuk said in PfSense 2.3.3-RELEASE-p1 will not Autoboot:

Hi,

No its beyond the bios, it is within pFsense itself after the boot selection screen.

I did check bios, it is identical to my other machines of exactly the same spec.

It is quite frustrating, think i might need to reinstall :(

Regards
Mat.

Okay

So I'm probably commiting a sin now by waking up this old thread, but it's the only one on topic that I can find.

I have the same issue, and it starts already from trying to boot first time with a known working USB to install. The boot loader just sits there waiting for user input rather than automatically counting down.

Did you ever find a solution for this?

Regards,
Christoffer

johnpoz

If they did it would be irreverent to your issue since 2.3 is no longer supported.. So your having said issue on 2.4.x? 2.4.4p1? Please create your own thread and document your exact issue your seeing.

Locking thread.