My WAN type is IPv4 DHCP. DNS config: [image: 1758148242529-dns.png] I have around 20 DNS IP's in General Setup. It's never been an issue before. Here is the output of pkg -d update: DBG(1)[4374]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[4374]> PkgRepo: verifying update for pfSense-core DBG(1)[4374]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense-core/db' DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[4374]> curl_open pkg: No SRV record found for the repo 'pfSense-core' DBG(1)[4374]> Fetch: fetcher used: pkg+https DBG(1)[4374]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf, left retry 3 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf, left retry 2 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf, left retry 1 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection pkg: An error occured while fetching package DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.txz pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.txz -- pkg+:// implies SRV mirror type repository pfSense-core has no meta file, using default settings DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.pkg pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.pkg -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.tzst pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.tzst -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/packagesite.pkg pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/packagesite.pkg -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/packagesite.tzst pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/packagesite.tzst -- pkg+:// implies SRV mirror type Unable to update repository pfSense-core Updating pfSense repository catalogue... DBG(1)[4374]> PkgRepo: verifying update for pfSense DBG(1)[4374]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense/db' DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[4374]> curl_open pkg: No SRV record found for the repo 'pfSense' DBG(1)[4374]> Fetch: fetcher used: pkg+https DBG(1)[4374]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf, left retry 3 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf, left retry 2 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection DBG(1)[4374]> CURL> No mirror set url to https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[4374]> CURL> attempting to fetch from https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf, left retry 1 * Couldn't find host pkg.pfsense.org in the .netrc file; using defaults * Could not resolve host: pkg.pfsense.org * Closing connection pkg: An error occured while fetching package DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.txz pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.txz -- pkg+:// implies SRV mirror type repository pfSense has no meta file, using default settings DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.pkg pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.pkg -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.tzst pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.tzst -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/packagesite.pkg pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/packagesite.pkg -- pkg+:// implies SRV mirror type DBG(1)[4374]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/packagesite.tzst pkg: packagesite URL error for pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/packagesite.tzst -- pkg+:// implies SRV mirror type Unable to update repository pfSense Error updating repositories! If I run pkg -d update 3-4 times, the output changes slightly: DBG(1)[8135]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[8135]> PkgRepo: verifying update for pfSense-core DBG(1)[8135]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense-core/db' DBG(1)[8135]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[8135]> curl_open DBG(1)[8135]> Fetch: fetcher used: pkg+https DBG(1)[8135]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/meta.conf DBG(1)[8135]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults * Host pkg01-atx.netgate.com:443 was resolved. * IPv6: 2610:160:11:18::209 * IPv4: 208.123.73.209 * Trying 208.123.73.209:443... * Connected to pkg01-atx.netgate.com (208.123.73.209) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Apr 10 00:00:00 2025 GMT * expire date: May 11 23:59:59 2026 GMT * subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * using HTTP/1.x > GET /pfSense_v2_8_1_amd64-core/meta.conf HTTP/1.1 Host: pkg01-atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Thu, 28 Aug 2025 16:50:33 GMT * Request completely sent off < HTTP/1.1 200 OK Fetching meta.conf: < Server: nginx < Date: Wed, 17 Sep 2025 22:26:01 GMT < Content-Type: application/octet-stream < Content-Length: 179 < Last-Modified: Thu, 28 Aug 2025 16:50:33 GMT < Connection: keep-alive < ETag: "68b088d9-b3" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection DBG(1)[8135]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.pkg DBG(1)[8135]> curl_open DBG(1)[8135]> Fetch: fetcher used: pkg+https DBG(1)[8135]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-core/data.pkg DBG(1)[8135]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults * Hostname pkg01-atx.netgate.com was found in DNS cache * Trying 208.123.73.209:443... * Connected to pkg01-atx.netgate.com (208.123.73.209) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Apr 10 00:00:00 2025 GMT * expire date: May 11 23:59:59 2026 GMT * subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * using HTTP/1.x > GET /pfSense_v2_8_1_amd64-core/data.pkg HTTP/1.1 Host: pkg01-atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Thu, 28 Aug 2025 16:50:33 GMT * Request completely sent off < HTTP/1.1 200 OK Fetching data.pkg: < Server: nginx < Date: Wed, 17 Sep 2025 22:26:01 GMT < Content-Type: application/octet-stream < Content-Length: 1632 < Last-Modified: Thu, 28 Aug 2025 16:50:33 GMT < Connection: keep-alive < ETag: "68b088d9-660" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection pfSense-core repository is up to date. Updating pfSense repository catalogue... DBG(1)[8135]> PkgRepo: verifying update for pfSense DBG(1)[8135]> Pkgrepo, begin update of '/var/db/pkg/repos/pfSense/db' DBG(1)[8135]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[8135]> curl_open DBG(1)[8135]> Fetch: fetcher used: pkg+https DBG(1)[8135]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf DBG(1)[8135]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults * Host pkg00-atx.netgate.com:443 was resolved. * IPv6: 2610:160:11:18::207 * IPv4: 208.123.73.207 * Trying 208.123.73.207:443... * Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Apr 10 00:00:00 2025 GMT * expire date: May 11 23:59:59 2026 GMT * subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * using HTTP/1.x > GET /pfSense_v2_8_1_amd64-pfSense_v2_8_1/meta.conf HTTP/1.1 Host: pkg00-atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Mon, 15 Sep 2025 15:21:37 GMT * Request completely sent off < HTTP/1.1 200 OK Fetching meta.conf: < Server: nginx < Date: Wed, 17 Sep 2025 22:26:02 GMT < Content-Type: application/octet-stream < Content-Length: 179 < Last-Modified: Mon, 15 Sep 2025 15:21:37 GMT < Connection: keep-alive < ETag: "68c82f01-b3" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection DBG(1)[8135]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.pkg DBG(1)[8135]> curl_open DBG(1)[8135]> Fetch: fetcher used: pkg+https DBG(1)[8135]> curl> fetching https://pkg.pfsense.org/pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.pkg DBG(1)[8135]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults * Hostname pkg00-atx.netgate.com was found in DNS cache * Trying 208.123.73.207:443... * Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / X25519 / RSASSA-PSS * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Apr 10 00:00:00 2025 GMT * expire date: May 11 23:59:59 2026 GMT * subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * using HTTP/1.x > GET /pfSense_v2_8_1_amd64-pfSense_v2_8_1/data.pkg HTTP/1.1 Host: pkg00-atx.netgate.com User-Agent: pkg/1.21.3 Accept: */* If-Modified-Since: Mon, 15 Sep 2025 15:21:37 GMT * Request completely sent off < HTTP/1.1 200 OK Fetching data.pkg: < Server: nginx < Date: Wed, 17 Sep 2025 22:26:02 GMT < Content-Type: application/octet-stream < Content-Length: 189698 < Last-Modified: Mon, 15 Sep 2025 15:21:37 GMT < Connection: keep-alive < ETag: "68c82f01-2e502" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection pfSense repository is up to date. All repositories are up to date.

