SSD Controller Technical Reference
Intel 660p (SM2263) Controller Reference
The Intel 660p was the first consumer QLC NVMe SSD, using a Silicon Motion SM2263 controller with Intel-custom firmware. Intel's custom firmware modifications are explicitly excluded from PC-3000's standard Silicon Motion utility support. QLC NAND stores 16 voltage states per cell with incredibly tight margins, causing cells to degrade much faster than TLC and overwhelming LDPC error correction. ACELab's PC-3000 SSD supported-controller list does not currently cover this controller. For context on the SSDs we do recover, see our SSD data recovery page.
Intel 660p (SM2263) is not on the current PC-3000 SSD supported-controller list
Intel 660p (SM2263) does not appear on the current ACELab PC-3000 SSD supported-controller list (PC-3000 SSD / PC-3000 SSD Extended 3.8.10) as of 2026-05-12. Case-by-case feasibility only. Contact us before shipping anything and we will tell you in writing whether we can do anything for your specific drive.
Source of truth: ACELab PC-3000 SSD supported-drives list. Internal evidence file: src/lib/ssd-support-matrix.ts.
Intel 660p (SM2263) Specifications
| Manufacturer | Intel |
| Interface | NVMe Gen3 |
| NAND Types | QLC |
| DRAM Cache | Yes |
| Channels | 4 |
| PC-3000 Support | Limited / Generic NVMe |
| Chip-Off Viability | Not viable (AES-256 hardware encryption) |
Intel custom firmware on SM2263 is NOT covered by PC-3000's standard Silicon Motion utility. Intel modifications are explicitly excluded from SMI support. Recovery relies on generic NVMe access or Intel-specific diagnostic modes.
Affected SSD Models
The Intel 660p (SM2263) is deployed in the following consumer drives. A failure in this controller impacts access to the NAND flash on these specific models.
| # | Drive Model | Interface |
|---|---|---|
| 1 | Intel SSD 660p (512GB, 1TB, 2TB) | NVMe Gen3 |
Common Failure Modes and Symptoms
Each failure mode below describes a specific way the Intel 660p (SM2263) 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.
- QLC endurance exhaustion
Limited QLC endurance (200 TBW for 1TB). Extreme cell degradation leads to uncorrectable bit errors, firmware panic, and read-only lockouts.
- Drive drops offline under load
- Uncorrectable read errors
- Drive locks into read-only mode
- Firmware corruption
SM2263 controller with Intel-custom firmware. Firmware corruption from power loss or NAND degradation causes the drive to enter ROM Mode, reporting 0 bytes or identifying by its silicon name (SM2263EN) rather than Intel 660p.
- NVMe SSD not detected
- Drive not seen in BIOS
- Partition lost
- Drive identifies as SM2263EN instead of Intel 660p
- SLC cache exhaustion performance collapse
The 660p relies on a massive dynamic pseudo-SLC cache (up to 140GB on the 1TB model). Once the cache fills, native QLC write speeds plummet to 85-175 MB/s, forcing aggressive garbage collection and folding loops that strain NAND wear leveling and can trigger a firmware panic or read-only lockout.
- Write speeds suddenly dropped below 200 MB/s
- Drive becomes sluggish during sustained writes
- Drive hangs or crashes during large file operations
- SMART shows rapid wear increase
How Is Data Recovered from a Failed Intel 660p (SM2263) SSD?
Data is recovered from a failed controller SSD by keeping the original board alive, reading controller state with PC-3000 SSD, and rebuilding the Flash Translation Layer from surviving NAND metadata. If firmware access requires Safe Mode or a volatile loader, that work happens before imaging. When the controller also handles decryption, chip-off returns unreadable data.
At our Austin, TX lab, the goal is to keep the original controller stable long enough to expose ROM state, firmware behavior, and NAND metadata without letting the drive keep writing to itself. Our SSD data recovery overview covers lab intake and triage, why SSDs report 0 bytes explains capacity failures, and how SSD controller encryption works explains why the original silicon matters.
- Intel 660p (SM2263) 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 Drive drops offline under load, Uncorrectable read errors, Drive locks into read-only mode are useful to recognize, but on this controller they do not unlock a tooling path we can offer in-lab.
- Intel 660p (SM2263) is not on ACELab's PC-3000 SSD supported-controller list (PC-3000 SSD / PC-3000 SSD Extended 3.8.10). Without firmware utility coverage, the controller's mapping tables, internal loader, and any factory diagnostic mode are inaccessible to us, which means no firmware-level recovery is on the table.
- Intel 660p (SM2263) fuses AES-256 keys to the controller silicon, so desoldering the NAND chips returns ciphertext that cannot be decrypted without reviving the original controller through tooling we do not currently have for this controller.
Frequently Asked Questions
Can software recover data from a dead Intel 660p (SM2263)?
Why not use chip-off recovery on Intel SSDs?
Does Rossmann recover data from Intel 660p (SM2263) drives?
Can you recover deleted files from a Intel 660p (SM2263) SSD?
Have a Intel 660p (SM2263) drive?
We do not currently offer in-lab recovery for Intel 660p (SM2263) SSDs because the controller is not on ACELab's PC-3000 SSD supported-controller list. Contact us before shipping anything; we will confirm in writing what we can and cannot do for your specific drive.