For over a decade, FreeNAS and TrueNAS CORE served as the gold standard of open-source network attached storage. Built on the bulletproof reliability of FreeBSD and native OpenZFS, CORE powered millions of enterprise storage arrays and homelab backup vaults. However, the modern infrastructure landscape—dominated by containerization, GPU-accelerated AI pipelines, NVMe-over-Fabrics, and modern hardware driver ecosystems—outpaced FreeBSD’s development velocity.

With the release of TrueNAS SCALE “Electric Eel” and subsequent updates in 2026, iXsystems consolidated all active engineering into the Linux Debian base, introducing native Docker Compose application management to replace legacy Kubernetes (k3s). For millions of TrueNAS CORE users, migration is no longer a question of “if”, but “how to execute without downtime or data corruption.”

Why Is TrueNAS CORE Deprecated in Favor of TrueNAS SCALE in 2026?

While FreeBSD’s storage stack is legendary for its stability, enterprise hardware manufacturers prioritize Linux kernel drivers. Hardware features such as Intel QuickSync GPU video transcoding on modern Arrow Lake / Raptor Lake architectures, NVIDIA NVENC GPU virtualization, and line-rate 100GbE networking require bleeding-edge kernel subsystems that FreeBSD cannot deliver on consumer and mid-tier platforms.

By standardizing on Debian Linux, TrueNAS SCALE delivers massive operational advantages:

Step-by-Step TrueNAS CORE to SCALE Migration Protocol (Zero Data Loss)

Follow this exact sequence to ensure zero data loss during the transition:

1. Step 1: Save Backup Configurations: In the TrueNAS CORE web UI, navigate to System > General > Save Config. Ensure the checkbox Export Password Secret Seed is selected. Without this seed, encrypted datasets and stored SMB passwords cannot be decrypted on the new system.
2. Step 2: Document Network Settings & MAC Addresses: FreeBSD interface names (such as cxgbe0, igb0, or re0) will change to Linux predictable interface names (such as enp3s0 or eth0). Note down your static IP addresses, VLAN tags, and LACP link aggregation groups.
3. Step 3: Execute the In-Place Sidegrade:
   • Flash the latest TrueNAS SCALE ISO to a USB flash drive.
   • Boot the server from the USB drive and select Install/Upgrade.
   • Choose the existing TrueNAS CORE boot SSD.
   • Select Upgrade Existing Installation (Preserve Data).
   • Choose Install into a new boot environment. This ensures that your original TrueNAS CORE FreeBSD installation remains untouched as a secondary boot option if emergency rollback is required!
4. Step 4: Post-Boot Storage Pool Verification: After the server reboots into TrueNAS SCALE, log into the web interface. Navigate to Storage > Pools. Your ZFS pools will automatically import in clean, healthy status.

Converting FreeBSD Jails and Plugins to Native Docker Compose Stacks

In TrueNAS CORE, applications ran inside FreeBSD jails with persistent mount points into your ZFS pools (e.g., /mnt/tank/media). To migrate an application like Plex Media Server to TrueNAS SCALE:

1. Create a dedicated ZFS dataset for Docker application metadata: /mnt/tank/appdata.
2. Ensure your media datasets remain mounted at /mnt/tank/media.
3. In the TrueNAS SCALE web UI under Apps > Custom App (Docker Compose), deploy the official container stack:

# Docker Compose configuration for migrated Plex Media Server
services:
  plex:
    image: lscr.io/linuxserver/plex:latest
    container_name: plex
    network_mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=UTC
      - VERSION=docker
      - PLEX_CLAIM=claim-your-token-here
    volumes:
      - /mnt/tank/appdata/plex:/config
      - /mnt/tank/media/tv:/tv
      - /mnt/tank/media/movies:/movies
    devices:
      - /dev/dri:/dev/dri # Hardware transcoding for Intel QuickSync
    restart: unless-stopped

Troubleshooting NFSv4 vs. POSIX ACL Permissions Post-Migration

The most common post-migration failure involves Windows SMB shares becoming read-only or rejecting administrative file modifications. This occurs because FreeBSD wrote complex NFSv4 rich ACL flags into the ZFS metadata that Linux Samba interprets as deny-overrides.

To repair permissions cleanly via the TrueNAS SCALE shell without risking data corruption:

# 1. Inspect existing dataset ACL type
zfs get acltype,xattr tank/data

# 2. Set dataset to POSIX ACL mode with system extended attributes
zfs set acltype=posixacl tank/data
zfs set xattr=sa tank/data

# 3. Strip legacy NFSv4 extended attributes recursively
setfacl -b -R /mnt/tank/data

# 4. Apply standard user and group ownership
chown -R 1000:1000 /mnt/tank/data
find /mnt/tank/data -type d -exec chmod 775 {} +
find /mnt/tank/data -type f -exec chmod 664 {} +

Alternatively, in the TrueNAS SCALE web interface, navigate to Datasets > Edit Permissions, select Preset: POSIX_OPEN or POSIX_RESTRICTED, check Apply permissions recursively, and click Save. Your SMB and NFS clients will immediately regain seamless read/write access.

Where to Expand Your Storage Architecture Next

Now that your storage array runs on modern Linux, optimize your system memory, deduplication tables, and filesystem performance:

• Prevent out-of-memory container crashes by tuning your storage memory in TrueNAS SCALE ZFS ARC Sizing in 2026: Why Linux OOM Killer Drops Apps & arc_max Tuning.
• Evaluate next-generation hardware deduplication in OpenZFS 2.3 Fast Dedup: How Log-Structured NVMe Deduplication Solves the 5GB/TB RAM Limit.
• Compare filesystem performance across homelab hypervisors in Btrfs vs. ZFS on Proxmox VE: Copy-on-Write Snapshots & RAM Overhead Forensics.

People Also Ask

Will migrating from TrueNAS CORE to SCALE wipe my hard drives?
No. The migration only affects your boot SSD or USB drive where the operating system is installed. Your ZFS storage pool data disks (the drives holding your media, documents, and databases) remain completely untouched and are imported automatically upon booting into TrueNAS SCALE.

Can I roll back to TrueNAS CORE if I encounter issues?
Yes, provided you did NOT upgrade your ZFS pool feature flags! Because the installer creates a new boot environment, you can simply reboot your server, enter the GRUB bootloader menu, select your previous TrueNAS CORE boot environment, and boot back into FreeBSD as if nothing happened.

Does TrueNAS SCALE support TrueNAS CORE encrypted pools (GELI)?
No! Legacy FreeBSD GELI full-disk encryption (used in FreeNAS 11 and early CORE versions) is completely unsupported on Linux. If your pools use legacy GELI encryption instead of native ZFS dataset encryption, you MUST decrypt or replicate your data to an unencrypted pool before attempting migration.