Hmm, so looks like a lagg/lacp issue then. Unless the ix driver is somehow dropping the pdus...

@stephenw10 Still haven’t figured that one out. BUT looking at the /cf/conf/config.xml of the two installations, I noticed an interesting discrepancy: <pkg_repo_conf_path>/usr/local/etc/pfSense/pkg/repos/pfSense-repo-2_8_0.conf</pkg_repo_conf_path> <pkg_repo_conf_path>2_8_1-preview</pkg_repo_conf_path> Even though both systems refuse to see the 2.8.1 release, for former is stuck on 2.8.0 and the latter on 2.8.1.beta Listing the (presumably) correct folder on the former yields: root: ls /usr/local/etc/pfSense/pkg/repos/ pfSense-repo-2.7.2.abi pfSense-repo-23_09_1_upgrade-cert.pem pfSense-repo-23_09_1_upgrade.name pfSense-repo-2.7.2.altabi pfSense-repo-23_09_1_upgrade-key.pem pfSense-repo-2_8_0.abi pfSense-repo-2.7.2.conf pfSense-repo-23_09_1_upgrade.abi pfSense-repo-2_8_0.altabi pfSense-repo-2.7.2.default pfSense-repo-23_09_1_upgrade.altabi pfSense-repo-2_8_0.conf pfSense-repo-2.7.2.descr pfSense-repo-23_09_1_upgrade.conf pfSense-repo-2_8_0.descr pfSense-repo-2.7.2.name pfSense-repo-23_09_1_upgrade.descr pfSense-repo-2_8_0.name while on the latter: /root: ls /usr/local/etc/pfSense/pkg/repos/ pfSense-repo-0000.abi pfSense-repo-0000.conf pfSense-repo-0000.descr pfSense-repo-0000.version pfSense-repo-0000.altabi pfSense-repo-0000.default pfSense-repo-0000.name Which looks rather different. So I changed the line on the second one to a (somewhat) consistent <pkg_repo_conf_path>/usr/local/etc/pfSense/pkg/repos/pfSense-repo-0000.conf</pkg_repo_conf_path> Maybe I can fix this, when I know what this line really should be and what correctly should be in /usr/local/etc/pfSense/pkg/repos/ Well, I messed around with these files and settings, and now they are all consistent in the what I guess is the new format. Then going twice through the troubleshooting section of the manual here finally got both systems upgraded to 2.8.1. So far so good, but unfortunately, the trouble still isn’t over. Going to the System > Update section in the WebUI, I still get: pfSense-repoc: failed to fetch the repo data and trying to install some package, I still, after hitting the green "confirm" button, get: <package> installation failed! Another instance of pfSense-upgrade is running. Try again later So close, yet….

