#truenascore — Public Fediverse posts

In some hidden place there is an interesting update on zvault.io.

https://github.com/zvaultio/Community/blob/main/posts/2025-07-13.md

#zvault #TrueNASCore #freenas
https://zvault.io/

#TrueNAS 25.04 Released For Unifying SCALE & CORE Offerings
TrueNAS 25.04 is notable for unifying their #Linux-based #TrueNASSCALE and #TrueNASCORE #FreeBSD-based platforms. While TrueNAS was previously known for its BSD base, Linux has proven viable for this network attached storage platform. TrueNAS 25.04 is powered by the Linux 6.12 LTS kernel while employing the #OpenZFS file-system support.
https://www.phoronix.com/news/TrueNAS-25.04-Released #OpenSource #NAS

#TrueNAS 25.04 "Fangtooth" Beta Unifies#Linux SCALE & #FreeBSD CORE Efforts
It was released on Thursday as another step toward unifying #TrueNASCORE derived from FreeBSD and Linux-based #TrueNASSCALE.
TrueNAS 25.04 "Fantooth" is an upgrade for TrueNAS SCALE 24.10 and TrueNAS CORE 13.x. TrueNAS 25.04 beta is powered by the Linux 6.12 LTS kernel, makes use of OpenZFS 2.3, there is much faster #OpenZFS #RAIDZ expansion, new instances support, and a number of other features.
https://www.phoronix.com/news/TrueNAS-25.04-Beta

#iXsystems: No one is being 'marooned' by #Debian focus
From now on iXsystems will develop #TrueNASSCALE faster than #TrueNASCORE (#FreeBSD), with #TrueNAS CORE becoming more of a maintenance product. SCALE is based on Debian #Linux, termed a #scaleout product, and supports #Docker Containers, #Kubernetes, #KVM, #Gluster, and a wider range of hardware than CORE.
https://blocksandfiles.com/2024/04/08/ixsystems-no-one-is-getting-marooned/

Long time #FreeNAS/TrueNAS Core user, my next build will be SCALE for sure

The resilvering finished yesterday and I moved everything from the 8TB drives onto the new array. Now wiping all of the remaining old 8TB drives with random data before selling them off. Also running #badblocks on an older 4TB drive (ALWAYS treat old drives as sus) and one of the 10TB ones since it encountered an error during the normal random data wipe.

So far Seagate Exos is proving to be very fast. They have a good rep, so hoping they all hold up well over time. Since most of the load is #Plex, it shouldn't be too punishing. #storage #homelab #zfs #TrueNAS #TrueNASCore

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.

I'm going to play along with #ShareYourHomelab and you should too! #homelab

Router:
HP EliteDesk 800 G2 SFF, Core i5-6500, 16GB RAM, 2x120GB SSD, Mellanox ConnectX-3 dual 10Gbps NIC running OPNsense

Core Switch:
Brocade ICX7250-48P

Wireless APs:
2x Ruckus R600 with Unleashed firmware

Server:
Quanta D51B-2U, dual E5-2660 v4, 384GB DDR4 ECC, onboard 10Gbps Intel NIC, 3x LSI SAS controller cards (2 internal, 1 external), 2x 120GB SSD boot volume, 2x EMC KTN-STL3 enclosures, 2x 1.6TB Intel P3605 PCIe NVMe (VM storage)

Server Storage:
6x 10TB WD Red
4x 4TB WD Red
28x 8TB HGST SAS

I reserve the first 10 IPs in my /24 for direct static assignments. That's exclusively for #OPNsense, DNS, switches, and other core network infra. The next 30 are used for DHCP reservations for servers, services running on it, and permanent network devices.

DNS filtering is handled by AdGuard Home because it'll run natively via plugin on OPNsense. Local resolution is handled by Unbound. I was previously using BIND in place of Unbound, but the plugin for OPNsense doesn't implement all of the features I need.

The server runs #TrueNASCore on bare metal. Everything else on it is in #bhyve VMs. This includes #Plex, #Docker, #HomeAssistant, and most recently #SecurityOnion (still in progress!).

Plex runs in its own VM. Supporting services are on the Docker VM. This includes #Jackett, #Sonarr, #Radarr, #Deluge with VPN, #Headphones, #Tautulli, and #Bazarr. The CPUs are powerful enough that I don't even consider GPU transcoding. I'm also on 1Gbps upstream so I tell everyone to Direct Play when possible.

Home Assistant runs on its own VM. I have a #Hubitat to provide a bridge to ZigBee and Zwave devices in the house. Right now that's primarily door sensors which trigger a chime sound on the Google Home Mini, but I'm also adding motion/light sensors and some switches to automatically turn off lights upstairs because my kids are terrible at it.

I have a second server for backups. It's a Supermicro 2U box with 12x 10TB HGST SAS drives, dual E5-2630L, 64GB DDR3 ECC. I'm in the process of getting WireGuard setup so I can move it offsite. It currently pulls data from the primary box nightly.

I have all user systems on the network backing up to the server nightly using Veeam. Those backups get cloned to the backup server. Veeam is free for home users and does a great job at endpoint backups.