25.10 (Goldeye) Version Notes

July 23, 2026

The TrueNAS team is pleased to release TrueNAS 25.10.5! This release updates the Linux kernel to address local privilege escalation and other security vulnerabilities. It also fixes a console memory leak, incorrect drive health data, stalled TrueCloud Backup jobs, SSH key handling for replication and cloud credentials, alert email delivery, and share ACL edits.

Notable changes:

• Updates the Linux kernel to the latest 6.12 LTS release (v6.12.95) (NAS-141384, NAS-141588, NAS-141696). TrueNAS 25.10.5 advances the kernel from the previous release through v6.12.93, v6.12.94, and v6.12.95. This update mitigates several kernel vulnerabilities, including the SharedFrag local privilege escalation (CVE-2026-43503) and the PeditCOW local privilege escalation (CVE-2026-46331). The v6.12.95 update adds further high-severity upstream fixes, including an out-of-bounds read in the rxrpc ACK parser (CVE-2026-53151), use-after-free issues in network bonding (CVE-2026-31419 and CVE-2026-52975), a use-after-free in eventpoll (CVE-2026-46242), an IPv6 tunnel network namespace issue (CVE-2026-52909), an SCTP UDP-tunnel handling fix (CVE-2026-53070), and a SELinux overlayfs access-check bypass (CVE-2026-46054), along with additional upstream security and stability fixes.

• Fixes a memory leak in the console CLI process that could cause system-wide out-of-memory crashes (NAS-141238). The CLI process running on the system console (getty@tty1) could leak a large amount of memory over time, eventually exhausting system RAM and triggering out-of-memory (OOM) kills that affected other processes. The leak is fixed so the console CLI no longer consumes excess memory.

• Fixes faulty parsing of smartctl output that could produce incorrect drive health information (NAS-141215). TrueNAS could misread the output of the smartctl utility when collecting SMART data from drives, which could lead to inaccurate disk health reporting. The parsing logic is corrected so SMART attributes are read reliably.

• Fixes TrueCloud Backup jobs that could hang indefinitely and hide restic error messages (NAS-141287). A KeyError while reading restic progress output caused TrueCloud Backup to discard all restic error messages, so failing jobs could appear stuck with no explanation. TrueNAS now handles the progress output correctly and surfaces the underlying restic errors.

• Fixes several SSH key handling issues affecting remote replication and cloud credentials (NAS-141677). Removing an SSH key pair now correctly updates SFTP cloud credentials that used that key. Encrypted SSH private keys are rejected more consistently during validation, and remote SSH semi-automatic setup returns a clear error when the selected key pair is missing or invalid. SSH pairing with TrueNAS 13 systems during remote replication setup now works correctly.

• Fixes alert emails that were not RFC 5322 compliant and could be rejected by mail providers (NAS-141699). Alert notification emails did not conform to RFC 5322, so some providers such as Gmail bounced them and administrators did not receive the alerts. TrueNAS now generates compliant messages so alert emails are delivered reliably.

• Fixes an issue that prevented editing a share ACL (NAS-139535). Attempts to edit the ACL on a share could fail, which blocked permission changes. Editing share ACLs now works as expected.

Click here to see the full 25.10 changelog or visit the TrueNAS 25.10.5 (Goldeye) Changelog in Jira.

June 3, 2026

The TrueNAS team is pleased to release TrueNAS 25.10.4! This release updates the Linux kernel and Samba to address multiple security vulnerabilities, and includes data integrity, NFS, iSCSI, networking, and Active Directory fixes.

Notable changes:

• Updates the Linux kernel to the latest 6.12 LTS release (v6.12.91). This update mitigates several kernel vulnerabilities, including the Dirty-Frag local privilege escalation (CVE-2026-43284 and CVE-2026-43500), the CIFSwitch local privilege escalation in the CIFS client (CVE-2026-46243), a ptrace privilege issue (CVE-2026-46333), and the related Fragnesia privilege escalation in the ESP-in-TCP path (CVE-2026-46300). It also enables additional CPU side-channel mitigations.

• Updates Samba to version 4.22.10 to address multiple security vulnerabilities. This Samba maintenance release resolves several CVEs, including a missing access check that let read-only users set or delete reparse point attributes (CVE-2026-1933) and a flaw in the WORM (Write Once, Read Many) module that allowed protected files to be overwritten by renaming a new file over them (CVE-2026-2340). See the Samba 2026 security release impact statement for the TrueNAS-specific impact assessment, or the Samba 4.22.10 release notes for the complete upstream list.

• Fixes a potential double free when freeing blocks cloned after deduplication table pruning. Blocks created through block cloning could be freed more than once if their deduplication table (DDT) entries had already been pruned, because the free path did not check the block reference table (BRT) first.

