Skip to main contentSkip to navigation

SSD Controller Technical Reference

Samsung MKX Controller Reference

Samsung's MKX controller powers the 870 EVO and 870 QVO. ACELab's PC-3000 SSD supported-controller list does not currently cover this controller, so we take these drives case by case rather than as a published service. For the rest of the workflow at our Austin, TX lab, see our SSD data recovery page.

Recovery Status

We take Samsung MKX drives case by case

The Samsung MKX is not on ACELab's PC-3000 SSD supported-controller list (PC-3000 SSD / PC-3000 SSD Extended 3.9.8), so no firmware utility we operate rebuilds its translator. We still look at these drives one at a time. A drive that still enumerates often needs nothing more than a logical recovery. Contact us with the model & the symptom before you ship anything, & we will tell you in writing what we think is possible.

Source of truth: ACELab PC-3000 SSD supported-drives list. Internal evidence file: src/lib/ssd-support-matrix.ts.

Author
Louis Rossmann
Written by
Louis Rossmann
Founder & Chief Technician
Updated May 2026
Samsung MKX Specifications

Samsung MKX Specifications

ManufacturerSamsung
InterfaceSATA
NAND Types3D TLC, 3D QLC
DRAM CacheYes
Channels8
PC-3000 SupportNot supported (absent from the ACELab list)
Chip-Off ViabilityNot viable (controller-bound data path)
Affected SSD Models

Affected SSD Models

Samsung's in-house controller is the part inside the following consumer drives. A failure in this controller impacts access to the NAND flash on these specific models.

#Drive ModelInterface
1Samsung 870 EVOSATA
2Samsung 870 QVOSATA
Common Failure Modes and Symptoms

Common Failure Modes and Symptoms

Each failure mode below describes a specific way the Samsung MKX fails and the symptoms you will observe. If your SSD matches any of these patterns, do not run recovery software; it cannot communicate with a dead controller. See the zero-byte SSD diagnostic reference for a deeper technical explanation of controller and FTL failures.

Controller failure causing non-detection

If the MKX controller is dead, the drive does not register in BIOS or the OS.

  • SATA SSD not detected
  • Drive completely invisible to BIOS
  • No response from drive
Controller Recovery Workflow

How Is Data Recovered from a Failed Samsung MKX SSD?

Controller-class recovery starts by keeping the original board alive, reading controller state, and rebuilding the Flash Translation Layer from surviving NAND metadata. No PC-3000 SSD utility rebuilds the translator on the Samsung MKX, so the firmware-level half of that workflow is closed to us. What is left is triage, logical recovery on a drive that still enumerates, and board-level repair of the original silicon.

Firmware access that needs Safe Mode or a volatile loader happens before any imaging. File-copy software never reaches this stage, since it needs a controller that already enumerates to the host. When the Samsung MKX also handles decryption, chip-off returns unreadable data, so the original silicon has to stay in the loop.

Holding a controller stable long enough to expose ROM state, firmware behavior, and NAND metadata without letting the drive write over itself is the core of controller-class recovery. Our SSD data recovery overview covers intake & triage, why SSDs report 0 bytes explains capacity failures, & how SSD controller encryption works explains why the original silicon matters.

  • Samsung MKX failures usually break the Flash Translation Layer, firmware boot path, or local power rail before macOS or Windows sees a mountable volume. Symptoms such as SATA SSD not detected, Drive completely invisible to BIOS, No response from drive tell us which bench the drive belongs on.
  • Samsung MKX is not on ACELab's PC-3000 SSD supported-controller list (PC-3000 SSD / PC-3000 SSD Extended 3.9.8), so no firmware utility we operate rebuilds its translator. We look at these drives one at a time instead of publishing a blanket refusal.
  • If the controller is electrically dead, the work is board-level repair of the original silicon. The media key is generated on and wrapped by that controller, so a donor chip reads its NAND as ciphertext.
FAQ

Frequently Asked Questions

Can software recover data from a dead Samsung MKX?
No. When the Samsung MKX fails, the drive does not enumerate in your operating system, and recovery software cannot communicate with a dead controller. This controller is not on ACELab's PC-3000 SSD supported-controller list, so no firmware utility we operate rebuilds its translator. Avoid running any consumer software or vendor MPTool flashing utility on the drive; both can overwrite NAND state.
Why not use chip-off recovery on Samsung SSDs?
Desoldering the NAND chips off a Samsung MKX drive and reading them in a programmer does not produce readable files: the controller's proprietary scrambling and LDPC error correction sit in front of the data, and on a drive whose hardware encryption is active the dump is ciphertext on top of that, because the media key is generated on and wrapped by the original controller. The only path is reviving that controller so it can read its own NAND, which depends on professional firmware utility coverage being available for it.
Does Rossmann recover data from Samsung MKX drives?
Case by case. The Samsung MKX is not on ACELab's PC-3000 SSD supported-controller list, so no firmware utility we operate rebuilds its translator. That is not the same as turning the drive away: one that still enumerates often needs nothing more than a logical recovery. Send us the model and the symptom and we will tell you in writing what we think is possible before you ship anything.
Can you recover deleted files from a Samsung MKX SSD?
TRIM marks deleted blocks for garbage collection on modern SSDs. Most controllers enforce Deterministic Read Zero after TRIM (RZAT on SATA, DLFEAT=001b on NVMe) at the protocol layer; every subsequent read to a TRIMmed LBA returns zeroes from the controller regardless of whether the NAND cells have been physically erased yet. The original charge states survive on NAND until garbage collection applies the +15-20V Fowler-Nordheim erase voltage, which is a narrow window. We specialize in recovering data from hardware failures: dead controllers, firmware corruption, and failed power delivery components.
Other Samsung Controllers

As Featured In

Have a Samsung MKX drive?

The Samsung MKX is not on ACELab's PC-3000 SSD supported-controller list, so no firmware utility we operate rebuilds its translator. We take these drives case by case anyway. Contact us before shipping anything; we will tell you in writing what we think is possible for your specific drive.

(512) 212-9111Mon-Fri 10am-6pm CT
No diagnostic fee
No data, no fee
4.9 stars, 1,837+ reviews