No boot after upgrade to 2.4.4
-
I tried both of the solutions suggested in the upgrade guide. I'm using a Minisys 4-lan box with an Atom E3845 (with 4*Intel WG82583 lan).
Firstly, the i915 graphics lines allowed the boot to proceed past the initial "Booting /" point. However, it then stopped and froze when trying to bring up the 4th LAN interface (em3), just as described in this post; this error appeared in the bootup log:
em3: 0x20000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). em3: Unable to allocate bus resource: memory em3: Allocation of PCI resources failed device_attach: em3 attach returned 6Next I removed the i915 lines and instead tried the "kern.vty=sc" fix and this allowed my system to fully boot.
So I'm wondering if the graphics change caused the failure to initialise the LAN adatper? -
It is possible. There was an issue on other hardware in the past that required disabling AGP video in order to use some add-on cards that required a lot of bus resources.
-
@gertjan can You able to help me.
After Upgrade its showing that no root found and Also I can able to find the Package Manager -
@gertjan pfSense-pkg-pfBlockerNG installation failed!
-
WARNING: Current pkg repository has a new OS major version.
pfSense should be upgraded before doing any other
operation
Failed -
Your waking up a thread that's done for more then 2 years.
Hardware evolved - software evolved.
Like posting Windows 10 bugs on a Windows XP forum : doesn't make sense.@franco22 said in No boot after upgrade to 2.4.4:
pfSense-pkg-pfBlockerNG installation failed!
A question for the forum Home pfSense Packages pfBlockerNG - but please don't say 'failed' as that tells us nothing.
The log that shows up during installation should show details.Btw : If you could install something, the system booted ?!
-
@gertjan yes
-
@gertjan Updating pfSense repository cata
-
@franco22 said in No boot after upgrade to 2.4.4:
cata
You are really using 2.4.4 : that's old. Why keeping an old version running ??
I presume you want to upgrade to 2.4.5-p1.
There is always the Plan B which is actually as good as Plan A :
Save (download) your config.
Download an ISO and burn it to a USB drive.
Boot from the USB drive, and install a proper, recent pfSense version.
My personal touch : do not import your config back in yet.
Do these steps first :
Login to the GUI.
Make WAN work - and stop doing any other config.
Install all the packages you use(d). Without setting them up. Just download them.
Do a reboot.
When it's up, notice that LAN works fine, every device has Internet access.
Only now, import your backed up config.
Do another reboot.
After this second reboot, check every pfSense package, see that its functioning, etc. -
@gertjan Thank You So Much...
-
@Gertjan hello can You help with this issue Shared object "libelf.so.2" not found, required by "pkg"
-
@franco22 said in No boot after upgrade to 2.4.4:
Shared object "libelf.so.2" not found, required by "pkg"
pkg is what you could consider as a core program.
So the correct lib file "libelf.so.2" is present by default.
If its not, consider the system broken.
It situation is very repairable :
Install the same pfSense version on a second system.
Now copy over all the files that are mentioned missing.
Reboot. Done.
Easy.If you prefer the no brain solution : re install pfSense - always take this version.
Btw : system libs can get overwritten. It can happen when the admin breaks the golden rule :
He/She installs a (recent) packages AND their pfSense version is not the latest.
( like installing Windows 10 programs on Windows 7 OS ..... )
Before installing a package, check first if you're up to date. -
You probably tried to install a package in 2.4.4 while the pkg repo was pointed at 2.4.5 so it has pulled in a bunch of incompatible libs.
Backup your config.
Install 2.4.5p1 clean.
Restore your config.Steve
-
@gertjan https://forum.netgate.com/topic/160418/site-to-site-vpn-configuration-between-pfsense-and-cisco-asa-5505
I can able to ping asa to pfsense but I can't able to ping pfsense to asa help pls
