Start with the exact product
A model family is not enough. Match the manufacturer part number, memory configuration, drive capacity, and seller condition. Similar names can refer to different processors, recording technologies, warranties, or included storage.
Our catalog separates diskless enclosures from systems with storage included. For hard drives, compare the exact MPN and CMR/SMR technology, rather than assuming every capacity in a family has identical characteristics.
What each source can establish
- Manufacturer documentation: specified ports, memory limits, supported features, and compatibility policy. A theoretical interface speed is not a measured transfer result.
- Published independent tests: performance, power, and noise for the tested configuration and workload. Different drives, software, clients, or test conditions can change the result.
- Community reports: setup friction, upgrade experiences, and possible issues to investigate. A collection of reports is not a controlled reliability study or a compatibility guarantee.
- Retailer product pages: a dated offer for a specific model and condition. They do not establish long-term availability or the final checkout price.
A page with several citations may include multiple official sources; the count does not mean that many independent laboratories tested the build. We do not claim a ChooseCompute hands-on result unless a test method and result are explicitly provided.
Capacity: what the numbers include
Our planning figures use equal-capacity disks and decimal TB. Two 8TB disks in RAID 1 provide 8TB before overhead. Four 12TB disks in RAID 5 provide 36TB; RAID 6 provides 24TB and tolerates any two drive failures. RAID 10 also gives 24TB in this example, but its failure tolerance depends on which mirror members fail.
One TB is 10¹² bytes; one TiB is 2⁴⁰ bytes. For example, 24TB is about 21.83TiB before system partitions, filesystem metadata, snapshots, and free-space reserves. The unit conversion is not formatting loss. RAID protects against some disk failures; it does not replace a separate backup.
Prices: a comparison, not a checkout promise
We record prices and availability separately. A recent price observation falls within our 7-day publication window; stock uses its own observation time. Captured prices appear directly, while missing seller, condition or stock details stay unknown. Older prices remain available as historical budget references; missing or unconfirmed evidence needs another check, and an editorial reference is always an estimate. A date-only record uses the start of its UTC day for a conservative freshness check.
Component totals inherit the least certain price status in the combination. They are calculated estimates for separately purchased items. Status evaluation does not refresh a merchant observation or guarantee a checkout price. Read each price label and date, then verify seller, condition, warranty, and stock at the store.
Complete-build estimates add the enclosure to the stated quantity of the exact drive. They may combine stores and generally exclude tax, shipping, extra memory, networking, a UPS, and separate backup storage. Cost per usable TB divides that hardware total by the stated decimal RAID capacity before overhead.
Why a recommendation can change
The best fit depends on required applications, data growth, playback devices, noise tolerance, and who will maintain the system. A higher tier is justified by those needs, not by the label alone. New prices, software restrictions, or compatibility evidence can change the comparison.
Before ordering, check the exact drive and memory support for the installed software release. Before migrating important data, test the intended application and an independent restore. Neither a compatibility label nor a successful benchmark proves that every workload will work.