TrueNAS 26.0.0-BETA.3 is Now Available!

Announcements
1

:warning: Early Release Software

Early releases are intended for testing and feedback purposes. Do not use early-release software for critical tasks.

The TrueNAS team is pleased to release TrueNAS 26-BETA.3!

This release updates the Linux kernel and OpenZFS, moves the NVIDIA GPU driver to the Long Term Support Branch for a longer support window, and adds dedicated spares for dRAID pools and spare activation for special and dedup vdevs. It also fixes upgrade issues that affected Active Directory and Enterprise update profiles, a cloud backup defect that stopped all scheduled tasks, Fibre Channel target mode crashes, and container, virtual machine, and networking issues.

26-BETA.3 Notable Changes

  • Fixes crashes on systems that use Fibre Channel target mode (NAS-142014, NAS-142018).
    The QLogic Fibre Channel target driver could follow a null target operations pointer from interrupt paths, and target mode could stay partly enabled after target registration failed. The driver now checks the pointer before it uses it and fails target enable when registration does not succeed.

  • Fixes cloud backup tasks that could stop the middlewared event loop and silently disable every scheduled task (NAS-141948).
    The cloud backup progress thread updated job progress from outside the event loop, which stopped the loop while the middlewared service still reported as active. Cron jobs continued to fire and log, but every scheduled task did nothing and raised no error. Progress updates now run on the event loop.

  • Fixes a memory leak in the console CLI that could exhaust system memory (NAS-141238).
    Continuous input on the physical console, such as a stuck key on an attached keyboard, made the CLI process grow to tens of gigabytes of RAM until the kernel out-of-memory killer stopped it. Console CLI memory use is now bounded regardless of how much input arrives.

  • Fixes upgrades to TrueNAS 26 that leave Active Directory non-functional (NAS-141469).
    On an Active Directory member server, the directory cache could go FAULTED after the post-upgrade reboot and winbind could fail to start, which locked users out until an administrator left and rejoined the domain. A related defect also logged a false message once an hour that the machine account password changed. The member state now survives the upgrade.

  • Fixes faulty parsing of smartctl output that filled /var/log/middlewared.log with errors (NAS-141215, NAS-141951).
    Systems updated to 25.10.5 logged repeated parse errors from drive health checks. The parser handles the full range of smartctl output so drive health checks complete without errors.

  • Improves failover speed by moving the remote disk retaste call out of the failover event (NAS-141988).
    A remote disk scan ran inside the critical failover path, where it could delay failover while services stayed offline. The scan now runs outside that path.

  • Fixes a database migration failure when updating from TrueNAS 25.04.2.6 to 25.10.3.1 (NAS-141221).
    The update stopped a few seconds after it started with an [EFAULT] error from the migrate command. The migration now completes so the update finishes.

  • Fixes an upgrade that forced the update profile to Mission Critical on Enterprise systems (NAS-140905).
    A database migration set the update profile to Mission Critical on every Enterprise system, regardless of the profile the running version actually used. The system then raised a warning that the running system version profile did not match the selected update profile. The migration now keeps the profile that the system already used.

  • Fixes replication failures for source systems that host a container when the task uses Full Filesystem Replication (NAS-140878).
    After an upgrade to TrueNAS 26, a replication task to a remote system on an earlier release could fail with an error about a failure to transfer all children of the container dataset. Turning off Full Filesystem Replication avoided the failure. These tasks now complete.

  • Fixes several issues with the SSH credentials used for replication (NAS-141677).
    The system now updates SFTP cloud credentials when the SSH key pair they use is removed, rejects encrypted SSH private keys consistently during validation, returns a clear error when semi-automatic remote setup uses a key pair that no longer exists or is invalid, and completes SSH pairing with TrueNAS 13 systems during remote replication setup.

  • Fixes Active Directory domain join failures caused by combined IPv4 and IPv6 PTR record updates (NAS-140548).
    nsupdate sent IPv4 and IPv6 PTR records in a single transaction, which returned a NOTZONE error and stopped the domain join. The records now go out in separate transactions.

  • Fixes SMB advertising file permissions that the file system does not enforce (NAS-141608).
    ZFS does not let the owner@, group@, and everyone@ entries carry WRITE_ACL or WRITE_OWNER, but Samba still reported those rights to clients. Samba now advertises only the rights the file system enforces, so SMB and NFS clients see the same permissions. Entries for named users and groups keep these rights.

  • Improves the speed of dataset creation with the SMB, Multiprotocol, and Apps presets (NAS-141154, NAS-141161).
    Creating a dataset with one of these presets could take several seconds on 26-BETA.1 and 26-BETA.2 because of the per-credential access check that runs during creation. Batched access probes restore normal dataset creation speed.

  • Adds support for dedicated spares on pools that use dRAID vdevs (NAS-140629, NAS-141277).
    Pool creation validation blocked dedicated spares on dRAID pools. Both the web interface and the middleware validation now allow this configuration.

  • Adds spare activation for special and dedup vdevs (NAS-141201).
    A failed device in a special or dedup vdev did not activate an available spare, which matters more as special vdevs come into wider use. Spares now activate for these vdev types.

  • Fixes the pool creation screen offering disks that SED encryption excludes (NAS-141096).
    Disk selection during pool creation did not filter for SED encryption. The disk list now applies the filter.

  • Fixes the maximum data transfer size applied to 9500 TriMode devices (NAS-140978).
    The driver did not apply the 2M limit that these devices report. An upstream fix is included so transfers stay within the supported size.

  • Fixes the storage screens showing a normal vdev status when a drive in that vdev is FAULTED (NAS-140955).
    A faulted drive did not change the vdev status, so an administrator had to expand each vdev to find the problem. The vdev status now reflects a faulted drive, as it already did for an unavailable drive.

  • Fixes a false alert that an SMB share is unavailable because it uses a locked dataset (NAS-141461).
    A ShareLocked alert could persist after boot for a share on an encrypted dataset, even though the dataset was unlocked and the share worked normally. The alert now clears when the dataset unlocks during boot.

  • Fixes custom app updates and private registry support for authenticated Docker registries (NAS-141149, NAS-141553).
    Custom app updates failed when the image came from a registry that requires authentication, and registries that use htpasswd authentication were not supported. Both authentication paths now work.

  • Fixes TrueCloud Backup errors that showed only error.message and jobs that could hang without end (NAS-141287).
    The progress reader looked for a flat error.message field, but restic nests the text inside an error object, so every restic error turned into a KeyError and the real message never reached the user or the job log. Errors now report the text that restic returns.

  • Fixes a dtype error that prevented pool selection for containers (NAS-141234).
    Virtual machine and container device settings are stored encrypted. On a system restored from a configuration whose encryption secret no longer matched, these settings decrypted to empty values and failed validation, so the form returned only dtype and the containers feature stayed unusable. Devices that cannot be decrypted are now dropped when the encryption secret resets.

  • Fixes missing IPv6 connectivity in LXC containers on a clean install (NAS-141468).
    A clean install of 26.0.0-BETA.2 enabled IPv4 forwarding but left IPv6 forwarding disabled on the host, so a container on the default truenas0 bridge received an IPv6 default route but could not reach IPv6 networks. IPv6 forwarding is now enabled.

  • Fixes WS-Discovery so the system appears in the Windows network browser (NAS-141440).
    A system running 26.0.0-BETA.2 did not show up in network discovery, even with the same configuration that worked on 26.0.0-BETA.1. Discovery works again.

  • Fixes IPv6 autoconfiguration settings that did not apply after the dhcpcd migration (NAS-141208, NAS-141386).
    An interface with Autoconfigure IPv6 disabled still received extra IPv6 default routes, and SLAAC stayed active on an interface with DHCP enabled. Both settings now apply as configured.

  • Fixes the Save button staying inactive when the device order changes in a virtual machine (NAS-140791).
    A change to Device Order on a VM device did not activate Save, so the new order could not be applied on 26.0.0-BETA.1. The change now saves.

  • Fixes virtual machines left suspended after a periodic snapshot task (NAS-141124).
    A VM with disks on a dataset covered by a periodic snapshot task could stay suspended without end, and it could only be resumed or powered off. These VMs now return to a running state.

  • Fixes certificate deletion blocked by TrueNAS Connect (NAS-141224).
    Deleting a certificate could fail with a message that TrueNAS Connect uses it, even after the system was removed from TrueNAS Connect and the force option was used. A certificate that TrueNAS Connect no longer uses now deletes.

  • Fixes the time field on system audit events (NAS-141949).
    Audit entries for svc=SYSTEM events recorded a time about seven hours behind UTC because the field used a fixed offset instead of the system time zone. Entries for svc=MIDDLEWARE and svc=SMB were already correct. System audit entries now record the correct time.

  • Updates the NVIDIA GPU driver to 580.173.02, the current Long Term Support Branch (LTSB).
    This version number is lower than the driver in 26-BETA.2, but it extends the support window for a more stable product. 26-BETA.2 shipped a 590 New Feature Branch driver, which is intended for early adopters and reaches end of life in December 2026. The 580 LTSB is supported until August 2028.

