TrueNAS 25.10.2.1 is Now Available!

Announcements
1

The TrueNAS team is pleased to release TrueNAS 25.10.2.1!

This is a small maintenance release to fix NIC bonding disruptions and SMB Legacy Share validation errors after the TrueNAS 25.10.2 release, and includes the NFS performance improvement for NFSv4 clients that was originally announced for 25.10.2.

Notable changes:

  • Improves NFS performance for NFSv4 clients (NAS-139128). Adds support for STATX_CHANGE_COOKIE to properly surface ZFS sequence numbers to NFS clients via knfsd. The NFS change_info4 structure now accurately tracks directory and file changes, which reduces unnecessary server requests. Client attribute cache invalidation is also improved. Previously, the system synthesized change IDs based on ctime, which could fail to increment consistently due to kernel timer coarseness.
  • Fixes NIC bonding configuration disrupted after a system update (NAS-139889). Resolves an issue where network interface bond configurations could break after a TrueNAS 25.10.2 update. Affected systems could lose network connectivity on bonded interfaces.
  • Fixes SMB Legacy Share validation errors that broke share management UI forms (NAS-139892). Resolves an issue where SMB shares using the Legacy Share preset with certain path_suffix variable substitutions failed middleware validation. The SMB share configuration forms became unusable in the web interface as a result.
  • Fixes API result serialization failures caused by unhandled validation errors (NAS-139896). Resolves an issue where certain Pydantic validation errors were not caught during API result serialization. This caused unexpected errors to appear in the web interface instead of proper error messages.
  • Fixes SSL certificate connection failure error handling (NAS-139938). Resolves an AttributeError that occurred when an HTTPS connection failed due to a certificate error. Cloud sync tasks, replication, or other SSL-dependent network operations could surface a secondary AttributeError instead of the original connection failure message.

See the Release Notes and changelog for more details.

25.10.2.1 Documentation : TrueNAS Documentation Hub
Download : https://www.truenas.com/download-truenas-community-edition

Thank you for using TrueNAS! As always, we appreciate your feedback!

7 Likes
ESXi 8 U2, nfs4 - Core works fine but Scale is causing issues
Goldeye (25.10) Takes Over
2

Is the file link on the website correct? Looks like I downloaded the same copy of 25.10.2, not 25.10.2.1. with identical file sizes.

3

The link may not have been updated yet on that page. There’s a direct link on https://www.truenas.com/docs/softwarestatus/#downloads that you can use in the meantime.

1 Like
4

It should be correct now.

https://www.truenas.com/download/

1 Like
5

Thanks. I figured that I’d beat everyone this one time. I just happen to be online. I plan to test it later today.

2 Likes
6

Updated without issues again, :+1:

1 Like
7

Four uneventful updates so far :+1:

8

New alerts:

  • Failed to check for alert BondStatus: Netlink socket busy

Current alerts:

  • Failed to check for alert BondStatus: Netlink socket busy

I have gota bunch of these since installing 25.10.2.1

I have 2 bridge interfaces, but no bonds

A cluster of 8 appeared shortly after midnight, then cleared. Since then nothing

9

Same error here with similar setup - 1 NIC with 2 vlans each with 1 bridged interface.

10

Just updated without issue … again :grinning_face:

11

If it repeats, please start a new General thread and post a link. We’ll need details on hardware to review.

If someone has a reproducable case, please report a bug…with diagnostics.

1 Like
12

25.10.2.1 is the best from the 25 series so far. Thank you TrueNAS Team!

3 Likes
13

Thanks, I should have noticed that NAS-139889 was present in this release and not fixed yet before jumping on board, so now my Discord server is going to spam me with a notification every 30 minutes.

15

“Failed to check for alert BondStatus: Netlink error: 16” Is Not fixed and it seams that I get the messages mor frequent that on 25.10.2.

EDIT: service middlewared restart stopped the alerts for now.

2 Likes
16

Thanks for noting that… did a simple reboot not work?

17

It restarts the middleware deamon your ui will be unreachable for a moment but if your whole system restarts than I guess something else is wrong.

18

Same for me, restarting middlewared did the trick. Came out of nowhere, no even first day after 25.10.2.1, and I’m not using Bonds, just a bridge and a VLAN.

Unfortunately I’m using install-dev-tools so no debugs incoming from me

19

I also got this error suddenly tonight about 5 times. I updated to 25.10.2.1, 4 days and 7 hours ago.
“Failed to check for alert BondStatus: Netlink socket busy”

I don’t have bonding, only a bridge connected to 1 Intel 10GB NIC. Only 2 network cables attached to the machine: 1 to my network and 1 for IPMI.

20

I can see two other report on this bug: NAS-140041 is one of them.

21

Somewhat reluctantly, I upgraded my main server from 25.04 latest to 25.10.2.1. No apparent issues–it took a few minutes for apps to start, but they did all come up without issue. I’d run into some poor responsiveness from the middleware in 25.04, so I’ll be interested to see if that’s improved.

ARC behavior already seems to have improved:

image
image557Ă—414 19.5 KB

1 Like