Homelab Storage Options: NAS vs DAS vs Raw Drives
How to think about storage for your homelab: the tradeoffs between a NAS, direct-attached storage, and drives in your server, with real recommendations.
Storage decisions are where homelab setups diverge sharply. Some people run a mini PC with a single SSD and call it done. Others build dedicated NAS systems with eight drives and redundancy. Both are right for their situations. The difference is understanding what you’re actually optimizing for.
Here’s how to think through it.
The Three Models
Raw drives in your server: the simplest approach. Your mini PC has an M.2 slot and maybe a 2.5” bay. Drives live inside the machine that runs everything. No separate hardware.
DAS (Direct-Attached Storage): an enclosure that connects to your server via USB or Thunderbolt and provides additional drive bays. The server runs everything; the DAS just extends available storage.
NAS (Network-Attached Storage): a separate device on your network with its own OS and drives. Synology, QNAP, TrueNAS on custom hardware, or an old PC running OpenMediaVault. The NAS handles storage independently; your server mounts it over the network.
When Raw Drives Are Enough
For most homelab setups, drives in the main server are the right call:
- One or two SSDs cover your Docker services, media library, and photo backups
- Everything is physically in one box (simpler to manage, simpler to back up)
- No network latency for storage access (services access drives directly)
- No separate device to power and maintain
A mini PC with a 1TB NVMe for the OS and services, plus a 4TB SSD for media, handles most homelab workloads. Total cost: $60-120 depending on capacity.
The limitation: you’re constrained by the drive bays in your machine. A mini PC typically has one M.2 and one 2.5” bay. When you hit the ceiling, you’re looking at a new machine or external storage.
When DAS Makes Sense
A DAS enclosure plugs into your server and gives you more drive bays without another computer on your network.
USB DAS (like the Mediasonic H82-SU3S2 or similar 2-4 bay enclosures): cheap (~$50-80), no special drivers, works with any machine. Bandwidth is limited to USB 3.0 (~400MB/s shared across all drives). Fine for media storage where you’re streaming one file at a time, not for high-throughput workloads.
Thunderbolt DAS: faster, but requires Thunderbolt on your server (most mini PCs and homelab hardware don’t have it). Expensive enclosures.
PCIe DAS / HBA cards: if your server has PCIe slots, a host bus adapter card can connect to a DAS with SAS drives. This is where the enterprise hardware rabbit hole begins. Useful for large storage arrays; overkill for most homelab setups.
DAS is the bridge between “I ran out of room in my server” and “I need a separate NAS.” It keeps everything logically on one machine while adding physical drive capacity.
When a NAS Makes Sense
A NAS is a separate device with its own CPU, RAM, OS, and drives, dedicated to storage. Your homelab server mounts storage from the NAS over the network (NFS or SMB).
Reasons to use a NAS:
Storage independence. If your main server dies, your data is still on the NAS. Rebuild the server, remount the storage, done. This is the most compelling argument.
Drive count. A 4-bay or 8-bay NAS holds more raw capacity than most homelab servers. If you need 16TB+ of accessible storage, a NAS is the right form factor.
RAID and parity. NAS software (Synology DSM, TrueNAS, OpenMediaVault) handles RAID configuration, parity-based redundancy (RAIDZ, Unraid), and drive failure alerts. If you want “one drive can fail and I don’t lose data,” a NAS OS handles this better than rolling it yourself on a general-purpose Linux machine.
24/7 spinning drives. Running spinning hard drives in a server that’s also doing compute work is fine, but purpose-built NAS hardware is designed and thermals-tuned for it.
Reasons not to buy a NAS:
Cost. A 4-bay Synology starts around $300, before drives. The software is polished but you’re paying for it. DIY TrueNAS on an old PC is cheaper but requires more setup.
Network latency. NFS mounts over gigabit are fine for media streaming. They’re not great for databases or Docker volumes that do heavy random I/O. Running your Postgres databases on NFS-mounted storage is asking for trouble.
Complexity. Two devices to manage, two devices to back up, network dependencies for storage access. Every additional component is another failure point.
The Practical Decision Tree
Under 4TB total storage: Drives in your server. One or two SSDs, done.
4-16TB, want simplicity: DAS enclosure with USB 3.0 plus drives in your server for the OS and databases. Keep compute-intensive storage local, move cold storage to the DAS.
8TB+ and want redundancy: TrueNAS Scale on old server hardware or a 4-bay Synology. Mount storage over NFS to your main server for media and file sharing; keep Docker volumes and databases on local drives.
Separating storage from compute is your goal: NAS regardless of capacity.
What I’d Actually Buy
For a budget homelab starting point:
Immediately: Beelink EQ12 with 1TB NVMe (included) + 1TB 2.5” SATA SSD for media (~$45). That’s 1.5TB of fast SSD storage for under $200 total.
When that fills up: 4TB portable USB drive (~$70) for cold storage and backups. USB performance is fine for things you access occasionally.
When serious about redundancy: An old mini PC or desktop running TrueNAS with a couple of used 4TB HDDs. Mounting that over NFS to the main server costs almost nothing if you’re repurposing hardware you already have.
If I had the budget upfront: 4-bay Synology DS423 (~$380) with 2x 4TB HDDs in SHR1 (one drive redundancy). Expensive, but the software is excellent and it just works. Worth it if storage reliability matters and you don’t want to build your own.
The Part People Skip: Backups Are Not Redundancy
RAID protects against a drive failing. It does not protect against accidental deletion, ransomware, file corruption, controller failure, or your house burning down. RAID means you don’t lose uptime when a drive dies, not that your data is backed up.
Run a NAS with RAID if you want redundancy. Also run off-site backups. These are separate concerns and you need both.
The backup strategy guide covers the backup side. RAID and backups are not substitutes for each other.