LIVE TELEMETRYGPT-5$1.25 / $10.00Sonnet 5.5$2.00 / $10.00Gemini 3.8$0.75 / $3.75DS V4.1$0.15 / $0.60RTX 50901,792 GB/sM4 Max546 GB/sUS Avg$0.182/kWh
TELEMETRY CONSOLE NAVIGATION

Guncelkal Telemetry Index

Search VRAM specs, API costs, or Dev tools

Hardware & Power9-RAID Matrix + Resilver Risk

NAS, Synology SHR & ZFS RAID Capacity Calculator

Model up to 12 mixed-capacity drive bays to compare Synology SHR multi-tier slicing against standard RAID 5/6/10, TrueNAS ZFS RAIDZ pools, binary TiB reality, and single-parity rebuild times.

Drive Bays & RAID Topology

Drive Bays (4 / 12)
B1
B2
B3
B4
140 MB/s

Active pool scrub reads during drive replacement typically sustain 110–180 MB/s on 7,200 RPM CMR SATA drives (slower if SMR or serving live IOPS).

Usable (Decimal)
28 TB
Raw: 44 TB (64%)
Real OS (TiB)
25.47 TiB
Binary 1024-base capacity
ZFS 80% Target
20.37 TiB
Avoids CoW fragmentation
Fault Tolerance
1 Drive
Parity: 16 TB
Estimated Drive Rebuild Window: 31.7 hours
Largest Bay: 16 TB | Array Read Stress: 48 TB

Rebuild Exposure Alert: 16 TB single-parity resilvering takes ~31.7 hrs while reading 48 TB. Consider dual-parity (SHR-2 / RAID 6 / RAIDZ2) to guard against URE or second-drive failure.

CHASSIS DRIVE BAY TELEMETRYUsable 28 TB | Parity 16 TB | Unallocated 0 TB
BAY 1ONLINE
8 TB
BAY 2ONLINE
8 TB
BAY 3ONLINE
12 TB
BAY 4ONLINE
16 TB

All-9-RAID Topology Matrix for This Exact Bay Set (Click Row to Switch)

TopologyUsable TBReal TiBEfficiencyFault Tol.
Synology SHR-128 TB25.47 TiB64%1 drive
Synology SHR-216 TB14.55 TiB36%2 drives
RAID 524 TB21.83 TiB55%1 drive
RAID 616 TB14.55 TiB36%2 drives
RAID 1016 TB14.55 TiB36%1 drive
ZFS RAIDZ124 TB21.83 TiB55%1 drive
ZFS RAIDZ216 TB14.55 TiB36%2 drives
RAID 1 Mirror8 TB7.28 TiB18%3 drives
RAID 0 Stripe32 TB29.1 TiB73%0 drives

Single-Parity URE Rebuild Window & Pool Sizing Rules

Modern 16 TB–24 TB HDDs exceed the unrecoverable read error (URE) statistical boundary during multi-day rebuilds. Understanding decimal vs. binary overhead and ZFS pool fullness prevents painful migrations later.

Bay Count / SizeRecommended SchemeWhy Engineers Choose It
2–4 Bays (Matched or Mixed)Synology SHR-1 / ZFS MirrorFlexible upgrade path without wiping volumes; rapid mirror resilvering.
5–8 Bays (≥ 14 TB Drives)SHR-2 / RAID 6 / RAIDZ2Dual-drive fault tolerance absorbs a second disk URE during 30+ hour rebuilds.
DB / VM Block StorageRAID 10 Striped MirrorsEliminates parity write amplification and restores IOPS fast after failure.

Telemetry Methodology & Benchmark Sources

Read full equations →

Marketing TB converts to true binary TiB via * 0.909495 (10^12 / 1024^4). Synology SHR computes layer-by-layer parity partitions across unequal drives, ZFS caps safe space at 80%, and rebuild time estimates sequential array read duration across the largest bay.

Primary Technical & US Grid Benchmarks

  • Synology Hybrid RAID (SHR) Multi-Layer Partitioning Spec
  • OpenZFS RAIDZ Parity & 80% Fragmentation Rule
  • IEC Binary TiB vs SI Decimal TB Standard
  • Enterprise SATA/SAS Drive URE Rebuild Analysis

Engineering & Pricing FAQ

Why does Synology SHR unlock more space than RAID 5 when drive sizes differ?
Standard RAID 5 clips every drive down to the smallest disk in the pool (wasting extra space on larger disks). SHR slices storage horizontally into multiple MDRAID layers so paired larger drives reclaim extra redundant capacity.
Why does my 20 TB drive only show ~18.19 TiB inside DSM or TrueNAS?
Hard drive manufacturers market decimal Terabytes (10^12 bytes), whereas Linux ext4, Btrfs, and ZFS report binary Tebibytes (2^40 = 1.0995 TB), creating a permanent ~9.05% reporting gap.
When does single-parity RAID 5 / SHR-1 become risky during a drive rebuild?
Once arrays exceed 4 bays with 14 TB+ drives, replacing one failed disk forces 24 to 45+ hours of heavy sequential reads across all remaining drives. A second bad sector on a degraded array destroys the volume unless you use 2-drive parity (RAID 6 / SHR-2 / RAIDZ2).
Why should TrueNAS ZFS pools stay below 80% allocated capacity?
ZFS uses Copy-on-Write (CoW) and cannot overwrite blocks in place. Above 80%–85% utilization, the metaslab allocator switches from first-fit to best-fit scanning, sharply inflating fragmentation and plummeting random write throughput.
Can you expand a RAIDZ1 or RAIDZ2 vdev by adding one single drive later?
OpenZFS RAIDZ expansion (released in newer ZFS versions) lets you attach single drives to an existing vdev, though pre-existing blocks keep their older parity ratio. Synology SHR allows instant single-bay expansion as long as the new drive matches or exceeds the largest existing disk.

Continue in Console Workflow

Hardware & Power

Bandwidth & Egress

Time multi-terabyte model weight downloads across 1G/10G/Fiber links and compare AWS S3 / GCP / Cloudflare R2 egress bills.

Open Workbench
Hardware & Power

kWh Power Cost Lab

Calculate daily, monthly, and annual kWh bills using 80+ PSU efficiency, duty cycle, optional AC cooling load, and 50 US state EIA rates.

Open Workbench
AI & LLM Economics

Local LLM VRAM Checker

Test Llama 70B, Qwen 32B, or DeepSeek R1 across RTX 3090/4090/5090 & Apple Silicon Macs with GQA KV-cache math and tokens/sec speed.

Open Workbench