See the Release Notes and changelog for more details.

Documentation : https://www.truenas.com/docs/scale/26
Download : https://www.truenas.com/download-truenas-community-edition

Thank you for using TrueNAS! Happy BETA testing! And as always, we appreciate your feedback!

2

Will there be any updates to the Docker Engine which is currently on 28.3.1, and built over a year ago. (Wed Jul 2 20:57:06 2025)

3

You would be looking at version 27 of TrueNAS.
I just ran this on a recent nightly

Welcome to TrueNAS
truenas_admin@truenas[~]$ sudo docker version
[sudo] password for truenas_admin: 
Client: Docker Engine - Community
 Version:           29.3.0
 API version:       1.54
 Go version:        go1.25.7
 Git commit:        5927d80
 Built:             Thu Mar  5 14:25:57 2026
 OS/Arch:           linux/amd64
 Context:           default
failed to connect to the docker API at unix:///var/run/docker.sock; check if the path is correct and if the daemon is running: dial unix /var/run/docker.sock: connect: no such file or directory
truenas_admin@truenas[~]$
4

Beta 2 has been rock solid for me so far, looking forward to trying Beta 3!

5

Considering there were so many CVEs fixed in the latest v28 releases, would you be able to update TrueNAS 26 to Docker Engine 28.5.2 (not to break backwards compatibility)? TrueNAS 27 means a 2027 release. It makes no sense to leave systems that vulnerable.

