2.7.0 to 2.7.2 fails with not possible to identify which meta package is installed

thearamadon

Switched to 2.7.0, ran pkg-static -d update with no issues. Then ran pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade, also no issues. Full dumps below.

Then I switch back to 2.7.2 in the GUI and try running the updater, but it fails. Looks like I'm missing a .so. I tried reinstalling a variety of packages, but nothing seemed to get it back.

[2.7.0-RELEASE][admin@Ark.nub.lan]/root: pfSense-upgrade
ld-elf.so.1: Shared object "libcrypto.so.30" not found, required by "php"
ld-elf.so.1: Shared object "libcrypto.so.30" not found, required by "php"
ld-elf.so.1: Shared object "libcrypto.so.30" not found, required by "php"
/usr/local/libexec/pfSense-upgrade: /usr/local/sbin/-repo-setup: not found
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 4 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: ......... done
Processing entries:
Processing entries............. done
pfSense repository update completed. 550 packages processed.
All repositories are up to date.
>>> Upgrading -upgrade... failed.

[2.7.0-RELEASE][admin@Ark.nub.lan]/root: pkg-static -d update
DBG(1)[19958]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[19958]> PkgRepo: verifying update for pfSense-core
DBG(1)[19958]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[19958]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/meta.conf
DBG(1)[19958]> curl_open
DBG(1)[19958]> Fetch: fetcher used: pkg+https
DBG(1)[19958]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/meta.conf

DBG(1)[19958]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults
*   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
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 21 00:00:00 2023 GMT
*  expire date: Apr 20 23:59:59 2024 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.
* using HTTP/1.1
> GET /pfSense_v2_7_0_amd64-core/meta.conf HTTP/1.1
Host: pkg00-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Wed, 28 Jun 2023 04:49:25 GMT

< HTTP/1.1 200 OK
Fetching meta.conf:   0%< Server: nginx
< Date: Wed, 28 Feb 2024 16:47:09 GMT
< Content-Type: application/octet-stream
< Content-Length: 163
< Last-Modified: Wed, 28 Jun 2023 04:49:24 GMT
< Connection: keep-alive
< ETag: "649bbbd4-a3"
< 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)[19958]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/packagesite.pkg
DBG(1)[19958]> curl_open
DBG(1)[19958]> Fetch: fetcher used: pkg+https
DBG(1)[19958]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/packagesite.pkg

DBG(1)[19958]> 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
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 21 00:00:00 2023 GMT
*  expire date: Apr 20 23:59:59 2024 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.
* using HTTP/1.1
> GET /pfSense_v2_7_0_amd64-core/packagesite.pkg HTTP/1.1
Host: pkg00-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Wed, 28 Jun 2023 04:49:25 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg:   0%< Server: nginx
< Date: Wed, 28 Feb 2024 16:47:10 GMT
< Content-Type: application/octet-stream
< Content-Length: 1748
< Last-Modified: Wed, 28 Jun 2023 04:49:25 GMT
< Connection: keep-alive
< ETag: "649bbbd5-6d4"
< 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)[19958]> PkgRepo: verifying update for pfSense
DBG(1)[19958]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[19958]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/meta.conf
DBG(1)[19958]> curl_open
DBG(1)[19958]> Fetch: fetcher used: pkg+https
DBG(1)[19958]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/meta.conf

DBG(1)[19958]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults
*   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
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 21 00:00:00 2023 GMT
*  expire date: Apr 20 23:59:59 2024 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.
* using HTTP/1.1
> GET /pfSense_v2_7_0_amd64-pfSense_v2_7_0/meta.conf HTTP/1.1
Host: pkg01-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Thu, 16 Nov 2023 20:56:14 GMT

< HTTP/1.1 200 OK
Fetching meta.conf:   0%< Server: nginx
< Date: Wed, 28 Feb 2024 16:47:11 GMT
< Content-Type: application/octet-stream
< Content-Length: 163
< Last-Modified: Thu, 16 Nov 2023 20:56:13 GMT
< Connection: keep-alive
< ETag: "655681ed-a3"
< 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)[19958]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.pkg
DBG(1)[19958]> curl_open
DBG(1)[19958]> Fetch: fetcher used: pkg+https
DBG(1)[19958]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.pkg

