Update or Fresh install of 25.07 causes HP ProLiant DL20 Gen9 to Reboot after PFSense Menu
-
@WB3FFV said in Update or Fresh install of 25.07 causes HP ProLiant DL20 Gen9 to Reboot after PFSense Menu:
@stephenw10 The million dollar question is, should load modern servers in BIOS or UEFI mode? I assumed now days UEFI was an improvement and the preferred method, but maybe not..
There is no million dollar answer.
Recently I run into issues due to a bug in freebsd that would only affect NON uefi installs. Using uefi, all worked fine. It was fixed later on.
Now it seems you are facing the opposite.Apart from that, uefi is probably the only way to go, longterm.
-
@malindsay I decided to try and update my own firewall to the 25.07.1 release, it's on an HPE DL360-G9. Well that was a big fail, as with others when I updated it would no longer boot, I even tried to select the prior kernel, but no go.
I think tried like @stephenw10 suggested and set it to Legacy BIOS mode, but I guess my initial install was old enough it would not boot, had to be UEFI.
Then I took and slicked the machine as I had backed it up, reloaded from the netgate installer, and loaded up 25.07.1 again, and yet again after the load and reboot it would not boot, just resets, like it did in the update before the reload. Now at this point I set the server back to Legacy BIOS mode and rebooted. This time it apparently did have the BIOS tracks from the fresh reload, so it booted PFsense and finished loading and I could restore my backup.
So at this time I had to load it fresh, and it's now running under 25.07.1 in BIOS mode, but I am online. Of course getting it back in UEFI mode seems the correct thing to do when a fix is available..
-
Hi, I haven't updated yet and I'm terrified.
In my motherboard's BIOS, I can't find any setting to set UEFI or Legacy.
Could it be UEFI only?My versione is PfSense Plus 24.11 with mainboard Asrock Industrial IMB-X1314MicroATX
Even using previous ZFS snapshots and boot environments, it wouldn't boot anymore?
Are there any issues restoring the license if I reinstall everything from scratch? I still have the lifetime Lab license. If I have to reinstall everything from scratch starting from the installer (so version 2.8.0), is it possible to restore the same Lab license to convert it to Plus?
-
@Unoptanio
https://forum.netgate.com/topic/198536/upgrading-from-25.07-to-25.07.1-causes-a-fatal-trap-12-on-boot.Press 3 on boot menu and type
staging_slop 268435456 boot -vAfter it boots, add
exec="staging_slop 268435456"Into loader.conf.local
It might also be the case that this problem doesn’t affect you at all and you won’t have any issues with booting.
-
-
@Unoptanio, no issues if the update fails and a fresh install is required. Prepare flash media in preparation and back up your system.
-
This post is deleted! -
@malindsay
On the same hardware, does restoring a version 24.11 backup over a new version 2.8.1 also restore and convert the license? -
@w0w said in Update or Fresh install of 25.07 causes HP ProLiant DL20 Gen9 to Reboot after PFSense Menu:
@Unoptanio
https://forum.netgate.com/topic/198536/upgrading-from-25.07-to-25.07.1-causes-a-fatal-trap-12-on-boot.Press 3 on boot menu and type
staging_slop 268435456 boot -vAfter it boots, add
exec="staging_slop 268435456"Into loader.conf.local
It might also be the case that this problem doesn’t affect you at all and you won’t have any issues with booting.
Should this change only be made after the update if the system crashes?
Or should it be made on version 24.11 before updating to 24.07.1? -
@WB3FFV, thanks for the information. I tried the same, but I didn't set it to legacy BIOS. I reinstalled 24.11 after failed attempts
-
Have you already checked to see if there is a newer BIOS firmware version to update for your hardware?
-
@Unoptanio said in Update or Fresh install of 25.07 causes HP ProLiant DL20 Gen9 to Reboot after PFSense Menu:
Should this change only be made after the update if the system crashes?
I don't think your BIOS is affected. This change can be made at any time, as long as there is enough RAM — and you have enough.
If I were you, I would try updating without any changes.
Of course, you should at least save your config just in case. -
@w0w said in Update or Fresh install of 25.07 causes HP ProLiant DL20 Gen9 to Reboot after PFSense Menu:
@Unoptanio said in Update or Fresh install of 25.07 causes HP ProLiant DL20 Gen9 to Reboot after PFSense Menu:
Should this change only be made after the update if the system crashes?
I don't think your BIOS is affected. This change can be made at any time, as long as there is enough RAM — and you have enough.
If I were you, I would try updating without any changes.
Of course, you should at least save your config just in case.With the amount of RAM I should be fine.
-
@stephenw10 I noticed that there is a brand new of the 2.8.1 release, does this have anything to do with the UEFI issue?
2.8.1.r.20250808.1925
Just wondered if I needed to update and try anything..
-Howard
-
Nope 2.8.1-rc doesn't have anything that might address this. Or at least not intentionally.
-
@stephenw10 Thanks, then I won't bother testing anything against it..
-
Well it would be good to know it's also affected for sure. But I'm pretty sure others have tested it.
-
This post is deleted! -
@w0w said in Update or Fresh install of 25.07 causes HP ProLiant DL20 Gen9 to Reboot after PFSense Menu:
@Unoptanio
https://forum.netgate.com/topic/198536/upgrading-from-25.07-to-25.07.1-causes-a-fatal-trap-12-on-boot.Press 3 on boot menu and type
staging_slop 268435456 boot -vAfter it boots, add
exec="staging_slop 268435456"Into loader.conf.local
It might also be the case that this problem doesn’t affect you at all and you won’t have any issues with booting.
WB3FFV
less than a minute ago@w0w So what does this change do, if I may ask? Also is there any harm if it's not needed?
I guess the million dollar question is, has anyone with an HPE server tried this yet?
-Howard
-
It moves the RAM space used for staging at boot. If the BIOS is using some space for something it hasn't told the kernel about via ACPI tables a conflict can prevent boot like this.
