TrueNAS NAS: Difference between revisions

From Eden's Homelab Wiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{PhysicalMachine
{{PhysicalMachine
  | cpu = Intel i5-9400T (6 cores)
  | cpu = Intel i5-9400T (6 cores)
  | memory = 64Gb
| image = GcyexeCW0AAYssz.jpeg
  | oss = TrueNAS Core 13
  | memory = 32Gb
  | disks = 1x 2Tb NVME SSD, 1x 8Tb SATA SSD
  | oss = TrueNAS Scale 24.10
  | disks = 1x 4Tb NVME SSD, 2x 8Tb SATA SSD
  | nics = Mellanox CX312A MCX312A-XCBT ConnectX-3, motherboard gigabit realtek nic
  | nics = Mellanox CX312A MCX312A-XCBT ConnectX-3, motherboard gigabit realtek nic
}}[[File:Jails.png|thumb|FreeBSD jails currently running on my main NAS|left]]
}}
[[File:ZFS Pools on main NAS.png|left|thumb|ZFS Pools on main NAS]]
[[File:GgDtPBnWoAA4qeX.jpg|left|thumb|SMB shares on the TrueNAS NAS]]
Here it is: my main server and NAS. It runs TrueNAS core, based off FreeBSD (since TrueNAS Scale didn't exist when I set it up). As a NAS, it has NFS, iSCSI and SMB shares running off a ZFS file system. In FreeBSD jails it runs jellyfin and a fully torrenting stack: transmission, sonarr, radarr, etc. FreeBSD jails seem to have much better preformance than docker for this. Moreover, they can be easily policy routed to use different networks which route out traffic through different VPNs; for example the torrenting jails are attached to my [[AirVPN LAN]] which routes out through an AirVPN VPN. Meanwhile jellyfin routes out through the [[Swiss LAN]] so I don't have to port forward from my home router. My Nextcloud Jail was recently moved to the [[TrueNAS Core Nextcloud]] VM on [[Routerbox]].


On a BHYVE VM, [[ubuntu0]] which runs lots of services in docker, including a netboot server, numerous websites and twitter and reddit bots.
Here it is- my main server. For years it ran TrueNAS Core, but nowadays updates for it are rare to come by. The migration from Core to Scale was very difficult because of how many FreeBSD Jails I used to have which needed to be migrated to Docker. Even as of 2025 it still lacks the features to limit containers to a single NIC in the web UI as you can with Core, so some of my containers are managed through [https://github.com/jwansek/TrueNASTorrentingStack the CLI instead using macvtap].  


In terms of hardware, it has a low powered six-core 9400T, 64Gb of memory for lots of VMs and a nice big ZFS cache. It has a dual port 10 gigabit NIC.
However, using Scale I do not need to run any VMs any more. RIP [[Ubuntu0]]!


It was recently moved to a 2U case to save space and power, it exclusively has SSDs which allow the power consumption to idle around 25w, even with that dual port 10 gigabit NIC. It is powered with a PicoPSU, which is very efficient at lower power usages. It has a passive CPU cooler.
In terms of hardware, it has two 8Tb Samsung QVO SSDs and a 4Tb NVME SSD for storage, a Mellanox dual port 10 gigabit NIC, 32Gb of memory for lots of tasks and a good ZFS cache, and an Intel 9400T due to its low power consumption and excellent encoding performance for jellyfin. It lives inside a nice 1U case to save space, cooled with 4 40mm noctua fans. One of the 10Gb NICs is connected to the rest of the network via the [[Switches#TL-SG3428XMP|TL-SG3428XMP]] switch, and the other to the [[Backup NAS]] directly through an ad-hoc network.
 
Interestingly, in Scale I also managed to get VLANs to work which I could never get to work in Core, which means I need to use one fewer NIC which further reduces power consumption. It typically uses ~30w even when under load, which it basically always is thanks to seeding torrents.

Latest revision as of 17:51, 30 December 2024

SMB shares on the TrueNAS NAS

Here it is- my main server. For years it ran TrueNAS Core, but nowadays updates for it are rare to come by. The migration from Core to Scale was very difficult because of how many FreeBSD Jails I used to have which needed to be migrated to Docker. Even as of 2025 it still lacks the features to limit containers to a single NIC in the web UI as you can with Core, so some of my containers are managed through the CLI instead using macvtap.

However, using Scale I do not need to run any VMs any more. RIP Ubuntu0!

In terms of hardware, it has two 8Tb Samsung QVO SSDs and a 4Tb NVME SSD for storage, a Mellanox dual port 10 gigabit NIC, 32Gb of memory for lots of tasks and a good ZFS cache, and an Intel 9400T due to its low power consumption and excellent encoding performance for jellyfin. It lives inside a nice 1U case to save space, cooled with 4 40mm noctua fans. One of the 10Gb NICs is connected to the rest of the network via the TL-SG3428XMP switch, and the other to the Backup NAS directly through an ad-hoc network.

Interestingly, in Scale I also managed to get VLANs to work which I could never get to work in Core, which means I need to use one fewer NIC which further reduces power consumption. It typically uses ~30w even when under load, which it basically always is thanks to seeding torrents.