When an HDD cannot read some areas, prioritize preserving readable data over repeatedly scanning the original. A suitable image can move later file analysis away from the source, but it cannot recreate sectors that were never acquired. If the disk is mechanically unstable or the only data matters, seek an acquisition assessment before a DIY imaging attempt.
Distinguish an observed read failure from a label
A “bad sector” report, an I/O error and a failed file copy are related clues, not identical diagnoses. Record the tool, operation, affected region if known, and whether the disk remains connected. Preserve existing logs without producing another full surface test merely to confirm the problem.
A file system’s bad-cluster record also does not describe every current physical failure. Health summaries should be considered alongside actual reading. Repeated hard clicking, grinding, disappearing capacity or worsening access are reasons to stop powered attempts.
Decide whether imaging is appropriate
Imaging reads source storage into another file or device. It helps when later scans would otherwise reread the same original. It also requires reads of its own, so the choice depends on the disk’s condition and the acquisition method.
The GNU ddrescue manual describes a strategy that saves progress in a mapfile and retrieves easier regions before revisiting difficult ones. This explains why acquisition planning matters. It is not a reason to run a copied command without understanding source, destination and resume behavior.
For unstable hardware, a professional may need equipment and methods beyond normal software imaging. Do not open the drive, try mechanical remedies or keep restarting a failed imaging job to chase a complete progress bar.
Keep the image and its read record together
Use healthy storage with enough space for the image, logs and recovered output. Identify the source by model and capacity; do not rely on a drive letter that could change. Retain notes of unreadable ranges and whether the acquisition completed or stopped.
XRecovery supports creating IMG images and scanning IMG, RAW and DD images. Keep the acquisition log and note any unreadable regions: an image of the expected size can still lack data the device did not return. Do not infer that unreadable bytes are correct because the image has the expected overall size.
Preserve the acquired image unchanged. If later repairs are explored, keep them on a separate working copy so that the acquired state and its logs remain available.
Recover files from the acquired data
Scan the readable image and export priority files to another destination. A result may include a correct name even when an unreadable region falls inside its content. Missing sectors can damage one file severely while leaving many others usable; a whole-image completion percentage is not a file-specific verdict.
Validate the content that matters: full document pages, required archive entries, image dimensions and later sections of video. Compare hashes against known-good originals where available. Keep partial or uncertain files clearly separated from verified output.
Do not run CHKDSK repair on the original as a substitute for acquisition. Fixing structures does not recover unreadable bytes. If too much remains missing, preserve the image, logs and unpowered original for assessment rather than repeatedly stressing the source with new scan combinations.