DiskSalvor › Help

Bad sectors, retries and hangs

Start here if your drive is failing · What a bad sector is, why one bad spot can freeze Windows for minutes, and how to read a failing drive without making it worse.

Every sector carries an error-correcting code. When the data doesn't match it, the drive retries, then reports a read error.

App asks for 64 KBone bad sector inside drive retries internallydesktop drives: up to 30 s or moreNAS drives with ERC/TLER: ~7 s Windows retriesthe whole request,several times minutes of"Not responding" That's why copying in Explorer "hangs" on a failing drive, and why each retry wears it further. A USB bridge may also give up and reset the connection ("drive disconnected").
physically damaged sector half-written sector (power cut) Both read as errors. The second kind is "soft": thesurface is fine, and rewriting the sector clears it.

DiskSalvor reads gently: on an error it skips the block and comes back later in small 4 KB steps; when the drive stops responding it moves on instead of waiting; it keeps a map of every problem; and it warns you when errors repeat.

← PreviousWhen the file index is damagedNext →The drive's health log (S.M.A.R.T.)

Free help for a failing drive

DiskSalvor is free, open-source data recovery for failing drives on Windows. It never writes to the drive, gets the easy files off first, goes back for the rest round by round, and explains what it's doing in plain English. No file limits, no paid edition, no account.

Start here if your drive is failing

How drives work

Reference