Considering you’re always updating to the latest kernel line patch, please also do so for Docker.

6

Just a FYI, SmallBarky is also just a community forum member and in no way affiliated with iX.
If you want it fixed you should file a bug report in jira…

7

You can go to https://security.truenas.com/ and check the status of the CVE. Report a Bug could be an idea too. I checked and the three CVE listed under Docker 28.5.2 in the linked release notes are listed on the security page and show “26.04.0” as Fix Version.

@eturgeon Can you or other Staff explain what the fix status means with the latest Beta?

8

I really hope the change to Nvidia driver is a mistake. Reverting to 580 causes users with 5060ti, 5060 and 5050 (which are great cards for NAS transcoding) to lose the GPU because only 590 branch supports it. My 5060Ti is over 1,5 years old, it was bonkers to need to be on the Beta channel to have it supported, and now the full release is heading into a direction where current, kinda old hardware isn’t supported. I really hope that this changes course and it’s looking for me to be on Beta.2 for over a year with yearly releases. :frowning:

9

Are you sure on that? The linked NVIDIA info on the driver in the first post shows those models as supported

image
image895×616 14.2 KB

10

My apologies. It seems to be OK, I’ve also seen it so I’ve tried the update and it seems to be working (at least nvidia-smi reports the GPU which wasn’t the case on Truenas 25). Truenas 25 has 570 driver, Truenas 26 beta had 590, but it turns out that the first driver to support those cards is 576 so 580 is fine (although it may lack the bugfixes from 590 and newer). But if it works I can deal with it. Again, apologies, I thought it was reversed into a version similar to the one shipped with 25.

11

Subversioning makes for weird numbers - compare release dates, not just version numbers. :slight_smile:

580.173.02 is newer than the 590.44.01 in TN26-BETA.2 - so it should have a number of fixes from a functionality perspective, just not a new feature branch - so it’ll cap out at a lower CUDA 13.x release, for example.

But it should have the GSP firmware fix for the 5060/Ti’s that didn’t want to start on the 570 release.

12

According to Software Component Versions ( TrueNAS 26 Version Notes | TrueNAS Documentation Hub ) Docker Engine should be 29.0.4 in 26-BETA.1/.2./.3

Something seems to be wrong here? Not yet implemented?

13

I’m guessing @spjsdm just asked without checking if it had been updated yet.

Welcome to TrueNAS
truenas_admin@truenas[~]$ cat /etc/version
26.0.0-BETA.3%                                                                                                                                                                             
truenas_admin@truenas[~]$ sudo docker version
[sudo] password for truenas_admin: 
Client: Docker Engine - Community
 Version:           29.0.4
 API version:       1.52
 Go version:        go1.25.4
 Git commit:        3247a5a
 Built:             Mon Nov 24 21:59:48 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          29.0.4
  API version:      1.52 (minimum version 1.44)
  Go version:       go1.25.4
  Git commit:       4612690
  Built:            Mon Nov 24 21:59:48 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v2.1.5
  GitCommit:        fcd43222d6b07379a4be9786bda52438f0dd16a1
 runc:
  Version:          1.3.3
  GitCommit:        v1.3.3-0-gd842d771
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
14

I am still on 25.10.6 - Goldeye, which is has the 28.3.1, and I assumed that because there was no mention of a Docker update in the Change list it was not going to be updated.
My apologies…

15

No apology needed!

16

Quick question, I’ve been having this issue on Beta 2 too and when I saw the point regarding the lxc container IP6 fix I thought it might be fixed.

So I’m trying to spin up the Netbird server on an Alpine 3.22/3.24 (tried on both) container, but when I run docker compose up -d I keep getting the ‘Error response from daemon: failed to set up container networking: failed to add interface to sandbox: error setting interface “” IPv6 to : failed to configure ipv6: failed to disable IPv6 on container’s interface eth0’.

ipv6 is set to true in /etc/docker/daemon.json and the NIC connected to eth0 is a bridge interface that has both IP4 and IP6 assigned from DHCP and couldn’t get to work.
I thought maybe it was a bug that was solved now in Beta 3, but it still happens :frowning: Tried with both containers created on Beta 2 and fresh containers on Beta 3
Does anyone know if I’m doing something wrong or it’s something that needs fixing?

I’m really sorry if this isn’t the place for the question, please let me know if I should create a separate post or anything :person_bowing:

17

Not an answer to your question, but I initially misread your username as “DrunkHobbitSysAdmin” and got a kick out of it.

18

Hm, attaching with SMB/Bonjour appears to still be broken on MacOS so I’ll revert back to Beta 1 since I have my time-machine backup on the nas.

19

You should open a different thread for your issue or try Report a Bug in the TrueNAS GUI.

20

Sure, but it will be of no use since I’m not sharing my logs.