More information would be helpful here.

First, what version of pfSense are you currently running?

Second, what package (or packages) are you looking to have updates for?

Packages for the current pfSense versions are updated, but not every package is updated at the same frequency. But if you are running an outdated pfSense version, (meaning not the current RELEASE or DEVEL branch), then package versions will indeed be "frozen" as package versions are tied to specific pfSense builds. The packages associated with older pfSense versions are not updated.

@jimp I did the following and still without luck to get the v5.0 running.

removal of all ntop packages deletion of all ntop folders reinstall ntopng package

However, I can tell the interface is looking like v5.0. v4.0 wouldn't be giving me some screens that I'm familiar with. At least my company is running both v4.2 and v5.1 so I could identify the difference.

I hope I have a chance to get it up in a VM. Or perhaps if I can pay to get it fixed because I run out of time for work.

@paco-0 I assume the filesystem check does nothing, how about pkg update && pkg upgrade from the shell?

@stephenw10 It was apparently a problem with the motherboard and or cpu. Switched to a different system( AMD a10 apu vs. original FX6300 ) and was able to compete boot DVD. Now thinking of using it as a 10Gb router/switch instead of firewall if possible.

@dominikhoffmann

Thanks, I had to change to UEFI (standard DUAL) in the bios of my Microserver.

@hoserman Are you looking at the FreeBSD version? 2.4.5 was FreeBSD 11.3 I think.

Overall there is an upgrade guide which has some version specific notes.

@gertjan
Thank you so much that did the trick

You can always reinstall clean if you think you may have some file system issue. Open a ticket with us to get the recovery image: https://go.netgate.com/

Steve

@needhelp404 said in 2.4.4 to 2.5.2 Issues:

pfSense will hang while booting up

Where exactly does it appear to hang?

There are a number of points that the boot can actually hang or appear to hang that indicate different issues.
If restoring the config appears to break it it's probably a bad console setting that makes it appear to hang.

Steve

I always recommend using Etcher to write the image to USB. It can write the compressed image directly so that eliminates any decompression issues. It runs in pretty much any OS.

Once you have the image on a USB drive though just boot that on the target device and follow the instructions on the console.
https://docs.netgate.com/pfsense/en/latest/install/install-pfsense.html

Steve

@lralvarez

https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html

But most likely you can just click upgrade..

But never hurts to make sure you have install media, get that from netgate - they will email you link to 21.05.1. Make sure you know and can console into the device. And have a backup of your config.

@chidinmairene
space key to select your 4 disks to run Raid10
else choose a different raid if you don't have 4 disks

Looks like it :

cf48c3bb-8803-4de2-83c8-294a4a986c71-image.png

@johnpoz said in Upgrade OpenSSH 8.7:

the version of ssh that comes with pfsense will be the one that is included with freebsd. When freebsd updates their version, then pfsense will update. Yeah its a bit dated.. Complain to freebsd about that ;)

thanks much ;)

@steveits

Thanks. I already tried all of those options. I have requested the link as you mentioned.

Rich

@fireblade OK

After a reinstall of pkg the signiture issue with pkg-static appears to be working

pkg install -fy pkg

The easy solution:
Create a pfSense VM with virtualbox
Load packages and settings from your bare metal device
Verify the config works as bare metal.
Shut the VM down

Restore:
Use vboxmanage to convert vdi to vhd
Use rufus to load the vhd on the ram device (taken out of the bare device mounted via usb)
Place storage back, done. (and tested)

I'm gonna test the reverse (take bare metal in to a VM) but have no doubts this will work.

nb. cloning the storage device as backup also works.

Try to reimage the appliance with 21.05.1
ask support@netgate.com