Solid state drives give no warning whatsoever. No noise, no gradual slowing, nothing to act on. Fine at five o'clock, gone by nine the following morning. This is a different trade from disk work altogether. No platters, no heads, no clean bench. It runs every day for households, for both universities, and for survey and design firms whose entire output sits on one laptop.
Every ssd job is diagnosed free. The fixed figure reaches you in writing first, before any tools come out.
No fix, no fee all jobs except electronic and mechanical failures, chip level work, DVR and Forensic jobs. Full pricing is on the data recovery cost page.
First job on any ssd is matching the symptom to the fault. Twenty-odd years in, these twenty-five cover nearly every one that reaches this bench.
The management chip quits and the drive leaves the bus. Every file is still held in the NAND behind it. What has been lost is the thing that speaks for that memory, and a firmware bench replaces it.
No drive is called that. It is a Phison controller stranded in its own boot loader. Your files sit behind a wrong name, undamaged, and service-mode work walks them out.
Translator failure. The drive answers politely with a size that belongs to no product. Rebuild it in service mode, image it completely, and only then ask it to do anything else.
Boot code, power rail or controller. All three produce an identical blank screen. Separating them needs a bench, and it is the first question the free diagnostic answers.
Write protection has engaged at end of life to hold on to what is already stored. Irritating if you need the drive. Helpful if you need the data, because a frozen drive cannot worsen its own position while we copy it.
Flash gives very little notice. That is why so many calls here open with somebody explaining that it behaved perfectly the last time they used it. It is not carelessness. It is how the technology fails.
Interrupt a write and the tables converting logical addresses into physical ones get scrambled. A real surge takes out the power stages as well. Both land on this bench regularly and both are firmware work.
Tired NAND returns different values from one read to the next, while SMART grumbles quietly in the background. Only the first complete image can be trusted, so it gets taken once and taken properly.
Background erasure of freed blocks runs any time the drive is powered up. Cut the power and it halts where it stands. Leave the drive plugged in while you think it over, and the thinking costs you files.
Thin boards lose to screwdrivers, upgrade attempts and stiff envelopes. A clean break near the edge is track-repair work under the scope. Anything more comprehensive goes to chip-off instead. Slower road, same files.
Samsung's MZ-76E500 sits in a huge number of British desktops and laptops, so every version of its ending passes through here. The signature one arrives without ceremony. It leaves the SATA bus part way through a session and returns reporting a tiny capacity, or reporting nothing whatsoever, and changing leads or ports alters none of it. The translator has gone from the controller. V-NAND underneath is normally untouched. Service-mode access followed by a complete image is the way back, and owners who cut the power the first time it stumbles get the best result.
MZ-77E1T0 units from the first runs were documented reallocating sectors quickly enough that Samsung published a firmware update. Unpatched examples still arrive. The memory reads. It is the map that wants rebuilding.
Crucial's CT500MX500SSD1 has a known habit of showing a climbing pending-sector count that worries owners more than it deserves, until the day it arrives alongside genuine read errors. Telling those two apart is bench work, not guesswork.
There is a documented habit here. WD's SATA Blue walks off the bus and stays gone until firmware attention gets applied. Familiar patient, familiar route. The NAND is very rarely the guilty party.
A400 SA400S37 units and their relatives shrink to a handful of megabytes, or vanish entirely, once the translator corrupts. Service-mode territory. The flash underneath has generally done nothing wrong.
These stop dead partway through a write and refuse all further conversation. Some can be woken in service mode. The rest get read at chip level, which reaches the same files by a longer road.
Blades of the SSUBX and SSPOLARIS families, fitted right through the 2013 to 2017 machines, fail exactly as any other solid state does, and they image on native adapters here. No donor Mac takes part at any point, which surprises most callers.
Without a DRAM cache the wear-levelling is crude, so a BX500 given serious work ages well ahead of schedule. Packages come off the board and the data comes off the packages.
Marketplace counterfeits loop writes back over a small slice of genuine memory. Whatever landed inside the real capacity recovers. Whatever came afterwards was never stored, and nobody can retrieve it.
The plastic tongue snaps during a routine swap and takes pads with it. Board-level repair puts it back, and the drive then behaves as though the accident never happened.
Years of heavy writing consume the rated life, and the drive then locks solid or reads unpredictably. There is margin left for a single imaging attempt. It gets planned as one, not started hopefully.
A vendor utility stopped part way through and left the drive unable to identify itself. Depending on what the controller can still be persuaded to say for itself, it gets reflashed here or bypassed altogether.
Reading one block repeatedly disturbs the charge held in its neighbours. On a drive full of archives that get read often and rewritten never, the errors build until ECC stops covering them. Slow repeated reads recover far more than a single confident pass.
Unpowered cells leak charge. Something last switched on in 2019 may come back as noise. Imaging by repeated read, with ECC given room to do its job, returns a great deal that a single quick pass writes off as unreadable.
Almost every current SSD encrypts on the way in, asked for or not, and the key lives inside the controller. Damage the key store and the memory reads perfectly and means nothing. We say so plainly instead of selling optimism.
An SSD does not keep your files anywhere the computer thinks it does. Wear levelling spreads them over the NAND packages as the controller pleases, and that layout is described in exactly one place: a translation table living inside the controller's firmware. Damage the table, or lose the controller, and the drive stops answering the bus while every byte behind it sits in good order. Two honest routes exist. The first is service mode: reach the controller down the manufacturer's own diagnostic channel and get it to rebuild or reload what it mislaid. The second is chip-off. Lift the NAND clear of the board, read each package directly, then rebuild the translation in software. That one is slower and does not care whether the drive ever answers again. Consumer utilities manage neither, because all of them need a drive the computer can already see.
The 860 EVO earns a paragraph of its own. It arrives here more than any other single model and the failure has a recognisable shape. A drive in apparent health drops off the SATA bus part way through a session. Next boot, the BIOS lists nothing at all, or it lists the drive at a couple of megabytes instead of 250GB, 500GB, 1TB or 4TB. Firmware corruption is what that pattern usually means: the controller powers up, fails its own integrity checks, and never presents the user area. Signature failure in the service area, or controller corruption that leaves the translator unreadable, look identical from outside. The point worth holding onto is that the V-NAND underneath is nearly always intact. The memory is fine. The thing describing the memory is not. Route in: service-mode access with the vendor terminal, repair or reload of the damaged firmware modules, then a full image taken immediately, before anything else is tried. Writes land in the service area that holds the firmware and nowhere near your data. Where service mode is refused, the packages come off and get read directly. One practical note. A vendor firmware update is a job for a healthy drive. Running one at the point of failure is a poor idea and occasionally a final one.
Samsung, Crucial, Kingston, SanDisk, WD, Intel, Solidigm, Kioxia, SK hynix and Apple's own removable blades turn up in the three usual shapes: 2.5-inch SATA, mSATA, M.2. The regulars are whatever the trade was fitting that year. Samsung 850 EVO, 860 EVO, 870 EVO and the QVO variants. Crucial MX500 and BX500. Kingston A400, KC600 and the older SSDNow V300. WD Blue SA510 and the WD Green that preceded it. SanDisk Ultra 3D and SSD PLUS. Behind those comes a steady run of SK hynix and Kioxia units pulled from prebuilt laptops. Two categories get refused, and hearing it now beats hearing it after you have paid postage. Storage soldered permanently to a mainboard is the first. Phones and tablets are the second; they fall outside this service completely. Aggressive TRIM and hardware encryption each make a job harder than it looks at the outset, and that gets said at the assessment rather than printed on an invoice later. SSD data restoration Scotland wide runs across this same bench, and a bare drive in a padded envelope is next-working-day post from anywhere in the country.
Solid-state recovery is firmware and chip surgery from the opening minute, and this bench is built for it:
Wakes a silent drive in its maker's service mode, repairs the firmware and rebuilds the translator, then captures a complete image before anything further is asked of it.
Stalling drives get hardware timeouts, with retry behaviour set for the exact unit in front of us. Defaults written for some other model are worse than useless.
Native sockets for every removable solid-state shape, Apple blades and short 2230 modules among them, with forced cooling for anything that misbehaves once warm. No USB caddies anywhere in the chain.
Where no service mode will rouse the controller, packages come off and get read individually. It takes longer and it arrives at the same files.
Interleave, XOR and ECC solved from bare dumps until the mapping exists in software again. The volume is then stood back up on top of it.
Burnt power stages and cracked boards get fixed first. A drive that browns out mid-image has told you nothing except that the board needed doing.
One part number owns this page, and its name is the Samsung 860 EVO. That MZ-76E500 was the upgrade nearly everybody fitted while hard drives were being retired, so a whole generation of those upgrades is wearing out at roughly the same moment. Its best-known ending needs no interpretation. Off the bus without warning, back as a sliver of its stated capacity or absent altogether. Translator failure standing above healthy V-NAND. It recovers. The 870 EVO follows that same script. Around them, the A400 SA400S37 mislays its map, the MX500 frets over pending sectors, the SA510 slips away quietly, the BX500 wears out early under work it was never sold for, the 870 QVO stalls once its fast cache is spent, and the NV2 turns up carrying whichever controller and flash were going that quarter. The rule is short. If it unplugs, we can work on it, whether that is 2.5-inch, mSATA or M.2, read-only lockouts included. Soldered onto a motherboard, so it is not, and phones and tablets are not either.
Nearly everything on this bench came by tracked, insured post. It is the safest way to shift a failing drive, and a parcel handed in at a North-East post office is usually here the next working day.
Still bolted into a laptop, desktop, MacBook, iMac, server or CCTV / DVR box? Get the hard drive or SSD out first. The bare drive travels on its own. Stripping machines down is not a job this lab takes on. Flash soldered to a motherboard, as on Apple Silicon Macs and a couple of very thin laptops, is our one flat no: if it will not unbolt, it cannot be worked on.
↓ Print the shipping & booking-in form (PDF)
Address it for the attention of Edinburgh Data Recovery. From Aberdeen that is roughly 130 miles and two and a half hours down the A90, or next working day by tracked post if you would rather not make the run. You get a call the moment it is booked onto the bench.
Not sure what belongs in the box? Ring 0800 689 0668 before you tape it shut, or work through the free online diagnostic.
Free diagnosis, one number written down, no fix no fee on the bulk of jobs. Start online or phone it in.