Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Use JBOD when pooled or independent capacity is more important than surviving a disk failure and every important file exists in a separate backup. Use a redundant RAID level when the storage must remain available after a defined disk failure. RAID 0 is not redundant, and no RAID level replaces an independent backup. The right choice also depends on your enclosure, drive count, workload, expansion plans, and—if you use ZFS—whether the operating system has direct access to the disks.
The short answer
RAID and JBOD solve different problems. JBOD (“just a bunch of disks”) can expose disks individually or combine them into one larger namespace, depending on the enclosure or software. In the Synology NAS implementation described in its RAID guidance (updated May 20, 2026), JBOD combines drives into one storage space, reports capacity as the sum of the drive sizes, and provides no drive-failure redundancy. Seagate’s NAS OS 4 documentation describes a different but related behavior: disks are filled sequentially, and data on a failed disk is lost. Those are product implementations, not a universal definition of every JBOD mode.
As an Amazon Associate I earn from qualifying purchases.
RAID is a family of layouts rather than a single protection setting. RAID 1, RAID 5, RAID 6, and RAID 10 add different forms of redundancy; RAID 0 only stripes data for capacity and performance. A redundant array can keep services online after a qualifying failure, but it cannot restore deleted files, protect against ransomware, or guarantee recovery from controller, enclosure, network, fire, theft, or user errors. Keep a separate backup regardless of the layout.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems| Choose this | When it fits | Main warning |
|---|---|---|
| JBOD | You need to use available disk capacity, can accept a disk-specific outage, and maintain another copy of important data. | There is no inherent drive-failure protection in the cited NAS examples; behavior varies by product. |
| RAID 0 | A temporary workspace where speed and aggregate capacity matter more than keeping data after a disk failure. | One failed member can make the array inaccessible. It is not redundant. |
| RAID 1 | A small array where straightforward mirroring and one-drive availability matter. | Usable capacity has mirroring overhead, and the enclosure must support the level. |
| RAID 5 | Capacity-efficient redundancy in an implementation that supports at least three disks. | It tolerates one failed disk in the cited Seagate implementation; a second failure before recovery can lose the array. |
| RAID 6 | More failure tolerance in an implementation that supports at least four disks. | Double parity consumes more capacity and can add write or rebuild cost. |
| RAID 10 | A supported multi-disk layout combining mirrored groups with striping. | Survival depends on which members fail, and mirroring reduces usable capacity. |
| ZFS mirror or RAID-Z | You want filesystem-managed checksums and repair from redundant copies. | Give ZFS direct disk access; do not hide disks behind hardware RAID. |
What JBOD actually means
Two common implementations
In a pass-through or controller mode, JBOD presents each physical disk to the operating system as a separate device. The operating system, filesystem, volume manager, or ZFS can then decide how to use those disks. This is useful when you want software rather than a hardware controller to manage pools, filesystems, or redundancy.
#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
In a NAS-specific concatenated mode, the appliance may present several disks as one storage space. The implementation determines how data is placed. Synology describes its JBOD option as combining drives into a single space without redundancy. Seagate NAS OS 4 says its JBOD mode fills disks sequentially. If a disk holding files fails, those files are lost; depending on the volume design, the remaining space may also become unavailable. Read the exact manual for your enclosure before assuming that “JBOD” means independent disks.
What JBOD is good at
- Using disks that do not form a supported redundant set.
- Creating a large namespace when a single-disk loss is acceptable.
- Keeping disks available for another software layer, such as ZFS, that will manage redundancy itself.
- Avoiding parity or mirror capacity overhead when the authoritative copy exists elsewhere.
What JBOD cannot promise
- Automatic recovery when a drive dies.
- Protection from accidental deletion, malware, filesystem corruption, or a damaged enclosure.
- Uniform behavior across NAS brands, operating systems, host bus adapters, or volume managers.
- Continuous access to every file after a disk failure.
Before creating a JBOD volume, identify whether the device uses independent-disk presentation, concatenation, or another vendor-specific scheme. Record which data resides on which disk if the system exposes disks separately, and test how the appliance reports a removed or failed member.
How the principal RAID levels differ
RAID 0: striping without redundancy
RAID 0 writes parts of each stripe across multiple disks. That can combine capacity and improve parallel I/O for suitable workloads, but every member is required to reconstruct the striped data. If one disk fails, the array can become inaccessible. Seagate’s NAS OS 4 manual explicitly describes RAID 0 as lacking drive-failure protection. Use it only for data that can be recreated or restored from another copy, such as a scratch workspace; never call it a protective RAID level.
Outdated 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 matchWindows 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 reinstallRAID 1: mirrored copies
RAID 1 writes the same data to mirrored members. In the cited Seagate implementation, data remains available on another drive after one drive fails. The trade-off is capacity: the usable space is limited by the mirror arrangement rather than the sum of all raw disks. Replacing a failed member requires a rebuild, and the array remains exposed to another failure or an unrelated incident until recovery completes.
RAID 5: single parity
RAID 5 distributes data and one parity set across the members. Seagate’s documentation requires at least three drives and describes tolerance of one failed drive. It offers more usable capacity than a full mirror for a given raw disk set, but a second member failure before the rebuild finishes can make the array unrecoverable. Actual rebuild time, write behavior, and expansion rules depend on the controller, drives, filesystem, and workload.
RAID 6: double parity
RAID 6 stores two independent parity sets. The cited Seagate manual requires at least four drives and describes tolerance of two failed drives. That extra tolerance consumes more capacity and generally creates more parity work, particularly for writes and rebuilds. It is a choice for larger arrays or environments where another disk may fail while the first replacement is being rebuilt, provided the enclosure supports it.
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.
RAID 10: mirrored groups with striping
RAID 10 stripes data across mirrored pairs or groups. It can provide strong read/write behavior for workloads that benefit from parallel disks while retaining mirror copies. Failure tolerance is positional: two failed drives may be survivable if they are in different mirror groups, but two failures in the same group can take the array offline. The required disk count and supported layouts are device-specific.
Vendor terminology is not a universal contract
The Seagate descriptions above apply to NAS OS 4, not to every RAID controller. Synology notes that supported RAID types vary by device model. A device may restrict levels by bay count, drive size, firmware, or expansion method. Treat the enclosure’s current documentation and management interface as authoritative for what can be created, expanded, migrated, or repaired.
Capacity, failure tolerance, and performance trade-offs
Raw capacity is not the same as usable capacity. Mirrors reserve space for duplicate copies; parity reserves space for recovery information; filesystems and metadata consume additional space; and a mixed-size set may be constrained by the smallest member or by the vendor’s allocation rules. Do not promise a final usable figure until the RAID level, number and sizes of disks, filesystem, and implementation are known.
| Setup | Capacity behavior | Disk-failure behavior | Performance and operations |
|---|---|---|---|
| JBOD | Synology reports the sum of drive sizes for its JBOD implementation; other systems may concatenate or expose disks individually. | No inherent redundancy in the cited NAS examples; data on a failed disk is lost in Seagate NAS OS 4. | Sequential placement, pooling, or pass-through behavior varies. Expansion and removal rules are product-specific. |
| RAID 0 | Combines member capacity through striping. | No tolerated member failure. | Parallel I/O can help some workloads; rebuild protection does not exist. |
| RAID 1 | Mirror overhead leaves less usable space than the raw total. | One failed member remains available in the cited implementation. | Simple recovery model; rebuild load and speed depend on hardware and data volume. |
| RAID 5 | One parity allocation reduces usable capacity. | One failed member in the cited implementation. | Parity writes and rebuilds affect performance; a second failure during recovery is dangerous. |
| RAID 6 | Two parity allocations reduce usable capacity further. | Two failed members in the cited implementation. | More parity and rebuild work in exchange for additional tolerance. |
| RAID 10 | Mirrored groups consume capacity, while striping uses the groups in parallel. | Depends on the locations of failed members. | Often chosen for mixed read/write workloads when the device supports the required disk count. |
| ZFS mirror/RAID-Z | Capacity and parity level are determined by the vdev layout and disk set. | Redundancy depends on mirror or RAID-Z design. | Checksums, scrubbing, and self-healing require ZFS-managed redundant copies and direct disk visibility. |
No cited documentation establishes a universal performance winner. Controller cache, interface speed, disk type, queue depth, filesystem, record size, concurrent users, and rebuild state can change the result. Benchmark the actual workload if latency or throughput is a requirement.
RAID is not a backup
RAID handles a narrower event: a qualifying disk failure while the array remains otherwise healthy. It does not create an independent historical copy. A mistaken deletion is duplicated across mirrors and parity; ransomware can encrypt every accessible member; a failed controller or power event can affect the whole enclosure; and theft, fire, water, or a network compromise can remove both the array and its files.
Seagate’s NAS OS 4 guidance recommends backing up to a direct-attached storage device or another NAS. Keep at least one backup independent of the array, verify that it can be restored, and consider an offline or geographically separate copy for irreplaceable data. Decide what recovery point and recovery time you need before selecting a layout: a mirror may keep a service online, while a backup is what lets you recover an earlier or clean version.
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
How ZFS changes the RAID-versus-JBOD decision
JBOD can be a presentation mode for ZFS
With ZFS, “JBOD” may mean passing individual disks through to the operating system so ZFS can create mirrors or RAID-Z vdevs. In that context, the disks are not the final protection scheme; the ZFS pool layout is. A pool of single-disk root vdevs is non-redundant even though ZFS is managing the devices.
Checksums and self-healing require redundancy
OpenZFS documents that data and metadata are checksummed. When a pool has mirror or RAID-Z redundancy, ZFS can use a good copy to repair data that fails a checksum check. The project’s zpoolconcepts documentation cautions: “While ZFS supports running in a non-redundant configuration, where each root vdev is simply a disk or file, this is strongly discouraged.” A non-redundant pool cannot reconstruct corrupted data when the only copy is bad.
Do not put hardware RAID underneath ZFS
OpenZFS’s hardware guidance states: “Hardware RAID controllers should not be used with ZFS.” The concern is specific to ZFS’s design: a controller can hide which disk returned bad data, limit self-healing opportunities, fail to pass sector-size information correctly, and introduce controller-replacement or write-cache risks. Use a suitable HBA or direct-disk path that lets ZFS see and manage the drives. This is project guidance for ZFS, not a blanket claim that every hardware RAID product is unsuitable for every non-ZFS workload.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A step-by-step method for choosing
- List the data and its recovery requirement. Separate replaceable scratch files, shared working data, backups, and irreplaceable records. Decide whether the system must stay online during one or more disk failures.
- Count bays and record each disk. Note capacity, interface, sector format, age, and health. Check whether the enclosure accepts mixed sizes and how it allocates them.
- Read the exact device documentation. Confirm supported RAID levels, minimum disk counts, migration paths, expansion limits, hot-spare behavior, and what the vendor calls JBOD. Synology’s guidance emphasizes that supported types vary by model.
- Choose the failure tolerance first. If no disk failure may be tolerated, do not use JBOD or RAID 0 for the authoritative copy. Select a mirror, single-parity, double-parity, RAID 10, or ZFS layout that matches the number and arrangement of failures you can accept.
- Calculate usable capacity from the implementation. Include parity or mirror overhead, filesystem reservations, and the smallest-member constraint where applicable. Use the enclosure’s estimator rather than a generic online formula.
- Match the layout to the workload. Large sequential media, virtual machines, databases, backups, and many small files stress arrays differently. Treat performance claims as hypotheses until measured on the actual hardware.
- Plan replacement and rebuilds. Confirm compatible replacement-drive specifications, monitoring alerts, scrub or consistency-check procedures, and where a failed disk can be obtained. A redundant array is most vulnerable while rebuilding.
- Design the backup separately. Select a DAS, second NAS, cloud target, or offline rotation that is not dependent on the primary array. Perform a test restore before trusting the design.
- Document the final layout. Record slot order, serial numbers, RAID or ZFS topology, encryption keys, backup locations, and recovery steps. Store the record somewhere the failed enclosure cannot take offline.
Which setup fits common situations?
Two-bay home or small-office NAS
Choose a mirror when the files must remain available after one disk fails and the enclosure supports it. JBOD can make sense for non-critical, independently backed-up data when maximizing raw capacity matters more than continuity. RAID 0 is appropriate only for disposable or reproducible data.
Three or more disks with a capacity-sensitive shared volume
Single-parity RAID may offer a useful balance when the implementation supports it and one-disk tolerance is sufficient. Build a tested backup before storing the only copy there. If the consequence of a second failure during recovery is unacceptable, evaluate double parity or another layout instead of assuming RAID 5 is automatically safe.
Larger arrays or longer rebuild exposure
Double parity can provide two-disk tolerance in supported implementations. The extra protection costs usable capacity and parity work, so confirm that the workload and hardware can handle it. Keep monitoring enabled and replace marginal disks before they become a rebuild event.
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
High-I/O workloads
RAID 10 may suit workloads that benefit from mirrored groups and striping, provided the enclosure supports the required member count and you understand its positional failure tolerance. Do not infer a performance result from the name alone; test with representative reads, writes, queue depths, and concurrent users.
ZFS server or storage appliance
Present disks directly to ZFS and create a mirror or RAID-Z topology appropriate to the required tolerance. Avoid a non-redundant root-vdev design for important data, and follow OpenZFS’s hardware guidance rather than placing a hardware RAID virtual disk beneath the pool.
Expansion, mixed disks, and failure recovery
Expansion is not automatic
Some appliances can expand a pool by adding disks, replacing members with larger disks, or migrating between levels; others require a new volume or backup-and-restore cycle. A JBOD volume may not let you remove one disk without losing the combined namespace. RAID levels can impose fixed group sizes or require every member to be upgraded before extra capacity appears. Verify the exact procedure before buying a disk or starting a migration.
Mixed-size drives need explicit rules
Combining different capacities can leave part of a larger disk unused, limit the array to the smallest member, or be rejected by the enclosure. Interface compatibility, sector size, firmware, vibration ratings, and workload suitability matter in addition to the advertised terabytes. Use the vendor’s compatibility list and capacity calculator for the model you own.
What to do when a disk fails
- Confirm the alert and identify the physical slot or serial number; do not pull a healthy disk based only on an ambiguous indicator.
- Check the array or pool status and verify that a current backup is readable before making changes.
- Install a compatible replacement of the required size and interface, following the enclosure’s documented hot-swap or shutdown procedure.
- Start or approve the rebuild, then monitor errors, temperature, and remaining time. Avoid unnecessary heavy workloads while the array is degraded.
- After completion, run the platform’s consistency check or scrub and investigate any additional SMART, checksum, or filesystem errors.
For JBOD, replacement usually does not reconstruct the lost files because there is no redundant copy in the cited implementations. Restore those files from backup, recreate the volume if the appliance requires it, and reassess whether a pooled non-redundant design still matches the data’s importance.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Pre-deployment checklist
- Have you identified whether JBOD means pass-through, concatenation, or a vendor-specific pooled volume on this device?
- Is the selected RAID or ZFS layout supported with your exact bay count and drive sizes?
- How many simultaneous or positional disk failures must the data survive?
- What usable capacity remains after mirrors, parity, filesystem overhead, and reserved space?
- What happens to the volume if a disk is removed, not merely if it reports an error?
- Can you replace a failed member with a compatible drive quickly?
- Where is the independent backup, and when was the last restore test?
- For ZFS, do the disks reach the operating system directly without a hardware RAID virtual disk?
- Are alerts, scrubs or consistency checks, and capacity thresholds configured?
- Is the recovery procedure documented for someone who did not build the system?
Bottom line for your decision
Pick JBOD for capacity or independent-disk access only when you have accepted the loss scenario and maintain another copy. Pick RAID 1, 5, 6, or 10 according to the number and arrangement of failures you need to survive—not according to the word “RAID” alone. Never treat RAID 0 as protection, and never treat any RAID level as a backup. If ZFS is managing the pool, give it direct disk access and use its mirror or RAID-Z redundancy so checksums and self-healing can work as designed.
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.
