upgrade from 2.7.0 to 2.7.2 failed
-
Hi!
I am attempting to upgrade from 2.7.0 to 2.7.2 and the upgrade failed:
>>> 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. 549 packages processed. All repositories are up to date. >>> Upgrading -upgrade... failed.My system has been upgraded to ZFS and 2.7.0 has been running for a while (a couple of months?). I believe I'm booting and running from ada0.
Reading through some of the other 2.7.0 to 2.7.2 posts, I'm not sure that I'm seeing the same EFI space issue.?.? Here is some data:
[2.7.0-RELEASE][admin@router.localdomain]/: df -hi /boot/efi/ Filesystem Size Used Avail Capacity iused ifree %iused Mounted on pfSense/ROOT/default 102G 1.1G 101G 1% 32k 212M 0% /[2.7.0-RELEASE][admin@router.localdomain]/: gpart show => 63 15269825 mmcsd0 MBR (7.3G) 63 1 - free - (512B) 64 15269823 1 freebsd [active] (7.3G) 15269887 1 - free - (512B) => 40 250069600 ada0 GPT (119G) 40 1024 1 freebsd-boot (512K) 1064 984 - free - (492K) 2048 2097152 2 freebsd-swap (1.0G) 2099200 247969792 3 freebsd-zfs (118G) 250068992 648 - free - (324K) => 0 15269823 mmcsd0s1 BSD (7.3G) 0 14503936 1 freebsd-ufs (6.9G) 14503936 763904 2 freebsd-swap (373M) 15267840 1983 - free - (992K)[2.7.0-RELEASE][admin@router.localdomain]/: cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ada0p2 none swap sw 0 0[2.7.0-RELEASE][admin@router.localdomain]/: geom -t Geom Class Provider mmcsd0 DISK mmcsd0 mmcsd0 PART mmcsd0s1 mmcsd0s1 PART mmcsd0s1a mmcsd0s1a LABEL ufsid/5cf59e2ec4059a3e ufsid/5cf59e2ec4059a3e DEV mmcsd0s1a DEV mmcsd0s1 PART mmcsd0s1b mmcsd0s1b LABEL label/swap0 label/swap0 DEV mmcsd0s1b DEV mmcsd0s1 DEV mmcsd0 DEV mmcsd0boot0 DISK mmcsd0boot0 mmcsd0boot0 DEV mmcsd0boot1 DISK mmcsd0boot1 mmcsd0boot1 DEV ada0 DISK ada0 ada0 PART ada0p1 ada0p1 LABEL gpt/gptboot0 gpt/gptboot0 DEV ada0p1 DEV ada0 PART ada0p2 swap SWAP ada0p2 DEV ada0 PART ada0p3 ada0p3 DEV zfs::vdev ZFS::VDEV ada0 DEVThis is a netgate SG-5100.
Any thoughts/pointers are very appreciated!
Thank you!
Gary
-
@garyn Are you purposefully running CE not Plus? Just wondering out loud if Netgate even tests CE on their hardware...
You can always erase the eMMC:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/multiple-disks.htmlAs far as the problem, the line "Upgrading -upgrade... failed" stands out to me...from memory only I'm wondering if that should read "pfSense-upgrade"??
-
We do test it on some things but not the 5100 specifically. However I would expect it to work there and it in fact probably was tested there because it's an easy platform to test the CE memstick serial image.
-
@garyn Did you ever find a solution to this?
I'm also stuck on 2.7.0 and can't update to either 2.7.1 nor 2.7.2, it stops on exactly the same error you're having.>>> 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. 549 packages processed. All repositories are up to date. >>> Upgrading -upgrade... failed. -
Run
pkg-static -d update, see what error is shown.The most common issue coming from 2.7.0 though is a cert issue. If it shows that try running
certctl rehashand retesting. -
@Johanna12221 - apologies for the really late reply! I have a Netgate SG-5100 which contained the factory EMMC and I added an M2 (possibly the wrong name, the extra slot for a second drive). Since approximately 2020 when I upgraded to ZFS, I was booting and running from the M2. The 2.7.0 to 2.7.2 seemed to be getting confused with the simultaneous content of original EMMC and M2. I wiped out the partitions on the EMMC (look in the netgate forums for the gpart commands - you can do these from shell or ssh). I think the original poster recommended dd'ing the EMMC drive, but I'm not brave with disk-destroyer commands. I reinstalled the serial-ISO for 2.7.2 on M2 and reloaded my configuration. That almost worked perfectly with one minor glitch - I was not aware that if you have personally created a local home list of sites that you've added to pfblockerng that the file is NOT included with your regular save-config command. The list goes in /var/db/pfblocker and our list was short but I needed to recreate it.
Hope this helps!
Gary
-
@SteveITS - yes, I'm purposely running CE. It works fine and I didn't see anything on the plus list that I needed. Clearing off the EMMC and a fresh 2.7.2 ISO install and restore configuration solved the problem.
-
@stephenw10 said in upgrade from 2.7.0 to 2.7.2 failed:
Run
pkg-static -d update, see what error is shown.The most common issue coming from 2.7.0 though is a cert issue. If it shows that try running
certctl rehashand retesting.I just had this error on a server that wouldn't update and "certctl rehash" fixed it.
Thank you for taking the time to post fixes, as it helps people years later!