DBG(1)[19958]> 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
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 21 00:00:00 2023 GMT
*  expire date: Apr 20 23:59:59 2024 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.
* using HTTP/1.1
> GET /pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.pkg HTTP/1.1
Host: pkg01-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Thu, 16 Nov 2023 20:56:14 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg:   0%< Server: nginx
< Date: Wed, 28 Feb 2024 16:47:12 GMT
< Content-Type: application/octet-stream
< Content-Length: 159352
< Last-Modified: Thu, 16 Nov 2023 20:56:14 GMT
< Connection: keep-alive
< ETag: "655681ee-26e78"
< 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.
[2.7.0-RELEASE][admin@Ark.nub.lan]/root: pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
The following package files will be deleted:
        /var/cache/pkg/pfSense-repo-2.7.0_2~bbaf1ea8ca.pkg
        /var/cache/pkg/pkg-1.19.1_2~d76bf5e50f.pkg
        /var/cache/pkg/pfSense-repo-2.7.0_2.pkg
        /var/cache/pkg/pkg-1.19.1_2.pkg
        /var/cache/pkg/pfSense-upgrade-1.0_33~bc1ca8a51c.pkg
        /var/cache/pkg/pkg-1.20.8_3~48cca6e983.pkg
        /var/cache/pkg/pfSense-upgrade-1.0_33.pkg
        /var/cache/pkg/pkg-1.20.8_3.pkg
The cleanup will free 19 MiB
Deleting files: 100%
All done
Updating pfSense-core repository catalogue...
Fetching meta.conf:   0%
Fetching packagesite.pkg:   0%
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:   0%
Fetching packagesite.pkg:   0%
pfSense repository is up to date.
All repositories are up to date.
The following 3 package(s) will be affected (of 0 checked):

Installed packages to be DOWNGRADED:
        pkg: 1.20.8_3 -> 1.19.1_2 [pfSense]

Installed packages to be REINSTALLED:
        pfSense-repo-2.7.0_2 [pfSense]
        pfSense-upgrade-1.0_33 [pfSense]

Number of packages to be reinstalled: 2
Number of packages to be downgraded: 1

The operation will free 6 MiB.
9 MiB to be downloaded.
[1/3] Fetching pfSense-repo-2.7.0_2.pkg: 100%    6 KiB   5.8kB/s    00:01
[2/3] Fetching pkg-1.19.1_2.pkg: 100%    9 MiB   9.3MB/s    00:01
[3/3] Fetching pfSense-upgrade-1.0_33.pkg: 100%   19 KiB  19.3kB/s    00:01
Checking integrity... done (0 conflicting)
[1/3] Reinstalling pfSense-repo-2.7.0_2...
[1/3] Extracting pfSense-repo-2.7.0_2: 100%
[2/3] Downgrading pkg from 1.20.8_3 to 1.19.1_2...
[2/3] Extracting pkg-1.19.1_2: 100%
[3/3] Reinstalling pfSense-upgrade-1.0_33...
[3/3] Extracting pfSense-upgrade-1.0_33: 100%
You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.

stephenw10

Hmm what do you see from pkg-static info -x pfsense?

thearamadon

I ended up following the instructions here: https://elatov.github.io/2024/01/upgrading-pfsense-to-27x/
and it worked.

I think it was doing a force reinstall of all the packages that fixed the php .so issue.

martinaz

Hello,
When i want to do upgrade from the 2.7.0 to 2.7.2 I receive this error. Do you have any ideas why ?

1 MiB to be downloaded.
[1/1] Fetching pfSense-boot-2.7.2.pkg: .......... done
Checking integrity... done (0 conflicting)
[1/1] Reinstalling pfSense-boot-2.7.2...
[1/1] Extracting pfSense-boot-2.7.2: .......... done
mount_msdosfs: /dev/msdosfs/EFISYS: Invalid argument
pkg-static: POST-INSTALL script failed
failed.
Failed

