RAID Capacity & Drive Layout Calculator
Model two traditional RAID arrays with independent drive capacities, RAID levels and selected offline slots. See the raw capacity split into usable data, copies or parity, and unused space on larger drives. The physical drive ledger explains each contribution in bytes. The failure comparison shows when a selected pattern leaves enough parity or a surviving disk in every RAID 10 mirror pair.
Compare RAID capacity and drive layouts
See what each array can store, how much space goes to protection, and what changes when you mark specific drive slots offline.
Where the raw capacity goes
The bars share one scale ending at 32 TB. The capacity figures describe the original array before the simulated drive losses.
Proposed usable capacity change +4 TB
Current layout · RAID 5
24 TB raw
- Usable data
- 12 TB
- Copies or parity
- 4 TB
- Unused drive tails
- 8 TB
Proposed layout · RAID 6
32 TB raw
- Usable data
- 16 TB
- Copies or parity
- 16 TB
- Unused drive tails
- 0 TB
Selected drive losses
Current layout · RAID 5
Insufficient modeled redundancy
Offline slots 1, 2
Modeled tolerance 1 offline slot in any pattern.
Proposed layout · RAID 6
Enough modeled redundancy
Offline slots 1, 2
Modeled tolerance 2 offline slots in any pattern.
Edit drive layouts
Current layout slot ledger
Every slot contributes up to the smallest drive’s 4 TB. Its unused tail is the drive capacity above that amount.
| Slot | Entered capacity | Array allocation | Unused tail | Simulated status |
|---|---|---|---|---|
| 1 | 4 TB4,000,000,000,000 bytes | 4 TB4,000,000,000,000 bytes | 0 TB0 bytes | Offline |
| 2 | 4 TB4,000,000,000,000 bytes | 4 TB4,000,000,000,000 bytes | 0 TB0 bytes | Offline |
| 3 | 8 TB8,000,000,000,000 bytes | 4 TB4,000,000,000,000 bytes | 4 TB4,000,000,000,000 bytes | Online |
| 4 | 8 TB8,000,000,000,000 bytes | 4 TB4,000,000,000,000 bytes | 4 TB4,000,000,000,000 bytes | Online |
Proposed layout slot ledger
Every slot contributes up to the smallest drive’s 8 TB. Its unused tail is the drive capacity above that amount.
| Slot | Entered capacity | Array allocation | Unused tail | Simulated status |
|---|---|---|---|---|
| 1 | 8 TB8,000,000,000,000 bytes | 8 TB8,000,000,000,000 bytes | 0 TB0 bytes | Offline |
| 2 | 8 TB8,000,000,000,000 bytes | 8 TB8,000,000,000,000 bytes | 0 TB0 bytes | Offline |
| 3 | 8 TB8,000,000,000,000 bytes | 8 TB8,000,000,000,000 bytes | 0 TB0 bytes | Online |
| 4 | 8 TB8,000,000,000,000 bytes | 8 TB8,000,000,000,000 bytes | 0 TB0 bytes | Online |
Export the array comparison
Save both drive layouts, exact integer byte totals, and the results of the selected loss scenarios.
Download RAID comparison CSVShow selectable CSV
How to use this calculator
- Start with RAID 5 vs RAID 6 or RAID 10 pair losses. Choose Current layout or Proposed layout to edit its drives and RAID level.
- Enter each drive’s capacity and unit. For paired RAID 10, list adjacent slots in mirror order.
- Select Simulate offline on individual slots. Compare the selected drive losses without changing the drive count or normal configured capacity.
- Use Capacity display to see TB or TiB. Open each slot ledger for exact byte amounts, unused tails and the state of RAID 10 pairs.
- Download RAID comparison CSV to save both layouts, component and slot totals, and offline-pattern results.
The Formula
The mathematical logic powering this calculation is:
Convert each entered capacity to whole bytes first. One TB = 10¹² bytes. One TiB = 2⁴⁰ bytes. If a decimal yields a fractional byte, round down per drive. Capacity totals and differences use exact integer arithmetic. TB and TiB displays round to four decimal places and show exact bytes when a nonzero value is too small to display at that precision.
Let n be the original drive count and s the smallest drive capacity in bytes. Each configured slot contributes s bytes. Raw capacity is the sum of all drive sizes. Total array allocation is n × s. A drive’s unused tail is its size minus s. Usable data equals s times the data-member equivalents. RAID 0 uses n equivalents. An n-way RAID 1 mirror uses one. RAID 5 uses n − 1, RAID 6 uses n − 2, and paired RAID 10 uses n/2. Copies or parity occupy total array allocation minus usable data. Usable data plus copies or parity plus unused tails exactly equals raw capacity. In parity levels, the reserved space is counted across the array.
The selected offline slots test the original member layout. Capacity figures describe that configuration, including offline slots. RAID 0 tolerates zero offline drives. RAID 1 retains a copy with up to n − 1 offline. RAID 5 tolerates one, RAID 6 tolerates two. RAID 10 stripes across adjacent two-drive mirror pairs. It tolerates one offline slot in any position and up to n/2 offline slots if every pair keeps one member online. Losing both members of any pair exceeds its modeled redundancy.
Choose 2–12 configured drives. RAID 5 requires at least three, RAID 6 at least four, and paired RAID 10 an even count of at least four. Drives accept values from 0.0001 through 1,000 TB or TiB with up to four decimal places. A displayed input conversion preserves original bytes until you enter a new value. Use the ledger or CSV for exact bytes and the original unit entries.
This is a capacity and offline-pattern model for equal-width RAID members. It excludes filesystem and RAID controller overhead, hardware-specific capacity rules, hot spares, hybrid and tiered RAID, rebuild stages, media errors, and performance estimates.Worked Example
If you input:
- Current layout: RAID 5 with 4, 4, 8 and 8 TB. Slots 1 and 2 offline.
- Proposed layout: RAID 6 with four 8 TB drives. Slots 1 and 2 offline.
Result:
The current array has 24 TB raw, 12 TB usable, 4 TB parity and 8 TB of unused tails. The proposed array has 32 TB raw, 16 TB usable and 16 TB parity. With slots 1 and 2 offline, the parity is insufficient in the current array and enough in the proposed array under the model.
Frequently Asked Questions
Why do larger drives leave unused space in mixed-size RAID?
In this equal-width model, the array allocates the capacity of its smallest drive from every member. The remaining part of each larger drive is an unused tail. Some implementations support other layouts, which use different sizing rules.
What is the difference between TB and TiB?
One TB is exactly 1,000,000,000,000 bytes and one TiB is 1,099,511,627,776 bytes. An unchanged array therefore has a smaller numeric capacity in TiB.
How many drive losses can paired RAID 10 tolerate?
Every mirror pair needs at least one online member. That permits the loss of any one drive and can permit more if the losses occur in different pairs. The example compares two patterns with the same number of offline drives.
Is parity assigned to a single physical slot?
The parity accounting for RAID 5 and RAID 6 is an array-wide capacity equivalent. The slot table reports each drive’s allocated width and unused tail. Parity remains an array-wide capacity figure.
Why does the capacity stay the same when I mark a drive offline?
The capacity columns describe the configured array before loss. The offline selection separately checks whether the chosen pattern leaves enough modeled redundancy to account for that original layout.
Will usable capacity match the total shown by my operating system?
This model calculates usable data capacity before controller metadata and filesystem formatting. Check the implementation’s settings and units when comparing with an operating system’s reported space.
Similar Calculators
Data Transfer Time Calculator
Estimate file upload, backup, copy, or migration time from data size, throughput, overhead, and batches.
Server Power Cost Calculator
Compare server fleets with active, idle and standby schedules, PUE, time-of-use rates and coincident demand. Visualize hourly power, monthly costs and upgrade payback.
Unit Converter
Convert between units of length, weight, volume, and area — all in one tool.
