The dissertation that’s suddenly symbols, the QuickBooks file the software rejects, the wedding video that plays four seconds and dies — corruption is data present but disordered, and the fix depends entirely on where the disorder lives: in the file, the file system, or the drive beneath both.
$ edr connecting…
Drive-level: failing sectors serve up files with holes in — corruption as a symptom of hardware decline, where the priority is imaging the drive before ‘a few odd files’ becomes ‘a drive that won’t mount’. File-system-level: the index linking names to content has tangled — files vanish, folders turn to gibberish entries, drives demand formatting — while the content itself sits intact awaiting reconstruction. File-level: the document itself took the hit (interrupted save, crash mid-write): here recovery means structural repair — rebuilding headers, salvaging streams, extracting text and objects from Office files, re-muxing video whose index never got written. The diagnostic pins the layer first, because treating the wrong one wastes the patient.
Straight talk for the file-level cases: repair reconstructs structure, not missing substance. A Word file with intact text but a broken wrapper returns whole; a video missing its index re-muxes and plays; a spreadsheet with damaged formulas can surrender its data even when Excel refuses the file. But content that was never written — the crash happened before the save finished — cannot be conjured, and a file whose middle third is zeros keeps its hole. You’ll get the file-by-file verdict at diagnostic: repairable, extractable, or honestly gone — free, before any decision.
Usually not: symbol-salad typically means a damaged wrapper around surviving content, and text extracts even from files Word refuses to touch. Send the corrupt file and any temp or backup versions alongside — Office scatters useful fragments the recovery can weave in.
Classically yes: that's a missing or truncated index, common when recording was interrupted, and re-muxing rebuilds the wrapper around footage that's fully present. If the camera or card it came from is available, send that too — the original source sometimes yields a cleaner copy.
Mass corruption is a symptom, not a coincidence: a failing drive, a tangled file system, or malware. Stop using the machine — especially stop running repair utilities on it — and bring the drive. Fixing files individually while the cause still runs is bailing a boat with the plug out.