TrueNAS CORE
TrueNAS Enterprise
TrueNAS SCALE
TrueCommand
Compare Editions
Software Status
FreeNAS
Systems Overview
M-Series
X-Series
R-Series
Mini Series
Download TrueNAS CORE
Download TrueNAS SCALE
Get TrueNAS Enterprise13.0 Release Notes
28 minute read.
Last Modified 2022-12-07 13:04 -0500TrueNAS Quality Lifecycle
| Release Stage | Completed QA Cycles | Typical Use | Description |
|---|---|---|---|
| NIGHTLY | 0 | Developers | Incomplete |
| ALPHA | 1 | Testers | Not much field testing |
| BETA | 2 | Enthusiasts | Major Feature Complete, but expect some bugs |
| RC | 4 | Home Users | Suitable for non-critical deployments |
| RELEASE | 6 | General Use | Suitable for less complex deployments |
| U1 | 7 | Business Use | Suitable for more complex deployments |
| U2+ | 8 | Larger Systems | Suitable for higher uptime deployments |
The Software Status page shows the latest recommendations for using the various TrueNAS software releases.
All release dates listed are tentative and are subject to change. The items in this list might not show every deadline or testing cycle that iXsystems uses to manage internal effort.
The progress and specific work is being tracked through tickets opened in Jira. If you have a feature suggestion or bug report, create a Jira account and file a ticket in the TrueNAS or TrueCommand projects. TrueNAS SCALE tickets are also tracked in the TrueNAS Jira Project.
| Version | Checkpoint | Scheduled Date |
|---|---|---|
| 13.0-U4 | Release | To be determined |
November 16, 2022
iXsystems is pleased to release TrueNAS 13.0-U3.1.
This is a small maintenance release to patch an issue found in the upstream Samba project.
- NAS-118951 don’t SMB_ASSERT() on mixed case sensitivity settings in vfs_shadow_copy_zfs
- NAS-118926 SMB_ASSERT() on FSCTL on alternate data stream
November 1, 2022
iXsystems is pleased to announce the release of TrueNAS 13.0-U3.
This is a maintenance release with some improvements for ACLs and rsync, updates Samba to 4.15.10 and updates the Asigra plugin. It adds Enclosure Management integration for the 3rd generation R50 and Storj as a new Cloud Sync provider.
- NAS-118437 Update net/samba to Samba 4.15.10
- NAS-118341 libzfsacl - add function to convert ZFS ACL to string
- NAS-118216 Record midclt enclosure.query in debug (Core/Enterprise/Scale)
- NAS-118199 Update rsync port in 13
- NAS-117828 Add Storj as Cloud Sync service (13 and Angelfish)
- NAS-116185 Enable trains redirect for 12.0 to 13.0
- NAS-118505 R50BM needs to be added to webUI codebase
- NAS-118068 Add R50BM to enclosure mapping code and to keyserver
- NAS-117923 Upgrade Asigra plugin
- NAS-117827 New cloud sync provider: “Storj iX” (13 and Angelfish)
- NAS-118787 Asigra Install fails
- NAS-118717 CVE-2022-3437 (Heimdal des/des3 overflow) Samba 4.15
- NAS-118563 fix service.restart and journal sync race
- NAS-118562 nameservers not propagating to standby nodes
- NAS-118546 Disable some cloud sync buckets
- NAS-118370 Merge FreeBSD SA-22:13 EN-22:20
- NAS-118166 Box (TrueNAS 13.0-U2) spontaneous reboot during install of nextcloud plugin
- NAS-117976 NIS does not start on it’s own after failover.
- NAS-117975 hwpmc(4) kernel panic on Proxmox
- NAS-117972 No error message when trying to delete snapshot with hold
- NAS-117964 VM created in Truenas 12.0 fails to boot or edit on Truenas 13.0-U2
- NAS-117957 netcli cannot edit lagg interfaces
- NAS-117899 TC Cloud Connection causing a Kernel Panic with R10
- NAS-117760 [13.0:U1.1] smbd.core when connecting from a macOS
- NAS-117710 ZFS space efficiency on devices with huge physical blocks
- NAS-117290 NAS-1 had an unscheduled system reboot. The operating system successfully came back online at Fri Jul 22 08:29:53 2022.
- NAS-115559 Use O_RESOLVE_BENEATH for opens in FreeBSD
| Seen In | Key | Summary | Workaround | Resolved In |
|---|---|---|---|---|
| 13.0-U3 | NAS-118832 | UI Does not show the correct status on HA systems | There is a known UI caching issue that impacts the status of failover in HA systems. The workaround is to refresh the browser screen or clear the cache after failing-over or making any UI change to update the UI screens to show the correct status of the two nodes. Note, this might require logging into the system again if your token has expired. | Targeted 13.0-U4 |
| 13.0-U3 | NAS-118787 | Asigra Install Fail | Configure the Asigra plugin on HA systems requires assigning a static IPs address rather than using DHCP to assign the node IP addresses. The Asigra plugin does not install correctly on HA systems that rely on DHCP-assigned IP addresses. | Targeted 13.0-U4 |
| 13.0-U3 | N/A | Netatalk deprection | Netatalk has been deprecated and users should begin migrating away from using it with TrueNAS. Netatalk is deprecated in 13.0, and like AFP will be completely removed post-CORE 13.0. Users should migrate to SMB shares. | N/A |
| 13.0-U2 | NAS-117663 | 2.5GigE Realtek NICs are unsupported in 13.0-U2. This is due to the Realtek NIC driver causing iSCSI data corruption and the driver is now disabled by default. | When the system is not used for iSCSI sharing and the NIC support is required, enabling the Realtek NIC driver is possible by going to System > Tunables and creating two new tunables. Click ADD, enter these values:
Click ADD again, enter these values:
To verify the realtek driver is loaded, reboot the system, go to the Shell, and type kldstat -n if_re.ko. The command returns the file name and details when it has been loaded. |
TBD |
| 13.0-U2 | NAS-117891 | 2FA login fails the first time after failover before succeeding. | It appears the UI presents the sign in screen before the system is ready. Occurs on High Availability systems. Suggest user not immediately attempt logging in, but wait a bit before trying to signing in with 2FA, or if sign in fails, refresh their screen and retry until the system presents the correct sign in screen with 2FA field. | Target 13.0-U3 |
| 13.0-U2 | NAS-117899 | TrueCommand connection causing a kernel panic with unscheduled system reboots. | Cause of this issue is under investigation. | Target 13.0-U3 |
| 13.0-U1.1 | NAS-117663 | iSCSI data corruption with RTL8125 NICs. Unlike FreeBSD native re(4) driver the vendor driver does not properly handle physically non-contiguous mbufs, used by our iSCSI target to avoid extra memory copy in TCP stack transmission path. Some chip models might work due to other workarounds applied, but those are exceptions. | With the lack of time for a fix on a planned 13.0-U2 freeze day, we decided to re-disable the vendor driver to avoid the data corruptions. Unfortunately it means loosing support for 2.5GigE Realtek NICs. People not using iSCSI can still re-enable the driver with loader tunables: if_re_load=“YES” if_re_name="/boot/modules/if_re.ko" |
Waiting for Realtek solution, TBD |
| 13.0-U1 | NAS-117071 | Shadow Copies in nested datasets not visible. | N/A, possible edge case that is still being investigated. | 13.0-U1.1 13.0-U2 |
| 13.0-Release | NAS-116493 | Nextcloud (official) plugin does not install . | Nexcloud issue could not be reproduced. Recommend users migrate to SCALE which provides a better experience with running applications. | 13.0-U2 |
| 13.0-Release | NAS-116217 | Disk replacement fails with JavaScript error. | Use the CLI to manually replace the disk: CLI method. | 13.0-U1 |
| 13.0-Release | NAS-116262 | NFS nconnect feature not stable on 13.0 | During multi-client usage with the client-side nconnect option used, the NFS server becomes unstable. This feature has been verified to work on SCALE, but resolution ETA is unknown for 13.0. | SCALE |
| 13.0-Release, 12.0-U8.1 | NAS-116160 | Netatalk 3.1.13 introduced an edge-case bug where AFP metadata could be stripped unexpectedly on file read | Deployments that rely on AFP sharing should avoid upgrading to 13.0 until the 13.0-U1 release. Snapshot any AFP-shared datasets before attempting to upgrade to a 13.0 release. | 13.0-U1 |
| 13.0-Release | NAS-116090 | Mini 3.0 E+ View Enclosure showing populated drive bay as empty. | The enclosure view for all Mini 3.0 platforms will show the top bay as unpopulated even when a drive is inserted. | 13.0-U1 |
| 13.0-Release | NAS-116185 | 13.0 Train shows Community Release Only - Not Enterprise Supported. | While core users can use this train to upgrade from the UI this release is not suitable for enterprise customers, and no support will be provided for enterprise customers. This notice will be removed in a future release. | 13.0-U2 release (targeted) |
| 13.0-BETA1 | NAS-114160 | Connection interrupt when managing jails or plugins. | This behavior was seen in early testing and is still being investigated. No workaround is necessary as the connection resumes after a brief interruption. | 13.1-ALPHA1 (targeted) |
| 13.0-BETA1 | NAS-114595 | VNC can’t connect to bhyve VMs. | Update to 13.0 Nightlies or 13.0-U1 (when available). | 13.0-U1 |
| 12.0-U8.1 and 13.0-BETA1 | NAS-115838 | Plugin install failures due to end of life (EoL) 12.2 FreeBSD release. | Resolved separately from TrueNAS releases on April 19, 2022. | 13.1-RELEASE |
| 13.0-BETA1 | NAS-114480 | Unable to connect to TrueCommand Cloud. | Avoid connecting 13.0-BETA1 systems to TrueCommand Cloud while this issue is investigated. | 13.0-RC1 |
| N/A | N/A | TrueNAS 12 cannot replicate to or from TrueNAS 13 | By default, TrueNAS 12 cannot initiate a replication to or from TrueNAS 13 due to an outdated SSH client library. Allowing replication to or from TrueNAS 13 to TrueNAS 12 requires allowing ssh.rsa algorithms. See OpenSSH 8.2 Release for security considerations. Log into the TrueNAS 13 system and go to Services->SSH. Add the SSH Auxiliary Parameter: PubkeyAcceptedAlgorithms +ssh-rsa. |
N/A |
| 12.0-BETA2 | NAS-107151 | Replication fails between legacy TrueNAS 9.10 systems and 13.0-BETA1 systems. | Due to numerous improvements in the replication engine and ZFS, TrueNAS 9.10 systems (or earlier) cannot replicate to or from TrueNAS 13.0-BETA1. Update the legacy TrueNAS system to 11.3 first, then 12.0, and then 13.0. | N/A |
These instructions apply to systems installed with 13.0-Release only.
CLI commands are meant for advanced users and, when improperly applied, can result in serious system instability or production down scenarios. Please use CLI commands carefully and always back up critical data before attempting this kind of procedure.
- On a system with 13.0-RELEASE installed, access the TrueNAS shell either by logging in to the web interface and clicking Shell or accessing the CLI remotely using SSH.
Type in the commands formatted in these code blocks and replace any
<text>strings with data unique to your system. - Find the pool and disk to replace:
zpool listshows the name of the pools on the system.zpool status <pool name>shows the specific pool and disk state for the pool. Replacewith the name of your specific pool. - copy or note the
gptid/####identifier for the disk to replace. - Example:
root@examplemini[~]# zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH tank 2.72T 444K 2.72T - - 0% 0% 1.00x ONLINE root@examplemini[~]# zpool status tank pool: tank state: ONLINE config: NAME STATE READ WRITE CKS UM tank ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gptid/c7a10e6d-ca3d-11ec-8ec6-d05099c356a4 ONLINE 0 0 0 gptid/c7acbd9e-ca3d-11ec-8ec6-d05099c356a4 ONLINE 0 0 0 errors: No known data errors
curl -s https://raw.githubusercontent.com/truenas/gist/main/replace_disk.py -o replace_disk.pydownloads the disk replacement tool.python3 replace_disk.py <pool_name> <gptid/####> <ada#>replaces the named disk in the pool with the designated spare. Replace <pool_name> with the name of the pool with the disk to be replaced, <gptid/####> with the disk identifier noted above in step 2, and <ada#> with the name of the unused disk to use as the replacement. Example:root@examplemini[~]# python3 replace_disk.py tank gptid/c7acbd9e-ca3d-11ec-8ec6-d05099c356a4 ada3 Replace initiated. root@examplemini[~]#zpool status tank pool: tank state: ONLINE scan: resilvered 13.0M in 00:00:01 with 0 errors on Thu May 19 14:12:21 2022 config: NAME STATE READ WRITE CKS UM tank ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gptid/c7a10e6d-ca3d-11ec-8ec6-d05099c356a4 ONLINE 0 0 0 gptid/5e10e97f-d7b8-11ec-889a-d05099c356a4 ONLINE 0 0 0 errors: No known data errors root@examplemini[~]#