@procrastrjf I’m afraid installation on this device will be non-trivial. It’s not detected because the onboard network cards are a newer Realtek 2.5 GbE model that requires its own driver. As far as I remember, that driver needs to be installed manually, and every system update can lead to the same situation you have now, since the new Realtek drivers are not included in the pfSense distribution. The solution would be to connect a compatible USB network adapter, configure the network, and then install the Realtek driver. Or... Just use Proxmox and install pfsense virtualized.

Will add just in case this is helpful for anyone: Installed with full installer CE 2.7.2 Edit gateway using a helper VM in the same subnet, subsequent config via helper machine. Set the routing option in gateway "Use non local Gateway" (below) Upgrade to CE 2.8.2 Set Outbound rules manually, automatic outbound rules seems not to work when gateway is out of scope. All works perfectly. Thanks for your help. [image: 1758009222438-7c4cb76a-a092-48ca-b95b-60f9174cd8d2-image.png]

@Gertjan said in Error when xxtrat PFSENSE ISO file: The error "0x80070522 " implies a lot. I put all my bets on "Microsoft Windows" ^^ You are probably right, not seen any for a long time ... not using the big W.

One other thing I also did was cp libmd.so.6 to libmd.so.7 to see if I could get pkg to work, and it did work. I don’t think it made a difference in the end, but wanted to mention it. Also after the upgrade finished, it did overwrite that copy with the actual proper file.