• Fixes virtual machines stored on NFSv4.1 datasets failing to power on. A change introduced in 25.10.2.1 could cause the NFSv4 change cookie to move backward after a file left the cache due to memory pressure, a remount, or a reboot. NFSv4.1 clients that depend on a monotonic change cookie, notably VMware ESXi, rejected the affected files. A virtual machine stored on an NFSv4.1-exported ZFS dataset then failed to power on with the error “The file specified is not a virtual disk.” This release reverts that change while a complete fix is finalized upstream.

• Fixes a kernel crash in the iSCSI target layer during SCSI bus or LUN resets. A use-after-free in the clustered locking path of the iSCSI target could crash the system during a SCSI reset, most often on Enterprise High Availability (HA) systems while a peer controller was leaving the cluster. The target layer now waits for lock teardown to complete before releasing the associated memory.

• Improves iSCSI LUN replacement during High Availability failover. On Enterprise HA systems, cleanup of a replaced LUN could stall during failover while a peer controller was being evicted from the cluster, which blocked later LUN replacements. Cleanup is now held until the cluster coordination it depends on has finished.

• Fixes a validation error that blocked static network configuration on some High Availability systems. On HA-capable systems, saving a static network configuration could incorrectly fail with “Enabling DHCPv4/v6 on HA systems is unsupported” even when DHCP was not being enabled. This affected fresh installs before any interface had a saved configuration. The check now triggers only when DHCP or IPv6 autoconfiguration is explicitly enabled.

• Improves Active Directory rejoin, reset, and recovery handling. This release hardens the Active Directory rejoin and directory services reset operations, improves domain controller selection on systems with more than one available controller, and produces clearer diagnostics when a join or authentication problem occurs.

• Fixes ZFS automatic snapshots not being created after a Time Machine backup until the Mac reconnects. When a Time Machine SMB share has automatic snapshots enabled, recent macOS versions (Tahoe and later) sometimes keep the SMB session open after a backup completes instead of disconnecting, which prevented the post-backup ZFS snapshot from being taken until the client reconnected or restarted. The snapshot logic is updated to handle these persistent Time Machine sessions.

• Reduces excessive winbind log messages for failed user and group lookups. When Active Directory is enabled, looking up a user or group that does not exist (for example through getpwnam or getgrnam) generated a warning for every failed lookup, which could rapidly fill the winbind log. These messages are now logged at informational level instead of as warnings.

Click here to see the full 25.10 changelog or visit the TrueNAS 25.10.4 (Goldeye) Changelog in Jira.

April 14, 2026

The TrueNAS team is pleased to release TrueNAS 25.10.3!

Notable changes:

• Fixes read authentication errors caused by block cloning between encrypted ZVOLs with different encryption keys (NAS-140263). Block cloning between encrypted ZVOLs that did not share compatible encryption keys was allowed, but subsequent reads of the cloned data produced authentication failures. TrueNAS now verifies that encryption keys match before allowing a block clone operation to proceed.

• Fixes Active Directory users and groups not found when using the idmap_ad backend with RFC2307 (NAS-140077). The idmap_ad backend failed when smb.conf was configured to disallow a private krb5.conf, preventing Active Directory users and groups from being resolved. Shares and services that depend on directory service identities were inaccessible on affected systems.

• Fixes pool creation errors on systems with a USB boot drive or other disk with a duplicate serial number (NAS-139947). The disk availability check incorrectly blocked pool creation if any disk on the system had a duplicate serial number, even when that disk was unrelated to the new pool. USB boot drives commonly have blank or duplicate serial numbers and were the most frequent cause. Note that TrueNAS does not recommend USB boot devices. Installing on SATA, SAS, or NVMe flash media is recommended.

• Fixes issues with log VDEV removal (NAS-140080). Resolves errors that could occur when removing a log VDEV from a storage pool. Affected systems encountered failures during the log VDEV removal process.

• Fixes link aggregation failover not working out of the box (NAS-136978). Resolves an issue where the MII polling interval was not correctly configured for bonding interfaces using the FAILOVER protocol. The bonding driver could not monitor slave link status, causing failover to fail silently when an interface lost carrier.

• Fixes Netlink socket errors that caused network interface operations to fail (NAS-140041). Concurrent netlink route operations could collide at the kernel level, producing “Netlink socket busy” (EBUSY) errors. This was most visible as bond status alert failures. The fix serializes netlink route operations to prevent collisions, increases the retry limit, and adds a short delay between retries to reduce the chance of repeated failures.

• Fixes NTB transport memory allocation failures during link state changes (NAS-139627). Non-Transparent Bridge (NTB) transport memory windows were allocated and freed on every link up/down event. Allocating several megabytes of physically contiguous memory on a running system could fail, causing instability. Memory windows are now pre-allocated at boot, avoiding repeated allocation attempts during link changes. This primarily affects TrueNAS Enterprise High Availability (HA) systems.

