TrueNAS 26 Version Notes

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

August 20, 2026

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.

• 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.

Click here to see the full 26 changelog or visit the TrueNAS 26-BETA.3 Changelog in Jira.

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

June 17, 2026

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

• Adds Forward Error Correction (FEC) mode as a configurable network interface setting on both Community Edition and Enterprise systems (NAS-139477, NAS-140329). Network interfaces that support FEC can now have the FEC mode configured directly from the interface settings in the UI.

• Adds the ability to view the reason for each system reboot on the local node (NAS-139412). TrueNAS now stores the cause of each reboot — for example, user-initiated, kernel panic, or scheduled update — so administrators can review reboot history when they investigate system events.

• Adds the missing en_US.UTF-8 locale to TrueNAS 26 (NAS-140692). The default English UTF-8 locale was not present in BETA.1, which could cause encoding errors for applications, scripts, and containers that depend on it. The locale is now available system-wide.

• Improves visibility of important pool states such as resilvering in the web interface (NAS-139007). Pool states like resilvering, scrubbing, and degraded operations were not prominently displayed. The Storage dashboard and pool status screens now surface these states with clearer indicators so administrators can identify maintenance activity at a glance.

• Improves webshell access control with per-shell-type role checks and adds audit logging for shell sessions (NAS-141011). Webshell sessions for containers, VMs, and apps previously wrapped commands in sudo -H -u <user>, which failed against root-owned libvirt and Docker sockets. Users with the FULL_ADMIN role but without unrestricted sudo encountered Polkit errors and broken shells. Webshell authorization now uses per-shell-type role checks (VM_WRITE, CONTAINER_WRITE, APPS_WRITE) alongside the existing webshell privilege, and shell sessions emit WEBSHELL_AUTHENTICATION and WEBSHELL_LOGOUT audit events.

• Improves the built-in ACL preset templates by auto-including local and directory service user and admin groups (NAS-140530). When a built-in preset such as NFS4_RESTRICTED is applied through Use Preset, TrueNAS now adds entries for builtin_users and builtin_administrators — and, on systems joined to Active Directory, the corresponding domain users and domain admins groups. The expanded ACL appears on screen before save so administrators can remove any entries they do not want. User-created templates are unaffected.

• Improves the performance of directory listings on SMB shares from macOS clients (NAS-141125). When macOS Finder lists a directory with the AAPL extensions enabled, the previous code path added three syscalls per file entry to probe the AppleDouble resource fork size. The probe now reuses the directory enumeration’s existing file descriptor with a single syscall, reducing roughly two syscalls per file and producing noticeable listing speedups on directories with many entries.

• Fixes the Map User And Group IDs option on LXC containers not working (NAS-140766). A blocker bug prevented containers configured with user and group ID mapping from applying those mappings to the container filesystem. The mapping now applies correctly when the container starts.

• Fixes false failed a SMART selftest alerts that appeared after upgrading from TrueNAS 24.10 (Electric Eel) to 25.10 (Goldeye) or later (NAS-140652). Stale SMART data carried over during the upgrade triggered false-positive alerts on drives that had no actual SMART test failures. Affected systems no longer receive these alerts.

• Fixes a timeout in NVMe namespace delete operations on drives that contain written data (NAS-140748). The disk_resize operation could hang or fail when it removed namespaces on NVMe drives with existing data. The delete operation now completes reliably regardless of the amount of data on the namespace.

• Fixes an out-of-memory condition triggered by posix_fadvise(POSIX_FADV_SEQUENTIAL) on ZFS datasets (NAS-140587). Applications that hinted sequential access on large files could cause the system to exhaust memory and trigger the OOM killer. The ZFS sequential prefetch path is updated so the hint no longer leads to runaway memory use.

• Fixes the SMB service crash on Legacy Share types with the recycle bin feature enabled when Spotlight search is active (NAS-140749). The TrueNAS per-dataset recycle bin (vfs_recycle) keeps file handles open to prevent symlink race conditions, while the Spotlight metadata service relied on a share connection that skipped the normal file-close step during teardown. The mismatched shutdown order triggered an assertion failure and crashed the SMB service. The service shutdown order is corrected so the recycle bin and Spotlight can coexist.

• Fixes an issue where LXC containers from earlier TrueNAS versions could not start after upgrade to TrueNAS 26 (NAS-140691). The upgrade migration script did not properly mount container ZFS datasets, leaving the container filesystem intact but inaccessible and causing the init executable to appear missing. The migration script now mounts datasets correctly so containers start without manual intervention.

