Taking work now — the first look is freeSpinning disks in a machine Quicker still, give us a ring:0203 0868633
ADR Advanced Data Recovery 0203 0868633 Price my job
ADR / Sorted by symptom / Disks nothing will detect

The symptom · a disk nothing will show

Undetected hard drive recovery, London. Unseen is not erased. Only the introduction failed.

A drive that no computer can see has not been wiped. What it has mislaid is the means of announcing itself, and that lives in the electronics and the firmware, neither of which is where documents are kept. Three questions in order tell you which of them has broken. Does the BIOS list it? Is it in Disk Management? Will Explorer open it? Whichever stage the drive drops out of is your answer — electronics, firmware, or else the volume. Disks reach this bench from every part of London with one sentence attached, that the computer cannot see it, and that sentence is describing a circuit. One drive costs £300 + VAT. Nothing is charged for the assessment. A written figure precedes any chargeable work, and on most jobs no invoice follows unless your files do.

On most jobs: no data, no bill A free look first, then one figure in writing Media posted in from Croydon, Ealing and Camden

Put it to an engineer — the first look costs nothing
0203 0868633

What the symptom usually means.

Different fault? Try the finder →
How it shows itselfThe usual reason for itWhere that leaves you
Windows reports Unknown, Not InitializedThe drive answers, but has no valid signature and no usable partition tableTurn that prompt down
A prompt reading “…before Logical Disk Manager can access it”Agree, and a blank partition map goes over the lotShut it down, then pull the cable
Disk Management shows No MediaThe controller alone is replying and nothing behind it can be reached, which makes this hardware rather than a logical fault.Keep it unplugged from here on
No drive at all in the BIOSElectronics or firmware — a finished board, a shorted protection diode, service-area code that will not loadA repair at component level
A 1TB disk listed by the BIOS as 8MBDamaged firmware, or a damaged translator, so the capacity it reports is meaninglessFirmware tools rather than software
It draws power and does nothing elseIts power circuitry has failed, and the TVS diode went short in the processUsually still recoverable
Packing it and posting it:box it so nothing can move about, and put the parcel's insured value at what those files are worth to you, not what the hardware cost. Send it tracked; parcels go to the intake lab, and the leg home is paid at this end. Want a word first about what goes in the box? Ring us before it is sealed and an engineer will run through it. You will find the lot spelled out on theguide to packing and posting.

Worked in order, the stages name the fault.

Nowhere in the BIOSThe lowest rung of the three. Either the electrics or the firmware: tracks broken, a diode gone short, service-area modules refusing to load. What is written across the platters is nearly always sound.
Listed by the BIOS, not by Disk ManagementThe drive itself is answering properly, so the damage has to sit higher: either the partition table or the record-keeping the file system does for itself. Both are mended on the copy, with your own disk left alone throughout.
Explorer alone cannot see itThe hardware beneath is sound, yet the volume will not mount. Work on the file system, in other words, and it usually finishes well.
Nowhere at all, on any screenWhere there are platters, a voltage spike has usually shorted the TVS diode that guards the supply rail. Fitting a second board by itself achieves nothing: the calibration belonging to your disk lives in a ROM chip carried on the damaged board, and that chip has to move over to the donor.

From the box arriving to your files going back.

Work we have closed →
01

Logged the day it lands, and the first look costs nothing Free

A case number goes on it the day the parcel lands, and an engineer settles what has truly failed before anything else happens — free of charge, and first in the order of work. Back to you come two things together: a straight note of what is liftable and what is not, plus one figure, fixed and written down. Accept it, or decline and owe us nothing.

Nothing to pay for lookingA single figure, put in writingNothing owed at this stage
02

The stage where it drops out

Nothing gets opened here, and nothing is set running while nobody watches. A moment in the BIOS to begin with. Disk Management second. Explorer third. By the end of those three the job has narrowed to mending electronics, or rebuilding a service area, or putting a file system right on the copy.

One stage checked at a timeYour own disk is never written to
03

Mending the board