• Fixes stale NFS file handles for ZFS snapshots that could not be recovered without a client reboot (NAS-140474). When mountd failed to resolve a snapshot’s filesystem ID — such as after failover, snapshot expiration, or an automount failure — it permanently cached a negative response, causing all subsequent file handle lookups to return ESTALE errors. Client-side remounts did not clear the cached state. The fix replaces the permanent negative cache with a 120-second retry window, allowing recovery once the snapshot becomes accessible again.

• Documentation improvement: Adds Drive Health Management documentation covering how TrueNAS 25.10 monitors drive health through ZFS real-time failure detection, automated 90-minute SMART polling, and improved alert filtering. Also covers manual SMART test scheduling options available to TrueNAS Community Edition users. See the Drive Health Management tutorial for full details.

Click here to see the full 25.10 changelog or visit the TrueNAS 25.10.3 (Goldeye) Changelog in Jira.

February 19, 2026

The TrueNAS team is pleased to release TrueNAS 25.10.2!

Notable changes:

• Fixes critical upgrade failure affecting some systems upgrading from TrueNAS 25.04 to 25.10 (NAS-139541). Resolves “Could not prepare Boot variable: No space left on device” error that caused affected systems to become unbootable after failed upgrade attempts.
• Fixes SMB service startup failure after upgrading from older TrueNAS versions with legacy ACL configurations (NAS-139076). Systems with legacy SMB share permission strings stored in their configuration database could not start the SMB service after upgrading to 25.10.1. This update automatically converts legacy permission formats to the current binary format during service initialization.
• Improves NFS performance for NFSv4 clients (NAS-139128). This item was included in the 25.10.2 release notes in a clerical error. This improvement is included in TrueNAS 25.10.2.1.
• Improves ZFS pool import performance and write operation responsiveness (NAS-138879). Limits the time async destroy operations can run per transaction group, preventing these operations from blocking pool imports and other write operations. Pool imports that previously took extended time due to prolonged async destroy operations complete more quickly.
• Fixes disk replacement validation incorrectly rejecting identical capacity drives (NAS-138678). Resolves “device is too small” error when attempting to replace failed drives with identical capacity models. The system now correctly validates replacement drive capacity and allows legitimate disk replacements to proceed.
• Reduces excessive API calls during user and group selection in the web interface (NAS-139459). Implements longer debounce period for autocomplete fields to prevent the system from making API requests for every keystroke. This reduces system load and eliminates logs filled with failed requests during routine typing.
• Reduces background CPU usage when running containerized applications (NAS-139089). Optimizes YAML processing and Docker stats collection to reduce asyncio_loop CPU usage caused by repeated container inspection operations holding the Global Interpreter Lock.
• Fixes Dashboard storage widget displaying “Unknown” for used and free space (NAS-138705). Resolves issue where secondary storage pools showed no capacity metrics in the Dashboard widget, preventing visibility into actual storage usage and availability.
• Fixes network configuration lockout caused by invalid IPv6 routes (NAS-139575). Resolves issue where unusual IPv6 route entries in the routing table prevented access to network settings, app management, and bug reporting. The system now gracefully handles invalid route entries instead of becoming unresponsive.
• Fixes network bridge creation validation errors (NAS-139196). Resolves Pydantic validation failures that prevented users from creating network bridges through the standard workflow of removing IPs from an interface, creating a bridge, and reassigning those IPs.
• Adds Hosts Allow and Hosts Deny network access controls to SMB shares (NAS-138814). Provides IP-based access restrictions for SMB shares across all relevant purpose presets. Also adds ability to synchronize Kerberos keytab Service Principal Names (SPNs) with Active Directory updates for improved multiprotocol share management.
• Fixes IPv6 address formatting in Kerberos configuration for Active Directory (NAS-139734). Resolves Active Directory authentication failures when using IPv6 addresses for Kerberos Distribution Centers (KDCs). The system now properly formats IPv6 addresses with square brackets in krb5.conf, preventing “Invalid argument while getting initial credentials” errors.
• Improves Users page default filter to include Directory Services users (NAS-139073). Directory Services users now appear in the default view without requiring manual filter adjustment. This improves discoverability of directory service accounts in the user management interface.
• Fixes SSH access removal for user accounts (NAS-139130). Resolves issue where clearing the SSH Access option appeared to save without error, but the SSH indicator persisted in the user list. Users can now properly disable SSH access through the web interface.
• Fixes session expiry settings not being respected (NAS-138467). Resolves issues where users were logged out unexpectedly during active operations despite configured session timeout settings, and where page refresh (F5) triggered the login screen despite an active session. Session expiration now functions as configured.
• Fixes certificate management for certificates with large Distinguished Names (NAS-139056). Certificates with DNs exceeding 1024 characters (typically those with many Subject Alternative Names) can now be properly imported and managed. Previously, these certificates would upload successfully but fail during subsequent listing operations.
• Fixes Cloud Sync tasks becoming invisible after upgrading from TrueNAS CORE to SCALE (NAS-138886). Resolves data inconsistency where the bwlimit field contained empty objects instead of empty arrays, preventing the UI from displaying cloud sync tasks. Tasks remained functional via command-line but were not visible in the web interface.
• Improves S3 endpoint URI validation for Cloud Sync tasks (NAS-138903). Adds upfront validation to ensure S3 endpoints include the required https:// protocol prefix. Previously, omitting the protocol resulted in an unhelpful “Invalid endpoint” error. The system now provides clearer guidance during configuration.
• Fixes iSCSI extent wizard hanging when adding second extent to a target (NAS-138856). Resolves issue where an unsaved changes popup appeared unexpectedly after saving, followed by duplicate item errors. The wizard pane now closes automatically as expected, though the extent is added successfully despite the confusing error messages.
• Fixes error notifications displaying placeholder text (NAS-139010). Resolves formatting bug where error notifications showed “%(err)s Warning” instead of descriptive error messages.
• Improves error dialog usability for long error messages (NAS-138424). Adds proper scrolling to error dialogs with lengthy content. Previously, users had to zoom out to 50% to see action buttons when error messages (such as those listing numerous dependent clones) extended beyond the visible area.
• Restricts root account group membership to preserve system stability. The system now locks root account group membership to the builtin_administrators group and prevents modification through the UI. This prevents accidental removal of required privileges that could cause scheduled tasks, cloud sync operations, cron jobs, and other system functions to fail. To disable root account access to the TrueNAS UI, use the Disable Password option in Credentials > Local Users instead of modifying group membership.