• Fixes GPU isolation and GPU passthrough to virtual machines after upgrade from earlier TrueNAS versions to 26 (NAS-140687). A regression in the upgrade script silently failed to apply required initramfs customizations for GPU device isolation, leaving the GPU in an unavailable state after the upgrade. Systems with a previously isolated GPU encountered a “device is not available” error when starting a VM with a passed-through GPU, or found that GPU isolation did not take effect. The upgrade script now applies the required customizations correctly so GPU isolation and passthrough work without manual recovery.

• Fixes the Send Feedback > Report a Bug feature failing to attach the debug file when Attach Debug is selected (NAS-140163, NAS-140237). The debug attachment could silently fail with no error in the UI, while ticket creation still succeeded without the debug file. The UI now uploads the debug file correctly and reports failures so users know when a manual attachment is needed.

• Fixes a regression in 26-BETA.1 that blocked virtual machine cloning (NAS-140792). Users could not clone existing VMs through the UI in BETA.1. VM cloning is restored in BETA.2.

• Fixes the GUI SSL Certificate field on System Settings > General > GUI Settings failing to save the selected certificate after upgrade from 25.10 to 26-BETA.1 (NAS-140354). The field displayed None even after a certificate was selected, and attempting to save other GUI settings produced a validation error stating the required certificate field was empty. The backend change in BETA.1 that returned the certificate as a numeric ID instead of a full object is now paired with a ui_certificate_name response field, so the UI can display and save the selected certificate correctly.

• Fixes an error that blocked saving E-Mail options when GMail OAuth is selected (NAS-140306). Users configuring outbound email with GMail OAuth could not save the configuration. The save action now completes successfully.

• Fixes the inability to pass Intel GPU devices through to LXC containers (NAS-140421). Intel GPU devices did not appear in the device picker for LXC containers, preventing assignment. The full set of supported GPU devices, including Intel, now appears and can be assigned.

• Fixes the inability to add ISO files to virtual machines through the creation wizard or by manually adding a CDROM device (NAS-140446). ISO files could not be attached to VMs either at initial creation or by manually adding a CDROM device after creation. ISO attachment now works in both flows.

• Fixes a bug where NVMe namespace resize operations dropped the list of attached controllers (NAS-140497). When a namespace was resized, the original controller attachment configuration was discarded and had to be reconfigured manually. The namespace resize now preserves controller attachments.

• Fixes incorrect storage usage estimates on the Snapshots screen (NAS-140637). Storage usage values displayed on snapshot rows did not reflect actual consumption. Usage estimates now calculate and display correctly.

• Fixes a VM XML configuration error caused by duplicate USB controllers with the same index when a VM contains two or more USB devices (NAS-140626). Adding multiple USB devices to a VM produced a libvirt XML conflict that could prevent the VM from starting. USB device controllers now use unique indexes.

• Fixes several TrueSearch and macOS Spotlight integration issues on SMB and NFS shares (NAS-140952, NAS-141078, NAS-140932). TrueSearch from macOS Spotlight failed to return results on supported SMB shares, search activity could trigger NFS timeout issues on the same system, and the WebShare service did not toggle TrueSearch support correctly when reloaded with SIGHUP. All three issues are resolved.

• Fixes USB device passthrough to virtual machines (NAS-139548). A regression caused USB passthrough to fail on some VM configurations. USB passthrough now works reliably across supported devices.

• Fixes stale container entries that remained in the UI after the host pool was disconnected (NAS-140621). Container names continued to appear in the UI after the pool that hosted them was disconnected, even though the underlying containers were gone. The container list now refreshes to reflect the current pool state.

• Fixes middleware not propagating configuration changes to the kernel nvmet subsystem (NAS-140266). NVMe-over-Fabrics target configuration changes made through the UI did not always apply to the running kernel target. Middleware now reliably updates nvmet when target settings change.

• Fixes LXC containers reporting a generic hostname instead of the configured container name (NAS-140185). Containers reported their hostname as LXCNAME regardless of the name set in TrueNAS. The container hostname now matches the name shown in the UI.

• Fixes an error that blocked edits to user accounts that belong to the docker group (NAS-139955). Editing a user account that included docker group membership returned an error and prevented saving. User edits now succeed regardless of docker group membership.

• Fixes the encryption dialog refusing to save when a validation error occurs on a hidden field (NAS-140293). Users could be blocked from saving the encryption configuration by a validation error on a field that was not visible in the current dialog state. The dialog now allows saving when hidden field errors do not apply.

