@sae did you see this? https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting

Ok, I don't expect 2.7.1 to be any different but the line numbers in the php error might have changed.

@mcpfl Move away from UFS. I did that as soon as ZFS came out as I was TIRED of having to fsck the "Firewall", every time the power went out. (and/or the UPS was weak, or the communication to the UPS usb had failed). Reinstall on different system/media and use ZFS instead.

It won't cause any issues uninstalling that. But I wouldn't expect either of those to be an issue during upgrade anyway. Steve

@stephenw10 said in Not booting after upgrade or clean install to CE 2.7.1: Does it support legacy (BIOS) install rather than UEFI? That would likely boot fine. Unfortunately there is no CSM options in the BIOS. Only UEFI is available. I would be thankful for an advice on how to troublshoot the UEFI boot. For some reason only booting with Verbose-ON works. I do not know what does it change, but it somehow works. I do not think it's a hardware incompatibility, because otherwise it would not boot at all. If there is no solution and nobody can check the bug in CE 2.7.1 installation it makes no sense to continue chatting. It does not even make sense to think abou upgrading to Plus version. Thanks for your efforts

Yes, I would also recommend backing up the config and reinstalling as ZFS. It's the simplest way to get to 23.09 that guarantees the system will be in a clean state. And you will then be on ZFS. It can probably be recovered but there would be at least some diagnostic commands needed to see exactly why it's failing. Steve

@stephenw10 thanks for your sharing, bro. this machine, i just had one version upgrade from 2.6 - 2.7 by uninstalling all packages so this time i will try without installing as yours the sokeada

@jimp said in Netgate 2100 - Update from 23.05.1 to 23.09: Firewall will not boot: Curious that you saw partial output -- that's usually what happens if two separate processes are attached to the serial port at the same time. They'll each see ~half the output and input won't work properly. Maybe you'd attached a screen to the terminal already and detached (not quit)? Hard to say. That sounds very plausible. I might have attached multiple processes like you say. Maybe the guide at https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/connect-to-console.html should warn against this? I feel like it's a pitfall for people like me that are not very familiar with the sceen command.

Of the log? The most useful way would be to add the log text directly by copy/pasting it from the serial console if you can. Adding a link to pastebin or similar would also work.

@CC88 Backup files can be restored to a later version. https://docs.netgate.com/pfsense/en/latest/backup/restore-different-version.html

@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