stephenw10

Is it actually failing to upgrade?

Is it a UEFI install?

martinaz

Is it actually failing to upgrade?
yes from gui i receive that error, I've tried also from 2.70 to 2.7.1 and same error

Installed packages to be DOWNGRADED:
pfSense-boot: 2.7.2 -> 2.7.1 [pfSense-core]

Number of packages to be downgraded: 1

1 MiB to be downloaded.
[1/1] Fetching pfSense-boot-2.7.1.pkg: .......... done
Checking integrity... done (0 conflicting)
[1/1] Downgrading pfSense-boot from 2.7.2 to 2.7.1...
[1/1] Extracting pfSense-boot-2.7.1: .......... done
mount_msdosfs: /dev/msdosfs/EFISYS: Invalid argument
pkg-static: POST-INSTALL script failed
failed.
Failed

stephenw10

Hmm, that was just after trying to upgrade? It shows the pkg being downgraded, what did you run to trigger that?

martinaz

@stephenw10
I've tried to upgrade, from gui I have the option to choose 2.7.1 or 2.7.2 but doesn't work, I receive the same error. Can be a ssd(hdd) issue?

stephenw10

It could be but I doubt it. It's trying to mount the EFI partition to update the loader and failing.

Is this actually a UEFI install?

stephenw10

Check the version of pfSense-upgrade you have. Run: pkg-static info -x pfsense

This should be fixed in current pfSense-upgrade versions:
https://redmine.pfsense.org/issues/14046

martinaz

@stephenw10
This is the output from the pkg-static info -x pfsense
pfSense-2.7.0
pfSense-Status_Monitoring-php82-1.8_3
pfSense-base-2.7.0
pfSense-boot-2.7.2
pfSense-default-config-serial-2.7.0
pfSense-kernel-pfSense-2.7.0
pfSense-pkg-zabbix-agent6-1.0.6
pfSense-rc-2.7.0
pfSense-repo-2.7.0_2
pfSense-repoc-20230912
pfSense-upgrade-1.2.1
php82-pfSense-module-0.95

stephenw10

Hmm, what do you see from: ls -ls /dev ?

Does /dev/gpt or /dev/msdosfs exist?

How about from: cat /etc/fstab ?

martinaz

@stephenw10

cat /etc/fstab

Device Mountpoint FStype Options Dump Pass#

/dev/ada0p2 none swap sw 0 0

