Video summary

UNRAID vs TrueNAS - Which is the BEST NAS OS? 5+ Years Experience

Main summary

Key takeaways

Technology

Technological concepts & feature comparison (Unraid vs TrueNAS)

1) Background / platform history

  • TrueNAS
    • Originated as FreeNAS (FreeBSD-based) using ZFS (at least from FreeNAS v8 onward).
    • iX Systems adopted FreeNAS early (2009).
    • In 2020, the FreeBSD-based line became TrueNAS Core, while a Linux-based line became TrueNAS Scale.
    • TrueNAS Community Edition is described as a feature-locked/free version of Scale; Core is phased out for most users, with enterprise options potentially still using FreeBSD-based deployments.
  • Unraid
    • Described as a Linux-based NAS OS with a paid licensing model.

2) Storage architecture (the “most important part”)

Unraid storage model

  • Uses a software-defined “array” approach for whole files stored on individual disks.
  • Data is not striped across disks like typical RAID:
    • Each file resides on a single disk.
    • Protection is provided by parity disks.
  • Drive flexibility:
    • Can mix drive sizes/types (e.g., different brands/capacities) and still form a valid array.
  • Expansion:
    • Add larger drives later and expand (workflow described).
  • Scheduled parity checks:
    • Example: monthly parity check taking ~15 hours on a ~6-drive setup.
  • Cache tier (“detection cache” / SSD cache):
    • Writes go to an SSD/cache pool first.
    • A scheduled mover task later transfers data to the main array.
    • Tradeoff: data in cache tier is unprotected by parity until moved (cache protection can be done with ZFS pools on SSDs, per note).
  • SSD warning:
    • No TRIM support for SSDs in the main array, making SSD use described as “horrendously bad.”

TrueNAS storage model (ZFS-based)

  • Uses ZFS pools built from vdevs (virtual devices), including RAID-Z variants and mirroring:
    • RAID-Z1/Z2/Z3 correspond to 1/2/3 parity disks.
    • Z0 described as no parity.
    • Mirroring as 1:1 duplication, reducing usable capacity.
  • Built-in integrity & self-healing:
    • Silent error correction / self-healing during reads.
    • ZFS scrub (scheduled) checks data + metadata and attempts repair.
  • Caching behavior:
    • ARC (RAM) is mandatory and described as memory-hungry (“RAM hog”).
    • Optional L2ARC on SSD:
      • Guidance: add only if ARC hit rate drops (e.g., below ~90% regularly).
    • Write logs / power-loss mitigation:
      • ZFS SLOG / ZIL helps protect data in flight during power loss.
  • Snapshot capability:
    • Highlighted as a major benefit:
      • Incremental, storage-efficient snapshots of changed data without a separate backup run.

3) UI / permissions / manageability

  • Both
    • Use web UIs with advanced settings nearby.
  • TrueNAS permissions
    • Strong built-in security using share permissions + ACLs across both share-level and filesystem-level settings.
    • The speaker finds it easy to get locked out if setup isn’t perfect.
    • Repeated emphasis on complexity of learning the “right” permissions model.
  • Unraid permissions
    • Simpler share access model via SMB/Samba.
    • User-based selection:
      • Read-only vs read-write per share.

4) Containers / apps / ecosystem

TrueNAS apps

  • Supports Docker-based app installation (moving away from older jail-based approach).
  • Apps tab described as having a very large catalog (example: ~340 apps).
  • Installation can involve complex configuration details:
    • user/group IDs
    • manual storage creation
    • CPU/memory allocation
  • Docker-based approach generally improves permissions compared to jails, but the speaker still reports more trouble than with Unraid.

Unraid apps

  • More “mature” and easier to grasp interface (as perceived by the speaker).
  • App marketplace described as larger/more straightforward:
    • example mention: ~3051 containers, with duplicates noted.

Unraid plugins (where Unraid is said to stand out)

  • Unraid supports plugins integrating more directly into the OS (community applications plugin used).
  • Examples mentioned:
    • Unassigned Devices
    • “Nerd Tools” pack
    • libvirt hot plug USB plugin

5) Virtual machines

  • Both support VMs.
  • Unraid VM experience described as easy.
  • TrueNAS VM setup also “fine,” including GPU passthrough.

6) System shell / admin workflow

  • Unraid
    • System shell button accessible immediately on-page (root shell quickly).
  • TrueNAS
    • Requires navigating through System → Shell with a warning about breaking the system.

This is used as an informal indicator of how “trusted” users feel in each UI/approach.

Review-style conclusions / recommendation bias

  • Speaker’s overall stance
    • TrueNAS: recommended for home gamers, despite being more complex; praised for core feature depth and ongoing evolution (UI/behavior can change).
    • Unraid: recommended as a high-stability workhorse for mission-critical use; but the speaker says data security isn’t as robust as ZFS, so full backups are required.
  • Personal use claims
    • Unraid used as the speaker’s workhorse system and editing workstation for ~5 years, repeatedly stable.
    • TrueNAS used for personal media server tasks (Plex / Jellyfin), now run via Docker containers; complexity is tolerated because it’s not mission-critical.

Main speakers / sources

  • Main speaker/source: the YouTube video narrator/author (presented as the person with ~5+ years Unraid and ~10 years FreeNAS/TrueNAS experience).
  • No external source or named collaborator mentioned in the subtitles.

Original video