Where Should the Disks Live in a Small Homelab?
- Published
- 19 June 2026
- Updated
- 19 June 2026
The question usually starts like this: should you use a mini PC with direct-attached storage (DAS), a mini PC with a separate network-attached storage box (NAS), or a NAS that is built mainly to look after disks?
That sounds like a shopping question. It is really a storage question. Before choosing boxes, ask where the disks live, which machine can see them properly, what breaks with them, and what you have to rebuild when the tidy little stack stops being tidy.
I started with a mini PC and direct-attached storage, and I still think that is a good way to learn. It makes storage tangible. You can attach disks, make filesystems, share folders, break things cheaply, and understand what all the NAS advice is actually talking about before you buy a dedicated storage box.
A mini PC plus DAS is not foolish. It just becomes awkward when a learning setup quietly becomes your main storage before you have checked whether it is ready for that job.
Once the disks hold data you care about, the question changes. You are no longer asking “can I attach drives to this?” You are asking who checks disk health, which backup includes the data, which cable or enclosure can make storage disappear, and how you recover when something has failed and you are already annoyed.
The Three Shapes
First, separate the three layouts:
| Shape | Plain meaning |
|---|---|
| Mini PC plus DAS | A small computer runs the services and uses disks in an attached enclosure, usually over USB or Thunderbolt. |
| Mini PC plus separate NAS | The mini PC runs apps or services. A separate NAS owns the disks and shares storage over the network. |
| Storage-first NAS | The storage box owns the disks, filesystem or storage pool, shares, health checks, backup jobs, and disk replacement process. It may be a commercial appliance or a self-built NAS. |
Keep the labels broad. This is not a buyer guide. A tiny used office PC with a four-bay USB enclosure, a mini PC using shares from another NAS, and a purpose-built storage box can all be sensible in different homes.
The real comparison starts when something fails. Which machine knows enough to tell you what happened?
The Short Version
For the quick answer, start here.
| Situation | Better fit | Why |
|---|---|---|
| You are learning storage, filesystems, shares, and backups | Mini PC plus DAS | It is modular, understandable, and avoids buying a full NAS before you know what you need. |
| You need cheap local media or scratch storage | Mini PC plus DAS | The failure cost is lower if the data is replaceable and the backup story is honest. |
| You want compute to stay flexible but storage to be a shared service | Mini PC plus separate NAS | The NAS owns disks and shares; the mini PC can be rebuilt or replaced separately. |
| Multiple clients need the same storage | Separate NAS or storage-first NAS | The storage role is clearer when clients consume shares instead of borrowing raw disks from one mini PC. |
| The data is important and storage is the main job | Storage-first NAS | Disk health, pool/filesystem status, replacement, shares, and backup jobs belong in one storage system. |
| You have no patience for extra power bricks and cable arguments | Storage-first NAS, if the physical box fits | Fewer external storage pieces usually means fewer ways to knock storage offline by tidying the shelf. |
Read that as a quick guide, not a ranking.
What The Disks Need
Disks need more than a place to plug in.
Before choosing hardware, make the platform answer these questions:
| Question | Why it matters |
|---|---|
| What owns the disks? | The owner is responsible for the filesystem or storage pool, shares, health checks, backup jobs, and replacement. |
| Can the system see each disk clearly? | Drive identity, serial numbers, SMART drive-health data, errors, and pool status affect monitoring and replacement. |
| What fails together? | Host, enclosure, cable, power supply, switch, and network dependencies all change the failure story. |
| What backup includes the data? | A disk enclosure is not a backup. A mirror is not a backup. A network share is not automatically backed up. |
| How does replacement work? | ”Pull failed disk, insert new disk, rebuild onto it” is very different from “which of these identical USB devices vanished?” |
| What has to be rebuilt? | The operating system, storage settings, shares, login details, mount paths, app data, and backup jobs may not live in the same place. |
Small homelabs do not need to copy storage appliances. They do need to make it obvious when storage has stopped being an extra part and has become something your services depend on.
Mini PC Plus DAS Is A Good Starter
For a first lab, mini PC plus DAS is a friendly way to start.
The mini PC can be inexpensive, compact, and easy to repurpose. You can add the enclosure only when the disks need somewhere to live. You can learn Linux storage, ZFS or another filesystem, file sharing with SMB/NFS, containers, backup jobs, and monitoring without committing to one vendor’s NAS software or one case layout.
Early on, you do not need to know your final setup. A modular setup helps you learn the difference between app data and media, between redundancy and backup, between “the drive is mounted” and “I know how to restore this.”
In a lab, media scratch space, backup target, or low-risk store, the lessons can matter more than tidiness.
Mini PC plus DAS fits well for:
- learning storage without buying a full NAS immediately
- media or scratch data that is replaceable
- a local backup target, especially if another real backup layer exists
- experiments with filesystems, shares, snapshots, and restore drills
- temporary storage while deciding what deserves a proper home
The layout gets weaker when the attached storage quietly becomes the main NAS.
At that point the direct-attached part starts to count. The mini PC, operating system, USB or Thunderbolt bridge, enclosure, enclosure power supply, cable, and disks are now one storage system whether or not they arrived in one box. The weak point may not be the disk; it may be the bridge, the power brick, the cable behind the shelf, or the monitoring you never finished because the setup still felt temporary.
TrueNAS warns against USB-connected hard disks as primary storage in its own hardware guidance and notes that USB-connected media can misreport serial numbers. Use that narrowly: it supports caution for TrueNAS-style primary storage, not a verdict that every DAS setup is bad.
SMART drive-health visibility is not the same in every enclosure. A USB bridge is the controller between the computer and the drives; smartctl supports SCSI-to-ATA Translation and specific USB bridge device types, as documented in the smartctl manual source. The tooling has ways to talk through some bridges. Your enclosure still has to prove that it exposes each disk, serial, and health attribute cleanly.
The rule I would use is simple: use mini PC plus DAS freely as a learning path. Before it becomes main storage, check the boring bits:
- each disk has a stable identity
- SMART or equivalent health data is visible enough for your monitoring plan
- the filesystem or storage pool can be imported or checked after moving or rebuilding the host
- backups exist outside the DAS
- a failed disk can be identified without guessing
- the cable, enclosure, and power supply are treated as part of the storage system
If that sounds like too much work, that is useful information. It may mean the learning setup has reached its ceiling.
Mini PC Plus Separate NAS Draws A Cleaner Line
A separate NAS takes the disks away from the mini PC.
The mini PC runs apps, containers, VMs, dashboards, or whatever else the machine runs. The NAS owns the disks and shares storage over the network.
The mini PC can be rebuilt, replaced, upgraded, or turned into something else without also being the disk shelf. The NAS can focus on pool health, shares, snapshots, replication, and disk replacement.
TrueNAS shows what that split looks like: drive health management, disk replacement, shares, and replication tasks all belong to the storage side. The exact platform does not have to be TrueNAS. What matters is that the disks have an obvious owner.
The catch is that you now own more system, not less: another box, another operating system or appliance, another power supply, another update stream, network mounts, login details, a switch path, maybe DNS, and maybe a backup job that lives on the NAS while app data still lives on the mini PC.
Storage ownership is cleaner, but the service path has more pieces. A container on the mini PC that depends on a NAS share now depends on the mini PC, the network path, the NAS, the share settings, and whatever login details or mount settings connect them.
Mini PC plus separate NAS works well when:
- compute and storage should fail separately
- multiple clients need the same storage
- the mini PC is likely to be rebuilt or repurposed
- disk health and replacement should live on the NAS side
- storage matters enough to deserve its own health screen and monitoring
It is less convincing when the second box exists only because it sounds more serious. If the NAS is just a network-attached version of the same unplanned storage mess, it has not solved the problem. It has taught the mess to use SMB.
Storage-First NAS Makes Storage The Product
A storage-first NAS makes sense when storage is the main job.
That might be a commercial appliance, a self-built NAS with a storage-focused operating system, or a compact board built around direct SATA, NVMe, or another deliberate disk layout. The category matters more than the brand: the box exists first to look after storage.
This is the direction I took with the ODROID H4 Ultra NAS build, but that article is a build rationale, not a universal recommendation. Do not generalise the board choice. Generalise the ownership: when the storage box owns the disks directly, the physical layout, power design, drive count, monitoring, and recovery path become one design instead of several attached guesses.
The payoff is less confusion. The NAS owns the disks, the pool or filesystem, the shares, the health checks, the backup jobs, and the replacement process. If a disk fails, you should know where the alert comes from and which screen handles the replacement. If a client fails, storage keeps serving the other clients.
OpenZFS documents the low-level pieces behind many of these workflows: zpool status for pool health, zpool import for importing pools, zpool replace for replacing devices, and zpool scrub for checking pool data. A NAS platform can wrap some of that in a UI or workflow; the underlying obligation remains the same.
The tradeoff is commitment. A storage-first NAS may be less flexible than a mini PC. It may cost more up front. It may have fewer compute options, weaker expansion, or a vendor’s idea of how storage should work. If you build it yourself, you own the operating system and hardware choices. If you buy an appliance, you inherit its update model, app model, disk support, and limitations.
It can also concentrate risk if you put too many services on it. A NAS that also runs every application has not eliminated failure domains. It has moved them into one important box. That may still be the right answer, but it should be deliberate.
Storage-first NAS works well when:
- storage is the main job, not an add-on
- important data has multiple clients or services
- disk health and replacement need to be obvious
- backup and replication should live on the storage side
- physical tidiness matters in a living space
- you want fewer unclear storage boundaries
It is less useful when you are still learning, when storage is not yet important, or when you need cheap, modular hardware to work out what you actually want.
The Failure-Mode Matrix
| Difference | Mini PC plus DAS | Mini PC plus separate NAS | Storage-first NAS |
|---|---|---|---|
| Disk ownership | The mini PC owns the filesystem or storage pool if the enclosure exposes disks directly. Some enclosures may hide details behind a bridge or RAID mode. | The NAS owns disks, filesystem or pool, shares, health, and replacement workflow. | The NAS/storage OS owns disks, filesystem or pool, shares, monitoring, backup jobs, and replacement workflow. |
| Health visibility | Potentially good, but bridge-dependent. SMART drive-health data, disk serials, and per-disk visibility must be checked. | The mini PC usually sees a share or mount, not raw disk health. Health lives on the NAS. | Strongest single-system story if the NAS sees the disks directly and exposes health, pool status, replacement, and alerts. |
| Failure domain | Mini PC, OS, DAS bridge, enclosure, enclosure power supply, cable, and disks can all affect storage. | Compute and storage are more separated, but NAS, network path, login details, and mounts become dependencies. | Fewer external pieces, but storage and any colocated services share one chassis, power path, and platform. |
| Rebuild path | Rebuild the mini PC, reconnect or import storage, verify disk identity, then restore services and shares. | Rebuild the mini PC separately; NAS disk replacement follows NAS workflow; mounts and app paths still need restoring. | Replace failed disks through NAS workflow; platform rebuild depends on appliance export/restore or self-built OS/config model. |
| Backup shape | Back up from the mini PC-owned filesystem or pool. DAS is not a backup by itself. | NAS backup/replication protects storage; mini PC service config and app state may still need separate protection. | Backup/replication can be centralised, but still needs an off-box and preferably offsite layer. |
| Monitoring burden | Highest. Monitor host, filesystem/pool, disk health if visible, enclosure/bridge, cable, and power. | Medium. Monitor NAS, mini PC, network/mount health, and backup jobs across both. | Lowest ownership ambiguity, but still needs alerts, update discipline, backup checks, and restore tests. |
| Power, heat, and noise | Extra enclosure, power supply, and possibly a fan. No numbers without measurement. | Two boxes and likely switch involvement. Heat and noise may be distributed, but hardware count rises. | One storage box concentrates drives, heat, airflow, and noise. Tidier is not automatically quieter. |
| Box and cable sprawl | Highest. Useful while learning; annoying if it becomes permanent infrastructure in a small room. | Medium to high. More intentional, but still more hardware. | Usually lowest, unless the chosen NAS is too large or awkward for the space. |
No row wins cleanly. Each one gives you a different shape of pain. Pick the one you can describe.
Backup Shape Changes With Ownership
Backup follows whoever owns the storage.
With mini PC plus DAS, the mini PC is the storage host. Back up the data from there, and do not treat the DAS enclosure as protection just because it has more than one bay. If the DAS is the only place the data lives, the data has one home.
With a separate NAS, the NAS can own snapshots, replication, and storage backup jobs. That is cleaner for files, media, and shared datasets. It does not automatically back up the mini PC’s service definitions, container volumes, local config, secrets, or mount assumptions.
With a storage-first NAS, backup can be centralised, but centralised is not complete. If all data and backup jobs live on the same machine, that machine still needs an off-box layer. The 3-2-1 backup strategy on this site uses the familiar idea of multiple copies and one offsite copy. The useful part is deciding what deserves each layer.
Do not let “NAS” and “backup” collapse into the same word. A NAS is where storage is served. A backup is a recoverable copy with a restore path.
Small-Room Reality Counts
Small homelabs live in rooms, cupboards, shelves, and corners that were not designed for infrastructure.
Physical mess counts.
Mini PC plus DAS can start neatly and become a small pile of kit: one mini PC, one DAS, one or two power bricks, a USB or Thunderbolt cable, network, maybe a hub, maybe a UPS, maybe an external backup disk, and the growing suspicion that moving any one item will make a filesystem vanish.
Separate NAS plus mini PC can be cleaner logically and messier physically. The boxes have clearer jobs, but there are still two boxes. They still need power, network, placement, updates, and airflow.
A storage-first NAS can be physically calmer if the case and drive layout suit the room. It can also be a poor fit if it is too large, too warm, too loud, or too awkward to place. Tidiness comes from the actual design, not from the product category.
Do not write fake power numbers in your head. If power, heat, or noise matters, measure the actual setup in the actual place. Until then, use plain observations: more boxes usually means more cables and more power supplies; one storage box usually means more heat and drive activity concentrated in one enclosure.
How To Choose
Choose the simplest answer that gives the disks a responsible owner.
| Choose this | When |
|---|---|
| Mini PC plus DAS | You are learning, experimenting, storing replaceable data, building a backup target, or proving what you need before committing to a storage platform. |
| Mini PC plus separate NAS | You want compute to stay flexible while storage becomes a shared service with its own health, shares, and replacement workflow. |
| Storage-first NAS | Storage is now important enough that disk ownership, health visibility, backup jobs, and rebuild path should belong to one storage system. |
Then ask the awkward questions:
- If one disk fails, how do I know which one?
- If the mini PC dies, can the data move or be imported calmly?
- If the enclosure dies, what exactly is lost?
- If the NAS dies, where is the recoverable copy?
- Which machine sends the alert?
- Which backup restores the data, and when was it tested?
- Does the physical layout invite accidental unplugging, heat buildup, or permanent cable mess?
If you cannot answer those yet, that does not mean the setup is bad. It means you are still in the learning phase. That is not a problem. Just do not confuse it with a finished NAS.
The Sensible Progression
Start with mini PC plus DAS if it helps you learn.
Mini PC plus DAS keeps the parts visible: the computer, the disks, the filesystem, the share, the backup job, and the failure modes all stay close together. That is how storage stops being abstract.
When the data becomes important, move the decision from “what can I plug in?” to “what owns this storage?”
The answer depends on whether storage is still an add-on or has become the thing the machine is actually for. If the DAS checklist is met, mini PC plus DAS may still be right. If compute and storage should fail separately, a separate NAS may be right. If the disks are the main thing the system exists to protect, a storage-first NAS may be right.
The correct topology is the one whose failure mode you can live with. Not the prettiest box, not the cleverest forum answer, and not the design that only works while nobody touches the cable behind the shelf.