Dell PERC puncture recovery
Dell describes a puncture as a rebuild-with-errors condition caused by inaccessible data in more than one member location within the same stripe. The virtual disk may later appear optimal while files or filesystem metadata remain damaged.
Understand the symptom
PERC logs can distinguish media errors, predictive failures, rebuild events, and punctured LBAs. The impact depends on where those LBAs fall: unused space, ordinary file content, or critical filesystem and database metadata. Recovery preserves the controller configuration and members, then correlates stripe damage with logical structures.
What you may see
PERC recorded a stripe that could not be reconstructed cleanly.
Redundancy returned, but unreadable source blocks were propagated as missing data.
Punctured LBAs may intersect allocation, directory, journal, or database pages.
Media errors or propagated puncture state may accompany hardware warnings.
Protect the source
On an unprotected damaged array, correction may commit assumptions over evidence.
Deleting and rebuilding the array changes controller state and may initialize data regions.
Original members and logs are needed to determine the double-fault timeline.
Do this now
Save event history, virtual-disk properties, member states, stripe size, firmware, and puncture details.
Label bays, serials, failed disks, replacements, and hot spares without clearing foreign state.
Do not start patrol read, check consistency, initialization, or another rebuild on the only copy.
List filesystems, VMs, databases, and the time window when errors began.
NEPFOSYS process
NEPFOSYS maps punctures, media errors, member transitions, and RAID geometry.
Each readable disk is preserved with bad regions recorded by LBA.
Affected stripes are correlated with logical structures and priority data is validated.
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
Often some or most data remains readable, but data in double-faulted stripe locations may be incomplete.
It may restore parity consistency, but it cannot recreate information lost when two stripe blocks were unavailable.
No. Preserve them until recovery and validation are complete; they may contain readable data missing elsewhere.
DFW local · Nationwide mail-in