clean install of 2.7.2 fails to boot
-
@stephenw10
That's it. The referenced issue had a usable work around. 2.7.1 and 2.7.2 'need' to have a serial port active to successfully boot UEFI (without some tweak at least).This is a hardware appliance. Since I was not using the serial console, I had the serial port disabled in the BIOS. Enabling that let the system boot.
-
Ah nice. Interesting. I'll pass that to our devs who are looking at it.
-
@stephenw10 said in clean install of 2.7.2 fails to boot:
Ah nice. Interesting. I'll pass that to our devs who are looking at it.
It turns out that is not quite enough. That got past the existing boot freeze, but I decided to start over with a clean bare metal install from the 2.7.2 iso. Even with the serial port enabled, I was getting the freeze on boot. Following the other instructions on the issue are getting past that, but it is needed on every boot. Good thing I do not expect to need a reboot very often once I get the configuration set up.
Catch the initial boot menu (7). Enable verbose (5), turn off verbose (5), exit to the main menu (1) normal multi user boot (1)
7 5 5 1 1
It seems to need something 'bumped' in the boot. Other variations have worked, but not always. It is not just a simple delay either. 7 «wait» 1 1 fails.
-
@mMerlin said in clean install of 2.7.2 fails to boot:
needed on every boot
There, I finally placed where I'd seen the "mask" message:
https://forum.netgate.com/topic/184214/not-booting-after-upgrade-or-clean-install-to-ce-2-7-1
"For some reason only booting with Verbose-ON works" -
I found a better fix for my specific environment.
I changed the BIOS settings on the XCY hardware box to turn off UEFI, then did another clean install of pfsense version 2.7.2 specifying MBR instead of GPT. With a full 'legacy' install, the boot process now runs to completion without any manual intervention.
I went that path because all of the information I saw here was referencing UEFI.
-
Yes it is entirely in the uefi console. If you're able to boot legacy instead that avoids it.
-
@stephenw10 I am having this issue as well with a bare metal install with 2.7.2-relesase. It started after upgrading from 2.6. In my bios I noticed I have options for: windows 7 UEFI, windows 8 UEFI, windows 7 legacy, windows 8 legacy. Any clue on which of the "legacy's" I should choose? Also, will I need to reinstall or would a simple bios change fix it?
-
You would probably need to re-install after changing the boot type so the correct loader gets added. I've no idea what the difference between Win7or8 would be. It probably makes no difference for pfSense(FreeBSD).
-
@stephenw10 i changed the bios to "legacy win 7" as opposed to uefi and rebooted. Pfsense booted as normal and hung at the same area that is related to this defect. I then booted a usb installer and reinstalled. One item I noticed was that the installer defaulted to gpt and I had to change it to mbr. You would think it would choose mbr for a non eufi bios. After the install, the work around appears to be working. Thanks for your help.
-
I had the same exact issue with my box. First couldn't update to 2.7.2 from 2.7.0 due to a bug with cert hashes. Had to run certctl rehash to update then after the update it wouldn't boot with no real error message. Luckily I stumbled on this thread. I was surprised to find that indeed using boot menu options 7 5 5 1 1 booted fine, but as they said above it's an every boot thing. My Lenovo M90q doesn't have a serial port so I attached a USB serial port which didn't do anything. In the end I updated my BIOS and it boots right up every time. Must be a UEFI bug that was patched.
