A PC Shop Ran Software First

The decode

Software can't reach a physically failed drive. That a recovery programme got no data points at a physical fault, because software reaches a drive's data through the drive's own normal path — it asks the working drive for its contents — so when the hardware has failed and the drive cannot present itself, there is no path for software to read, and it returns nothing. So the empty result reflects the kind of fault, not the absence of data: the drive has a hardware fault software cannot cross, which is why the programme got nothing, rather than the recording being gone. Her data is usually still on the drive, behind that fault, reached by reading it directly. Software can't reach a physically failed drive.

The referral to open it up is sound. That the local person, unable to get data with software, advised taking it apart is a sound judgement, because a physically failed drive is read by working on its hardware directly — opening it where the fault is mechanical, or reaching its firmware and board where it is not — which is beyond what a recovery programme can do. So their handling points the right way: software was tried, it could not reach the fault, and the drive needs the direct, hardware-level work a lab does. Recognising that and referring it on was correct. Her data is reached by that direct work, as the referral suggested. The referral to open it up is sound.

It's opened and read directly. Because the fault is physical, the drive is read directly — connected on recovery equipment, its firmware, board, and mechanism assessed and the fault addressed, then imaged, so the data is read at the drive's own level rather than through a path the failure has closed. If the fault is mechanical, the drive is opened in clean air and the mechanism repaired; if it is firmware or the board, that is addressed without opening. Her data is reached from the image, which is how a physically failed drive is recovered. The free diagnostic establishes the fault, and one fixed quote goes in writing before any work is agreed.

The honest prognosis is generally good, established at assessment. If the fault is firmware or the board over sound platters — common for a failed drive software can't read — reading it recovers the data well, usually in full. If the mechanism is at fault, that's addressed in clean air, confirmed before any work goes ahead.

On the bench

The drive was read directly behind a hardware write-blocker on PC-3000 UDMA, its firmware, board, and mechanism assessed to establish the physical fault. The fault was addressed (firmware or service-area repair, board repair with this drive's ROM, or clean-air head or motor work under laminar flow if mechanical). It was imaged on DeepSpar, the filesystem parsed in R-Studio and the data validated onto fresh media.

The outcome

The physical fault addressed, the drive read directly, and the data recovered onto fresh media. The diagnostic stage is free and reports back within two working days of the media arriving; after it you hold one written quote, fixed with VAT included. Opening a drive commits donor stock and clean-air bench time, so half the quoted figure is payable before that stage begins, and the remaining half falls due only once the recovery has succeeded — if it fails, the rest is never billed. The decode: software couldn't reach a physically failed drive — it's opened and read directly, and the referral was sound. Read directly, your data comes back.

Our case files are written up from genuine enquiries our lab has handled for customers across Swindon and Wiltshire, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.