Data Recovery Case File · Desktop Externals & Aging Drives · It Refused Its Own Remedy
A Device That Will Not Complete a Format Is Not Accepting Writes at All
Her enquiry describes a loop worth reading carefully. A drive that stopped mid-use — "the programs shut down and now I can't access anything" — reporting that it is "not accessible (parameters incorrect)" and that it needs formatting, but when she attempts the format it stops. The refusal is doing her a considerable favour, and it also narrows the fault: a device that cannot complete a write is telling you something about its condition.
| Media | External hard drive — volume reporting incorrect parameters, host offering to format, format operation not completing; failure occurring during active use |
| Reported situation | External drive in use when applications closed unexpectedly · volume subsequently inaccessible · host reporting incorrect parameters · host prompting for the drive to be formatted · format attempted and not completing · content required |
| Fault class | Volume parameters unreadable with writes not completing — device-level degradation or protective state indicated; existing structures preserved by the failure of the format |
| Equipment used | Failure of the format credited as preserving the existing structures · no further write attempts permitted · current draw measured across the start-up cycle on a controlled bench supply · imaged write-blocked under strict per-sector timeouts · filesystem structures interpreted with their duplicate copies |
The decode: what the error names, and what the failed format establishes
What incorrect parameters actually reports: a volume description that does not make sense. The system read the structures defining the volume's size and layout and found values it cannot reconcile, so it declines to present it.
Why that is a statement about the description rather than the content: the values were read and rejected. Files sit in regions the system never reached, because it stopped at the point of interpretation.
Why the format was offered: it is the only remedy a system has for a volume it cannot interpret. Presenting it as the fix is the standard behaviour and it is presented as a repair.
What the format failing tells us, and this is the useful part: the device would not accept the writes. A format writes new structures, and an operation that cannot complete indicates the device is not taking writes.
The first explanation — protective refusal. Drives switch to a read-only state when their reserve capacity is exhausted. They will still return data and will not accept any, which is the honest failure mode and stops exactly this operation.
The second — the region cannot be written. Structural areas that have become unreadable are frequently also unwritable. A format attempting to write there stops rather than completing.
Why either is good news in the same way: both preserved her structures. A format that had succeeded would have replaced the very records a reconstruction reads.
Why the applications closing is consistent: the failure occurred during use. A drive that stops responding mid-operation takes down whatever was reading it, and the volume became uninterpretable at the same moment.
Why that timing also matters for the recovery: writes may have been in progress. An interruption during a structural update is a common route to precisely this error.
What must not happen now: no further format attempts, no repair and no consistency check. The device has refused once and may not refuse consistently — and a write that does succeed would land on the structures being reconstructed.
On the bench
The failure of the format was credited as preserving the existing structures — an incorrect-parameters report indicating volume-defining values read and found irreconcilable, so the system stops at interpretation without reaching content regions. A format writes new structures, and its failure to complete indicates the device is not accepting writes, from either a protective read-only state following reserve exhaustion or unwritable structural regions. Imaging ran write-blocked under strict per-sector timeouts.
The outcome
The failed format credited as preservation, further write attempts stopped, 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 format refusing to run is the best thing that has happened here. It would have written new structures over the ones a reconstruction reads — and its failing tells us the device is not accepting writes.
When a drive offers to format and then will not
Don't try again, and don't run a repair or check either. The device refused once but may not refuse consistently, and a write that does go through would land on exactly the structures needed to rebuild your volume. Read both messages usefully: incorrect parameters means the system read the values describing your volume and couldn't reconcile them, so it stopped before reaching any files; and a format that won't complete means the device isn't accepting writes at all, which is either a protective read-only state or unwritable regions.
Don't try again — call Cambridge Data Recovery on 01223 655015; the failed format credited as preservation, imaged under capped timeouts, structures rebuilt from 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.