21.7 Boot hang at “Configuring VLAN interfaces...” with imported 21.1 config

[ajeffco]

Thanks much Franco, the effort is much appreciated!

I'm going to leave the primary VIPs in maintenance mode and let the updated secondary server stay online as the active firewall until the fix is officially released.  Once that happens I'll use the as yet untouched primary firewall to test the upgrade from 21.1.9 -> 21.7fixed.

Have a great day!
Al

[franco]

For reference the change was: https://github.com/opnsense/src/commit/79ea2ec061b


Cheers,
Franco

[skazi]

I've just tested the 21.7.r_6 version of kernel on a previously upgraded (in-place) custom build with J3160-ITX + I350-T4 and it booted correctly.
Thanks a lot!

[dinguz]

I was having the AHCI timeouts/errors, and with the new test kernel they seem to be gone. Uptime is now over an hour or so. Sensei running fine with native netmap driver.
Thanks to all involved in getting this fixed!

[blblblb]

Is it now safe to update? Do I need to do anything specific to get the right kernel? ex. either before or after the GUI update process.

[mb]

Hi @blblblb, things are going in the right direction; however, I'd advise waiting for a while and tune in for more updates from the OPNsense team.

[blblblb]

Hi @blblblb, things are going in the right direction; however, I'd advise waiting for a while and tune in for more updates from the OPNsense team.

Thank you! So, better to hold on to 21.1.8? I have the system in question operating through a lagg with vlans and 2 out of 3 interfaces there are ix based/igb, and they are the fallback ones in case the main 10g link falls apart. It's a critical point of that network and I don't mind dealing with manual kernel installs but I definitely need to confirm what works. I'm atm quite far from a system lookalike that uses the same HW so I can't just test and try my luck ;P

[mb]

21.1.8 should be all ok; and expect updates from @franco or @adschellevis

[guyp2k]

Is the following OK to upgrade?

[dinguz]

I’m not sure, unless they’ve replaced the package in the stock 21.7 repository, this would get you back the default 21.7 kernel with the bug still in it.

[franco]

Wait till Monday. We did replace the previous "21.7" kernel but depending on your mirror it may not be there yet.

In any case new images with 21.7.1 will be out soon to avoid this problem.


Cheers,
Franco

[ajeffco]

Wait till Monday. We did replace the previous "21.7" kernel but depending on your mirror it may not be there yet.

In any case new images with 21.7.1 will be out soon to avoid this problem.


Cheers,
Franco

Hello Franco,

I've never paid much attention to the updrade screen until now.  I'm assuming when the System -> Firmware -> Updates: New Version = 21.7.1 (currently shows 21.7), it will then be safe to update?

Thank you,

Al

[franco]

Hi Al,

We did replace the 21.7 kernel and it should be safe to upgrade (although I can't guarantee that a third party mirror will not catch the old bad kernel). The default mirror will definitely have the corrected version.

The 21.7.1 kernel should follow next week and will likely be the same kernel as the replacement currently for 21.7 (which is also the same as 21.7.r_6). And then it will be super-safe to upgrade.


Cheers,
Franco

[N0_Klu3]

@franco can you link to the correct mirror with the replaced 21.7 with the fixes?

[franco]

It's the "(default)" mirror setting.


Cheers,
Franco