• Fixes the Manual Update screen linking to a 404 page for the manual image installation guide (NAS-140366). The See the manual image installation guide link pointed at an outdated URL that no longer exists. The link now points to the correct documentation.

• Fixes Cloud Sync tasks targeting custom S3-compatible endpoints failing after the 25.10 upgrade (NAS-140383). A signing behavior change in 25.10 broke custom S3 backup destinations on non-AWS providers. Compatibility with non-AWS S3 providers is restored.

• Fixes dashboard widgets not rendering on some systems upgraded from 25.10.2 (NAS-139966). Dashboard widgets could fail to load after the upgrade because of stale widget configuration data. The widget configuration is migrated correctly so the dashboard renders without intervention.

• Fixes incorrect sort order on the Virtual Machines screen when sorting by the Running column (NAS-140501). Sorting VMs by running state did not group running and stopped VMs predictably. The sort now produces a consistent grouped order.

• Fixes the Alerts panel opening behind an active slide-in form (NAS-140108). When a configuration slide-in was open, clicking the alerts icon opened the alerts panel below the slide-in, where users could not see or interact with it. The alerts panel now opens above the slide-in.

• Removes a legacy USB boot detection workaround that could add a 15-second delay to system boot (NAS-140745). A workaround introduced in 2021 to address an early SCALE alpha boot-pool import race on USB boot disks injected ZFS_INITRD_POST_MODPROBE_SLEEP=15 into /etc/default/zfs on systems where any boot-pool vdev appeared to be on a USB bus. USB boot is no longer a supported TrueNAS configuration, and the workaround is removed. Systems upgraded from a version that wrote the sleep line have it stripped automatically.

Click here to see the full 26 changelog or visit the TrueNAS 26-BETA.2 Changelog in Jira.

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

April 7, 2026

The TrueNAS team is pleased to release TrueNAS 26-BETA.1! This first public release version of TrueNAS 26 has software component updates and new features that are in the polishing phase. See 26 Major Features for an overview of what’s new in this release.

Upgrading from TrueNAS 25.10 to 26-BETA.1 is not available in the TrueNAS UI until TrueNAS 25.10.3 is released. Users on TrueNAS 25.10 who wish to test 26-BETA.1 before that time can manually install or upgrade by downloading directly:

• TrueNAS-26.0.0-BETA.1.iso
• TrueNAS-26.0.0-BETA.1.update

Special thanks to (GitHub users): Franco Castillo, AquariusStar, Rogelio Tajes Piñeiro, Aurélien Sallé, dany22m, ReiKirishima, Christos Longros, Lee Jihaeng, Aui162, Seele Volleri, Ban, Michael Rohrhirsch, PCAsusM1981, Cantabile, Fernando G. Monteiro, Joda Stößer, Marius, herbkk, saso-g1, René, Jehu Marcos Herrera Puentes, Amir Burbea, Piotr Jasiek, Eric Schultz, Kent Ross, fkwp, Gautam krishna R and Joel May for contributing to TrueNAS 26-BETA.1. Visit our guide for information on how you too can contribute.

• Adds support for LXC containers in Enterprise High Availability (HA) configurations (NAS-138309). Containers can now fail over between HA controllers. HA container failover requires a static IP configuration. See Containers for configuration details.

• Adds GPU passthrough support for LXC containers (NAS-138569, NAS-138570, NAS-138700). Users can assign NVIDIA and other supported GPU devices to LXC containers from the container configuration screen in the UI.

• Adds Multi-Path I/O (MPIO) support for Fibre Channel connections (NAS-137252). Fibre Channel configurations can now use multiple paths for improved redundancy and throughput. This option is available in the Fibre Channel port configuration.

• Adds SMB3 unix extensions support for multiprotocol shares (NAS-139988). When a share uses the Multi-Protocol purpose (for example, SMB combined with NFS or local app and container access), TrueNAS now enables SMB3 unix extensions. Linux clients with SMB3 POSIX support can use filesystem primitives not normally available through standard SMB semantics. Windows clients without unix extension support continue to behave normally.

• Adds BRT (Block Reference Table) support to the zpool prefetch command for faster pool import operations (NAS-139230). Pool imports on systems that use block cloning are now faster, as the prefetch operation includes BRT metadata.

• Adds an option to de-register a system from TrueNAS Connect (NAS-139544). Users can now remove a system’s TrueNAS Connect registration from the TrueNAS Connect configuration screen without needing to contact support.

