Data Recovery Case File · Desktop Externals & Aging Drives · It Refused for a Reason
A Drive That Has Gone Read-Only Has Protected Itself From the Repair You Ran
His enquiry reports an outcome that reads like an obstacle and was a rescue. An external drive holding a photograph archive that the system reports as corrupted, where "the check says the drive is protected" and therefore will not run. Drives switch themselves to read-only when their own reserves are exhausted — and in this case that protection stopped a repair that would have made things considerably worse.
| Media | 1TB portable external hard drive holding a photographic archive — volume reported corrupt; drive refusing write operations, preventing a consistency check from running |
| Reported situation | External drive holding an archive of photographs · volume visible to the host and reported as corrupted · consistency check attempted by the owner · check reporting the drive as write-protected and not proceeding · content required |
| Fault class | Device-level write protection engaged — reallocation reserve exhausted or firmware protective state entered; volume structures damaged and content retained |
| Equipment used | Write refusal credited as preservation of the existing structures · no attempt made to clear the protective state · imaged write-blocked under strict per-sector timeouts before any interpretation · filesystem structures interpreted with their duplicate copies · content carved independently where structures did not reconcile |
The decode: why a drive stops accepting writes, and what that saved
Why a drive would refuse writes at all: it has decided that writing is unsafe. Drives monitor their own condition and can enter a protective state in which they will still return data but will not accept any.
What usually triggers it: exhaustion of the reserve. A drive relocates failing sectors into spare capacity held for the purpose, and when that capacity runs out it has nowhere to put a write it cannot complete safely — so it stops accepting them.
Why that is a deliberate design rather than a malfunction: a drive that kept accepting writes it could not honour would lose data silently. Refusing is the honest failure mode, and it preserves what is already there.
Why it happened at the moment he ran the check: it did not. The protection was already engaged and the check was simply the first operation to require a write — reading had continued to work, which is why the volume was still visible.
What the check would have done had it run: reconciled the volume's structures and discarded references it could not verify. On a drive with unreadable regions that means dropping references to intact content, because the content behind them could not be confirmed.
Why that makes the refusal a genuine escape: the operation he attempted is among the most damaging available on a failing drive. The drive declined it on his behalf, and the structures a reconstruction needs are still there.
Why the corruption report and the protection fit together: both follow from the same underlying degradation. Sectors failing produced the structural inconsistency the system reports, and the same failures exhausted the reserve.
Why the read-only state should not be cleared: utilities exist that attempt to reset it. Restoring write capability restores the ability to damage the drive, and nothing about the recovery requires writing to it.
Why imaging is unaffected by any of this: a capture only reads. A drive that returns data and refuses writes is entirely readable, which is the state a recovery wants.
What must not happen: no further checks or repairs on any machine, and no attempt to force the drive writable. The refusal is the only thing currently protecting the archive.
On the bench
The write refusal was credited as preservation of the existing structures — drives monitoring their own condition and entering a protective state in which data is returned but not accepted, typically on exhaustion of the reserve capacity into which failing sectors are relocated, refusal being the honest failure mode rather than a malfunction. A consistency check reconciles structures by discarding unverifiable references, which on a degrading drive drops references to intact content. Imaging ran write-blocked and was unaffected.
The outcome
Write refusal credited as preservation, no attempt made to clear the protective state, and structures interpreted with their duplicate copies. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: the check refusing to run is the best thing that has happened here. Your drive stopped accepting writes because its reserve is exhausted — and that refusal blocked the one operation most likely to have made this worse.
When a repair tool says the drive is write-protected
Leave it that way and don't run any utility that promises to clear the protection — restoring the ability to write restores the ability to damage it, and nothing about recovering your files requires writing to the drive at all. What's happened is that the drive relocates failing sectors into reserve capacity, that reserve has run out, and it has stopped accepting writes rather than accepting ones it can't honour. The refusal blocked a consistency check, which on a degrading drive discards references to content it can't verify.
Leave it protected — call Manchester Data Recovery on 0161 871 0788; write refusal credited as preservation, protective state left engaged, structures interpreted with their duplicate copies.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.