Plan NAS Capacity and Power Before Choosing the Box

By LK Wood IV · Published 2026-10-03 · St. Louis County, MO

Start a NAS capacity and power project. The template keeps the capacity and power routes together and names the WD Red Plus 8TB WD80EFPX so the example has an exact source-linked drive identity, without claiming that you own the model or that it is currently available; replace the drive, layout, electricity rate, and wattage when the real plan differs, before treating the example as a bill of materials.

A NAS plan can look complete while four different questions remain mixed together: how much data fits, how many device failures the array tolerates, whether existing hardware is worth reusing, and what the finished machine costs to leave on. This project answers them in that order. Product selection comes after the workload and failure plan.

1. Inventory the data and its growth

Start with the data you have now. Separate it into three groups:

• Primary data: files for which the NAS will be the working copy.
• Replicas: data already held somewhere else and safe to recreate.
• Replaceable data: downloads, caches, media transcodes, and other material that can be rebuilt.

Record the current amount for each group, the expected growth, and the time window you want the system to serve before expansion, because a single total hides the difference between ten terabytes of family photos and ten terabytes of replaceable media.

Then state the usable-capacity target, meaning the space available after the chosen RAID or RAIDZ layout but before you spend it on snapshots, filesystem overhead, free-space headroom, or a rebuild strategy. Keep those reservations visible instead of quietly treating every reported terabyte as available project space.

I would also name the largest single restore. Restoring one workstation, one media library, or one project archive can change the network and backup plan even when total capacity stays the same.

2. Choose the failure tolerance before the drive count

Write down how many simultaneous device failures the storage layout must tolerate and what happens while a failed device is replaced, because failure tolerance is the project requirement while the RAID label is only its implementation.

Open the NAS and RAID Storage Calculator and test the smallest drive count that meets the usable target, then one layout with more fault tolerance. Because a project keeps one current state for each tool, an open trade requires either a full JSON export before replacing that state or a separate project for the alternative. The calculator shows capacity math; it cannot decide how much downtime or rebuild exposure is acceptable for your data.

For a large six-bay plan, read Six-Bay NAS Drives: The Rebuild Math at 20TB+. That guide ties its drive, layout, rebuild-floor, and price conclusions to a named size class and dated sources. Use it when your plan matches that scope. Do not copy its old price into a different date or apply its result to another bay count without doing the math again.

RAID and RAIDZ keep a service running through some device failures. They do not create an independent backup. Record where the second copy lives, how it is disconnected or protected from the primary system, and the last time a restore was tested.

3. Qualify the hardware you already own

If an old desktop is available, do not price a new NAS until the existing machine has passed the basic qualification in the old-PC NAS guide, which walks through CPU architecture, memory, SATA ports, drive bays, a separate boot device, network path, HBA use, and operating-system choices.

Capture the exact machine in the project:

• CPU and motherboard model.
• Installed memory and available slots.
• Native SATA and M.2 ports, plus occupied ports.
• Physical bays and airflow across the intended drives.
• Network interface and the slowest link to the main client.
• Existing power supply, connectors, and age.
• The boot device and where configuration backups will live.

Mark anything you have not opened or measured as unknown. “Old gaming PC” is not a hardware record. The motherboard model and a photograph of the drive cage can answer questions that a processor name cannot.

Use the AM5 ECC Compatibility Checker only when the plan actually uses an AM5 platform represented in its source records. A missing board or an unverified firmware path stays a limitation. Do not promote a nearby model’s result into compatibility evidence for yours.

4. Pick the storage software from the operating constraint

The operating system follows the hardware, drive layout, and administration job. Open the storage backend comparison when the plan includes virtualization or competing storage stacks. Keep three questions visible:

1. Will this box primarily serve storage, run applications, or host virtual machines?
2. Are the drives matched, or does the project need to mix capacities?
3. Who will maintain updates, replacement procedures, alerts, and backups?

Record the chosen software and the reason in the project constraints. “Popular” is not an operating requirement. A straightforward storage appliance and a lab host that also exposes storage have different recovery paths even when they use the same disks.

Do not install onto the only copy of any data. The project should show a separate temporary location or backup for every disk that will be erased during setup.

5. Carry capacity into power, then replace assumptions

Once the drive count and platform are plausible, continue from the NAS calculator to the Power Cost Calculator. The handoff preserves capacity context, but capacity does not determine wattage. The destination begins from a labeled estimate that must be replaced with your hardware’s idle and load draw. Use 24/7 Homelab Idle Power Costs to see which rows are measurements and which are estimates, which sources support them, and where a comparable-hardware row can serve as a planning reference without becoming a measurement of your machine.

Enter your electricity rate and expected load schedule. Save the calculator state to the project. When hardware exists, measure idle at the wall after services settle and measure the workload you care about. Before replacing the estimate, export the planning record or copy the old value into the project constraints with its date. The attached evidence list is display-only. Then replace the estimate and record the meter and date so the error remains visible in the exported record or note. Power can decide whether “free” old hardware remains the cheaper plan, while a small gap can also show that replacing a working machine is difficult to justify. The project should carry the arithmetic; the decision still belongs to the owner.

6. Finish with a recovery drill

The project is ready for implementation when it names:

• Current data, growth window, and usable-capacity target.
• Chosen fault tolerance and a second-copy location.
• Drive count, size assumption, and an alternate layout.
• Exact existing hardware or the unresolved product categories.
• Storage software and the job it serves.
• Estimated idle/load power, electricity rate, and a plan to measure the result.
• One replacement procedure and one restore test.

After setup, unplug nothing at random. Use the platform’s documented failure procedure or a non-destructive test environment, then record what the restore or replacement drill actually proved. If a fault appears during setup, open the Diagnostic Workbench and keep the symptom and recent change, the observations, completed tests, plus the outcome with this project.

Export the final JSON when the NAS reaches its known-good state. The browser save stays on this device. A shared snapshot retains the title, product labels, and tool inputs while omitting the use case and constraints, all evidence, plus diagnostic text.

What the sources establish

The capacity calculator establishes arithmetic from the inputs you provide. The six-bay drive guide establishes its published conclusions only for its stated drive class, source dates, and layout. The old-PC guide establishes a qualification path, while the power article separates cited measurements from estimates. This guide connects those decisions. It adds no drive benchmark, current price, measured wattage, or universal operating-system verdict. The template’s WD Red Plus reference is a planning default backed by the attached Western Digital data sheet and TechFuel HQ drive guide. It is not an ownership or current-availability claim.