• Adds support for the include: key in custom app Docker Compose configurations (NAS-137498). Custom app Compose files can now reference external Compose files that define services, allowing users who manage their own Docker Compose files outside TrueNAS to use modular configurations.

• Updates the Pools and storage screens to reflect OpenZFS 2.4 changes, including the new separation of special and dedup vdev types (NAS-138129). Pool creation and management dialogs now correctly represent the new vdev types available in OpenZFS 2.4.

• Improves the Storage Dashboard to show the reason a pool is degraded (NAS-138613). Previously, a degraded pool indicator offered no detail on the cause. The dashboard now provides context so users can take corrective action.

• Updates the Samba build to version 4.23 (NAS-139190). See the Samba 4.23.0 release notes for upstream changes. Note that changes to Samba defaults do not necessarily change TrueNAS defaults. See Software Component Versions for all component version updates in this release.

• Improves touch and mobile usability for side panels and configuration screens (NAS-139925, NAS-139786, NAS-138896). Side panels now scroll correctly in mobile browsers, canvas edge spacing is improved for touch targets, and the Save button on the Add Rsync Task screen is no longer hidden on small screens.

• Fixes TrueNAS updates failing with errors that could leave apps non-functional or set a broken boot environment as default (NAS-139794, NAS-139545). A “pool or dataset is busy” error during updates could set an incomplete boot environment as default. A separate regression also caused apps to fail to start after updating. Both issues are resolved.

• Fixes the System > Services screen showing as empty (NAS-139571). A regression could cause the services list to appear blank on affected systems, preventing users from starting, stopping, or configuring services from the UI.

• Fixes an issue where datasets could not be loaded in the UI (NAS-140389). A middleware issue could prevent dataset information from loading on the Datasets screen, showing an error instead of the dataset tree.

• Fixes available space calculations for pools with special or dedup vdevs (NAS-139820). Incorrect accounting could cause available space to display inaccurate values on pools using special allocation or dedup vdevs.

• Fixes an issue where virtual DRAID devices appeared as physical disks in the disk inventory (NAS-140344). On pools using DRAID vdevs, virtual devices could be incorrectly counted alongside physical drives, causing inaccurate disk inventory results.

• Fixes datasets becoming unavailable after a ZFS send replication operation (NAS-139363). A ZFS issue could cause target datasets to enter an unavailable state after a send operation completed. Datasets are now accessible immediately after replication finishes.

• Fixes a boot delay of up to 120 seconds on systems with VLAN interfaces configured for DHCP (NAS-139038). Systems using VLAN interfaces with DHCP experienced long waits during boot due to a dhcpcd configuration issue. Boot now completes without the delay.

• Fixes an error that prevented setting secondary IP address aliases on network interfaces (NAS-139803). A KeyError: 'alias_interface_id' error could occur when saving secondary aliases in the network interface configuration.

• Fixes the Samba Spotlight metadata service connection so that macOS Spotlight search works correctly on SMB shares (NAS-137715). The Spotlight AF_UNIX socket connection was established as a non-privileged user, causing authentication failures. The connection now runs with the correct permissions.

• Fixes an error that prevented editing share ACLs (NAS-139535). Users attempting to modify permissions on SMB or NFS shares through the ACL editor could receive errors and be unable to save changes.

• Fixes NFS shares showing no available actions in the Shares screen (NAS-139490). The action buttons for NFS shares could fail to render correctly, preventing users from editing or deleting NFS shares from the UI.

• Fixes an error that prevented updating an iSCSI auth method when Mutual CHAP was selected (NAS-139397). Users could not save changes to iSCSI authorized access entries with Mutual CHAP configured.

• Fixes USB and PCIe device passthrough to virtual machines (NAS-139045, NAS-139356). A regression in an earlier nightly build broke the ability to pass USB and PCIe devices through to VMs. Both USB and PCIe passthrough are restored in BETA.1.

• Fixes Rsync task setup failures related to remote path validation and host key verification (NAS-139773). Remote path validation could incorrectly reject valid paths, and host key verification could fail even after accepting the key. Both issues are resolved.

• Fixes SNMP alerts that stopped sending notifications (NAS-140259). A regression could cause SNMP alert notifications to fail silently on affected systems. SNMP monitoring integrations relying on TrueNAS alerts now receive notifications correctly.

• Fixes the CPU reporting chart to show both per-core and total CPU usage (NAS-135633). The Reporting screen previously only showed aggregated CPU usage. Users can now view individual core utilization alongside the total.

