PFSense CW 2.6.0 upgrade to 2.7.0dev no longer works.
-
It creates a non-bootable system.
This worked fine back in January as I was upgrading some 2.6.0 systems to 2.7 via the web interface.
This is no longer working more recently.
I first tried it several weeks ago on a Hyper-V VM.
And yesterday I tried on three different pieces of hardware and had the same problem.
The problem is very easy to reproduce.
On any 2.6.0 (system including a fresh install with default settings)
Head over to the update page and switch to the system\update page.
Change the branch to "Latest development snapshots (Experimental 2.7.x DEVEL)
Current Base System is 2.6.0
Today's Latest Base System is: 2.7.0.a.20230420.0600
Click confirm to update.
It will update and reboot.
You will have a system that is not bootable.
With funny (not normal) looking characters mix into the text on the initial boot screen.
This is 100% reproducible for me and has been this way for about 3 weeks now.You can hit 6 and boot the old kernel (works).
I'm not sure what the drawback is if you use the old kernel since the new one is not working
for some reason.I also don't know how to auto boot the other kernel.
I have the same issue no matter what hardware or VM I install 2.6 on.
Did not have the issue in January.If I do a clean install of the 2.7 installer (from February).
And then update to the lates snapshot from here, it works.
So I seem to have a workaround to get out of this problem.
Hyper-V VM stops at point shown in screenshot for a few seconds and reboots 3 times
then shuts off.
Hardware (non-VM) stop at (other 3rd photo)
Line that start out with "masks" and hangs forever. ctrl-alt-del does not respond
Screenshots from Hyper-V
-
Upgrade from 2.7.0.a.20230127.0600
-to-
2.7.0.a.20230420.0600 Worked!But an upgrade from 2.6.0
-to-
2.7.0.a.20230420.0600
Does not work.Screenshots from Hyper-V working vs. not working boot screens.
-
Easy to reproduce on 5 different systems.
I don't see any other posts about it.
I went ahead and filed an issue in redmine on this.
link text https://redmine.pfsense.org/issues/14305 -
Did you test only on UEFI systems?
It appears to apply there only from my testing.
-
@stephenw10 Great question. I'll have to double check.. I thought I tried it on one MBR system but was mostly on UEFI.
Want me to give it a go?
Only takes a few minutes in Hyper-V
Or would you like me to try bare metal first?
If we gather any info here I can update the issue/notes -
I'll also bet that's why it worked fine for me months back..
They were likely older bios/MBR installs.
I mean to try this but somehow pretty sure I missed it somehow.
Good catch.
I joke a lot about UEFI being more trouble than it's worth.
:)
It is taking a long time for the world to fully catch up with it. -
Yup, I've certainly hit a lot more problems than solutions with UEFI!
Yeah if you can confirm it that would be good. It seems very likely though just from where it stops booting. Last time there was a UEFI issue it stopped in the same place.
Steve
-
@stephenw10 You tested on a VM so I will test on hardware next.
-
@n8lbv I tested on Hardware.
a simple Dell i5 desktop with Intel Nic.
Forced all bios settings to "bios" and not UEFI.
Did a MBR install.
Worked fine and did not have the problem.However my single nic VLAN arrangement with a managed switch..
Where I tag one vlan and use it as the WAN and leave LAN on the default VLAN (no vlan) which works Flawlessly in 2.6.0 does not work at all after upgraded to latest 2.7.0 snapshot :(
Tried every form of reconfiguring from scratch/factory default after it was upgraded to 2.7
It's not happy.
A bit complicated
grumbleI'll try some other hardware as well.
sidenote that all of my openvpn site to site stuff is working flawlessly on any version of 2.7 I have tried..
But does not work well in 2.6.0 LOL. -
Hmm, so it boots fine but the VLAN doesn't work?
What NIC type is that? How does it fail? The WAN just has no connectivity?
-
@stephenw10 I don;t have much detail yet.
But started a new post where I'll update that as I learn more:link text https://forum.netgate.com/topic/179686/any-changes-to-intel-nic-vlan-support-in-2-7-to-be-aware-of
