TrueNAS 25.04 Fangtooth: CORE and SCALE merge into one system

This week saw the release of TrueNAS 25.04, codenamed “Fangtooth”. This release matters because it’s the first to offer a common way forward for users of both the FreeBSD-based TrueNAS CORE and the Linux-based TrueNAS SCALE: iXsystems is merging the two branches into a single open-source product, TrueNAS Community Edition. The release is built on the Linux 6.12 kernel and OpenZFS 2.3, and it replaces the virtualisation layer with Incus.

Below we summarise what has changed, who should upgrade now, and what to watch for if you use TrueNAS as storage for Proxmox VE.

What’s new in TrueNAS 25.04?

Fangtooth carries on from the SCALE 24.10 (“Electric Eel”) release, so technically it’s a Debian-based Linux. The most important changes:

Area 24.10 (Electric Eel) 25.04 (Fangtooth)
Kernel 6.6 6.12
OpenZFS 2.2.99 (a preview of 2.3) 2.3
Virtual machines libvirt (KVM) Incus (“Instances”), experimental
Containers Docker-based apps only Docker apps + LXC containers on Incus
REST API supported deprecated, to be removed later
  • Incus-based “Instances”. Virtual machines and the new LXC containers can be run from one interface, through the Incus manager. The LXC containers are the successors of CORE’s jails. VMs now have Secure Boot and a TPM device, which some guest operating systems require. For now, iXsystems marks the feature as experimental.
  • OpenZFS 2.3. RAIDZ expansion, introduced in 24.10 (an existing RAIDZ vdev can be expanded with new disks one at a time), has become five times faster according to the vendor, and the new, less resource-hungry deduplication (“fast dedup”) has been added.
  • Apps. For newly installed apps, you can specify which IP address they listen on; according to the plans, existing apps will get this option by 1 June.
  • Deprecated and removed parts. The REST API is deprecated, and the WebSocket-based API should be used instead; if you manage the NAS with scripts or an external tool, review your integrations. The built-in Netdata interface has been removed for security reasons.

The release also has new features (Fibre Channel, NFS and iSER over RDMA, STIG compliance) that are only available in the Enterprise edition.

CORE and SCALE: what happens to the FreeBSD branch?

TrueNAS CORE 13.x has been in maintenance mode for a year and a half already: it gets security and bug fixes, but no new features. 25.04 is an upgrade target from there too, but this isn’t a simple version change – it’s an operating system swap from FreeBSD to Linux:

  • The documented path is a fresh installation from the ISO, then restoring the saved configuration file. The ZFS pools, the SMB, NFS and iSCSI shares and the users come across.
  • The move is one-way: you can’t go back from Linux to the FreeBSD-based CORE.
  • Jails and plugins don’t migrate. These have to be rebuilt as apps (Docker) or LXC containers.
  • After the upgrade, don’t immediately upgrade the pools to the new ZFS features (zpool upgrade) until you are sure you are staying – an upgraded pool can no longer be imported on an older system.

When saving the configuration, also tick the option to export the “Password Secret Seed”, otherwise the passwords and credentials stored in the system won’t be restored; and back up the keys of encrypted pools separately as well.

Is it worth upgrading now?

In short: not yet on a production system. iXsystems itself says that 25.04.0 is recommended for early adopters, and for new installations it recommends 24.10.2.1. It advises conservative users to wait for the official upgrade recommendation.

Be especially careful if virtual machines run on the NAS. VMs from 24.10 (libvirt-based) don’t move to Incus automatically: after the upgrade, the machines have to be created again, with the existing zvol specified as the disk. According to the documentation, if you run production VMs on 24.10, don’t upgrade until the feature matures.

Our recommendation:

Situation Recommendation
SCALE 24.10, file sharing and apps only Fine to try on a test machine; in production, wait for the first fix releases
SCALE 24.10, with production VMs Stay on 24.10
SCALE 24.04 or older First upgrade to the latest fix release of 24.10
CORE 13.x Plan the move (replacing jails and plugins), but don’t rush
Machines managed with TrueCommand Upgrade TrueCommand to 3.1 first

TrueNAS as Proxmox storage

At many small businesses, TrueNAS is not just a file server but also the shared storage of the Proxmox VE cluster. There are two proven ways to do this.

NFS. The simplest: a dataset as an NFS share, on which Proxmox stores the VM disks in qcow2 format, and which can also hold the ISOs and backups. Because of qcow2, Proxmox snapshots work, and so does live migration, because every node sees the same storage.

pvesm add nfs truenas-nfs --server 192.168.10.20 \
  --export /mnt/tank/proxmox --content images,iso,backup

iSCSI. A zvol as an iSCSI target, with a shared LVM volume group on top of it on the Proxmox side. This is block-level, so it’s usually better for databases, but Proxmox 8 can’t take snapshots on shared LVM. Proxmox’s built-in “ZFS over iSCSI” storage type doesn’t work directly with the TrueNAS iSCSI server; it needs a third-party plugin, which we are reluctant to recommend in production.

pvesm add iscsi truenas-iscsi --portal 192.168.10.20 \
  --target iqn.2005-10.org.freenas.ctl:proxmox --content none

In both cases it’s worth using a separate storage network, ideally 10 Gbit/s (or at least a separate VLAN), and don’t run TrueNAS as a virtual machine on the same Proxmox cluster whose storage it provides. When designing the pools, our article on RAID levels helps, and we also wrote there about choosing between ZFS mirror and RAIDZ. If you are only now deciding on the hypervisor, we explained in this article why we recommend Proxmox VE for small businesses, and you can read about the reasons for moving away from VMware in our article on Broadcom’s licensing changes.

What do we recommend?

TrueNAS 25.04 is an important release: the era of two parallel branches is ending, and in future all development goes into the Linux-based version. The Incus integration is promising but still experimental, so on a production system it’s worth waiting for the fix releases and the vendor’s recommendation. And if you use CORE, now is the time to assess what runs in your jails and what you will replace them with.

We help with designing and running NAS systems, Proxmox clusters and the storage network between them; you can read about this on the Infrastructure and operations page.

Let’s talk about your project

Tell us briefly how we can help, and we will get back to you as soon as we can.

Get in touch