Remote 2.0.3 Upgrade to 2.1 Failure?
-
See below.
-
A reboot didn't fix this error by the way.
I had a perfectly functional 2.0.3 firewall that was in standby mode to another 2.0.3 (primary) firewall.
Everything has been hunky-dory for the past 5 years.
Today I decided to try a remote upgrade of our standby firewall and it failed at the point I included in my image.
-
What sort of hardware is it running on? Are you running any packages? Anything unusual about the setup?
Do you have a keyboard attached? http://forum.pfsense.org/index.php/topic,67141.0.html
Are you running igb NICs? http://forum.pfsense.org/index.php/topic,65361.0.html
Steve
-
What sort of hardware is it running on? Are you running any packages? Anything unusual about the setup?
Do you have a keyboard attached? http://forum.pfsense.org/index.php/topic,67141.0.html
Are you running igb NICs? http://forum.pfsense.org/index.php/topic,65361.0.html
Steve
x86 (same as my home firewall), tons of packages, and they are in a pfSync cluster.
Yes, they are running Intel NICs.
I'm heading to the DC this weekend to see what's up.
-
Are you running igb NICs? http://forum.pfsense.org/index.php/topic,65361.0.html
Yes, they are running Intel NICs.
So try the suggested disabling MSI-X for that driver. Try adding:
hw.igb.enable_msix="0"to /boot/loader.conf.local.
Steve
-
Are you running igb NICs? http://forum.pfsense.org/index.php/topic,65361.0.html
Yes, they are running Intel NICs.
So try the suggested disabling MSI-X for that driver. Try adding:
hw.igb.enable_msix="0"to /boot/loader.conf.local.
Steve
How do I do that if it fails during boot? Am I going to have to boot off the pfSense CD and use (R)escue mode? I tried a fresh reload of 2.1 and although it loaded fine, it failed with the same error upon first boot. I reloaded 2.0.3 and it's up and running again.
It looks like this was fixed in a later FreeBSD kernel.
-
Re-reading this I would first try to change the HD controller mode. 2.1 included better support for various SATA controllers and some which previously worked fine in 'IDE' or legacy mode now must use SATA or AHCI mode.
Steve
-
Re-reading this I would first try to change the HD controller mode. 2.1 included better support for various SATA controllers and some which previously worked fine in 'IDE' or legacy mode now must use SATA or AHCI mode.
Steve
I believe I had to use IDE mode for 2.x to originally install. I will try this the next time I am at the datacenter.
If I set hw.igb.enable_msix="0" in the loader.conf, will that persist across an upgrade?
-
If I set hw.igb.enable_msix="0" in the loader.conf, will that persist across an upgrade?
No but if you add it to loader.conf.local it will.
Steve
-
If I set hw.igb.enable_msix="0" in the loader.conf, will that persist across an upgrade?
No but if you add it to loader.conf.local it will.
Steve
I have an identical server here at home minus one thing, a 2-port PCI-Express Intel NIC. I performed an upgrade on it and it went flawlessly. I think the Intel NIC in our co-lo firewalls are to blame.
To test, I changed the server here at home from AHCI to IDE mode and it failed at the mountroot> prompt much later in the boot process, not as in my screenshot above, immediately after initializing the processors.
I'm going to give the hw.igb.enable_msix="0" option a shot when I return to the datacenter in a few weeks. I'll report back.