Click here to see the full 25.10 changelog or visit the TrueNAS 25.10.2 (Goldeye) Changelog in Jira.

December 18, 2025

The TrueNAS team is pleased to release TrueNAS 25.10.1!

Notable changes:

• Fixes issue where storage pools appeared offline after upgrading to 25.10.0 (NAS-138236). Affected systems experienced temporarily missing VDEVs that required a system reboot to restore pool access.
• Adds Final Cut Pro Storage Share purpose preset for SMB shares (NAS-138402). Provides optimized configuration for Final Cut Pro workflows. See Setting Up Final Cut Pro SMB Shares for more information.
• Adds automatic validation for SMB share audit logging configurations. TrueNAS 25.10.1 automatically disables SMB shares when auditing is enabled and watch or ignore lists contain invalid groups (deleted/renamed groups or groups that are no longer SMB-type). This protective measure prevents auditing misconfigurations that could cause security or compliance issues. The system generates alerts identifying affected shares and problematic groups. See Configuring SMB Auditing for configuration details and troubleshooting steps.
• Adds REST API usage monitoring alert. TrueNAS now displays a daily alert when deprecated REST API endpoints are accessed, helping identify integrations that need migration. TrueNAS deprecated the REST API in version 25.04. Full removal is planned for TrueNAS 26. For more information about the JSON-RPC 2.0 over WebSocket API, see the API documentation.
• Adds Clear Config button to the directory services configuration form. This button allows users to easily remove existing directory service configurations. This is useful for troubleshooting, reconfiguration, or switching between directory service types.
• Updates Samba from 4.22.5 to 4.22.6 (NAS-138644). Includes upstream fix for Time Machine backup failures on newer macOS versions. Resolves an issue where Time Machine backups failed on macOS 15.2 (Tahoe) and later due to a Samba 4.22 behavioral change affecting directory rename operations for open files. TrueNAS 25.04 releases are unaffected.
• Fixes Windows 11 virtual machine Trusted Platform Module (TPM) persistence (NAS-138165). Resolves issue where BitLocker PINs and other TPM data reset after every VM restart. Users need to reset their PIN after upgrading, after which persistence functions normally.
• Fixes Secure Boot for virtual machines (NAS-137898). Resolves issue where VMs with Secure Boot enabled failed to boot signed operating systems like Windows 11 due to missing Microsoft keys in OVMF firmware.
• Fixes VM image file upload default location (NAS-138502). Prevents ISO files from being saved to the boot drive /mnt folder when users do not change the default upload location during VM image upload.
• Fixes VDI disk import for virtual machines (NAS-137897). Resolves errors when creating VMs using .vdi disk images.
• Improves error handling for legacy FreeNAS dataset properties (NAS-138629). Users can encounter "aclmode: failed to get property" errors when editing datasets on long-running systems that contain invalid aclmode=discard_chmod property values from legacy FreeNAS versions. This update improves error messaging to help identify affected datasets. If you encounter this error, run zfs set aclmode=passthrough dataset_name via CLI to reset the property to a valid value, then reboot the system.
• Improves error messaging for pool operations (NAS-138330). Provides clearer error messages when attempting to extend VDEVs or replace disks fails due to ZFS checkpoints or other conditions.
• Fixes rsync tasks using SSH keychain credentials (NAS-138334). Resolves UnboundLocalError that prevented saving or running SSH-based rsync tasks after upgrading to 25.10.0.
• Improves replication error messages (NAS-138202). Provides clearer error messages when replication tasks fail due to interrupted SSH connections or network issues.
• Fixes email sending error after upgrading to 25.10.0 (NAS-138270). Resolves 'str' object has no attribute 'decode' error when attempting to send test emails or system notifications.
• Restores HDD temperature data via SNMP (NAS-138433). Resolves issue where SNMP queries for disk temperature (OID .1.3.6.1.4.1.50536.3) returned no data after upgrading to 25.10.0.
• Fixes issue disabling SSH and Shell access for user accounts (NAS-138307). The Save button no longer disables when clearing these access options.