ls -ls /dev
total 5
0 crw-rw-r-- 1 root operator 0x2e Mar 1 18:01 acpi
0 crw-r----- 1 root operator 0x7a Mar 1 18:01 ada0
0 crw-r----- 1 root operator 0x7c Mar 1 18:01 ada0p1
0 crw-r----- 1 root operator 0x7e Mar 1 18:01 ada0p2
0 crw-r----- 1 root operator 0x80 Mar 1 18:01 ada0p3
0 crw-rw-r-- 1 root operator 0x30 Mar 1 18:01 apm
0 crw-rw---- 1 root operator 0x2f Mar 1 18:01 apmctl
0 crw------- 1 root kmem 0x19 Mar 1 18:01 audit
0 crw------- 1 root wheel 0x18 Mar 1 18:01 auditpipe
0 crw------- 1 root wheel 0x17 Mar 1 18:01 bnxt_mgmt
0 crw------- 1 root wheel 0x1e Mar 1 18:01 bpf
0 lrwxr-xr-x 1 root wheel 3 Mar 1 18:01 bpf0 -> bpf
0 crw------- 1 root wheel 0x6 Mar 1 18:02 console
0 crw------- 1 root wheel 0xd Mar 1 18:01 consolectl
0 crw-r----- 1 root kmem 0x84 Mar 1 18:01 cpuctl0
0 crw-r----- 1 root kmem 0x85 Mar 1 18:01 cpuctl1
0 crw-r----- 1 root kmem 0x8f Mar 1 18:01 cpuctl2
0 crw-r----- 1 root kmem 0x90 Mar 1 18:01 cpuctl3
0 crw-rw-rw- 1 root wheel 0x91 Mar 1 18:01 crypto
0 crw-rw-rw- 1 root wheel 0x14 Mar 1 18:01 ctty
0 crw-rw---- 1 uucp dialer 0x46 Mar 1 18:01 cuau0
0 crw-rw---- 1 uucp dialer 0x47 Mar 1 18:01 cuau0.init
0 crw-rw---- 1 uucp dialer 0x48 Mar 1 18:01 cuau0.lock
0 crw-rw---- 1 uucp dialer 0x4c Mar 1 18:01 cuau1
0 crw-rw---- 1 uucp dialer 0x4d Mar 1 18:01 cuau1.init
0 crw-rw---- 1 uucp dialer 0x4e Mar 1 18:01 cuau1.lock
0 crw------- 1 root wheel 0xa Mar 1 18:01 devctl
0 crw-r--r-- 1 root wheel 0x5 Mar 1 18:01 devctl2
0 cr--r--r-- 1 root wheel 0x59 Mar 1 18:01 devstat
0 lrwxr-xr-x 1 root wheel 11 Mar 1 18:01 dumpdev -> /dev/ada0p2
1 dr-xr-xr-x 3 root wheel 512 Mar 1 18:01 enc@n3061686369656d30
1 dr-xr-xr-x 2 root wheel 512 Mar 1 18:01 fd
0 crw------- 1 root wheel 0x10 Mar 1 18:01 fido
0 crw-rw-rw- 1 root wheel 0x1b Mar 1 18:01 full
0 crw-r----- 1 root operator 0x9 Mar 1 18:01 geom.ctl
1 dr-xr-xr-x 2 root wheel 512 Mar 1 18:01 gpt
0 crw-r--r-- 1 root wheel 0x31 Mar 1 18:01 hpet0
1 dr-xr-xr-x 2 root wheel 512 Mar 1 18:01 input
0 crw------- 1 root wheel 0x21 Mar 1 18:01 io
1 dr-xr-xr-x 2 root wheel 512 Mar 1 18:01 iov
0 lrwxr-xr-x 1 root wheel 7 Mar 1 18:01 kbd0 -> kbdmux0
0 crw------- 1 root wheel 0x12 Mar 1 18:01 kbdmux0
0 crw------- 1 root wheel 0xc Mar 1 18:01 klog
0 crw-r----- 1 root kmem 0x16 Mar 1 18:01 kmem
1 dr-xr-xr-x 2 root wheel 512 Mar 1 18:01 led
0 crw------- 1 root wheel 0xb Mar 1 18:01 mdctl
0 crw-r----- 1 root kmem 0x15 Mar 1 18:01 mem
0 crw-rw-rw- 1 root wheel 0x29 Mar 1 18:01 midistat
0 crw-r----- 1 root operator 0x6d Mar 1 18:01 mlx5ctl
0 crw-r----- 1 root operator 0x5a Mar 1 18:01 mmcsd0
0 crw-r----- 1 root operator 0x5e Mar 1 18:01 mmcsd0boot0
0 crw-r----- 1 root operator 0x5f Mar 1 18:01 mmcsd0boot1
0 crw-r----- 1 root operator 0x5b Mar 1 18:01 mmcsd0p1
0 crw-r----- 1 root operator 0x5c Mar 1 18:01 mmcsd0p2
0 crw-r----- 1 root operator 0x60 Mar 1 18:01 mmcsd0rpmb
1 dr-xr-xr-x 2 root wheel 512 Mar 1 18:01 msdosfs
0 crw-rw-rw- 1 root wheel 0x2b Mar 1 18:01 music0
0 crw------- 1 root wheel 0x53 Mar 1 18:01 netdump
0 crw------- 1 root wheel 0x1a Mar 1 18:01 netmap
0 crw-rw-rw- 1 root wheel 0x1c Mar 1 22:16 null
0 lrwxr-xr-x 1 root wheel 4 Mar 1 18:01 ovpns2 -> tun2
0 crw------- 1 root operator 0x77 Mar 1 18:01 pass0
0 crw------- 1 root operator 0x78 Mar 1 18:01 pass1
0 crw-r--r-- 1 root wheel 0x20 Mar 1 18:01 pci
0 crw-rw---- 1 root proxy 0x55 Mar 1 18:01 pf
0 crw------- 1 root wheel 0x54 Mar 1 18:01 pfil
1 dr-xr-xr-x 2 root wheel 512 Mar 1 18:04 pts
0 crw-r--r-- 1 root wheel 0x7 Mar 1 18:01 random
1 dr-xr-xr-x 2 root wheel 512 Mar 1 18:01 reroot
0 crw-rw-rw- 1 root wheel 0x2a Mar 1 18:01 sequencer0
0 crw------- 1 root operator 0x76 Mar 1 18:01 ses0
0 crw-r--r-- 1 root wheel 0x4 Mar 1 18:01 sndstat
0 crw------- 1 root wheel 0x2c Mar 1 18:01 speaker
0 lrwxr-xr-x 1 root wheel 4 Mar 1 18:01 stderr -> fd/2
0 lrwxr-xr-x 1 root wheel 4 Mar 1 18:01 stdin -> fd/0
0 lrwxr-xr-x 1 root wheel 4 Mar 1 18:01 stdout -> fd/1
0 crw------- 1 root wheel 0xe Mar 1 18:01 sysmouse
0 cr-------- 1 root wheel 0x2d Mar 1 18:01 tcp_log
0 crw------- 1 root tty 0x43 Mar 1 18:02 ttyu0
0 crw------- 1 root wheel 0x44 Mar 1 18:01 ttyu0.init
0 crw------- 1 root wheel 0x45 Mar 1 18:01 ttyu0.lock
0 crw------- 1 root wheel 0x49 Mar 1 18:01 ttyu1
0 crw------- 1 root wheel 0x4a Mar 1 18:01 ttyu1.init
0 crw------- 1 root wheel 0x4b Mar 1 18:01 ttyu1.lock
0 crw------- 1 root tty 0x61 Mar 1 18:02 ttyv0
0 crw------- 1 root wheel 0x62 Mar 1 18:02 ttyv1
0 crw------- 1 root wheel 0x63 Mar 1 18:02 ttyv2
0 crw------- 1 root wheel 0x64 Mar 1 18:02 ttyv3
0 crw------- 1 root wheel 0x65 Mar 1 18:02 ttyv4
0 crw------- 1 root wheel 0x66 Mar 1 18:02 ttyv5
0 crw------- 1 root wheel 0x67 Mar 1 18:02 ttyv6
0 crw------- 1 root wheel 0x68 Mar 1 18:02 ttyv7
0 crw------- 1 root wheel 0x69 Mar 1 18:01 ttyv8
0 crw------- 1 root wheel 0x6a Mar 1 18:01 ttyv9
0 crw------- 1 root wheel 0x6b Mar 1 18:01 ttyva
0 crw------- 1 root wheel 0x6c Mar 1 18:01 ttyvb
0 crw------- 1 uucp dialer 0x92 Mar 1 18:01 tun2
0 crw------- 1 root wheel 0x4f Mar 1 18:01 ufssuspend
0 lrwxr-xr-x 1 root wheel 9 Mar 1 18:01 ugen0.1 -> usb/0.1.0
0 crw------- 1 root wheel 0x22 Mar 1 18:01 uinput
0 lrwxr-xr-x 1 root wheel 6 Mar 1 18:01 urandom -> random
1 dr-xr-xr-x 2 root wheel 512 Mar 1 18:01 usb
0 crw-r--r-- 1 root operator 0x56 Mar 1 18:01 usbctl
0 crw------- 1 root operator 0x57 Mar 1 18:01 xpt0
0 crw-rw-rw- 1 root wheel 0x1d Mar 1 18:01 zero
0 crw-rw-rw- 1 root operator 0x51 Mar 1 18:01 zfs

