Now Available: pfSense® Plus 25.07-RELEASE

[stephenw10]

Ok this works for me: 175.diff

It's a very simple (one character!) change so you might just manually edit the file. Let us know if you're able to test that.

[jos-andel]

@stephenw10

Just tested the patched pfSense-rc on our spare unit.

/etc: diff pfSense-rc.org pfSense-rc
590c590
< SWAPDEVICE=/bin/cat /etc/fstab | /usr/bin/grep swap | /usr/bin/awk '{ printf $1 }' | /usr/bin/head -n 1

SWAPDEVICE=/bin/cat /etc/fstab | /usr/bin/grep swap | /usr/bin/awk '{ print $1 }' | /usr/bin/head -n 1

Works like a charm:
: swapinfo
Device 1K-blocks Used Avail Capacity
/dev/ada0p2 1048576 0 1048576 0%
/dev/ada1p2 1048576 0 1048576 0%
Total 2097152 0 2097152 0%

: cat /tmp/fstab.swap

Device Mountpoint FStype Options Dump Pass#

/dev/ada0p2 none swap sw 0 0
/dev/ada1p2 none swap sw 0 0
[25.07-RELEASE][admin@arn1-ops-vpnspare.mgmt.sidn.nl]/etc:

[mvikman]

@stephenw10

I'm planning to upgrade, but still on 24.11 and I have ZFS mirror with GEOM mirrored swap, would this problem affect my system or is it just for systems with multiple separate (non-mirrored) swap partitions on the both drives?

[stephenw10]

Try running the new command in 24.11: /bin/cat /etc/fstab | /usr/bin/grep swap | /usr/bin/awk '{ printf $1 }' | /usr/bin/head -n 1

If that returns a valid device it will be fine in 25.07.

Either way it won't prevent you upgrading. And you should just be able to apply the patch afterwards to regain SWAP. If you need it.

[mvikman]

@stephenw10
It returns "/dev/mirror/swap" so guessing it should be ok.
Never had pfSense using any swap, but better safe than sorry... :)

[stephenw10]

Yup should be fine.

[jos-andel]

@stephenw10

As expected, also works just fine on 25.07.1-RELEASE.

[matsan]

Is the SG-3100 a still supported device? Just bricked one of ours updating 24.11 -> 25.07.1 - notice the "unsupported platform" message from the update log.

...
Installed packages to be UPGRADED:
	pfSense-boot: 24.11 -> 25.07.1 [pfSense-core]

Number of packages to be upgraded: 1
[1/1] Upgrading pfSense-boot from 24.11 to 25.07.1...
[1/1] Extracting pfSense-boot-25.07.1: .......... done
>>> Upgrading pfSense kernel...
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pfSense-kernel-pfSense-3100: 24.11 -> 25.07.1 [pfSense-core]

Number of packages to be upgraded: 1
[1/1] Upgrading pfSense-kernel-pfSense-3100 from 24.11 to 25.07.1...
[1/1] Extracting pfSense-kernel-pfSense-3100-25.07.1: .......... done
===> Keeping a copy of current kernel in /boot/kernel.old
>>> Removing unnecessary packages...done.
>>> Upgrading boot code...
Unsupported platform.
System is going to be upgraded.  Rebooting in 10 seconds.
Success

[matsan]

Scratch that last post. The problem was related to +30k backup config files as noted in other posts.
Problem solved unit on 25.07.1 now. Will clear the directory before doing our other units.

[stephenw10]

Yup it's only the boot code update script reporting that there. The 3100 is EoL but 25.07(.1) does still support it.

[Phizix]

All,

On my SG5100 just upated to 25.07.1 over the weekend. No issues. It uninstalled and re-installed one package automatically. Otherwise I did nothing else.

To be clear, my setup is fairly simple.

Phizix