Odd problem booting pause on new 2.4.5-0 install.
I installed pfsense 2.4.5 on a Atom E3845 1.9Ghz with Modern GPT partition table 8GB ram 64 GB HD. Followed all the defaults on install.
It finishes and reboots but doesn't actually boot unless you press enter staying forever it seems on the welcome menu.
Ammended so here in begins the mini-rant
I'm sure we all make mistakes but the simple thing a router that can't boot headless with all install defaults makes me wonder do they actual do any real testing before release I guess nothing much I wonder what other bugs await makes me think I should go back a release to one that has been fully tested by the community and had a number of patches. Is there a release cycle like the Linux kernel where even numbers are stable and odd numbers are unstable or something?
To the netgate guys a test plan should consist of the basic install path at least. Plus all the first course branches msdos partitions etc. Plus automated tests for all the bugs you have had with virtual machines that should be straightforward. With Docker containers it should be easy enough to roll the different test cases and run through them.
I beginning to understand the reluctance to try out some of the forum messages indicating a hesitance to jump into new releases.
I thought I tracked it down adding an autoboot_delay="-1" to the loader.conf.local having seen that file included and apparently it doesn't get over written which I just looked is true. Of course there on this in the trouble shooting and no description at all of how the boot process works loader.conf
It seems to only work once though. This has stalled me from moving the device to where it should be and annoying I moved the device to where it should be only to discover it wasn't working because it was stuck on the boot menu again arrrgghhh.
Anyway if any one has any tips. Perhaps we the community need to do a post release errata fixes sheet.
@daboone72 I updated my test system from 2.4.5 (which has been running well on my main system and my test system since it was released) to 2.4.5_1 today it worked fine, just like it almost always does. Problems happen, but claiming that the testing is terrible and wondering "do they do any real testing" is uncalled for. There is a release cycle and development snapshots are available for anyone to test. A lot of people at netgate and in the community put a lot of effort into developing and testing pfSense. You should think a bit before dissing so many people.
Anyway if any one has any tips.
Yes, open a support ticket with them. My experience has been great and they have been responsive.
Not sure specifically what is causing your device to have the outcome you are seeing, but posting "terrible testing.. what else developers missed.." is premature in my opinion.
I would suggest give them a chance to help. If you or pfSense resolves the issue, be sure to post what was done as it it may help others in the community.
Is your problematic instance running on supported hardware? If not, one should expect no guarantee of functionality from the software.
As a previous poster said, just file a bug report! Support has been OK for me so far.
We test installations on a wide variety of hardware before every release. Sounds more like your hardware/BIOS/UEFI is complaining about something than it being a pfSense issue.
@bimmerdriver Yes your right I was just in a frustrated bad mood. I'd spent Friday/Saturday installing Gentoo on an old box went for a walk on sunshine while it did some of the more meaty emerge's.
The pfsense router gear arrived on Monday afternoon. I then spent the next two installing that and trying to get it to boot so I could move it in place. It somehow felt harder than the Gentoo install which too my mind was saying something.
And for router gear not to auto boot I could understand a normal Linux distribution not auto booting it's GUI focused but a router that's the sort of thing you normally update remotely for security concerns patching openSSL or whatever and todo that and not have it come up again without someone with remote console access logging in to press enter. Anyway I'll stop now.
I saw release +1 and there are alot of good changes in the list there so I see fixes come thick and fast which is a good thing. For 2.5 when does arrive I'll buy another small SD drive and install it first in a VM and then on the machine in question.
@e-1-1 Ok not fully supported hardware but a Pico PC aka link below. I was having a bit of late night rant out of frustration having spent two days previously installing Gentoo that was comparatively plain sailing. You can understand a router that doesn't boot right is a bit of a blocker to get cracking on setting up the rest of the stuff.
@jimp Thanks for the reply sorry I was really have a late night rant after a frustrating couple of days should have wrapped in rant tags. I lost count of the number of reboots I did to try and solve it. Thought I had it moved the router and then discovered it still wasn't working. It's very strange to be pausing on a boot menu. hardware is this not wide left field I believe it's quite similar to the kit you ship yourselves and is built to run pfSense 2.5 with the AES-NI when it comes.
I'll have a look for unsupported clock but I'd be very surprised sleep 3 seconds shouldn't need a great clock you can do that on a Pi without one.
I'll install it in a Virtual Box VM see if I get the same behavior perhaps this weekend when I've made more progress configuring it, and also add some debugging. Whatever the delay seconds and auto boot routine is it isn't working for me in the loader scripts. My hunch is as it's loading stuff and FreeBSD scripts it's probably more FreeBSD than pfSense will see.
It's definitely not acknowledging the autoboot_delay="3" it just sits there with the single vertical bar. I guess normally it's supposed to spin as it waits?
NB I Changed the kern.cam.boot to match just experimenting.
kern.cam.boot_delay=3000 kern.ipc.nmbclusters="1000000" kern.ipc.nmbjumbop="524288" kern.ipc.nmbjumbo9="524288" autoboot_delay="3" hw.usb.no_pf="1" net.pf.request_maxcount="400000"
The fix that worked for me add this line to loader.conf.local I did add to try-include /boot/loader.rc.local the rc file but then corrected it. This boot stuff is a mine field for a FreeBSD new player.
From the defaults file.
autoboot_delay="10" # Delay in seconds before autobooting, # -1 for no user interrupts, NO to disable
Though of course that's set to read only. I removed keyboard in case it was a sticky key user interrupt as per comment above you know press any key to pause boot etc it wasn't though. Visual it was an HDMI screen maybe that's not a combo you try very often.
Final positive though cuedoes for nice forum editing software a pleasure to use. I'll brave the patch release when I've sorted some backups out.
@daboone72 Can you post the prompt you are seeing, or a screen cap? Normally pfSense/FreeBSD pauses like you've indicated from the settings, to allow for recovery options, and then goes on.
Can you change the headline to something more positive?? :)
Raffi_ last edited by
To be clear, the pause at startup you're describing is not normal behavior the whole pfsense community is experiencing. You keep mentioning that a router shouldn't be doing that... correct. pfsense doesn't either, your specific setup does. Never had to make any modifications to any files to fix a problem that never existed in my case. I can see how it would be frustrating for a first time experience, but normally when I run into problems with something I have zero experience with, my normal reaction is to assume it's something I did wrong, or my setup. When I get frustrated, I walk away from it for a while, usually get back on it the next day and things progress better. I don't jump straight to blaming the entire pfsense team. The pfsense community is one of the best. People are always helpful and the software is incredibly good. Give it some time and patients. You will be rewarded.
Buying AliExpress grade gear but blaming pfSense devs? Is this thread serious?
Did you read about the other guy buying "100% genuine Intel" but getting Realtek? https://www.amazon.co.uk/product-reviews/B071GD2KNH/ref=cm_cr_arp_d_viewpnt_rgt?ie=UTF8&filterByStar=critical&reviewerType=all_reviews&pageNumber=1#reviews-filter-bar
I can't follow.
My Netgate Hardware working so nice, if a new version is out, i hit the trigger and i got it.
You have to by serious hardware, if you want to run a firewall.
Especially the NICs are important, if you got crap there, its run like that.
But dont blame the Dev Team, if you buy unsupported hardware, aks there for help!
@Rico Well I didn't buy from there because of that found another guy on ebay but the kit picture is more accurate. It's Pico sense I did get a Console port rather than a VGA port. Yes mine has all Intel Nics 8GB Ram 64GB for £249.00
If this is the reaction though every time there is a issue with the boot process or anything ( FYI this is before the kernel even loads drivers or any hardware) , it must be your hardware then I will have to consider whether to commit to Pfsense more seriously.
@daboone72 I think you've missed the point here. Had you posted a simple, I'm having an issue and don't understand why, you'd have had great responses from people trying to help. However, you chose to attack pfsense as an inferiorly tested and QA'ed product. That's why you have received less than a warm welcome. Your post subject says it all. I find it ironic that someone who bought outside hardware and has paid nothing to use pfsense is now threatening to walk away after people give him a smack for a making a very inflamtory and, based on the experience of many others including myself, factually incorrect claim that pfsense sucks. Not sure you'll find anyone holding you back should you decide to go elsewhere.
Raffi_ last edited by
@daboone72 I know you didn't mean to come off the way you did, but all these responses are a testament to the pfsense team and community. When you attack the pfsense team the whole community takes it personally. We all love the community, team, and software enough to respond the way we do. Don't take it personally. If you spend enough time here, you might understand where we're coming from.
@Cool_Corona Thanks good thought have figured out howto and done that.
@teamits When I have some time I'll do a revert of my change and do some exploratory debugging. There are options you can add to rc.conf to turn on boot debugging.
I am thinking more positively now if Netgate guys haven't seen it. I guess it just doesn't happen with a fresh install on Virtual Box is that the tool? Or is there a docker container for Pfsense?
Amost certainly doesn't happen with an upgrade. Even bizaare looking at the base FreeBSD code for pfsense I may be looking in the wrong place though. It is the menu with the MultiUser option 1. With pfSense in ASCII text.
Actually found a screen shot. https://docs.netgate.com/pfsense/en/latest/solutions/apu/reinstall-pfsense-ce.html It's this menu just appears on the normal boot and waits with a vertical bar at the bottom.
I can't see anything that's changed in the boot style directory. Which is just down right strange.
FWIW I've installed the CE version several times on PC hardware and on a couple VMs in Virtuozzo but not had the issue you describe. It should pause there for a few seconds and continue on.
@teamits Hi well your last comment is encouraging. Some more experimenting tonight.
I tracked down some old images from some kind person who kept an archive:
2.3.5 works as it should see screen shot. It pauses for 3 seconds shows a countdown timer and then boots.
2.4.4-patch3 also does the pause behaviour same as 2.4.5
2.4.5-patch 1 Finally I installed the latest and still same behaviour.
NB: Can't seem to upload images here I guess there's a file size limit of somekind.
The fix add auto_bootdelay=-1 to the loader.conf.local works though that is not of course a patch worthy fix it's a bypass really.
Interesting thing about 2.3.5 is it does have a load.conf.local file though the property in it is the same as the one in the defaults for 2.5.0 series kern.cam.boot_delay=10000.
Still at least tonight I doubt it's my hardware. 2.3.5 boots just fine.
Actually I would say the 2.3.5 installer was a better surprise too. Full screen on my 42 inch 4k TV and more detail as in seeing the commands running as it installed. I liked that plus the default screen at the start I thought was nice you only have to change something if you need too.
Though the keyboard selection was a drag no page down and somewhat of a guessing job to find the right one.
Anyway just the latest. A diff between the 2.3.5 boot scripts and the 2.4.0 boot scripts should find the problem I suspect.
Getting there slowly
Logs from my upload attempts both dieing at the last.
.![1_1591910911009_Working2.3.5_BootMenuSml.png](Uploading 98%) ![0_1591910911005_MyPauseScreenSml.png](Uploading 98%)
@daboone72 Keep in mind the FreeBSD version can change between pfSense versions also. Perhaps try searching for your hardware and boot hangs with FreeBSD 11.2 or 11.3?
@teamits I did that already for two days. That's why I posted first email. Googling for boot hangs was getting me nowhere. I'll figure out howto put debugging statements in and figure out why it stops. Now I know it's the menu.4th menu.rc script that does all the menu including the timeout. It's just a bunch of loader script commands. https://www.freebsd.org/cgi/man.cgi?loader(8)