stephenw10

Ah, it does have a GPT device.
Check: gpart list

martinaz

@stephenw10
Geom name: mmcsd0
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 61071319
first: 40
entries: 128
scheme: GPT
Providers:

Name: mmcsd0p1
Mediasize: 524288 (512K)
Sectorsize: 512
Stripesize: 512
Stripeoffset: 0
Mode: r0w0e0
efimedia: HD(1,GPT,11fe5cdb-5c2b-11ed-a7b4-0008a20ea319,0x28,0x400)
rawuuid: 11fe5cdb-5c2b-11ed-a7b4-0008a20ea319
rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
label: (null)
length: 524288
offset: 20480
type: freebsd-boot
index: 1
end: 1063
start: 40
Name: mmcsd0p2
Mediasize: 31137988096 (29G)
Sectorsize: 512
Stripesize: 512
Stripeoffset: 0
Mode: r0w0e0
efimedia: HD(2,GPT,11fefb2c-5c2b-11ed-a7b4-0008a20ea319,0x428,0x39ffbff)
rawuuid: 11fefb2c-5c2b-11ed-a7b4-0008a20ea319
rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 31137988096
offset: 544768
type: freebsd-ufs
index: 2
end: 60817446
start: 1064
Consumers:
Name: mmcsd0
Mediasize: 31268536320 (29G)
Sectorsize: 512
Stripesize: 512
Stripeoffset: 0
Mode: r0w0e0

