Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Choose JBOD when you mainly need to combine or expose available disks, can tolerate losing the data on a failed disk, and maintain an independent backup. Choose a redundant RAID layout when the storage must remain available after a specified disk failure. RAID 0 is not redundant, and no RAID level replaces a separate backup.
The practical choice depends on your enclosure or NAS model, drive count and sizes, workload, expansion plans, and recovery process. The labels are not perfectly universal: “JBOD” can mean individual-disk pass-through in one controller and a concatenated volume in another.
What RAID and JBOD actually do
JBOD: capacity or individual disks, not automatic protection
JBOD commonly means “just a bunch of disks,” but products implement it in different ways. A pass-through enclosure presents each disk separately to the operating system. A NAS may instead concatenate disks into one logical storage space. In either case, JBOD itself does not calculate parity or maintain a second copy of data.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →For example, Synology’s storage guidance describes its JBOD option as combining drives into one storage space with usable capacity equal to the sum of the drive sizes and no data redundancy. The Seagate NAS OS 4 manual is more specific to that product: disks are filled sequentially, and data stored on a failed disk is lost. Those descriptions should not be generalized to every controller; check the documentation for your exact system.
#1 Best Overall
- IronWolf internal hard drives are the ideal solution for up to 8-bay, multi-user NAS environments craving powerhouse performance
- Store more and work faster with a NAS-optimized hard drive providing ultra-high capacity up to 16TB and cache of up to 256MB
- Purpose built for NAS enclosures, IronWolf delivers less wear and tear, little to no noise/vibration, no lags or down time, increased file-sharing performance, and much more
- Easily monitor the health of drives using the integrated IronWolf Health Management system and enjoy long-term reliability with 1M hours MTBF
- Three-year limited warranty protection plan included and three year Rescue Data Recovery Services included
RAID: a family of layouts
RAID distributes data, copies, or parity information across multiple drives according to a level. Some levels improve availability after a disk failure; others only increase throughput or combine capacity. “RAID” by itself therefore says nothing about how many failures are tolerated, how much space is usable, or whether a rebuild is possible.
Usable capacity is determined by the RAID level, the smallest member drive, parity or mirror overhead, filesystem metadata, and the implementation’s rules. A vendor’s calculator or storage manager is more reliable than a generic formula, especially when mixing drive sizes.
RAID levels compared with JBOD
| Setup | How data is arranged | Drive-failure tolerance | Capacity trade-off | When it fits |
|---|---|---|---|---|
| JBOD (implementation-specific) | Individual disks or a concatenated volume; no parity or mirror supplied by JBOD itself | None inherent. In Seagate NAS OS 4, data on a failed disk is lost. | Synology reports the sum of drive sizes for its JBOD implementation; other products may expose disks separately. | Independent disks, maximum pooled capacity, scratch data, or data that exists elsewhere. |
| RAID 0 | Blocks are striped across all members | None. One failed member can make the array inaccessible. | Most raw capacity is available, but every disk is a dependency. | Re-creatable temporary data where speed matters more than availability. |
| RAID 1 | Each block is mirrored to another drive | The cited Seagate implementation keeps data available after one drive fails. | Usable capacity is approximately one drive in a two-way mirror, before filesystem overhead. | Small arrays needing straightforward redundancy and simple recovery. |
| RAID 5 | Data and single distributed parity are striped | One failed drive in the cited implementation; a second failure before recovery can lose the array. | One drive’s worth of parity reduces usable capacity. | Capacity-efficient redundancy when the enclosure supports it and rebuild risk is acceptable. |
| RAID 6 | Data and double distributed parity are striped | Two failed drives in the cited implementation. | Two drives’ worth of parity reduces capacity and adds write overhead. | Larger arrays where surviving a second failure is important. |
| RAID 10 | Mirrored pairs or groups are striped together | Depends on which members fail: failures in separate mirrors may be survived, while losing both members of one mirror is fatal. | Roughly half of raw capacity is usable, subject to implementation. | Workloads needing mirror-style protection and strong random-I/O behavior. |
| ZFS mirror or RAID-Z | ZFS manages mirrors or parity groups and verifies data with checksums | Depends on mirror width or RAID-Z parity level. | Varies with vdev layout, parity level, and drive sizes. | Systems where ZFS should manage redundancy, integrity checking, and repair directly. |
The minimum disk counts and supported levels are device-specific. In the Seagate NAS OS 4 documentation, RAID 5 requires at least three drives and RAID 6 at least four; available modes depend on the number of installed drives. Treat those as NAS OS 4 requirements, not universal RAID rules.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchDoes JBOD protect your data?
No—not against a drive failure in the usual NAS meanings of JBOD. If a disk fails, files stored on that disk are unavailable. With a concatenated volume, the failure may also make the entire logical volume inaccessible even though the other physical disks are healthy. With pass-through JBOD, other disks may remain independently mountable, but the failed disk’s data still needs restoration from backup.
JBOD can be reasonable when each disk contains replaceable or replicated data, when you deliberately want separate volumes, or when you are using software above the disk layer to provide redundancy. Before selecting it, determine whether your product means pass-through or concatenation and how the filesystem reacts to a missing member.
Is RAID 0 redundant?
No. RAID 0 stripes each file across multiple drives without a mirror or parity copy. It can improve parallel throughput and presents combined capacity, but one failed member removes part of every striped file. Use it only for data that can be recreated or restored quickly from another copy.
RAID 0 is sometimes confused with “zero redundancy” only after the fact; the name is not a safety rating. A fast array used for a working set still needs a backup or source copy.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
- Store more, compute faster, and do it confidently with the proven reliability of BarraCuda internal hard drives
- Build a power house gaming computer or desktop setup with a variety of capacities and form factors
- The go to SATA hard drive solution for nearly every PC application from music to video to photo editing to PC gaming. Ax. Sustained transfer rate OD: 190MB/s
- Confidently rely on internal hard drive technology backed by 20 years of innovation
- Frustration Free Packaging - This is just an anti-static bag. No cables, no box.
How to choose: a decision process
- Classify the data. Decide whether the files are replaceable, reproducible, or unique. A media cache and a family archive should not have the same failure policy.
- Set the availability requirement. Ask how long the service may be offline and whether one or two failed disks must be survivable without restoring from backup.
- Count compatible drive bays. Confirm the enclosure’s supported RAID levels and minimum disk count. Do not assume an empty bay can be added later without a migration or rebuild.
- Record drive sizes and models. Many implementations base the array on the smallest member, wasting the excess on larger disks. Check whether unequal sizes are accepted and how capacity is allocated.
- Match the workload. Large sequential files, virtual machines, databases, surveillance recording, and many small random writes stress layouts differently. Controller, drives, filesystem, cache, and rebuild state all affect results.
- Plan replacement and recovery. Keep a compatible spare or a purchasing plan, monitor drive health, and document the procedure for replacing a failed member and verifying the rebuild.
- Verify the backup. A redundant array is still one system. Confirm that an independent copy can be restored, including permissions and application data.
Capacity, mixed-size disks, and expansion
Capacity is not simply “number of drives multiplied by the biggest drive.” Mirrors reserve copies, parity reserves space, and many arrays effectively use only the smallest member size. For example, placing a larger disk beside smaller members may leave part of its capacity unused until every member is replaced or the product supports a separate expansion scheme.
Expansion rules vary sharply. Some NAS systems can replace disks one at a time and expand after the rebuild; others require creating a new pool, adding a complete disk group, or migrating data. RAID 10 generally needs a supported number of mirrored members, while RAID 5 and RAID 6 have their own minimums and expansion constraints. Read the model’s storage-manager documentation before buying drives, not after the array is full.
Mixed interfaces, sector formats, rotational speeds, and recording technologies can also affect compatibility and performance. Verify drive form factor, interface, maximum supported capacity, sector-size support, and the enclosure’s compatibility list. A drive that fits mechanically may still be unsupported or unsuitable for the workload.
Performance and rebuild behavior
There is no universal performance winner. Striping can raise sequential throughput; mirroring can serve reads from multiple copies; parity layouts add calculation and write-modification work; and JBOD may avoid parity overhead while providing no protection. The actual result depends on queue depth, file size, concurrency, network speed, controller, filesystem, cache policy, and the drives themselves.
Rebuilds are a separate operating state. A redundant array may remain online while reconstructing a replacement disk, but performance can fall and the surviving members are read intensively. A second failure during a RAID 5 rebuild, for example, exceeds the single-failure tolerance described in the Seagate implementation. RAID 6 provides a second-failure margin there, at the cost of more parity and capacity overhead.
The Seagate manual notes that synchronization time and performance depend on configuration and available resources. Schedule rebuilds with enough power and cooling, avoid unnecessary heavy workloads during synchronization, and do not treat an array as fully protected until the rebuild and post-rebuild health checks complete.
RAID is not a backup
RAID addresses selected disk-failure scenarios; it does not protect against accidental deletion, ransomware, fire, theft, filesystem mistakes, controller failure, or a bad synchronization that propagates corrupted data. A mirrored deletion is still deleted on every mirror. A parity array can preserve availability while silently retaining an application-level mistake.
Rank #3
- IronWolf internal hard drives are the ideal solution for up to 8-bay, multi-user NAS environments craving powerhouse performance.date transfer rate:6.0 gigabits_per_second
- Store more and work faster with a NAS-optimized hard drive providing 8TB and cache of up to 256MB
- Purpose built for NAS enclosures, IronWolf delivers less wear and tear, little to no noise/vibration, no lags or down time, increased file-sharing performance, and much more
- Easily monitor the health of drives using the integrated IronWolf Health Management system and enjoy long-term reliability with 1M hours MTBF
- Three-year limited product warranty protection plan and three year Rescue Data Recovery Services included
Maintain at least one independent backup, preferably with a copy that is not continuously writable from the production system. The Seagate NAS OS 4 documentation specifically recommends backing up to a direct-attached storage device or another NAS. Test restores rather than merely checking that backup jobs report success.
- Keep backup media or a destination independent of the primary enclosure.
- Use versioning or snapshots where appropriate so older, uncorrupted copies remain available.
- Encrypt off-site or portable copies and protect recovery credentials.
- Perform a representative file restore and, for critical systems, a full service recovery test.
When ZFS changes the JBOD-versus-RAID question
With ZFS, presenting individual disks to the operating system does not mean accepting unprotected storage. ZFS can build mirrors or RAID-Z vdevs, checksum data and metadata, and repair bad data from a known-good copy when redundant copies exist. Its concepts documentation states: “While ZFS supports running in a non-redundant configuration, where each root vdev is simply a disk or file, this is strongly discouraged.”
ZFS redundancy is managed by ZFS, not by placing a conventional hardware RAID volume underneath it. The project’s hardware guidance says, “Hardware RAID controllers should not be used with ZFS,” because a controller can hide individual-drive information, limit self-healing opportunities on checksum failures, and mishandle sector-size information. The guidance also identifies controller replacement and write-cache failure as concerns. This is ZFS project advice for ZFS deployments, not a universal claim that every hardware RAID controller is unsuitable for every operating system.
For a ZFS build, give ZFS direct disk access as recommended by OpenZFS hardware documentation, then select mirrors or the RAID-Z level that matches your required failure tolerance and capacity. A non-redundant ZFS pool still needs a separate copy and carries corruption risk that redundancy could have helped repair. The storage concepts are documented at OpenZFS zpoolconcepts(7).
Practical setup checklist
Before creating the array or pool
- Update the enclosure or NAS firmware and confirm the exact model’s supported layouts.
- Back up data that will be moved; creating or changing an array can erase disks.
- Confirm every drive is detected, has compatible sector format, and passes an initial health check.
- Choose a filesystem and encryption plan that your operating system and recovery tools support.
- Write down drive serial numbers and bay positions so a failed member is not removed accidentally.
During creation
- Open the product’s storage-management interface and select the documented RAID, JBOD, or pool option.
- Review the displayed usable capacity and failure tolerance before confirming. If the interface does not state these, stop and consult the model manual.
- Set alerting for drive failure, degraded status, temperature, and completed synchronization.
- Allow initialization or parity synchronization to finish; do not assume the array is protected immediately after creation.
- Create the backup job and perform a test restore before placing irreplaceable data on the new storage.
After a drive failure
- Confirm which bay and serial number the system reports as failed; do not pull a healthy member based only on physical position.
- Check whether the array is degraded, offline, or already rebuilding, and preserve logs for support.
- Install a compatible replacement meeting the enclosure’s size and interface requirements.
- Start the documented rebuild and monitor temperature, errors, remaining time, and backup status.
- After synchronization, run the system’s consistency or scrub check and verify that important files can be opened or restored.
Common mistakes and better choices
“I want all capacity, so I will use JBOD.”
That is acceptable only when the data can be restored elsewhere and you understand whether one disk failure affects one volume or the whole concatenated space. If uninterrupted access matters, use a supported redundant layout instead.
“RAID means my files are backed up.”
It does not. Add an independent, tested backup with retention that covers accidental deletion and other site or system failures.
“RAID 5 is always the best compromise.”
RAID 5’s single-failure tolerance may fit a small, well-monitored array, but the rebuild window and a second failure can be unacceptable for larger or critical pools. Compare RAID 6, mirrors, RAID 10, and the product’s actual rebuild behavior.
Rank #4
- Available in capacities ranging from 2 to 22TB(1) | (1) 1GB = 1 billion bytes and 1TB = 1 trillion bytes. Actual user capacity may be less depending on operating environment.
- For RAID-optimized NAS systems with unlimited number of bays
- Rated for 550TB/yr workload rate(2) | (2) Annualized Workload Rate = TB transferred x (8760 / recorded power-on hours). The maximum rated workload is specified for operating at typical temperature of 40C. Workload Rate will vary depending on your hardware and software components and configurations.
- Designed to handle the demands of high-intensity 24x7 multi-user NAS environments
- Western Digital partners with a wide range of NAS system vendors for extensive testing to ensure compatibility with most NAS enclosures
“I can mix any drives and expand whenever I want.”
Capacity, sector format, bay count, and expansion procedures are implementation-specific. Confirm them before purchase and keep enough free capacity for replacement and migration operations.
“A hardware RAID card is fine under ZFS.”
OpenZFS advises direct disk access and warns that hardware RAID can obscure information ZFS needs for checksumming and self-healing. Follow the project guidance for a ZFS deployment unless you have a documented, tested reason to do otherwise.
A concise selection guide
| Your priority | Likely starting point | Condition to verify |
|---|---|---|
| Maximum usable space and data already exists elsewhere | JBOD or individual disks | Confirm the product’s JBOD behavior and restore path. |
| Simple protection for a small number of drives | RAID 1 or a ZFS mirror | Accept the roughly one-drive capacity trade-off and verify supported mirror width. |
| Capacity-efficient protection with one failure tolerance | RAID 5 | Use only where the enclosure supports it and the rebuild risk is acceptable. |
| Protection against two concurrent drive failures | RAID 6 or an appropriate RAID-Z level | Check minimum disk count, parity overhead, and workload performance. |
| Mirrored protection with striping for demanding I/O | RAID 10 | Confirm supported disk count and understand which failure combinations are survivable. |
| Checksummed, software-managed integrity | ZFS mirror or RAID-Z with direct disks | Follow OpenZFS hardware guidance and maintain independent backups. |
Frequently Asked Questions
Can JBOD use different-size drives?
Some pass-through implementations can expose different-size disks independently, while a concatenated NAS volume may impose its own rules or waste unused space. Check the exact enclosure documentation; size mixing is not a universal JBOD capability.
What happens if a drive fails in RAID 1?
In the cited Seagate NAS OS 4 implementation, the mirrored copy keeps data available after one drive fails. The array remains degraded until a compatible replacement is installed and synchronization completes.
Should I choose RAID 5 or RAID 6?
Choose based on required failure tolerance, drive count, rebuild exposure, capacity loss, and workload. The cited Seagate implementation assigns one-drive tolerance to RAID 5 and two-drive tolerance to RAID 6; those are not substitutes for a tested backup.
Can ZFS run on a single disk?
Yes, but OpenZFS strongly discourages a non-redundant configuration because corruption can make data unavailable. Use a mirror or RAID-Z layout when you need ZFS to repair damaged data, and back up the pool independently.
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.