• Fixes UI regressions introduced by an Angular framework upgrade, including session logouts on page refresh in Firefox and broken tooltips across multiple screens (NAS-139491, NAS-139342). Firefox users were logged out unexpectedly on page refresh, and tooltips and contextual popovers stopped working throughout the interface. Both issues are resolved.

• Fixes the TrueNAS web UI preventing NVIDIA driver removal when the GPU has already been uninstalled (NAS-137282). When an NVIDIA GPU was physically removed, the UI did not allow removing the associated driver package. The driver can now be removed independently of hardware presence.

Click here to see the full 26 changelog or visit the TrueNAS 26-BETA.1 Changelog in Jira.

These are ongoing issues that can affect multiple versions in the 26 series.
When resolved, issues move to Notable Changes for the appropriate release.

• The Backup Tasks dashboard card does not display TrueCloud Backup or Periodic Snapshot tasks, even when those tasks are configured and have completed successfully. The tasks run normally and appear as expected on the Data Protection screen; only the dashboard card omits them. Other task types, such as Replication and Cloud Sync, appear on the card as expected.
• Upgrading to TrueNAS 26 can disrupt two-factor authentication (2FA) for any account with a stored token interval other than 30 or 60 seconds. TrueNAS 26 supports only these two intervals and clears the stored 2FA secret for any affected account during the upgrade. A non-standard interval can come from the API, or from the global 2FA interval setting in TrueNAS releases before 24.04, which applied a single interval to every 2FA account on the system and persists across upgrades. The current web interface always uses a 30-second interval. See Two-Factor Authentication for who is affected and how to restore access.

See the latest status on Jira for public issues discovered in TrueNAS 26 that are being resolved in a future TrueNAS release.

See the Release Notes section of the TrueNAS forum for ongoing updates about known issues, investigations, and statistics about TrueNAS releases.

For additional resources, see the Feature Deprecations page.

• The TrueNAS REST API is removed in TrueNAS 26. Systems still using the REST API must migrate to the JSON-RPC 2.0 WebSocket API before upgrading. See API Changes for migration guidance and details about API authentication improvements in TrueNAS 26.

You can access TrueNAS API documentation in the web interface by clicking laptop My API Keys on the top right toolbar account_circle user settings dropdown menu to open the User API Keys screen. Click API Docs to view API documentation.

TrueNAS 26 introduces auth.login_ex as a unified WebSocket API authentication method that supports password (PASSWORD_PLAIN), API key (API_KEY_PLAIN), OTP token (OTP_TOKEN), and the new SCRAM-SHA-512 (SCRAM) mechanism. SCRAM provides mutual authentication between client and server without transmitting raw key material.

The legacy auth.login and auth.login_with_api_key methods are deprecated and scheduled for removal in TrueNAS 27. Their functionality is fully replaced by auth.login_ex, which continues to support API_KEY_PLAIN and the other non-SCRAM mechanisms beyond TrueNAS 27. SCRAM is the recommended choice for new clients that can adopt it.

See the SCRAM Authentication primer for guidance on implementing SCRAM in custom API clients and migrating pre-TrueNAS 26 API keys to the optimized precomputed format.

For the full list of deprecated and removed API methods, see Feature Deprecations.

TrueNAS 26 restricts the two-factor authentication (2FA) token interval to 30 or 60 seconds. TrueNAS 26 validates Time-based One-Time Password (TOTP) login codes and accepts only these two intervals.

A non-standard interval could have been set through the API, or through the global 2FA setting in TrueNAS releases before 24.04, where the web interface exposed an editable interval field that applied a single value to every 2FA account on the system. That value persists across upgrades. The current web interface always sets a 30-second interval and no longer exposes this field, so 2FA configured through the UI on TrueNAS 24.04 or later uses the supported 30-second interval. A non-standard interval worked for web interface logins in earlier releases but stops working after upgrading to TrueNAS 26. Both local accounts and directory services (Active Directory or LDAP) accounts are in scope.

During the upgrade, TrueNAS clears the stored 2FA secret and resets the interval to 30 for any affected account. That account has no working 2FA until the user sets up 2FA again.

To avoid any interruption, affected users re-enroll before upgrading. Go to Credentials > Two Factor Auth, click Renew 2FA Secret, then scan the new QR code with an authenticator app. The renewed secret uses the default 30-second interval. If you are not sure whether an account is affected, renew the 2FA secret for that account anyway. A renewal is safe for accounts that are not affected.

To restore 2FA for an affected account after upgrading:

• On standard systems, where 2FA is not required to log in, the user signs in with their password, then re-enrolls 2FA at Credentials > Two Factor Auth.

• On systems that require 2FA to log in (for example, STIG mode), an administrator issues a one-time password for the affected user. An administrator who can still sign in generates it at Credentials > Users: select the affected user, then click Generate One-Time Password on the Password widget. If every administrator is locked out, an administrator with console access generates it from the console:

  midclt call auth.generate_onetime_password '{"username": "account-name"}'

  Replace account-name with the name of the affected user account. The command returns a one-time password (for example, 1_nIaCpK-OhJPNQ-I6BfKr-29CyQB). The user enters it in place of their password at the login screen, then reconfigures 2FA at Credentials > Two Factor Auth.

LXC containers, introduced as an experimental feature in earlier TrueNAS releases, are fully supported in TrueNAS 26. Containers running in TrueNAS 25.10 migrate automatically to TrueNAS 26, except on TrueNAS Enterprise High Availability (HA) systems and Enterprise systems without the Apps license feature enabled. Contact TrueNAS Enterprise Support if you have containers on one of these systems.

TrueNAS 26 adds the following container improvements:

• Enterprise HA support — Containers can now fail over between HA controllers (NAS-138309). HA container failover requires a static IP configuration. Containers using DHCP do not fail over.
• GPU passthrough — NVIDIA and other supported GPU devices can now be assigned to LXC containers from the container configuration screen (NAS-138569, NAS-138570, NAS-138700).
• USB and PCIe passthrough fixes — A regression that prevented USB and PCIe device passthrough to containers and VMs is resolved in BETA.1 (NAS-139045, NAS-139356).

See Containers for configuration details.

Legacy virtual machines from the Instances screen, still shown on the Containers screen in TrueNAS 25.10, are not automatically migrated to TrueNAS 26. No migration tool, wizard, or notification exists for these VMs. TrueNAS does not preserve the VM configuration, UEFI variables, or Trusted Platform Module (TPM) state. The VM disk remains on the pool.

Before upgrading, record each VM configuration and back up the VM disk while still running TrueNAS 25.10. See Preparing to Upgrade to TrueNAS 26 in the TrueNAS 25.10 documentation.

After upgrading, see Migrating Legacy VMs to Virtual Machines to re-create the VM and reattach the VM disk.

TrueNAS monitors the condition of installed HDD and SSD drives (SAS, SATA, and NVMe) through three integrated layers:

• ZFS detects sudden failures in real time during active read and write operations and marks affected vdevs or disks as faulted immediately.
• TrueNAS Middleware polls SMART data from every drive every 90 minutes. When a polled attribute crosses a failure threshold, TrueNAS generates an alert.
• Alert logic filters incoming SMART and ZFS data to suppress known-benign attribute fluctuations, reducing false-positive alerts by approximately 50% compared to prior releases.

Drive health status is visible on the Disk Health card on the Storage dashboard. Active alerts appear in the Alerts panel with details on the affected disk and recommended next steps.

Community Edition users can supplement automated monitoring with manual SMART tests run via cron jobs or the smartctl command-line tool. Third-party tools such as Scrutiny are also available from the TrueNAS Apps catalog.

See Drive Health Management for full details.

Depending on the specific system configuration, migrating from a FreeBSD-based TrueNAS version can be a straightforward or complicated process. See the Migration articles for cautions and notes about differences between each software and the migration process.

TrueNAS Enterprise

TrueNAS Enterprise customers with High Availability (HA) or Non-HA TrueNAS Hardware should consult with TrueNAS Enterprise Support for assistance before attempting to migrate.

Customers who purchase TrueNAS hardware or that want additional support must have a support contract to use TrueNAS Support Services. The TrueNAS Community forums provides free support for users without a TrueNAS Support contract.

TrueNAS Customer Support
Support Portal	https://support.ixsystems.com
Email	support@ixsystems.com
Telephone and Other Resources	https://www.ixsystems.com/support/

Click the component version number to see release notes for that component.

*TrueNAS (25.10 and later) includes the NVIDIA open GPU kernel module drivers. These drivers work with Turing and later GPUs. Earlier architectures (Pascal, Maxwell, Volta) are not compatible. See NVIDIA GPU Support for more information.

TrueNAS integrates many features provided by the upstream OpenZFS project. Any new feature flags introduced since the previous OpenZFS version that was integrated into TrueNAS (OpenZFS 2.3.3) are listed below:

For more details on feature flags, see OpenZFS Feature Flags and OpenZFS zpool-feature.7.