Click here to see the full 25.10 changelog or visit the TrueNAS 25.10.1 (Goldeye) Changelog in Jira.

October 28, 2025

The TrueNAS team is pleased to release TrueNAS 25.10.0!

Special thanks to (Github users): Aurélien Sallé, ReiKirishima, AquariusStar, RedstoneSpeaker, Lee Jihaeng, Marcos Ribeiro, Christos Longros, dany22m, Aindriú Mac Giolla Eoin, William Li, Franco Castillo, MAURICIO S BASTOS, TeCHiScy, Chen Zhaochang, Helak, dedebenui, Henry Essinghigh, Sophist, Piotr Jasiek, David Sison, Emmanuel Ferdman and zrk02 for contributing to TrueNAS 25.10. For information on how you can contribute, visit https://www.truenas.com/docs/contributing/.

New Features:

• NVMe over Fabric: TCP support (Community Edition) and RDMA (Enterprise) for high-performance storage networking with 400GbE support.
• Virtual Machines: Secure Boot support, disk import/export (QCOW2, RAW, VDI, VHDX, VMDK), and Enterprise HA failover support.
• Update Profiles: Risk-tolerance based update notification system.
• Apps: Automatic pool migration and external container registry mirror support.
• Enhanced Users Interface: Streamlined user management and improved account information display.

Performance and Stability:

• ZFS: Critical fixes for encrypted snapshot replication, Direct I/O support, improved memory pressure handling, and enhanced I/O scaling.
• VM Memory: Resolved ZFS ARC memory management conflicts preventing out-of-memory crashes.
• Network: 400GbE interface support and improved DHCP-to-static configuration transitions.

UI/UX Improvements:

• Redesigned Updates, Users, Datasets, and Storage Dashboard screens.
• Improved password manager compatibility.

Breaking Changes Requiring Action:

• NVIDIA GPU Drivers:
  • TrueNAS 25.10 switches to open GPU kernel drivers supporting Turing and newer (RTX/GTX 16-series+). Pascal, Maxwell, and Volta architectures are no longer supported. See NVIDIA GPU Support for compatibility details.
• Active Directory IDMAP:
  • The Active Directory AUTORID IDMAP backend is removed and auto-migrated to RID to improve consistency across multi-server environments. Users should review their ACLs and permissions after upgrade and might need to reconfigure them in some edge cases.
• Certificate Management:
  • 25.10 removes the Certificate Authority (CA) functionality that allowed TrueNAS to create and sign certificates. Users can continue to manage certificates by creating Certificate Signing Requests (CSRs) to be signed by external certificate authorities or and importing certificates that have been signed by external CAs or directory services. These alternatives provide the certificate management capabilities most users need while ensuring proper certificate validation through established certificate authorities.
• SMART Monitoring:

  • 25.10 removes the built-in SMART test scheduling and monitoring interface. TrueNAS continues automated drive health monitoring through middleware-integrated SMART polling and ZFS failure detection. Existing scheduled SMART tests are automatically migrated to cron tasks during upgrade, and smartmontools binaries remain installed.

    See Drive Health Management for more information on disk health monitoring in 25.10 and beyond.

• SMB Shares:

  • In 25.10, SMB share configuration only displays options relevant to each purpose-based preset. Existing shares that previously used the No Preset option are automatically migrated to the Legacy Share preset during upgrade. New shares cannot access legacy configuration options.

    Legacy Share options include enabling SMB guest access, the SMB recycle bin, home directory export, AFP compatibility shares, and disabling shadow copies. The SMB recycle bin feature is no longer available for new shares due to security and usability concerns. For file recovery and versioning, use ZFS snapshots, which provide more reliable and predictable data protection. For more information, see Legacy Share Settings and the TrueNAS API documentation sharing.smb.create return values for options LegacyOpt.

• Virtual Machine Startup Changes:
  • VMs created in TrueNAS 25.04 (pre-25.04.2) and displayed on the Containers screen no longer automatically start on system boot to prevent conflicts with VMs on the Virtual Machines screen. See Containers and Virtual Machines for more information.

See the 25.10 Major Features and Full Changelog for more information.

Notable changes since 25.10-RC.1:

• Samba version updated from 4.21.7 to 4.21.9 for security fixes (4.21.8 Release Notes | 4.21.9 Release Notes)
• Improves ZFS property handling during dataset replication (NAS-137818). Resolves issue where the storage page temporarily displayed errors when receiving active replications due to ZFS properties being unavailable while datasets were in an inconsistent state.
• Fixes “Failed to load datasets” error on Datasets page (NAS-138034). Resolves issue where directories with ZFS-incompatible characters (such as [) caused the Datasets page to fail by gracefully handling EZFS_INVALIDNAME errors.
• Fixes zvol editing and resizing failures (NAS-137861). Resolves validation error “inherit_encryption: Extra inputs are not permitted” when attempting to edit or resize VM zvols through the Datasets interface.
• Fixes VM disk export failure (NAS-137836). Resolves KeyError when attempting to export VM disks through the Devices menu, allowing successful disk image exports.
• Fixes inability to remove transfer speed limits from SSH replication tasks (NAS-137813). Resolves validation error “Input should be a valid integer” when attempting to clear the speed limit field, allowing users to successfully remove speed restrictions from existing replication tasks.
• Fixes Cloud Sync task bandwidth limit validation (NAS-137922). Resolves “Input should be a valid integer” error when configuring bandwidth limits by properly handling rclone-compatible bandwidth formats and improving client-side validation.
• Fixes NVMe-oF connection failures due to model number length (NAS-138102). Resolves “failed to connect socket: –111” error by limiting NVMe-oF subsystem model string to 40 characters, preventing kernel errors when enabling NVMe-oF shares.
• Fixes application upgrade failures with validation traceback (NAS-137805). Resolves TypeError “’error’ required in context” during app upgrades by ensuring proper Pydantic validation error handling in schema construction.
• Fixes application update failures due to schema validation errors (NAS-137940). Resolves “argument after ** must be a mapping” exceptions when updating apps by properly handling nested object validation in app schemas.
• Fixes application image update checks failing with “Connection closed” error (NAS-137724). Resolves RuntimeError when checking for app image updates by ensuring network responses are read within the active connection context.
• Fixes AMD GPU detection logic (NAS-137792). Resolves issue where AMD graphics cards were not properly detected due to incorrect kfd_device_exists variable handling.
• Fixes API backwards compatibility for configuration methods (NAS-137468). Resolves issue where certain API endpoints like network.configuration.config were unavailable in the 25.10.0 API, causing “[ENOMETHOD] Method ‘config’ not found” errors when called from scripts or applications using previous API versions.
• Fixes console messages display panel not rendering (NAS-137814). Resolves issue where the console messages panel appeared as a black, unresponsive bar by refactoring the filesystem.file_tail_follow API endpoint to properly handle console message retrieval.
• Fixes unwanted “CronTask Run” email notifications (NAS-137472). Resolves issue where cron tasks were sending emails with subject “CronTask Run” containing only “null” in the message body.

Click here to see the full 25.10 changelog or visit the TrueNAS 25.10.0 (Goldeye) Changelog in Jira.

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

TrueNAS Enterprise

• UI login delays during High Availability failover with STIG configuration changes. When toggling STIG settings in System > Advanced > System Security that require a system reboot, UI login authentication can experience extended delays (over 2 minutes) during failover when one controller is rebooting.

  Workaround: Wait 2-3 minutes for authentication timeout to complete.

• High Availability STIG configuration changes can cause production downtime if active controller is rebooted prematurely. When enabling or disabling STIG in System > Advanced > System Security, the system automatically reboots the standby controller in the background. Both controllers must reboot to complete the configuration change.

  Workaround: After saving STIG settings, wait until the standby controller is fully online before rebooting the active controller. Rebooting the active controller while the standby is still booting can cause disrupt production.

  This issue is resolved in TrueNAS 26.

• Apps using SMB/NFS storage can experience race condition during boot. When apps are configured to use SMB or NFS shares as storage passthroughs, there can be an occasional race condition during TrueNAS boot where the app startup conflicts with the sharing services startup. This causes affected apps to not fully start and show a “crashed” status.

  Workaround: Restart the affected app after a minute or two.

• Long-running systems with legacy FreeNAS datasets might encounter dataset editing errors (NAS-138629). Users might see "aclmode: failed to get property" errors when attempting to edit dataset properties. This affects datasets with invalid aclmode=discard_chmod property values carried over from legacy FreeNAS versions. TrueNAS 25.10.1 improves error messages to help identify affected datasets.

  Users encountering this issue should run zfs set aclmode=passthrough dataset_name via CLI for each affected dataset (replacing dataset_name with the actual dataset path), then reboot the system.

• NVMe over TCP is incompatible with VMware ESXi environments (NAS-137372). TrueNAS 25.10 uses the Linux kernel NVMe over TCP target driver, which lacks support for fused commands required by VMware ESXi. This is an upstream kernel limitation that prevents path initialization in ESXi environments.

• Two-Factor Authentication (2FA) can fail during daylight saving time transitions (NAS-138200). Systems with two-factor authentication configured can experience login failures for approximately one hour during daylight saving time transitions when clocks move backward. The authentication system resolves automatically once the duplicated hour passes.

• Locking encrypted datasets fails when actively shared via iSCSI or SMB. Attempting to lock an encrypted dataset while it is actively shared via iSCSI or SMB fails with an EBUSY error. No alert is generated and no email notification is sent when the lock operation fails.

  Workaround: Before locking the dataset, disable the share (iSCSI extent or SMB share) in the sharing configuration. After locking the dataset, you can re-enable the share if needed.

  This issue will be resolved in a future TrueNAS release.

• Existing SMB sessions cannot connect to shares created after the session was established. SMB clients with active sessions might be unable to access newly-created shares without first reconnecting to the server. This is a long-standing behavior that affects all SMB clients, not specific to any operating system.

  Workaround: Restart the SMB service in System > Services, or disconnect and reconnect the SMB client (unmount and remount the server).

  This issue is resolved in TrueNAS 26.

• Fibre Channel iSCSI initiator changes do not apply to the running configuration until the iSCSI service is restarted. When updating a Fibre Channel initiator on an iSCSI share, SCST updates with the change but the running configuration file does not reflect the update until the iSCSI service is stopped and started.

  Workaround: After updating the Fibre Channel initiator, stop and then start the iSCSI service in System > Services to apply the change to the running configuration.

• Switching to the General update profile can display a TypeError on the Update screen (NAS-140736). When a TrueNAS version is promoted from Early Adopter to General availability, users already running that version who then change their update profile to General can see a TypeError: 'NoneType' object is not subscriptable error on the Update screen. The error persists after refreshing the page or logging out and back in, but clears after a system reboot.

  Workaround: Reboot the system after changing the update profile to clear the error message.

  This issue is resolved in TrueNAS 26.

• The Reload button in the new license confirmation dialog does not reload the web interface (NAS-140931). After applying a new license, the confirmation dialog appears with a Reload button. Clicking Reload does not trigger a page reload; the license is applied correctly but the web interface continues to display the pre-license state until the page is manually refreshed.

  Workaround: After applying a new license, manually refresh the browser page to update the web interface.

See the latest status on Jira for public issues discovered in 25.10 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.

• The TrueNAS REST API was deprecated in TrueNAS 25.04. Full removal of the REST API is planned for TrueNAS 26.

  Starting with TrueNAS 25.10.1, the system displays alerts when deprecated REST API endpoints are accessed to help identify integrations that require migration to the JSON-RPC 2.0 over WebSocket API.

  TrueNAS (25.04 and later) uses a versioned JSON-RPC 2.0 over WebSocket API. API versions are numbered in conjunction with TrueNAS version releases.

  The API documentation provides information about supported API methods and events. Documentation is included for all API versions supported by the current TrueNAS release and defaults to the latest supported API. Use the dropdown to view documentation for different supported API versions.

  Advanced users can interact with the TrueNAS API to perform management tasks using the TrueNAS API Client as an alternative to the TrueNAS web UI. This websocket client provides the command line tool midclt and allows users to communicate with middleware using Python by making API calls. The client can connect to the local TrueNAS instance or to a specified remote socket.

  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.

• NVIDIA GPU Compatibility: TrueNAS 25.10 switches to open GPU kernel drivers that are incompatible with legacy NVIDIA GPUs (Pascal, Maxwell, Volta architectures). See NVIDIA GPU Support for compatibility details.

• Virtual Machine Startup Changes: VMs created in TrueNAS 25.04 (pre-25.04.2) and displayed on the Containers screen no longer automatically start on system boot to prevent conflicts with VMs on the Virtual Machines screen. See Containers and Virtual Machines for more information.

• Active Directory AUTORID IDMAP Backend Removal: TrueNAS 25.10 removes this option to improve consistency across multi-server environments (NAS-136630). Existing configurations using AUTORID are automatically migrated to RID during upgrade. Users should review their ACLs and permissions after upgrade and might need to reconfigure them in some edge cases.

• TrueNAS 25.10 removes the built-in SMART test scheduling and monitoring interface. TrueNAS continues automated drive health monitoring through middleware-integrated SMART polling and ZFS failure detection. Existing scheduled SMART tests are automatically migrated to cron tasks during upgrade, and smartmontools binaries remain installed. See Drive Health Management for more information on the SMART monitoring transition.

• TrueNAS 25.10 removes the Certificate Authority (CA) functionality that allowed TrueNAS to create and sign certificates. Users can continue to manage certificates by creating Certificate Signing Requests (CSRs) to be signed by external certificate authorities or and importing certificates that have been signed by external CAs or directory services. These alternatives provide the certificate management capabilities most users need while ensuring proper certificate validation through established certificate authorities.

• TrueNAS 25.10 improves SMB share configuration by displaying only options relevant to each purpose-based preset. Existing shares that previously used the “No Preset” option are automatically migrated to the “Legacy Share” preset during upgrade. New shares cannot access legacy configuration options. The SMB recycle bin feature is no longer available for new shares due to security and usability concerns. For file recovery and versioning, use ZFS snapshots, which provide more reliable and predictable data protection. See Legacy Share Settings for more information.

• Pool usage, disk temperature, and related metrics can have a short delay of no more than 10 minutes before displaying. This is typically seen when TrueNAS boots or in situations where the reporting system restarts.

TrueNAS Enterprise

Virtual Machines are now “Enterprise ready” with support for TrueNAS Enterprise High Availability (HA) systems and failover (NAS-136509).

• The Enable Secure Boot option is added to virtual machine configuration screens (NAS-136466).

• Virtual machines created in 25.04 (pre-25.04.2) and displayed on the Containers screen do not automatically start on system boot to prevent conflicts with VMs on the Virtual Machines screen that might use the same zvols (NAS-136946).

• Virtual machines created in 25.04.0 or 25.04.1 using the Instances (now Containers) screen can be migrated to conventional VMs in 25.10 and later using the process described in the Migrating Containers VMs tutorial.

• Resolves ZFS ARC memory management conflicts that were causing out-of-memory crashes in Virtual Machines due to memory fragmentation issues (NAS-135499).

• TrueNAS 25.10 adds an option to automatically migrate existing applications when changing apps pool locations (NAS-135720). See Migrating Existing Applications for details.
• 25.10 supports configuring external container registry mirrors as alternative sources for Docker images (NAS-136553). See PD-2125 for more information.
• 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.
• Fixes the NVIDIA GPU-related error “RenderError: Expected [uuid] to be set for GPU in slot” (NAS-134152).
• Fixes a bug to reenable available update notifications for custom apps (NAS-135124).

TrueNAS Apps Market

Your source for general apps documentation, a browsable catalog, and individual app resources.

TrueNAS 25.10 changes how disk health monitoring works, transitioning from built-in SMART test scheduling to a flexible approach that better serves modern storage environments.

• SMART test scheduling was built into the TrueNAS UI
• Tests were configured through Data Protection Tasks screens
• SMART test results appeared on the Storage Dashboard and individual disk screens

• SMART test scheduling UI is removed
• TrueNAS continues automated drive health monitoring through middleware-integrated SMART polling and ZFS failure detection
• Manual SMART testing can be scheduled via cron jobs or third-party apps
• The smartmontools binaries remain installed and functional
• Drive temperature monitoring uses the enhanced drivetemp kernel module, extended to include SCSI/SAS disk temperatures

This transition addresses several limitations:

1. Modern Storage Realities: Traditional SMART tests (short and long) designed for mechanical hard drives are less relevant for SSDs and NVMe drives, which now represent an increasing percentage of deployments. These devices focus on different health metrics like write endurance rather than mechanical wear patterns.

2. Flexibility: The previous system was restrictive and difficult to customize for advanced users.

3. Reliability: The integrated SMART test scheduler had persistent bugs and maintenance challenges. Scheduled tests could produce false positives and were difficult to troubleshoot.

4. Better Tools Available: Dedicated monitoring applications like Scrutiny provide superior disk health tracking with historical data storage, customizable alerts, and automatic drive detection.

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 the Drive Health Management tutorial for full details.

TrueNAS 25.10 introduces support for NVIDIA open GPU kernel module drivers, preparing TrueNAS to support the latest NVIDIA graphics cards including newer architectures like Blackwell. This driver update ensures TrueNAS Apps and Containers can utilize modern GPU acceleration workloads.

The open GPU kernel drivers are compatible with Turing architecture and later GPUs, which includes GTX 16-series cards and all RTX series cards. Newer architectures like NVIDIA Blackwell (RTX 50-series, RTX PRO Blackwell) require the nvidia-open driver to function, as this driver leverages the built-in NVIDIA GSP (GPU System Processor).

To verify your GPU is supported, check the installed NVIDIA driver version in Software Component Versions. Click the driver version number to view the NVIDIA release page, which includes a “Supported Products” tab listing all compatible GPUs for that driver version.

Users with compatible hardware can enable TrueNAS to install NVIDIA drivers. See the TrueNAS Apps Market for installation instructions.

GPUs based on earlier architectures, including Pascal (GTX 10-series, Quadro P-series), Maxwell (GTX 700 and 900-series), and Volta (GTX Titan V) are not supported by the NVIDIA open drivers. This is because these older GPUs lack the required GSP component.

Users with incompatible legacy cards can still utilize them by deploying a TrueNAS Virtual Machine and isolating the GPU to it. This approach involves creating a VM, isolating the legacy GPU to that VM, installing the proprietary NVIDIA driver within the VM environment, and running GPU workloads from within the virtual machine. However, this workaround requires a secondary GPU (such as integrated Intel graphics or an IPMI console) to handle system display duties, as isolating the only GPU in the system would leave TrueNAS without console access.

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.0) are listed below:

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