@sandie Cleaning up boot environments also resolved this issue on a Netgate 4100. It would be great if they caught the issue and provided better error message, or remove old boot environments that are over a year old. Went from 1.9GB of free disk space to 4GB of usable space. for others seeing this issue. this output was during the clean up process, there were several more entries at the start, but weren't in my buffer anymore. [25.07.1-RELEASE][root@pfSense.home.arpa]/root: df -h Filesystem Size Used Avail Capacity Mounted on pfSense/ROOT/default 3.2G 1.3G 1.9G 40% / devfs 1.0K 0B 1.0K 0% /dev pfSense/var 1.9G 3.5M 1.9G 0% /var pfSense/tmp 1.9G 888K 1.9G 0% /tmp pfSense/home 1.9G 96K 1.9G 0% /home pfSense/var/db 5.9G 4.0G 1.9G 68% /var/db pfSense/var/log 1.9G 4.1M 1.9G 0% /var/log pfSense/var/cache 1.9G 96K 1.9G 0% /var/cache pfSense/var/tmp 1.9G 112K 1.9G 0% /var/tmp pfSense/ROOT/default/cf 1.9G 1.7M 1.9G 0% /cf pfSense/ROOT/default/var_cache_pkg 2.3G 402M 1.9G 17% /var/cache/pkg pfSense/ROOT/default/var_db_pkg 1.9G 7.9M 1.9G 0% /var/db/pkg tmpfs 4.0M 140K 3.9M 3% /var/run devfs 1.0K 0B 1.0K 0% /var/dhcpd [25.07.1-RELEASE][root@pfSense.home.arpa]/root: bectl list BE Active Mountpoint Space Created auto-default-20240314022141 - - 627M 2024-03-14 02:21 default NR / 5.01G 2025-09-13 14:18 default_20240413162830 - - 29.8M 2024-04-13 16:28 default_20240413162830_20240413162833 - - 532M 2023-05-22 16:08 default_20250913141802 - - 822M 2025-01-21 10:06 [25.07.1-RELEASE][root@pfSense.home.arpa]/root: bectl destroy default_20240413162830_20240413162833 [25.07.1-RELEASE][root@pfSense.home.arpa]/root: bectl list BE Active Mountpoint Space Created default NR / 4.07G 2025-09-13 14:18 default_20240413162830 - - 1.06G 2024-04-13 16:28 default_20250913141802 - - 822M 2025-01-21 10:06 [25.07.1-RELEASE][root@pfSense.home.arpa]/root: df -h Filesystem Size Used Avail Capacity Mounted on pfSense/ROOT/default 5.4G 1.3G 4.1G 24% / devfs 1.0K 0B 1.0K 0% /dev pfSense/var 4.1G 3.5M 4.1G 0% /var pfSense/tmp 4.1G 240K 4.1G 0% /tmp pfSense/home 4.1G 96K 4.1G 0% /home pfSense/var/db 8.1G 4.0G 4.1G 50% /var/db pfSense/var/log 4.1G 4.1M 4.1G 0% /var/log pfSense/var/cache 4.1G 96K 4.1G 0% /var/cache pfSense/var/tmp 4.1G 112K 4.1G 0% /var/tmp pfSense/ROOT/default/cf 4.1G 1.7M 4.1G 0% /cf pfSense/ROOT/default/var_cache_pkg 4.5G 402M 4.1G 9% /var/cache/pkg pfSense/ROOT/default/var_db_pkg 4.1G 7.9M 4.1G 0% /var/db/pkg tmpfs 4.0M 140K 3.9M 3% /var/run devfs 1.0K 0B 1.0K 0% /var/dhcpd/dev

It looks like we are close to finding a solution to the HP DL issue (and likely other hardware).

fwiw, after checking a few other systems I am seeing this exact notice on several other 2.8.0 systems. Now I am geussing the above system had the notice before upgrading to 2.8.1.

Hmm, I agree. Let me see what we can do here.

Check for rogue repo files here: [2.8.1-RELEASE][admin@cedev-2.stevew.lan]/root: ls -ls /usr/local/etc/pkg/repos/ total 1 1 -rw-r--r-- 1 root wheel 25 Aug 28 17:10 FreeBSD.conf 1 lrwxr-xr-x 1 root wheel 55 Sep 5 12:02 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-0002.conf It's been a long while since I tried pf2ad but I'm pretty sure it has an install/uninstall script that should do it. Unless it's completely broken!

Everything should be back to normal now for IPv6 connectivity, there was an upstream issue that's been resolved.

You can always just reinstall 2.7.2 which will give you the new larger sized EFI partition and then upgrade again from there.

The driver firmware loading issue is not fixed in 2.8.1. It's still broken upstream AFAIK. You will still need to apply one of the workarounds.

@stephenw10 Yeah I am not sure what went wrong originally but glad it is working now!