How a SATA SSD Differs from NVMe
A SATA SSD speaks AHCI over a 6 Gbps SATA III link. An NVMe SSD speaks NVMe over PCIe with up to 32 Gbps on a Gen4 x4 connection. The protocols, command queues, & physical layers are different, & so are the recovery procedures.
SATA III caps single-drive throughput at roughly 550 MB/s on sequential reads. The AHCI command set was designed for spinning disks; it supports a single command queue of 32 entries (NCQ). NVMe by contrast allows up to 65,535 queues of 65,536 entries each. From a recovery perspective the practical consequence is link behavior: SATA SSDs use Link Power Management states (HIPM, DIPM, DevSleep) that can mask intermittent controller faults during normal-mode imaging unless those states are explicitly disabled on the test bench.
The NAND, FTL concepts, garbage collection, wear leveling, & TRIM behavior are shared across both interface families. The difference relevant to recovery is what happens when the controller dies: on a SATA SSD the host expects a SATA identify response, on NVMe the host expects an NVMe controller capability register read. PC-3000 SSD has separate utilities for each. For NVMe-specific procedures see the NVMe SSD recovery page.
Dominant SATA SSD Controller Families & Their Failure Modes
Four controller vendors account for the bulk of SATA SSDs sold over the past decade: Silicon Motion, Phison, Marvell, & Samsung. Each family has characteristic failure modes that determine which recovery tier applies.
Silicon Motion SM2258 / SM2259
Found in Crucial MX500, Crucial BX500, ADATA SU800 / SU900, Plextor S2C, Transcend SSD370S, WD Green G1, & many DRAM-less budget drives (the XT variants). Common failure modes: firmware-area corruption that causes the drive to enumerate with a wrong model string ("SATAFIRM S11" being the canonical SM2258 fault state), bad blocks accumulating in the system area, & controller hangs during boot. The SM2258XT & SM2259XT use Host Memory Buffer instead of dedicated DRAM, which makes them more sensitive to power-loss FTL corruption.
Phison PS3110 / PS3111 / PS3112 (S11 / S12)
Found in Kingston A400, Patriot Burst, GOODRAM CX400 / IRDM, Apacer AS340 / AS450, Lite-On MU3, OCZ Trion 100, Seagate BarraCuda Q1, & many rebrands. Common failure modes: the controller enters a "BSY" busy state on boot & never clears it, blocking host enumeration; the drive enumerates but reports the wrong capacity; or the drive disappears entirely after a power event. PC-3000 SSD has a Phison-specific utility that can communicate with these controllers in technological mode for FTL reconstruction.
Marvell 88SS1074 & SandForce legacy
The 88SS1074 powers SanDisk SSD Plus, SanDisk Ultra II, & WD Blue G1. It is one of the more reliable SATA controllers in the field; failures usually trace to NAND wear-out rather than controller logic faults. Older SandForce SF-2281 drives (Intel 520, OCZ Vertex 3, Kingston HyperX) are no longer in active production but still arrive at the lab regularly; they have well-documented failure patterns including the infamous "8MB bug" where the drive presents as an 8 MB device after power loss.
Samsung SATA (MGX, MHX, MJX, MKX)
Samsung 840, 850 EVO, 860 EVO, & 870 EVO. Older generations (MGX / MHX) permit firmware-level technological mode access in PC-3000 SSD for FTL reconstruction. Samsung locked that path on the MKX (870 EVO) generation, so 870 EVO recovery relies on board-level stabilization plus normal-mode imaging rather than loader-based firmware rewrites. AES-256 hardware encryption is applied transparently on all Samsung SATA drives, so chip-off is not a viable path when the controller is dead.
Other SATA controllers we work on regularly include Maxio MAS0902 (ADATA SU630 / SU635 / SU650, Apacer AS340 / AS350, HIKVISION C100 / C260, Lexar NS100, Verbatim Vi550), Indilinx Barefoot (Crucial M225, OCZ Vertex 1), OCZ Barefoot 3 (OCZ Vector, OCZ Vertex 450, AMD Radeon R7), & Intel PC29AS21AA0 (Intel X25, Intel 310, Intel 710). The Sandisk SSD Plus / Ultra II case has its own dedicated SanDisk firmware failure page.
Crucial models are common enough to have their own page; see the Crucial SSD recovery page for MX500 / BX500 / M500-series specifics.
Why Software-Only Recovery Usually Fails on Modern SATA SSDs
Once the operating system has issued the SATA TRIM command (DATA SET MANAGEMENT with the Trim bit set) for a range of LBAs, the SSD controller marks those NAND pages as no longer holding valid user data. Garbage collection then physically erases the blocks on its own schedule. After that, reading those LBAs returns deterministic zeros (DZAT) on most drives. There is no software trick that retrieves data from a physically erased NAND block.
This is the single biggest difference between SSD recovery & spinning-disk recovery. On an HDD a deleted file is still magnetically present until the sector is overwritten; file-carving tools can recover it for months. On a SATA SSD with TRIM enabled the window is seconds to minutes. Once TRIM has fired & garbage collection has run, no tool & no lab can reverse the erase. The data is gone at the hardware layer.
For the underlying physics, see our dedicated TRIM & DZAT physics page, & for the practical decision tree on what is & is not recoverable see TRIM & garbage collection data loss. Recovery is realistic only when TRIM was disabled (some legacy systems & specific filesystems), the drive was pulled before the OS issued the TRIM commands, or the drive was already in a failed state that prevented garbage collection from running.
Recovery software like Disk Drill, EaseUS, PhotoRec, & R-Studio is genuinely useful when an SSD is physically healthy & the failure is logical: an accidentally formatted partition that has not been written over, a corrupted partition table, or a deleted file on a drive where TRIM did not fire. Those tools cannot help when the controller is dead, the firmware is corrupted, or TRIM has already erased the blocks. That is when the case escalates to lab-tier work.
SATA SSD Recovery Does Not Need a Cleanroom
SATA SSDs have no platters, no read/write heads, no spindle motor, & no helium fill. The case opens to a PCB with a controller IC, a few NAND packages, sometimes a DRAM cache, & passive components. There is nothing inside that can be damaged by airborne particulates.
SATA SSD recovery is electronics repair plus PC-3000 SSD work. We use FLIR thermal cameras to localize shorts on the PCB, Hakko FM-2032 microsoldering irons (on FM-203 or FX-951 base stations) for component-level rework, Atten 862 hot air for chip removal, & Zhuo Mao precision BGA stations for controller reflow. None of this work requires ISO 14644-1 air-quality control. Any vendor adding a cleanroom surcharge to an SSD quote is either misinformed or padding the bill.
For the full breakdown of where the SSD cleanroom myth comes from & how to spot it in the wild, see the SSD cleanroom myth page.
The Modern SATA SSD Encryption Reality
Most SATA SSDs sold since roughly 2015 apply AES-256 hardware encryption to all writes by default, whether or not the user enabled BitLocker or set an ATA password. The encryption key lives on the controller silicon. If the controller dies, the NAND holds only ciphertext.
This is the encryption barrier that drives most modern SATA SSD recovery toward board-level repair rather than chip-off. When a Crucial MX500, Samsung 870 EVO, or Kingston A400 controller fails, the only recovery path that preserves the key relationship is to revive that exact controller IC: locate the failed component on the PCB (typically a PMIC channel, a voltage regulator, or a shorted decoupling capacitor) using FLIR thermal imaging, then replace the failed part with the original controller still in place. When the controller boots again, the AES engine has its key, & the NAND is readable over SATA.
Older unencrypted SATA SSDs (pre-2015 SandForce, early Marvell) can still be recovered through chip-off & FTL reconstruction; the NAND content is plaintext, so a separate read jig plus PC-3000 SSD's chip-off utility can rebuild the logical layout. Modern encrypted drives cannot be recovered this way. For chip-off scope & limits on legacy drives see our chip-off NAND page.
How a SATA SSD Case Moves Through the Lab
- 01
Intake & free evaluation
The drive ships in or arrives at the Austin lab. We power it on a PC-3000 SSD bench with link power management disabled & host timeouts extended. If the controller enumerates, we read identify data, S.M.A.R.T. attributes, & system-area metadata. If it does not enumerate, we move to PCB diagnosis. No diagnostic fee.
- 02
Tier classification & firm quote
Based on what the bench reports, the case is classified as simple copy, file system, board, firmware, or NAND swap. We give you a firm quote in writing before any paid work begins. You decide whether to proceed.
- 03
Board repair (if applicable)
If a PCB component has failed, we localize the fault with FLIR thermal imaging, desolder the failed part with Atten 862 hot air or Zhuo Mao BGA rework, & solder the replacement with Hakko FM-2032 on an FM-203 or FX-951 base. The original controller IC stays in place to preserve the AES encryption key.
- 04
Firmware reconstruction (if applicable)
When the controller boots but the firmware is corrupted (wrong model string, wrong capacity, missing modules), PC-3000 SSD enters technological mode for the controller family & rebuilds the corrupted FTL, module table, or system area. This is the path that "SATAFIRM S11" Silicon Motion drives & BSY-state Phison drives typically follow.
- 05
Imaging & file delivery
Once the drive enumerates cleanly, imaging proceeds with error isolation. Marginal LBAs are revisited with extended per-command timeouts. The image is mounted on a separate workstation, the file system is parsed, & files are delivered on your choice of return media.
SATA SSD Data Recovery Pricing
Five tiers, set by what failed on the drive. Free evaluation determines which tier applies before any paid work begins.
Low complexity
Simple Copy
Your drive works, you just need the data moved off it
Functional drive; data transfer to new media
Rush available: +$100
$200
3-5 business days
Low complexity
File System Recovery
Your drive isn't showing up, but it's not physically damaged
File system corruption. Visible to recovery software but not to OS
Starting price; final depends on complexity
From $250
2-4 weeks
Medium complexity
Circuit Board Repair
Your drive won't power on or has shorted components
PCB issues: failed voltage regulators, dead PMICs, shorted capacitors
May require a donor drive (additional cost)
$450–$600
3-6 weeks
Medium complexity
Most Common
Firmware Recovery
Your drive is detected but shows the wrong name, wrong size, or no data
Firmware corruption: ROM, modules, or system files corrupted
Price depends on extent of bad areas in NAND
$600–$900
3-6 weeks
High complexity
PCB / NAND Swap
Your drive's circuit board is severely damaged and requires NAND chip transplant to a donor PCB
NAND swap onto donor PCB. Precision microsoldering and BGA rework required
50% deposit required; donor drive cost additional
50% deposit required
$1,200–$1,500
4-8 weeks
Hardware Repair vs. Software Locks
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
No data, no fee. Free evaluation and firm quote before any paid work. Full guarantee details. NAND swap requires a 50% deposit because donor parts are consumed in the attempt.
- Rush fee
- +$100 rush fee to move to the front of the queue
- Donor drives
- 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.
- Target drive
- The destination drive we copy recovered data onto. You can supply your own or we provide one at cost plus a small markup. All prices are plus applicable tax.
Data Recovery Standards & Verification
Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to make sure your hard drive is handled safely and properly. This approach allows us to serve clients nationwide with consistent technical standards.
Open-drive work is performed in a ULPA-filtered laminar-flow bench, validated to 0.02 µm particle count, verified using TSI P-Trak instrumentation.
Transparent History
Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.
Media Coverage
Our repair work has been covered by The Wall Street Journal and Business Insider, with CBC News reporting on our pricing transparency. Louis Rossmann has testified in Right to Repair hearings in multiple states and founded the Repair Preservation Group.
Aligned Incentives
Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.
Technical Oversight
Louis Rossmann
Louis Rossmann's well trained staff review our lab protocols to ensure technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.
We believe in proving standards rather than just stating them. We use TSI P-Trak instrumentation to verify that clean-air benchmarks are met before any drive is opened.
See our clean bench validation data and particle test videoFrequently Asked Questions
How much does SATA SSD data recovery cost?
Pricing depends on what failed. A working drive that just needs the data moved off starts at $200. File-system recovery starts From $250. Board-level work on a dead PCB runs $450–$600. Firmware reconstruction with PC-3000 SSD runs $600–$900. NAND transplant onto a donor PCB runs $1,200–$1,500; 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. Free evaluation, no diagnostic fee, & no data means no recovery fee.
How long does SATA SSD recovery take?
Simple copy: 3-5 business days. File-system recovery: 2-4 weeks. Board repair: 3-6 weeks. Firmware recovery: 3-6 weeks. NAND swap: 4-8 weeks. +$100 rush fee to move to the front of the queue.
Why does recovery software fail on a modern SATA SSD?
Two reasons. First, when the controller is dead the drive does not enumerate over SATA, so software has nothing to talk to. No tool can scan a device that the OS cannot see. Second, when TRIM has run, the controller has already issued physical erase commands to the NAND blocks holding the deleted file. Those blocks now read back as deterministic zeros (DZAT). Software cannot reverse a hardware-level erase. Recovery software is useful when the drive is healthy & the file system is intact; it is the wrong tool when the controller, firmware, or NAND has failed.
What arrives in working condition versus needing board work?
If the drive enumerates over SATA & the host can see a model string, the case is usually file-system or firmware tier. If the drive does not power up, draws abnormal current, gets warm at the controller IC, or shows up with a wrong model string, the case is board-level: a failed PMIC, shorted decoupling capacitor, or open voltage regulator on the PCB. We diagnose this with a bench multimeter, FLIR thermal imaging for short-localization, & PC-3000 SSD for controller communication.
What happens if the SATA controller is dead?
Modern SATA SSDs apply AES-256 encryption transparently inside the controller. The encryption key lives on the controller silicon, not on the NAND. If the controller IC itself is dead (not just the surrounding board), the only path to your data is reviving the original controller through PMIC replacement or component-level repair so the encryption key relationship is preserved. Desoldering the NAND chips & reading them on a separate jig yields ciphertext on encrypted drives. Older unencrypted SATA SSDs (pre-2015 SandForce, early Marvell) can still be recovered through chip-off & FTL reconstruction; modern ones cannot.
Is a cleanroom required for SATA SSD recovery?
No. SATA SSDs have no platters, no read/write heads, & no spindle motor. There is nothing inside the case that can be contaminated by particulates. Recovery is an electronics-repair discipline: PCB diagnosis, microsoldering, & PC-3000 SSD work. Any lab that quotes a cleanroom surcharge for an SSD is either confused or upcharging. See our cleanroom myth page for the full breakdown.
Can deleted files be recovered from a SATA SSD?
Only if TRIM did not run on the affected blocks. On Windows 7+ & macOS 10.6.8+ with a healthy SSD, TRIM fires within seconds to minutes of file deletion & the controller's garbage collection then physically erases the NAND pages. Once that happens, the data is gone at the hardware layer & no lab can reverse it. Deleted-file recovery on SATA SSDs is realistic only when TRIM was disabled, the drive was pulled immediately, the file system did not support TRIM, or the drive was already in a failed state that prevented garbage collection from running.
Which SATA SSD controllers does the lab support?
PC-3000 SSD covers the dominant SATA controller families: Silicon Motion (SM2236, SM2246, SM2256, SM2258, SM2259 & their XT variants), Phison (PS3105, PS3108, PS3109, PS3110, PS3111, PS3112), Marvell (88SS9174, 88SS9187, 88SS9189, 88SS9190, 88SS1074), Samsung SATA (S3C29MAX01, S4LJ204X01, S4LN021X01, S4LN045X01, S4LN054X02), Maxio MAS0902, Indilinx Barefoot, OCZ Barefoot 3, & Intel PC29AS21AA0. Maxio MAS1102 is partially supported (ADATA SU650 240GB only).
SATA SSD failed? Get a free evaluation.
Pricing $200–$1,500. No diagnostic fee. No data, no recovery fee. +$100 rush fee to move to the front of the queue.