Off comes the shorted TVS diode and a fresh one replaces it. Where a board cannot be saved, a donor deputises for it and takes your own ROM chip across, since the adaptive values written on that chip came from your platters and fit no other disk.

Donor PCB carrying your ROMShorted diodes exchanged
04

Work happens on the copy

A sector-by-sector copy is made the moment the drive answers. Everything from then on runs against that copy, with your own drive shelved and untouched.

Every sector copied firstYour drive is not written to
05

You see the file list before you pay

What was recovered is listed for you first, and only then does a bill exist. Approve the list and it is invoiced; turn it down and it is not — and where nothing has come back, most jobs carry no charge whatever. Recovered data travels home on fresh media bought in for your job, with the postage at our end. Your case is not closed until you have read those files on a machine of your own.

No charge until you accept the figureFresh media, supplied with the jobThe post home is ours

What arrives most often

  • Each stage implicates a different part — some disks stop before the BIOS ever notices them, some get as far as Disk Management and no further, some show up in Explorer and will still not mount. Settling which of the three describes yours is most of the diagnosis.
  • Failing is the TVS diode's whole purpose — it shorts the rail on purpose and absorbs the spike itself, and that is the reason a disk which refuses to power up so often has perfectly sound platters behind the fault.
  • A matching model number proves nothing — calibration figures belong to one set of platters and are held in the ROM fitted to that drive's board, so a donor still wearing the chip it left the factory with is tuned to a different disk altogether.
  • Flash manages the same trick differently — a halted controller, or firmware that refuses to load, standing between you and NAND in perfectly good order. The example seen most weeks is a WD Blue SA510 reporting 0MB. SSDs have a page of their own.

Worth keeping hold of: when a disk turns up unseen by its computer, the explanation is almost always an electronic fault or a firmware one. Both exist to manage the introduction between a disk and a machine; neither goes anywhere near the part where documents are kept. An absent drive is therefore reporting a hardware problem about itself and nothing further, which is why work of this kind has a better ending than most. Establishing which of the two you are holding costs nothing.

One job, followed all the way through.

LDN · ADR-2026-3168JOB LOGGED ✓

A TVS diode gone short, and a WD with no spin at all

Mains power failed overnight at an office and by morning the desktop was listing one disk where it had listed two. The WD was silent, the BIOS gave it no entry at all, and the TVS diode on its board turned out to be the whole of the fault. Its own ROM went across onto a donor PCB, and a complete image was made of the drive two days after the parcel landed.

100%imaged sector for sector2days here, and back to you

What helps, and what harms.

Do this much first

  • Another cable, another port, and then stop there
  • Tell us whether it can be heard or felt turning
  • Mention any power cut, spike or lightning
  • Leave it unopened; send it exactly as found

What sets us back

  • Agreeing to the Initialize Disk box
  • Fitting a same-model PCB with its own ROM still on it
  • Working it through every machine in the house
  • Buying a donor board and reaching for a soldering iron at home

Questions answered before you commit.

Not a sound out of it. Can the files still come off?

Generally, yes. A finished board gets mended or swapped, and whatever finished it seldom carries on through the electronics to reach the platters — or, on flash, the NAND sitting behind them. Among all the ways a disk can go wrong, complete silence is one of the more predictable.

Windows wants to initialise it. Yes or no?

No, never. What that box writes is an empty partition map, laid straight over the one that records where everything sits. Decline it, take the drive out, and let an engineer look before anything else has a turn at it.

The BIOS shows nothing. Is it finished?

No. What a drive in that state has mislaid is its means of introducing itself, not anything ever written to it. The trouble lies in the electronics, or else in firmware held in the service area — and no file of yours is kept in either.

There was a power cut, and then nothing. Connected?

Very likely. The spike goes into a protection diode that shorts itself, which is the entire reason it is there — to go first, ahead of anything dearer. The electronics are finished; whatever you saved sits where you saved it.

Nothing gets worse while the power is off.

Looking at it is free. Back comes a list of what opened and what did not, together with a single price to finish, set down in writing while you are still free to say no. On most jobs an invoice only follows the data. Until that list reaches you, leave the drive switched off.

0203 0868633