24.03 no auto boot
-
Hmm. Just to confirm do you always have a console connected? It could be sending some rogue character perhaps?
-
What Blinkboot/BIOS version is shown? You should see:
CORDOBA-03.00.00.03t -
@mrsunfire said in 24.03 no auto boot:
Yep the 3 second countdown doesn't show up. It stops here and waits for serial input.
Just a thought :
The 3 seconds count down (== autoboot_delay="3" setting) will be interrupted if there was a 'character' detected on the main console serial port.
It could be as simple as a serial 'COMM port' interface that was reset but bits were still received while the electrical connection stabilizes. So a fragment of a false character was received, the boot process detected that one, and is now waiting for more instructions.
And/or the cable is badly electrically isolated - ground plain mass issues, and a phantom char is received during power on.Maybe not simple to do, but : what happens when you cut the (pfSense) RX pin ? (the wire in the cable actually). Leave the TX wire and mass connected so you can follow the process.
Now your 6100 won't (should not) receive anything.Maybe (now I'm really dreaming) the boot script can be modified so you 'remove' first all chars present in the 'input buffer', and then enter the boot delay mode. This will take care of stray characters on the console port. Thus auto boot will work.
Btw : I've a 4100 MAX, and the console is always connected to a device (server with a serial port) and this server is always 'on', my 4100 boots fine. Even when I remote login into the server, and launch Putty on the the comm 'COM1' port to follow the boot process.
Silly reflection is incoming : stop rebooting your 6100 and all will be fine. Reboots are needed for upgrades, and these don't happen very often, ones or twice per year
(sorry again) -
@stephenw10 That must be the case! I did unplug the console cable (Cisco USB cable) and it booted up fine!
If I plug it back in and reboot, the same issue reappears. The most left blue LED is static on. I'm using putty 0.81 serial connection with that Cisco USB cable.
-
@mrsunfire said in 24.03 no auto boot:
That must be the case!
What was the case ?
If you have one : get another cable ?! Maybe this one is 'inventing' traffic by itself, and this makes pfSense stops auto booting, and waiting for further input from you.
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
@Gertjan I don't know. I edit my earlier post.
-
Ah, interesting!
So that was a Cisco USB to RJ45 cable? Using the RJ45 socket at the 6100?
-
@stephenw10 Exactly.
-
@Gertjan said in 24.03 no auto boot:
Maybe this one is 'inventing' traffic by itself, and this makes pfSense stops auto booting, and waiting for further input from you.
I've seen this before with a sketchy cable
-
@cmcdonald So I will try a new cable, thanks.
-
Go a new cable and it works now! Thanks.
