ZFS special-vdev recovery
The ZFS special allocation class can hold metadata, indirect blocks, deduplication tables, and optionally small file blocks. If a nonredundant special device or all sides of its mirror fail, the entire pool can become unavailable even when normal data vdevs are healthy.
Understand the symptom
A special vdev is not L2ARC. Its block pointers and payload participate in the pool's normal tree, so redundancy must be at least as strong as normal vdevs. Recovery maps pool labels, vdev GUIDs, allocation classes, transaction groups, and device health before attempting a read-only import or member reconstruction.
What you may see
The missing device may be a top-level special vdev required to traverse metadata.
One side failed and the surviving member may be the only copy of special-class blocks.
Metadata and indirect blocks on the special class are unreadable or inconsistent.
Datasets may have directed small blocks to the special class.
Protect the source
Removing a failed special device is not equivalent to removing L2ARC.
A weak surviving member can deteriorate under full reconstruction load.
A similar device or stale label does not prove membership in the same pool generation.
Do this now
Disable services, scrubs, resilvers, imports, and automatic replacement actions.
Save zpool status, import output, device paths, GUIDs, serials, bay order, and special_small_blocks settings.
Include failed and replaced special members plus normal, log, cache, and spare devices.
Acquire weak special devices before resilver or extended traversal.
NEPFOSYS process
NEPFOSYS identifies special vdev membership, redundancy, labels, and pool transaction state.
Readable source devices are imaged and candidate mirrors compared before pool reconstruction.
The pool is evaluated without production writes and priority datasets are verified from protected copies.
A clear next step
Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.
Start with a case reviewQuestions, answered
No. It permanently stores unique metadata, indirect blocks, dedup data, and possibly small file blocks.
If the pool lost a required top-level special vdev without another valid replica, normal import may be impossible.
Yes. OpenZFS advises redundancy at least equal to the normal vdevs because losing the special vdev can lose the pool.
DFW local · Nationwide mail-in