Upgrade from 2.7.0 to 2.7.2 fails to boot - kernel hangs
-
Recently updated from 2.6.0 to 2.7.0 with no issues.
Updated to 2.7.2 and the kernel hangs after "masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000"
Selecting the previous kernel via option 6 (kernel.old) and it boots fine (it didn't work properly but it booted).
I've seen others have had issues where setting Verbose:ON would cause it to boot, I've tried that, it doesn't work for me.
Physical hardware. EFISYS is not too small, plenty of space on /, no errors seen in the upgrade. It just didn't boot.
I've rolled back now but anyone know what is going on and how it can be avoided?
-
Looks like it's trying to boot the serial console. Try forcing a different console:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/boot-issues.html#booting-with-an-alternate-consoleSteve
-
Primary console is set to serial as it normally runs headless. I stuck a monitor on just to see what it was doing.
Surely however even if the console is wrong it shouldn't fail to boot. It does fail, its not just displaying on serial and I can't see it.
-
Ah, OK does it show anything on the serial console?
-
@stephenw10 I'll be 100% honest, I didn't even check it.
Actually, I wonder if it's there isn't a physical serial (I have a USB adaptor on it) and it's related to this issue https://docs.netgate.com/pfsense/en/latest/releases/2-7-2.html#efi-issue-on-proxmox-ve
I can try forcing it to video on my next attempt but I need to have more time available when I attempt it!
-
Yup, exactly. That doesn't happen in VMs that have a com port.
-
@stephenw10 I mean arguably the upgrader should check first and fail rather than leaving it in a broken state... but lets not go there!
Is there anything on 2.7.0 I can manual check first?
I'll download 2.7.0, 2.7.1 and 2.7.2 images beforehand this time (I had to revert back to 2.6.0 and then upgrade again to 2.7.0 as I was lulled into a false sense of complacency from the 2.6.0->2.7.0 upgrade and didn't bother with downloading 2.7.0).
-
Unclear if there's anything that can be tested. AFAIK there is no significant difference between the console drivers in 2.7.0 and 2.7.2.
What hardware are you actually using there?
-
Basically one of these: https://www.aliexpress.com/item/1005004844606515.html
Although that was the one I bought mine is with an N5000, 4GB RAM and 128GB SSD. -
Hmm, well I'm not aware of any specific issue with that CPU platform. Could be something BIOS specific.
I would try a clean 2.7.2 install and see if it fails the same way.
