You can combine older hard drives into a RAID array, but there is no universal recipe. The correct layout depends on your operating system or storage platform, the number and usable capacities of the drives, the fault tolerance you need, and whether you can maintain an independent backup. Creating an array or pool can erase existing data, so copy and verify anything important before selecting a disk.
RAID can keep storage available after certain drive failures; it is not a backup and does not make aging disks reliable. Use it as one layer in a storage plan that includes health monitoring, prompt replacement of failed members, and a separate copy of irreplaceable files.
As an Amazon Associate I earn from qualifying purchases.
What RAID changes—and what it cannot protect you from
RAID (redundant array of independent disks) presents multiple physical drives as one logical storage arrangement. Depending on the level, it may stripe data for capacity, mirror copies for redundancy, or calculate parity so missing data can be reconstructed. The layout determines how much space is usable and which drive failures the array can survive.
A RAID array does not protect against accidental deletion, ransomware, filesystem corruption, theft, fire, controller failure, or a mistake during setup. A mirrored deletion is still deleted on every mirror member. Keep a separate, verified backup before and after building the array.
#1 Best Overall
- 【Reliable External Storage System for Individuals and Business】The 4 Bay Hard Drive Enclosure supports 2.5/3.5 inches HDD and SSD, max capacity up to 80TB( 20TB for each hard drive), it's a ideal external hard drive enclosure for personal or enterprise using.Save space on your desktop or laptop.
- 【No heat】The 4 bay hard drive reader built in Aluminum-Alloy materials and 2 inch Fan.Maximize the security of your data.NOTE：Fan noise is around 40-50 decibels, not recommended if you are very sensitive to noise.
- 【Up to 5Gbps】This 4 bay enclosure equips with advanced chip and USB 3.0 output interface, Max 5Gbps under UASP control.Transfer 1G movie in 3-5 seconds with USB 3.0 Ports, which is 10 times faster than USB 2.0.
- 【Wide Compatibility, Plug and Play】Equipped with USB A/C 3.0 Cable Cable.Compatible with Windows 7 and above, Mac 9.1 and above, Linux.Plug and play, no fuss, no muss.
- 【Stable power supply】Equipped with DC 12V power adapter to provide stability for high-speed transmission.
| Layout | Typical use | Failure tolerance | Capacity trade-off | Important warning |
|---|---|---|---|---|
| RAID 0 (stripe) | Temporary or replaceable data where maximum aggregate space is more important than availability | None; one failed member loses the array | Uses the members for data, but the smallest drive commonly limits each stripe component | TrueNAS states that a failed disk in a stripe requires recreating the pool and restoring from backups |
| Mirror (such as two-way RAID 1) | Small arrays and workloads that need straightforward redundancy | Usually one member in a two-drive mirror; exact tolerance depends on the mirror arrangement | Usable space is approximately the capacity of one member in a two-drive mirror, limited by the smallest drive | More copies improve availability but do not replace a backup |
| Single-parity (such as RAID 5 or RAIDZ1) | Arrays with enough drives to trade one drive’s worth of capacity for parity | One failed member, subject to the platform’s implementation and a successful rebuild | Approximately the sum of the smallest-member capacities minus one member’s worth for parity | A second failure or an unrecoverable read error during recovery can leave data unavailable |
| Dual-parity (such as RAID 6 or RAIDZ2) | Larger arrays where tolerating two member failures is worth the additional capacity cost | Two failed members in the combinations supported by the implementation | Approximately the sum of the smallest-member capacities minus two members’ worth for parity | Requires more drives and provides less usable space than single parity |
The capacity descriptions are planning approximations, not promises of marketed capacity. Filesystem overhead, metadata, reserved space, and the platform’s rules reduce what you can actually store.
Prepare the old drives before creating anything
Make and verify an independent backup
Copy valuable files to storage that will not become part of the new array. Open representative files from that copy and check that the backup completed; a list of copied filenames alone is not verification. Do not use one member of the planned array as the only backup of another member. Array creation, pool creation, and replacement workflows can wipe selected disks.
Inventory every disk
Record each drive’s model, serial number, interface, reported capacity, and the data currently on it. Save the inventory outside the drives being reused. Confirm that the computer, HBA, or storage enclosure presents every intended disk to the operating system. Stable device identities and serial numbers are safer selection criteria than a changing device name or port order.
Free tools Windows power users keep installed
One-click scans. No signup required.
Check actual capacity and health
Compare the device-reported capacity, not only the rounded number printed on a retail label. Linux mdadm ordinarily sizes array components from the smallest member. TrueNAS similarly limits a VDEV to the usable capacity of its smallest attached device. A replacement that is advertised as the same size can still be rejected if its actual capacity is slightly smaller.
Run the platform’s SMART checks and an appropriate self-test on every disk. TrueNAS documentation explains how to start a long HDD self-test in its CORE guidance and cautions that the uncertain age and condition of used drives matter. A passing test is evidence about the drive’s present condition, not a guarantee that it will survive the next day, a rebuild, or years of service. TrueNAS documentation states: “Hard drives and solid-state drives (SSDs) have a finite lifetime and can fail unexpectedly.”
Rank #2
- Secure private cloud - Enjoy 100% data ownership and multi-platform access from anywhere
- Easy sharing and syncing - Safely access and share files and media from anywhere, and keep clients, colleagues and collaborators on the same page
- Automated Backup Protection - Set-and-forget backups for Macs, PCs and mobile devices to multiple destinations including cloud and external drives
- Home Security System - Record and monitor your property 24/7 with support for multiple IP cameras and remote viewing
- 2-Year Warranty - Reliable hardware backed by Synology's expert customer support team and ongoing software updates
Confirm physical compatibility
Count available SATA, SAS, USB, or other connections and check that the controller supports the drives. An adapter or SATA controller card is relevant only if the machine lacks suitable ports or connectivity; it is not automatically required. Do not assume mixed models are interchangeable. TrueNAS hardware guidance discusses conventional magnetic recording (CMR) and shingled magnetic recording (SMR) media and advises checking the drive manufacturer to identify which technology a disk uses.
Choose the platform before choosing the layout
| Platform | What it provides | Best fit | Decisions to verify |
|---|---|---|---|
| Linux software RAID with mdadm | Kernel-managed arrays with documented levels and operations | A Linux host where you want the operating system to manage the block-level array | Supported RAID level, component size, filesystem choice, boot arrangement, monitoring, and replacement procedure for your distribution |
| TrueNAS with ZFS | Pools built from VDEVs, including mirrors and RAIDZ layouts, with integrated health and replacement workflows | A dedicated storage system where pool management, alerts, and data services are central | The stable TrueNAS release, VDEV layout, drive visibility, replacement capacity, scrub and alert schedules, and expansion behavior |
These systems are not interchangeable. An mdadm array is not a ZFS pool, and a ZFS VDEV should not be assembled as though it were an mdadm component. Pick one platform, read its current documentation for the stable release you are running, and follow that platform’s creation and recovery workflow.
Select a layout from capacity, failures, and workload
Start with the failure you can afford
Decide how many simultaneous member failures you need to tolerate and how quickly you can obtain a replacement. A two-drive mirror is simple to understand, while parity layouts require more drives and a rebuild or resilver after replacement. If you cannot maintain a backup or replace a failed disk promptly, no layout is a safe home for irreplaceable data.
Account for unequal drives
With differently sized disks, the smallest usable member commonly sets the size available from every member. For example, adding a larger disk to a group of smaller disks does not make the existing members larger. The unused portion may be unavailable to the current array unless the platform offers a separate, supported design for it. Plan from the smallest reported capacity and verify the result shown by the platform before committing.
Match the layout to the workload
Striping can aggregate devices but has no redundancy. Mirroring keeps a copy on another member and is often easier to recover. Parity arrangements trade capacity and write complexity for redundancy. Actual performance depends on the platform, controller, drive type, queue depth, filesystem, and workload, so do not rely on a generic ranking. Prioritize a layout that meets your failure and capacity requirements, then validate it with the monitoring and recovery tools your platform supports.
Rank #3
- High-Speed Data Transmission: The D4-320 hard drive enclosure (a DAS, NOT a NAS) utilizes the USB 3.2 Gen2 protocol, achieving high-speed data transmission of up to 10Gbps. When equipped with four hard drives, the actual read/write speed can reach up to 1,016 MB/s (combined read/write with four SATA III HDDs of 8TB each). With just one SSD installed, the read speed effortlessly reaches 510 MB/s (SATA III 1TB SSD). The D4-320 supports a single HDD up to 30TB, with a total capacity of 120TB, and is compatible with various hard drives, including 3.5-inch SATA hard drives, 2.5-inch SATA hard drives, and 2.5-inch SATA SSDs
- Plug-and-Play Compatibility: The D4-320 USB storage supports 4 individual disks (NO RAID function), and is plug-and-play, eliminating the need for drivers. It is highly compatible with MAC, Windows, and Linux operating systems. The USB Type-C interface supports various computer interfaces, including USB 3.0, USB 3.1, USB 3.2, Thunderbolt 3, and Thunderbolt 4
- Hot Swappable Convenience: The D4-320 HDD enclosure supports hot swapping, allowing users to replace hard disks without powering off the device. This feature enhances convenience and efficiency in data transfer processes
- Tool-Free Hard Drive Management: Featuring a tool-free hard drive tray design, the D4-320 external HDD enclosure enables easy installation and removal of hard drives without requiring additional tools. Furthermore, the D4-320 incorporates TerraMaster's unique Push-lock design, automatically securing the hard drive tray upon insertion, preventing the hard drive from falling out or disconnecting
- Efficient Heat Dissipation and Quieter Operation: The D4-320 direct attached storage incorporates an intelligent temperature-controlled fan for optimal heat dissipation. Additionally, specialized sound-absorbing panels and vibration damping measures contribute to a quieter operation, with noise levels reduced by up to 50% compared to the previous generation. In standby mode, the noise level drops below 21 dB(A), creating a remarkably quiet user environment
A safe build workflow
- Inventory and identify. Label the physical drives with their serial numbers or another unambiguous identifier. Match each label to the operating system’s device list and confirm that all intended members are present.
- Back up and verify. Copy valuable data to independent storage. Test the backup by opening files or performing a restore of representative data.
- Test drive health. Review SMART information and run a suitable short or long self-test according to the platform’s documentation. Record warnings, pending sectors, uncorrectable errors, and failed tests. Do not treat a clean result as a lifetime guarantee.
- Choose one platform and release. Decide whether Linux mdadm or TrueNAS/ZFS will own the storage. For TrueNAS, identify the stable release before following interface directions because development and version-specific documentation can differ.
- Model the layout. Write down the number of drives, the smallest usable capacity, expected usable space after redundancy, and the number of failures you intend to tolerate. Check that the chosen platform supports the layout with your drive count.
- Recheck destructive selections. Before clicking a create, initialize, or wipe action, compare the selected serial numbers with your inventory. Remove any disk that still contains the only copy of important data.
- Create the array or pool using the platform’s current procedure. The exact screens and commands vary by distribution, controller, and TrueNAS release; do not apply an mdadm procedure to ZFS or vice versa. Allow initialization, synchronization, or other preparation to finish as the platform indicates.
- Create the storage layer. On Linux, create and mount a filesystem appropriate to the array. In TrueNAS, create the required dataset or sharing configuration after the pool is online. Set permissions and verify that a test file can be written, read, and deleted as intended.
- Enable monitoring. Configure health alerts, scheduled SMART tests, and integrity checks or scrubs where supported. Make sure alerts reach an account or device that someone actually watches.
- Document recovery. Save the layout, member serial numbers, platform version, filesystem or dataset names, and backup location. This information reduces the chance of selecting the wrong disk during an emergency.
Linux mdadm: details that affect old-drive arrays
The mdadm manual documents multiple RAID levels and operations, but it does not make one layout correct for every Linux machine. Confirm that your distribution’s mdadm version and boot process support the level you select. Decide whether the array will contain the operating system, data only, or both; a boot arrangement may require additional devices or configuration that is separate from the data array.
mdadm ordinarily derives the component size from the smallest member. A replacement drive can be refused when its actual size is even slightly smaller than the original, despite both devices carrying the same rounded capacity on their labels. Keep a record of the component size and leave room for platform-specific metadata where required.
After creation, verify that the array reports the expected members and state before placing production data on it. During a rebuild, monitor progress and errors and avoid unnecessary reboots or drive removal. Do not replace a second member until the array has returned to its healthy state and your backup is current.
TrueNAS and ZFS: pools, VDEVs, replacement, and resilvering
Build the pool with the right VDEV layout
TrueNAS groups disks into VDEVs, and the pool’s usable capacity and fault tolerance come from those VDEVs. A VDEV is limited by the usable capacity of its smallest attached device. Choose mirrors, RAIDZ1, RAIDZ2, or another supported arrangement based on drive count and the failures you need to survive. Once a VDEV is part of a pool, changing the design is not the same as changing a single disk.
Replace a failed member carefully
TrueNAS’s replacement workflow wipes the replacement disk. Confirm the failed member and the replacement’s serial number before starting. The replacement must have capacity equal to or greater than the failed member according to the documented workflow. After the disk is accepted, TrueNAS resilvers the pool by reconstructing the necessary data.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #4
- 【Reliable External Storage System for Individuals and business】The 3.5 hard drive enclosure supports 2.5/3.5 inches HDD and SSD, max capacity up to 20TB for each hard drive, it's a ideal external hard drive enclosure for personal or enterprise using.Save space on your desktop or laptop.
- 【No heat】The sata enclosure built in Aluminum-Alloy materials and 2 inch Fan.Maximize the security of your data.Fan noise is around 40-50 decibels, not recommended if you are very sensitive to noise.
- 【Up to 5Gbps】This dual bay enclosure equips with advanced chips and USB 3.0 output interface.Transfer 1G files in 3-5 seconds with USB 3.0 Ports, which is 10 times faster than USB 2.0.
- 【Hot Swappable Convenience】The HDD enclosure supports hot swapping, allowing users to replace hard drives without powering off the device. This feature enhances convenience and efficiency in data transfer processes.
- 【Tool-Free Installation】Featuring a tool-free hard drive tray design, the external hard drive enclosure enables easy installation and removal of hard drives without requiring additional tools. Plug and play! No fuss, no muss!
Resilvering can take a long time when a pool contains a large amount of data. Watch the pool’s health and alerts, and wait for the resilver to finish before replacing another disk. Replacing members while redundancy is still reduced increases exposure to another failure.
Understand expansion choices
Adding a new VDEV, replacing every member with larger drives, and extending a RAIDZ VDEV are different operations. Current TrueNAS documentation describes RAIDZ extension as rewriting data across the new configuration while maintaining the RAIDZ fault-tolerance level. The pool should be healthy before extension begins. Existing data blocks retain their original data-to-parity ratio until they are rewritten, so the immediately available space and long-term distribution may differ from a newly created layout. Verify these version-sensitive behaviors against the stable TrueNAS release you use.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to do when a disk starts failing
- Act on alerts promptly. Record the affected serial number and confirm which physical disk it represents.
- Check the backup first. Make sure an independent copy of important files is available before beginning a replacement.
- Do not keep testing a visibly failing member unnecessarily. Follow the platform’s documented offline, detach, and replacement process.
- Use an equal-or-larger replacement where required. Compare actual reported capacity, not rounded retail size.
- Monitor the rebuild or resilver. Investigate new read errors, a stalled operation, or a pool that remains degraded.
- Wait for healthy status. Do not start another replacement until the platform reports that redundancy has been restored.
Troubleshooting common problems
The platform sees fewer drives than expected
Power down and check cabling, backplanes, adapters, and controller compatibility. Confirm that the controller exposes the disks individually rather than presenting an unsupported hardware abstraction. Recheck serial numbers after reconnecting because device order can change.
The larger disk contributes less space than expected
This is usually the smallest-member rule. Review the actual capacity reported by every member and the platform’s component or VDEV size. The unused portion of a larger disk may not be usable in the existing layout.
A replacement disk is rejected
Compare its exact reported capacity with the failed member and check sector-size, interface, and platform requirements. A disk sold under the same nominal capacity can be marginally smaller. Use a genuinely equal-or-larger compatible device.
Best Value
- Entry-level NAS Personal Storage：UGREEN NAS DH2300 is your first and best NAS made easy. It is designed for beginners who want a simple, private way to store videos, photos and personal files, which is intuitive for users moving from cloud storage or external drives and move away from scattered date across devices. This entry-level NAS 2-bay perfect for personal entertainment, photo storage, and easy data backup (doesn't support Docker or virtual machines).
- Set Your Devices Free, Expand Your Digital World: This unified storage hub supports massive capacity up to 64TB.*Storage drives not included. Stop Deleting, Start Storing. You can store 22 million 3MB images, or 2 million 30MB songs, or 43K 1.5GB movies or 67 million 1MB documents! UGREEN NAS is a better way to free up storage across all your devices such as phones, computers, tablets and also does automatic backups across devices regardless of the operating system—Window, iOS, Android or macOS.
- The Smarter Long-term Way to Store: Unlike cloud storage with recurring monthly fees, a UGREEN NAS enclosure requires only a one-time purchase for long-term use. For example, you only need to pay $459.98 for a NAS, while for cloud storage, you need to pay $719.88 per year, $2,159.64 for 3 years, $3,599.40 for 5 years. You will save $6,738.82 over 10 years with UGREEN NAS! *NAS cost based on DH2300 + 12TB HDD; cloud cost based on 12TB plan (e.g. $59.99/month).
- Blazing Speed, Minimal Power: Equipped with a high-performance processor, 1GbE port, and 4GB RAM on Board, this NAS handles multiple tasks with ease. File transfers reach up to 125MB/s—a 1GB file takes only 8 seconds. Don't let slow clouds hold you back; they often need over 100 seconds for the same task. The difference is clear.
- Let AI Better Organize Your Memories: UGREEN NAS uses AI to tag faces, locations, texts, and objects—so you can effortlessly find any photo by searching for who or what's in it in seconds. It also automatically finds and deletes similar or duplicate photo, backs up live photos and allows you to share them with your friends or family with just one tap. Everything stays effortlessly organized, powered by intelligent tagging and recognition.
The pool or array is degraded after a drive alert
Identify the failed member by serial number, confirm your backup, and begin the supported replacement process. Avoid destructive commands or pool recreation merely to clear an alert; recreating a stripe or pool can erase the remaining data.
You are considering RAID 0 for valuable files
Do not use a stripe as the only copy of important data. One failed member makes the array unavailable and, in TrueNAS, requires recreating the pool and restoring from backup.
Maintenance after the array is online
Schedule SMART tests and platform integrity checks, review alerts, and keep replacement hardware plans current. Periodically test restoring files from the independent backup. Revisit capacity before the array fills: expansion paths differ between mdadm and ZFS, and a healthy pool may be a prerequisite for a RAIDZ extension. Keep the platform updated according to its release guidance, but do not begin a version-sensitive expansion or replacement without checking the documentation for that exact stable version.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsFinally, document who responds to an alert, where replacement drives are stored, and how to restore data if the array cannot be recovered. RAID is most useful when it reduces downtime without becoming the only place your data exists.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
