Regression #14305
closed
Boot loader is not updated during upgrade from pfSense CE 2.6 to 2.7
Added by Steve Gladden over 1 year ago.
Updated over 1 year ago.
Release Notes:
Force Exclusion
Description
Trying to upgrade to 2.7dev from 2.6 results in a failed boot.
Appears to be kernel or driver related as hitting 6 and choosing the boot the old kernel from 2.6 works.
I discovered this more recently as the upgrades used to work fine back in January.
This no longer works with newer more recent DEV snapshots.
I'm sorry I don't know exactly when it stopped working, first noticed three weeks ago.
Tried on different hardware including Hyper-V VM and same problem.
Easy to recreate:
Install 2.6.0 fresh on any system,
Go to system\update
Switch branch to DEVEL version
Update to Latest Base System
update will work but fails to boot.
Boot screen is peppered with "funny" characters mixed with text.
Hangs forever at line that begins with the word masks. (see photos)
capslock not responsive
ctrl-alt-del no response.
Files
Reproduced on Windows 11 Hyper-V after upgrading a fresh Gen2 ZFS install of 2.6.
- Tracker changed from Bug to Regression
- Target version set to 2.7.0
This appears to be a UEFI issue. Everything legacy I have tested upgraded OK but UEFI systems hang at the frame buffer.
Further testing:
- Issue occurs when updating from CE 2.6 to 2.7 (tested
2.7.0.a.20230424.0600) using Gen2/UEFI.
- No issue occurs when updating a Gen2/UEFI install of
2.7.0.a.20230215.0600 to 2.7.0.a.20230424.0600.
- Subject changed from Upgrade from 2.6.0 to 2.7DEVEL no longer works to Boot loader is not updated during upgrade from pfSense CE 2.6 to 2.7
- Affected Architecture deleted (
amd64)
To work around the issue:
- After the first reboot when it fails to boot, use option 6 to boot with
kernel.old
- Let it finish the upgrade - it will reboot once more; use option 6 again
- Once booted, go into the shell and mount the efi partition:
mount_msdosfs /dev/da0p1 /mnt (find the right partition with gpart list | egrep 'Name:|label:'
- Replace the old loader:
mv /boot/loader_lua.efi /mnt/efi/boot/BOOTx64.efi
- Status changed from Confirmed to Resolved
- Release Notes changed from Default to Force Exclusion
Retesting this from 2.6 to 2.7.0.a.20230510.0600, the issue no longer occurs.
Also available in: Atom
PDF
Updated by 
Updated by 
