@stephenw10 Actually, I believe the update somehow only was partially applied.

TAC sent me a link to firmware I could install from the console / USB stick, and I did this, and all is well and good now. Thanks everyone!

You need to go through 2.7.0 because that was the first version to include the dynamic pkg repos.

@pool15 said in libcrypto.so.30 and libssl.so.30 missing after updating Snort to 4.1.6_13, Pfsense CE 2.7.0-Release:

OK missed the 2.7.1 update notice! Will unwind that symlink and run the update 🤞

Yep, always login to the Dashboard page first and let it check for any available pfSense updates BEFORE you do anything with a package. If there is a pfSense update available, install that before you touch any package update.

As you found, updating a package when there is a pfSense update out there also will bring down all new versions of shared libraries. Those new versions will almost certainly break things in the existing non-upgraded pfSense installation.

@SteveITS
The nice thing about using a L3 switch is DHCP is in the switch not Pfsense so I have no issues with DHCP.

@Ofloo said in pfSense 2.7.0 CE upgrade error, just tought i'd share:

pkg update
ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"

I will note that that in itself is not a problem. It's an expected error if you are running 2.7.0 after 2.7.1 was released. The pkg system pulls in the new pkg version which means you need to use pkg-static update at the CLI. The pkg system itself always uses the static linked versions so doesn't hit that.

Steve

Yes, it's almost always quickest to reinstall clean from a situation like that as long as you have a config backup to restore from.

Reading this phorum it seems, that the last upgrade provide more issues... not good, ff course, create ticket.

Use pkg remove.

I meant install an mSATA drive into the 4860 and switch to booting from that instead. But if you have a complete spare unit it's not really an issue.

@Gertjan Thats quite an approach... maybe it was too much out of the box for me 😳

@stephenw10,

Here is the original post where I installed and configured the boot options. I have never changed the BBS priorities since in the BIOS.

--> [https://forum.netgate.com/topic/141300/sg-5100-verify-that-m-2-ssd-is-recognized-after-physically-installing?_=1700249887071](link url)

Again my motto at this point is "if it ain't broke - don't fix it".

Phizix

Connect to the command line (console or ssh) and then run: pkg-static upgrade.

See what it offers you. But upgrading the rest of the packages manually should get you to 23.09.

Steve

Console access was required. cmd line upgrade via pkg upgrade allowed the device to upgrade. Was not able to detect why the prior UI upgrade did not succeed.
Thank you.
Regards,

Send me your NDI in chat and I'll check it.

You're seeing ssl library or pkg issues after a clean re-install?

It's because the install image is multiboot, it has an EFI partition and loader, but the APU is not UEFI so the installed image on the SSD does not. The upgrade script looks for an EFI partition to update the loader and the only one on the system is on the SD card. It wouldn't happen on a UEFI system.
But that seems like a bug. It shouldn't really do that.

Steve

https://redmine.pfsense.org/issues/14983

@stephenw10 I've sent you the NDI. Thanks!

@Mission-Ghost said in SG1100 Update USB Console Failed:

As an aside, I hope future Netgate products always include a hardware factory reset button in their design. The absence of such a button on the 1100 lacks customer focus and makes contending with failed upgrades and malfunctions such as this much more difficult than it has to be.

We don't always have complete and total control over every aspect of the hardware as we develop new platforms, but we do try to have a config reset button if at all possible since we know it makes things easier for users (and TAC). Plus we are always trying to make the process easier for users. Just wait until you see the reset process on the next device, it's the best one yet. :-)

Send me your NDI in chat and I'll check it.

@dfe_pfsense

Hello Everybody,

Finally I do an upgrade from CLI interface with pfSense-upgrade command.
I was obliged to do this command twice as following:

1 - As indicated from "Troubleshooting Upgrade":

pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade

2- With only the pfSense-upgrade cmd with Debug option:

pfSense-upgrade -d

All is fine for me
Best regards