As of September 2026, ZimaOS documents JBOD as a current storage option again, so you should not replace a disabled historical JBOD button with RAID0 unless you understand the capacity and failure trade-offs. JBOD concatenates disks into one large volume, while RAID0 stripes data across disks. They are both non-redundant, but they behave very differently with mixed-size drives.
The December 2025 source thread captured a period when JBOD was greyed out and users were considering RAID0 as a workaround. Current ZimaOS documentation now lists JBOD explicitly, so the useful guide is how to choose and verify JBOD today.
JBOD and RAID0 Are Not the Same Thing
JBOD concatenates capacity from multiple disks into one volume. RAID0 stripes blocks across every member for speed. With unequal drives, RAID0 can waste capacity because the smallest member constrains the stripe geometry.
The screenshots used 2TB, 1TB, and 500GB NVMe drives. The raw total was roughly 3.5TB, but the RAID0 usable space shown was far lower. That is why RAID0 is a poor substitute when the goal is simply to use mixed-size capacity.
Current ZimaOS JBOD Behavior
The current ZimaOS RAID and JBOD guide defines JBOD as one continuous non-redundant volume and warns that a member failure can make the whole volume unusable.
When JBOD Makes Sense
- mixed-capacity disks;
- one namespace matters more than redundancy;
- the data already has another backup;
- you accept whole-volume risk if one member fails.
When RAID0 Is the Better Choice
Use RAID0 only when you deliberately want striping/performance and the data is disposable or backed up. Do not choose it merely because JBOD was historically unavailable.
How to Create Storage on Current ZimaOS
Update first, then open Settings → Storage → Combine and inspect the available layouts. The current ZimaOS storage setup guide explains the workflow.
If JBOD is still unavailable, record the ZimaOS version, disk models, connection type, and existing filesystems before wiping anything.
Protect Data Before Changing Layout
Creating a combined volume can require reformatting or metadata changes. Copy irreplaceable data elsewhere first. The backup planning guide is useful before restructuring the pool.
How Capacity Differs with Unequal Drives
With JBOD, a 2TB, 1TB, and 500GB set can contribute close to the sum of their usable capacities. With RAID0, usable capacity is normally constrained by the smallest member across the stripe set, so large drives can leave substantial space unused.
Always trust the capacity estimate shown by the current Storage wizard before clicking Create. If the number does not match your expectation, stop and verify the selected layout rather than assuming ZimaOS will recover the unused space later.
JBOD Is Not a Replacement for Backup
JBOD maximizes usable capacity, not resilience. Losing a member can damage files whose extents fall on that disk and can make the combined filesystem difficult or impossible to mount cleanly. Keep at least one independent copy of important data on another device or cloud destination.
When Separate Disks Are Safer
If the disks contain unrelated data sets, leaving them as separate storage spaces can reduce the blast radius of a single drive failure. You can still expose multiple shared folders without concatenating every disk into one volume.
FAQ
Is JBOD available in current ZimaOS?
Current September 2026 documentation lists JBOD as a supported layout.
Does JBOD protect data if one disk fails?
No. It is non-redundant.
Can I mix different-size drives?
Yes, but always verify the estimated capacity before creation.
Is RAID0 safer than JBOD?
No. RAID0 also has no redundancy.
