{
  "status": "shipping",
  "advantages": [],
  "limitations": [
    {
      "text": "A rebuild cannot reconstruct a region for which the surviving data and parity no longer provide enough information.",
      "citationIds": [
        "zconcepts"
      ]
    }
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-13",
  "slug": "raid-rebuild",
  "term": "RAID rebuild",
  "aliases": [
    "RAID reconstruction",
    "Array rebuild"
  ],
  "definition": "A RAID rebuild reconstructs the required contents of a replacement or out-of-sync member from the array's surviving redundancy.",
  "note": "Linux MD calls recovery the construction of a hot spare to replace a missing or failed member, and distinguishes it from resync after an unclean shutdown and check or repair scans [md]. Rebuilding redundancy is not restoration of an independent backup.",
  "related": [
    "raid",
    "degraded-array",
    "hot-spare",
    "resilver",
    "data-scrubbing",
    "raid-write-hole",
    "parity-declustering",
    "distributed-spare"
  ],
  "citations": [
    {
      "id": "md",
      "title": "Linux 6.12 documentation: RAID arrays, recovery, resync and degraded state",
      "url": "https://docs.kernel.org/6.12/admin-guide/md.html",
      "accessed": "2026-10-13"
    },
    {
      "id": "zconcepts",
      "title": "OpenZFS 2.3: zpoolconcepts(7), device failure and hot spares",
      "url": "https://openzfs.github.io/openzfs-docs/man/v2.3/7/zpoolconcepts.7.html",
      "accessed": "2026-10-13"
    },
    {
      "id": "hesela-rebuild",
      "title": "Hesela: RAID rebuild read-error models and resilver boundaries",
      "url": "https://hesela.com/analyses/raid-rebuild-ure-math-and-resilver/",
      "accessed": "2026-10-13"
    }
  ]
}