Geom name: ada0
modified: false
state: OK
fwheads: 16
fwsectors: 63
last: 250069639
first: 40
entries: 128
scheme: GPT
Providers:

Name: ada0p1
Mediasize: 524288 (512K)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 20480
Mode: r0w0e0
efimedia: HD(1,GPT,432d156c-61a0-11ed-ba99-0008a20ea319,0x28,0x400)
rawuuid: 432d156c-61a0-11ed-ba99-0008a20ea319
rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
label: gptboot0
length: 524288
offset: 20480
type: freebsd-boot
index: 1
end: 1063
start: 40
Name: ada0p2
Mediasize: 1073741824 (1.0G)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 1048576
Mode: r1w1e0
efimedia: HD(2,GPT,43328133-61a0-11ed-ba99-0008a20ea319,0x800,0x200000)
rawuuid: 43328133-61a0-11ed-ba99-0008a20ea319
rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
label: swap0
length: 1073741824
offset: 1048576
type: freebsd-swap
index: 2
end: 2099199
start: 2048
Name: ada0p3
Mediasize: 126960533504 (118G)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 1074790400
Mode: r1w1e1
efimedia: HD(3,GPT,43356ccc-61a0-11ed-ba99-0008a20ea319,0x200800,0xec7b800)
rawuuid: 43356ccc-61a0-11ed-ba99-0008a20ea319
rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
label: zfs0
length: 126960533504
offset: 1074790400
type: freebsd-zfs
index: 3
end: 250068991
start: 2099200
Consumers:
Name: ada0
Mediasize: 128035676160 (119G)
Sectorsize: 512
Mode: r2w2e3

stephenw10

Are you booting ZFS from the SSD or UFS from the eMMC?

stephenw10

Do both fail to upgrade?

stephenw10

Hmm, I assume it must be ZFS from the SSD since the /dev/gpt device is created.

I can't replicate this locally. Do you know what version was installed initially?

martinaz

@stephenw10
The device boot from the SSD, and the initial version it was 2.6.0-RELEASE, the upgrades worked with no issues until today.

stephenw10

Can you confirm it's booting ZFS from the SSD?

The dashboard will show the ~120GB drive and that is's ZFS.

I think the issue here is being caused by the fact you have two installed drives and it's trying to update the wrong one. Trying to replicate it locally.