What Is an M.2 SSD?
M.2 is a physical card format that replaced the older mSATA & 2.5-inch SATA form factors in most laptops & desktops manufactured after 2015. The M.2 slot accepts drives running either the SATA protocol or the NVMe protocol, but the two are not interchangeable; the connector keying determines which interface the drive supports.
The keying difference is simple. B-key (a notch on the left side of the connector, 6 pins wide) means SATA. M-key (a notch on the right side, 5 pins wide) means NVMe over PCIe x4. B+M key (notches on both sides) fits in either slot but typically runs at SATA speeds or PCIe x2. This matters for recovery because connecting a SATA M.2 drive to an NVMe-only PC-3000 adapter produces no response at all.
Recovery pricing starts at $200 for SATA M.2 drives & $200 for NVMe M.2 drives. The first step in every M.2 case is identifying which protocol the drive uses, which takes under 30 seconds by checking the key notch.
M.2 Sizes & Which Devices Use Them
M.2 drives come in four standard lengths. The first two digits (22) are the width in millimeters; the last two or three digits are the length. All four sizes use the same edge connector, so recovery hardware adapters are universal. The difference is which devices ship with which size.
- 2230 (22mm x 30mm)
- The smallest standard M.2 size. Found in the Steam Deck, Microsoft Surface Pro 8/9, Dell XPS 13, Framework Laptop, & Xbox Series X expansion cards. The compact PCB means denser component placement & tighter thermal margins. A 2230 NVMe drive crammed into a Steam Deck with no heatsink runs hotter than a 2280 in a desktop with active airflow, accelerating controller wear over time.
- 2242 (22mm x 42mm)
- Found in some compact ultrabooks, industrial embedded systems, & thin-client PCs. Less common in consumer hardware than 2230 or 2280. Transcend & Kingston produce 2242 SATA M.2 drives for legacy systems that need the shorter length.
- 2280 (22mm x 80mm)
- The standard desktop & laptop M.2 size. Samsung 980/990 Pro, WD Black SN770/SN850X, Crucial P5 Plus, Corsair MP600, Sabrent Rocket 4 Plus all ship as 2280. This is the drive we receive most often for recovery. The longer PCB allows better thermal spreading & room for a DRAM cache chip.
- 22110 (22mm x 110mm)
- Enterprise & server M.2 form factor. Used in Intel Optane M.2 drives & some data center NVMe SSDs. Requires a motherboard or riser card with a 22110 standoff position. Rare in consumer devices.
How Much Does M.2 SSD Data Recovery Cost?
M.2 SSD recovery costs between From $200 and $2,500, depending on the interface (SATA or NVMe) & the failure mode (logical, firmware, board-level, or NAND transplant). The form factor size doesn't affect the price. A 2230 NVMe with firmware corruption costs the same as a 2280 NVMe with the same failure. Free evaluation, firm quote before work begins, no data recovered means no charge.
| Failure Type | SATA M.2 Price | NVMe M.2 Price |
|---|---|---|
| Simple Copy | $200 | $200 |
| File System Recovery | From $250 | From $250 |
| Circuit Board Repair | $450–$600 | $600–$900 |
| Firmware Recovery | $600–$900 | $900–$1,200 |
| PCB / NAND Swap | $1,200–$1,500 | $1,200–$2,500 |
Circuit board repair involves component-level microsoldering: replacing failed PMICs, voltage regulators, or shorted capacitors using a Hakko FM-2032 iron. On encrypted drives, this tier revives the original controller & preserves the AES-256 encryption key. +$100 rush fee to move to the front of the queue. A donor drive is a matching SSD used for its circuit board. Typical donor cost: $40–$100 for common models, $150–$300 for discontinued or rare controllers.
What Should You Do if Your M.2 SSD Stops Working?
The actions you take in the first minutes after an M.2 SSD failure determine whether marginal data survives. Every unnecessary power cycle gives the controller a chance to run garbage collection or attempt a firmware recovery that overwrites recoverable NAND pages.
- Power off the device immediately. Shut down the laptop or desktop. Don't restart it to "see if it comes back." Each boot attempt triggers controller initialization routines that can overwrite FTL metadata.
- Don't run recovery software. If the drive isn't detected in BIOS, software can't reach it. If it is detected but showing wrong capacity, software read attempts stress degraded NAND cells & can push them past the ECC correction threshold.
- Don't reinsert the drive in different slots. Repeatedly pulling & reinserting an M.2 drive risks scratching the gold edge connector contacts. M.2 connectors are rated for 60 insertion cycles; a damaged connector adds a physical repair step to the recovery.
- Don't reinstall your operating system. Installing an OS on the same drive triggers TRIM on the old partitions & overwrites NAND pages. Both actions destroy data.
- Note what happened. Did the drive disappear after a BIOS update, a power outage, a sleep/wake cycle, or gradually over time? This narrows the failure mode before we open the case.
- Ship it to us. M.2 drives are small & fragile. Wrap in anti-static material, place in a rigid box with cushioning. See our mail-in recovery page for free inbound shipping labels. Call (512) 212-9111 if you have questions.
When Does Recovery Software Work on M.2 SSDs?
Recovery software like Disk Drill, EaseUS, PhotoRec, & R-Studio works when the M.2 SSD is physically healthy & the operating system can see it as a normal block device. The problem is logical: accidentally deleted files, a corrupted partition table, or a formatted volume. In these cases, software reads the NAND through the controller's normal interface & reconstructs directory entries.
There's one major limitation even on healthy drives. If TRIM is enabled (the default on Windows 7+ & macOS 10.6.8+), the controller unmaps deleted blocks and schedules garbage collection, which erases the NAND cells back to their unprogrammed state (0xFF) within seconds to minutes. Software can't recover data the controller has unmapped and erased. Recovery is only possible if TRIM didn't execute: the drive was pulled immediately, TRIM was disabled, or the file system doesn't support TRIM.
Lab recovery is required when the controller is dead (drive not detected in BIOS), firmware is corrupted (drive stuck in safe mode or reporting wrong capacity), NAND is degraded (accumulating uncorrectable read errors), or the controller's encryption key needs to be preserved. In these cases, the PC-3000 SSD accesses the controller's internal command set through vendor-specific diagnostic commands that consumer software can't issue.
How Does M.2 SATA Recovery Differ from M.2 NVMe Recovery?
M.2 SATA & M.2 NVMe drives share the same physical connector but use different protocols, different command sets, & require different PC-3000 adapter modules. A SATA M.2 drive connected to an NVMe-only adapter produces no enumeration at all; the protocols are electrically incompatible.
| Attribute | M.2 SATA | M.2 NVMe |
|---|---|---|
| Command Set | ATA (AHCI) | NVMe (PCIe) |
| PC-3000 Module | PC-3000 SSD (SATA adapter) | PC-3000 Portable III (NVMe adapter) |
| Max Bandwidth | 600 MB/s (SATA III) | 14,000 MB/s (PCIe 5.0 x4) |
| Hardware Encryption | Some (TCG Opal on SED models) | Many, but not all (varies by model) |
| TRIM Behavior | Standard DATA SET MANAGEMENT | Deallocate (NVMe equivalent) |
| Connector Keying | B-key or B+M key | M-key |
| Common Controllers | SM2259, SM2258, Phison PS3111 | Phison E12/E18, SM2262/SM2269, Samsung Elpis |
| Recovery Price Range | $200–$1,500 | $200–$2,500 |
The encryption difference is the most consequential for recovery. Many NVMe controllers implement AES-256 encryption by default, though several widely used DRAM-less models (WD SN770, Crucial P1/P2/P3) lack hardware encryption entirely. On drives with always-on encryption, a dead controller means chip-off NAND extraction yields only ciphertext. SATA M.2 drives are less likely to use always-on encryption unless they implement TCG Opal. See the hardware encryption recovery page for the full breakdown.
Common M.2 SSD Failure Modes
M.2 drives fail from connector damage, thermal stress, firmware corruption, NAND wear, & power delivery faults. The exposed PCB format (no protective enclosure like a 2.5-inch SATA SSD) makes M.2 drives physically vulnerable to ESD, flexing, & improper insertion during user installation.
Connector Pin Damage
M.2 edge connectors use 67 or 75 pins at a 0.5mm pitch. Inserting the drive at the wrong angle, forcing it into an incompatible slot, or repeatedly removing & reinserting it scratches or shears the gold contacts. A single damaged signal pin can prevent PCIe link training or SATA negotiation entirely. The drive appears dead to the system, but the controller & NAND are unharmed.
Recovery approach: board-level repair to restore the damaged traces or bypass the connector entirely by soldering directly to the PCB test points.
Thermal Cycling Controller Burnout
M.2 slots in laptops are often sandwiched between the battery & the CPU, with zero airflow. The 2230 form factor is worse: less PCB surface area to dissipate heat. Repeated thermal cycling (hot during use, cold at shutdown) stresses BGA solder joints between the controller IC & the PCB. Over time, microcracks form in the solder balls, creating intermittent connections that progress to complete failure.
Recovery approach: FLIR thermal imaging to identify the fractured joint, then Zhuo Mao BGA rework station for controller reflow or replacement.
BGA Joint Fracture from PCB Flexing
M.2 drives are secured by a single standoff screw at the far end. If the standoff is missing or the wrong height, the PCB flexes under mechanical stress (laptop in a backpack, for example). This flexing cracks the BGA solder balls under the controller or NAND packages. The drive works intermittently, then fails permanently.
Recovery approach: Zhuo Mao BGA rework to reflow or reball the affected IC. Board repair cost for this failure falls in the $450–$600 (SATA) or $600–$900 (NVMe) range.
Firmware Corruption After Power Loss
A sudden power loss during a write to the SSD's service area corrupts the Flash Translation Layer mapping table. The FTL is the index that tells the controller which physical NAND page holds which logical block address. Without a valid FTL, the controller can't boot, and the drive reports 0 capacity or shows a generic "SATAFIRM S11" identifier instead of its real model name.
Recovery approach: PC-3000 SSD enters technological mode, loads the controller without the corrupted user firmware, scans NAND pages for FTL checkpoint copies, & reconstructs the mapping table. Cost falls in the firmware recovery tier: $600–$900 (SATA) or $900–$1,200 (NVMe). See firmware corruption recovery for controller-specific details.
NAND Cell Degradation
Every NAND cell has a finite number of program/erase cycles: roughly 3,000 for TLC and 1,000 for QLC. As cells wear, the voltage thresholds between states shift, increasing bit error rates beyond the ECC correction capability. The drive starts returning uncorrectable read errors, then goes read-only, then becomes completely unresponsive. The 2230 form factor accelerates this degradation because higher operating temperatures speed up charge leakage in NAND cells.
Recovery approach: PC-3000 SSD performs multiple read passes with shifted reference voltages to recover data from marginal cells. Severe NAND degradation may require chip-off extraction & raw NAND page reassembly at the $1,200–$1,500 (SATA) or $1,200–$2,500 (NVMe) tier.
Samsung 980 Pro Read-Only Firmware Bug
Samsung's firmware version 3B2QGXA7 for the 980 Pro 2TB caused rapid SMART health degradation unrelated to actual NAND wear. The drive drops to read-only mode, then becomes completely inaccessible. Samsung released firmware patch 5B2QGXA7, but drives that degraded before the patch accumulated real block errors on top of the reporting bug. The PC-3000 Samsung utility reads actual NAND health counters independent of the firmware's reported values to assess true cell condition before attempting recovery.
WD SN770 Windows 11 24H2 Conflict
The WD SN770 has a documented Host Memory Buffer conflict with the stornvme.sys driver in Windows 11 24H2. The HMB allocation fails, causing the SSD to disappear from BIOS or trigger BSOD loops. In some cases, the SSD becomes permanently unresponsive after the driver corrupts the FTL metadata stored in host RAM during the crash. Recovery requires board-level diagnosis to determine whether the controller firmware can be restored or if the FTL metadata loss is permanent.
Why Does Encryption Make M.2 Recovery Harder?
Many M.2 NVMe SSDs encrypt data automatically using AES-256, even if you never enabled encryption. Popular exceptions exist: the WD SN770 and Crucial P1/P2/P3 lack hardware encryption. On drives that do encrypt, the key is fused to the controller silicon. If the controller dies, removing the NAND chips & reading them directly produces only ciphertext with no way to retrieve the key.
Board-level repair to revive the original controller is the only recovery path for encrypted M.2 drives. We locate the failed component (typically a PMIC, voltage regulator, or shorted capacitor) using FLIR thermal imaging, replace it with a Hakko FM-2032 microsoldering iron on an FM-203 base station, & bring the original controller back to life. When the controller boots, the encryption keys are intact & the data is accessible through normal PC-3000 channels.
SATA M.2 drives are less uniformly encrypted. Budget SATA M.2 drives with SM2259 or SM2258 controllers often don't implement TCG Opal or self-encrypting drive (SED) features, meaning chip-off NAND extraction remains a viable fallback if the controller is destroyed. We determine encryption status during the free evaluation before quoting a recovery path.
Board repair for encrypted M.2 drives isn't a separate service from data recovery; for encrypted SSDs, it IS data recovery. Most data recovery labs outsource board-level failures or declare them unrecoverable. We perform the repair in-house at our Austin, TX lab using Hakko FM-2032 irons, Atten 862 hot air rework, & Zhuo Mao BGA stations. Single location, no outsourcing. The technician who diagnoses your drive is the technician who repairs it.
PC-3000 SSD Recovery Workflow for M.2 Drives
Every M.2 recovery starts with identifying the interface & controller family. Using the wrong PC-3000 module or the wrong diagnostic mode entry procedure can overwrite the FTL metadata that makes recovery possible. The workflow below applies to both SATA & NVMe M.2 drives, with the adapter & module differing based on the interface.
- Interface identification. Check the connector keying: B-key notch means SATA, M-key means NVMe. Confirm by reading the label or checking the controller IC markings under a microscope. SATA M.2 goes to the PC-3000 SSD SATA adapter; NVMe M.2 goes to the PC-3000 Portable III NVMe adapter.
- FLIR thermal scan. Before applying power, scan the PCB with a FLIR thermal camera to check for shorts. A shorted PMIC or voltage regulator draws excess current on power-up, which can cause secondary damage to the controller. If a short is detected, the component is replaced before the drive is powered.
- PC-3000 SSD connection. Load the correct vendor-specific utility module: Phison utility for PS3111/E12, Silicon Motion utility for SM2258/SM2259/SM2262/SM2269, Samsung utility for Phoenix/Elpis controllers. Each module contains the diagnostic mode entry commands specific to that controller family.
- Technological mode entry. The utility sends vendor-specific commands that put the controller into a low-level diagnostic state instead of loading the corrupted user firmware. In technological mode, the controller exposes direct NAND access. Some controllers require GPIO pin shorting on the PCB to enter this mode.
- FTL reconstruction. If the Flash Translation Layer is corrupted, the utility scans NAND pages for surviving metadata checkpoints & rebuilds the logical-to-physical block mapping. This step can take hours on high-capacity drives because every NAND page must be read & analyzed for valid mapping data.
- Sector-by-sector imaging. With the FTL reconstructed, the drive presents its full logical capacity. Data is imaged sector-by-sector to a known-good target. The utility logs unreadable NAND pages, retry counts, & ECC correction statistics for each pass.
- Escalation to chip-off. If the controller is dead & can't be revived through board repair, and the drive does not use hardware encryption, the case escalates to chip-off NAND recovery. NAND chips are desoldered using the Atten 862 hot air station, read on a specialized reader, & the FTL is reconstructed from raw page data. If the drive uses encryption & the controller is dead beyond repair, we inform you that the data is unrecoverable before any paid work.
M.2 Physical Vulnerabilities vs. 2.5-Inch SSDs
A 2.5-inch SATA SSD sits inside a metal or plastic enclosure that shields the PCB from physical contact, ESD, & environmental contamination. An M.2 drive has none of that protection. The bare PCB slides into a slot with exposed components on both sides.
Three physical risks are unique to M.2 drives. First: ESD damage during user installation. Touching the exposed controller or NAND packages without proper grounding can discharge static through the IC, damaging internal transistor gates. Second: connector pin wear from repeated insertion. The M.2 edge connector is rated for roughly 60 cycles; enthusiasts who swap drives frequently approach that limit. Third: PCB flex damage from improper standoff installation, as described in the failure modes section.
These physical vulnerabilities add recovery steps that 2.5-inch SATA SSDs rarely need. A 2.5-inch SSD arrives with intact connectors & protected components. An M.2 drive may arrive with a bent PCB, scratched contacts, or ESD damage to the controller that requires board-level repair ($450–$600 for SATA M.2, $600–$900 for NVMe M.2) before the diagnostic tools can even communicate with it.
M.2 SSD Data Recovery FAQ
Can data be recovered from a dead M.2 SSD?
Does the physical size of my M.2 drive affect recovery?
How do I know if my M.2 SSD uses SATA or NVMe?
Why is my M.2 SSD not detected in BIOS?
Can recovery software fix an M.2 SSD that won't show up?
Does M.2 SSD data recovery void my warranty?
How long does M.2 SSD data recovery take?
What happens if TRIM has already run on my deleted files?
M.2 SSD not responding?
Free evaluation. SATA M.2 from From $200. NVMe M.2 from From $200. No data, no fee.