Samsung EVO SSD Not Recognised? Don't Run the Samsung Magician Update.
UK SSD data recovery specialists since 2002. Samsung Phoenix and Pascal controller recovery, NAND chip-off, FTL reconstruction. Free UK collection. No-fix-no-fee.
What this means and what to do next
The Samsung 870 EVO and 980 EVO are two of the UK's most popular SSDs — the 870 in SATA, the 980 in NVMe M.2 form — and both are based on Samsung's in-house Phoenix or Pascal controllers. When either drive stops appearing in BIOS, Windows Disk Management, or macOS Disk Utility, the most common cause is not dead NAND. It's a firmware-level fault inside the Samsung controller: the controller has powered on, run its internal health checks, encountered an inconsistency in the Flash Translation Layer (FTL) or config block, and placed itself in a protected state that refuses all host commands. Your data is still on the NAND chips. The question is how to get at it.
Samsung's controllers are both a strength and a specific weakness here. On the strength side, the Phoenix and Pascal families are very well-documented — PC-3000 SSD has Samsung-specific technology modes that can talk to these controllers in ways that normal host commands cannot, bypassing the protection state and giving direct access to the FTL and user data. On the weakness side, the 980 PRO (a separate line from the 980 EVO) had a well-documented firmware issue from 2022 through 2023 that caused premature failure on heavily-written drives; some of those drives are still failing now as they reach the end of their replacement window.
The 870 EVO specifically has a reputation for firmware-induced failures after a problematic Samsung Magician update in late 2022, and there are a number of drives where the controller's internal log shows a failed firmware flash as the last event before the drive stopped responding. If your 870 EVO stopped showing up after running Magician, tell us that when you call — it tells us exactly which recovery path to try first.
The three most common causes of a Samsung EVO SSD not being recognised
1. Flash Translation Layer (FTL) corruption on power loss or controller fault. The FTL is the index that tells the Samsung controller which physical NAND locations hold which logical sectors. It lives in a reserved area of the NAND and is updated continuously during writes. A sudden power loss — a laptop battery dying, a desktop PSU failing, a USB cable disconnected mid-write — can leave the FTL in an inconsistent state. On restart, the controller validates the FTL, finds it inconsistent, and refuses to come online as a safety measure. The drive may show up in BIOS as "0 GB" or with a generic drive ID, or may not appear at all. The NAND still has your data; the controller just can't find it without a working FTL.
2. Failed Samsung Magician firmware update. Samsung Magician periodically prompts users to update SSD firmware. In most cases this is safe. In a small percentage of cases — particularly on 870 EVO drives and particularly on drives with high write counts — the flash process corrupts the controller's config block or writes firmware that's incompatible with that specific drive's NAND revision. The drive stops responding immediately after the update. Recovery via PC-3000 SSD technology mode can usually repair the config block and bring the drive back to a state where the FTL can be read and the data extracted.
3. NAND wear threshold crossed — controller in read-only or offline protection. Both the 870 EVO and 980 EVO use Samsung's 3D V-NAND, which has good endurance for consumer drives but does have a finite lifespan. As the drive accumulates write cycles, cells wear out and are retired by the controller. At some point, the total number of retired cells crosses a threshold where the controller no longer trusts the remaining cells enough to serve data reliably. Some Samsung SSDs respond to this by going silently read-only; others drop offline. Recovery depends on how many cells are still readable; in many cases, most of the data can be extracted from the surviving cells via technology-mode imaging.
How Data Clinic recovers an unrecognised Samsung EVO
On arrival we identify the exact Samsung EVO model (870 EVO SATA in 2.5" or M.2; 980 EVO or 980 NVMe in M.2) and the controller revision. This matters because PC-3000 SSD's Samsung technology mode profiles are controller-specific, and the correct profile is the difference between a fast recovery and a chip-off. We test the drive in two known-good interfaces to rule out a motherboard slot or SATA port fault — about 5% of "not recognised" cases are the slot, not the drive, and it's a quick check that saves a lot of unnecessary work.
If the Samsung controller is responsive in technology mode, we connect via PC-3000 SSD's Samsung-specific module. From technology mode we can read the controller's internal log, inspect the FTL state, and choose between repairing the FTL in-place (fastest) or extracting a raw image past the broken FTL (slower but more complete). A successful technology-mode recovery typically returns 95 to 100% of sectors and completes in 1 to 3 working days.
If the controller is not responsive in technology mode — typically the case when the flash update has fully bricked the controller chip rather than just corrupting config — we move to NAND chip-off. The drive is opened, the NAND chips are desoldered using a hot-air rework station, and each chip is read directly using a specialist NAND reader. Samsung V-NAND uses a well-documented page structure, and our forensic toolkit reconstructs the FTL from the NAND dump before assembling the file system. More about our SSD recovery service →.
Get a free initial diagnosis in 60 seconds
In the tool below, choose SSD → Not detected by computer for a Samsung-EVO-specific result.
What our customers say
"Three years of family photos on a drive that suddenly failed. Data Clinic collected next day, kept me updated through the cleanroom work, and got everything back. Worth every penny."
"Honest, fixed-price, no-fix-no-fee. Quoted by another lab at three times the price. Recovered 100% of my files."
"Reasonable cost, clear communication, and they were straight with me about what was recoverable and what wasn't. Recommended."
Frequently asked questions
Should I try Samsung Magician's diagnostic tools?
No. Magician connects to the drive via standard ATA commands, and a drive in protection mode doesn't respond to standard commands — Magician will either not see the drive at all or report it as failed and offer to secure-erase it. Do not click secure-erase under any circumstances; it sends a command that instructs the controller to discard all encryption keys and the data becomes unrecoverable immediately, even from chip-off.
My 870 EVO died right after a Magician update — is recovery still possible?
Yes, in most cases. Post-Magician-update failures on the 870 EVO are one of the most common Samsung cases we see and the recovery path is well-established. The config block corruption from a failed flash is repairable via PC-3000 SSD technology mode. Success rates for this specific failure are around 90%. Tell us it was a Magician update when you call so we start with the right tool.
How much does Samsung EVO recovery cost in the UK?
Technology-mode recoveries (controller responsive): typically £395 to £595 including VAT. NAND chip-off recoveries (controller dead): £695 to £1,195 depending on capacity and NAND chip count. We give a fixed price after free diagnosis. No fee if we cannot recover your data.
870 EVO vs 980 EVO vs 980 PRO — different recovery approaches?
The 870 EVO is SATA and uses the Samsung Phoenix controller; the 980 EVO is NVMe and uses Pascal. Both are handled via PC-3000 SSD technology mode, but the Samsung-specific profiles differ. The 980 PRO uses a different, higher-performance controller and had the documented 2022 to 2023 premature-failure issue — those are also recoverable via technology mode in most cases, but the profile is different again. Tell us your exact model number when you call.
How long does Samsung SSD recovery take?
Technology-mode recoveries: 1 to 5 working days. NAND chip-off: 5 to 10 working days. Emergency 24-hour and 48-hour services are available for technology-mode cases — call 0800 151 2207 to discuss.
Can I use data recovery software?
Only if the SSD is still being detected by your system. If the drive doesn't show up in BIOS, Disk Management or Disk Utility, software has nothing to connect to — it operates at a layer that assumes the drive is already presenting itself as a block device. Don't run software on a drive that isn't detected; it won't help and can interfere with our diagnosis.