SG-1100 Cannot update past 2.4.5-RELEASE-p1

mrnrsc

I have a netgate SG-1100.

It is currently stuck on 2.4.5-RELEASE-p1, and there are no available updates.

I cannot choose the next branch, other than 2.4.x. in System -> Update -> System update.

I ran the following command in the shell which I heard may sheld light on whatever is happening. See below:

[2.4.5-RELEASE][admin@router.office.rschicago.org]/root: pkg-static -d update
DBG(1)[28263]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[28263]> PkgRepo: verifying update for pfSense-core
DBG(1)[28263]> PkgRepo: need forced update of pfSense-core
DBG(1)[28263]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[28263]> Request to fetch pkg+https://repo.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.conf
DBG(1)[28263]> opening libfetch fetcher
DBG(1)[28263]> Fetch > libfetch: connecting
DBG(1)[28263]> Fetch: fetching from: https://repo00.atx.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.conf wi                                                         th opts "i"
7604124:error:14099044:SSL routines:ssl3_send_client_verify:internal error:/usr/local/poudriere/jails/pfSense_factory-v2                                                         _4_5_aarch64/usr/src/crypto/openssl/ssl/s3_clnt.c:3266:
DBG(1)[28263]> Fetch: fetching from: https://repo00.atx.netgate.com/pkg/pfSense_factory-v2_4_5_aarch64-core/meta.conf wi                                                         th opts "i"
Segmentation fault (core dumped)

Any ideas on how I can fix this so I can update to the latest branch? My goal is to migrate to pfsense Plus.

SteveITS

@mrnrsc https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#segmentation-fault-in-pkg

rcoleman-netgate

@mrnrsc Alternatively open a ticket for the download image of the 22.05-RELEASE firmware at https://go.netgate.com/

You will need to back up your config before installing from the image as the installation process is destructive.

mrnrsc

@steveits

Thank you both for your insight.

I will attempt the power-off method first, but I won't be able to do that unless I'm on-site this upcoming weekend.

I will report back with updates if it doesn't work out.