Why Run TrueNAS Inside Proxmox Instead of Buying a NAS Box?
A TrueNAS Proxmox setup is a homelab storage solution where the Proxmox hypervisor hosts a TrueNAS virtual machine with direct disk access, combining ZFS-based network-attached storage and virtualized services on the same affordable hardware for a flexible, expandable virtualized home server that avoids the cost of dedicated NAS appliances.
If you have one decent PC and a pile of drives, running TrueNAS on Proxmox lets you turn that box into both an affordable NAS configuration and a general-purpose virtualized home server. Proxmox can run on any old x86 system with as little as 1GB of memory, which means even modest machines can host multiple services and storage pools. On top of that, TrueNAS brings ZFS, snapshots, checksums, and enterprise-grade features without the price tag of a dedicated appliance, as long as you feed it disks correctly. The big prerequisite is being comfortable editing a few Proxmox config files and understanding PCI passthrough; this is not a "click next" wizard install, but it’s well within reach if you’ve set up a VM before. When you follow the iXsystems-recommended method, the hybrid Proxmox + TrueNAS configuration can be reliable enough for both storage and everyday self-hosted apps on one machine.
What You Need and the Gotchas You Should Respect
Before touching any configs, check that your hardware and expectations match this setup. You need a 64-bit x86 machine that can run Proxmox, at least a few gigabytes of RAM, and a SATA controller with drives dedicated to TrueNAS. Proxmox’s low system requirements mean even 5–10-year-old budget-friendly systems can power plenty of virtual guests for homelab use. TrueNAS itself is heavier than lightweight NAS distros, so very weak machines may be better off with alternatives. OpenMediaVault, for example, remains a solid option for DIY storage rigs that don’t have enough processing power to run something as bulky as TrueNAS.
The main caveat: you cannot treat TrueNAS like a normal Linux VM. Deploying a TrueNAS VM like a conventional distro—giving it virtual disks from Proxmox’s storage—is a recipe for disaster, even if it looks fine at first. TrueNAS uses ZFS, which needs direct control over physical disks. If you stack extra virtualization layers between ZFS and the drives, you can break write caching; in a crash, write operations may be reordered, risking your pool’s integrity. You also lose proper S.M.A.R.T. stats, accurate disk information, and reliable cache flushes, which undermines the whole point of using ZFS for data safety. The safe path is to pass the entire SATA controller to the TrueNAS VM using PCI(e) passthrough, giving it hardware-level access.
Step-by-Step: Configuring PCI Passthrough and the TrueNAS VM
You’re going to make Proxmox hand the SATA controller straight to the TrueNAS VM. That’s the iXsystems-recommended way and the reason this hybrid setup behaves like a proper NAS instead of a fragile lab experiment. It looks scary on paper, but if you treat it as a small checklist and don’t rush, you’ll be fine.
- Enable IOMMU in GRUB: edit /etc/default/grub, find GRUB_CMDLINE_LINUX_DEFAULT="quiet" and add intel_iommu=on right after quiet, then run update-grub to enable IOMMU provisions.
- Load VFIO modules: open /etc/modules and add these lines on separate rows: vfio, vfio_iommu_type1, vfio_pci, vfio_virqfd, then reboot so Proxmox loads them at startup.
- Identify SATA controller IDs: run lspci -nn and note the PCI device IDs for your SATA controllers that will host TrueNAS disks.
- Bind controllers to VFIO: create or edit /etc/modprobe.d/vfio.conf and add a line in the format options vfio-pci ids=Device_1,Device_2, using the IDs you found.
- Reboot and verify: reboot Proxmox, then confirm the SATA controllers are bound to vfio-pci and no longer used by the host for storage.
- Attach controllers to the TrueNAS VM: in the TrueNAS VM’s Hardware tab in Proxmox, add the passed-through SATA controllers as PCI devices so TrueNAS can see all connected drives directly.
The most common mistake is skipping PCI passthrough and assigning individual disks as virtual drives from the Proxmox storage backend. That looks convenient but adds those harmful layers between ZFS and the hardware, and it’s the fastest way to end up with broken storage pools after a crash. Another trap is mixing host usage and passthrough on the same controller; dedicate that controller entirely to TrueNAS so S.M.A.R.T., disk info, and cache flushes all behave as expected. Once the VM boots with the controller passed through, you can create ZFS pools inside TrueNAS like you would on bare metal, with confidence that the disks are under its full control.
Living With a Hybrid Proxmox + TrueNAS Home Lab
When the passthrough is set up correctly, TrueNAS runs reliably in a Proxmox VM. One user has kept this virtualized NAS running for well over a month without issues, which is impressive given that it shares hardware with other workloads. The trade-off is obvious: if the Proxmox node crashes, the TrueNAS VM goes down too. For most home labs, as long as you don’t go overboard with risky experiments on the same host, the iXsystems-recommended configuration is stable enough for daily storage duties.
The payoff is big. A single machine can host your NAS, backup server, and a stack of services—personal cloud, document tools, finance apps, and more—without monthly subscription bills. Proxmox’s KVM tools, clustering options, and network features make it easy to grow into more complex setups as your homelab evolves. Meanwhile, TrueNAS takes care of ZFS snapshots, checksums, and storage management, giving you an expandable homelab storage solution on hardware you already own. Running a hybrid Proxmox + TrueNAS configuration on the same machine is considered a bit unconventional by some homelab purists, but in practice it’s a cost-effective way to get enterprise-grade features without dedicated NAS hardware.
Is This Setup Worth It for You?
If you’re on a budget, comfortable editing a few config files, and want one box to do "storage plus services," this TrueNAS Proxmox setup is worth the effort. Proxmox’s ability to run on old x86 hardware means you can repurpose outdated machines into self-hosting hubs instead of buying new server gear. TrueNAS gives those repurposed rigs ZFS-based reliability, as long as you follow the PCI passthrough pattern and let it talk directly to your disks.
The main things to watch for are simple: don’t treat TrueNAS like a normal VM, don’t skip PCI passthrough, and don’t share the passed-through controller with the host. Respect those rules and you get an expandable homelab storage solution that consolidates storage, backups, and apps into one flexible virtualized home server, instead of scattering roles across multiple boxes. It’s not plug-and-play, but once it’s running, the combination of Proxmox flexibility and TrueNAS storage management can quietly serve your data and projects for a long time.
