SSD Controller Technical Reference
Phison PS3110-S10 Controller Reference
The Phison PS3110-S10 is a quad-core, 8-channel SATA controller with onboard DRAM that predates the ubiquitous S11. Its BCH error correction is less robust than modern LDPC, and aggressive OEM rebranding by Toshiba (TC58NC1000) and Lite-On means drives sharing identical silicon may require different PC-3000 loader profiles for recovery. 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.
Phison PS3110-S10 is not on the current PC-3000 SSD supported-controller list
Phison PS3110-S10 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.
Phison PS3110-S10 Specifications
| Manufacturer | Phison |
| Interface | SATA |
| NAND Types | MLC, TLC |
| DRAM Cache | Yes |
| Channels | 8 |
| PC-3000 Support | Supported (Active Utility) |
| Chip-Off Viability | Viable (older unencrypted models) |
32-bit quad-core microcontroller. BCH ECC less robust than LDPC, vulnerable with 3D TLC.
Affected SSD Models
The Phison PS3110-S10 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 | PNY CS1311/CS2211 | SATA |
| 2 | Patriot Ignite | SATA |
| 3 | Gigabyte UD PRO | SATA |
| 4 | Mushkin Striker | SATA |
| 5 | Kingston UV300 | SATA |
| 6 | OCZ Trion 100 | SATA |
| 7 | OCZ Trion 150 | SATA |
| 8 | Corsair Neutron XT | SATA |
| 9 | Toshiba Q300 (rebranded as TC58NC1000) | SATA |
| 10 | Seagate 600 SSD (select models) | SATA |
Common Failure Modes and Symptoms
Each failure mode below describes a specific way the Phison PS3110-S10 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.
- FTL corruption from NAND degradation
BCH error correction is less robust than modern LDPC. As the quad-core S10 controller detects that it can no longer manage physical addressing without errors from worn NAND cells, it triggers a self-preservation state that locks out all data access.
- SSD not detected
- Read errors increasing
- Sudden drive failure after years of use
- Safe Mode / 2MB capacity detection
Severe NAND errors force the controller into Safe Mode during power-on. The drive reaches READY state briefly then drops into Safe Mode, reporting a fractional capacity of 2MB, 20MB, or 0GB. This small capacity represents the internal firmware buffer, not the actual NAND storage.
- Drive reports 2MB or 20MB capacity in BIOS
- Drive shows generic Phison factory name instead of brand name
- Drive detected but partition inaccessible
- Drive enters BSY state and fails to initialize
- OEM firmware mismatch lockout
Aggressive OEM rebranding by Toshiba (TC58NC1000) and Lite-On modified the S10 firmware and command structure. Standard PC-3000 generic Phison loaders may be rejected by deeply proprietary firmware variants, requiring exact firmware family matching (e.g., SBFM or SBFK revisions).
- PC-3000 loader upload fails on rebranded drive
- Drive identified as Toshiba but uses Phison silicon
- Recovery utility does not recognize drive variant
How Is Data Recovered from a Failed Phison PS3110-S10 SSD?
Controller-class recovery starts by keeping the original board alive, reading controller state, and rebuilding the Flash Translation Layer from surviving NAND metadata. That firmware-level path depends on PC-3000 SSD utility coverage, which is not available for the Phison PS3110-S10.
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 Phison PS3110-S10 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.
- Phison PS3110-S10 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 SSD not detected, Read errors increasing, Sudden drive failure after years of use are useful to recognize, but on this controller they do not unlock a tooling path we can offer in-lab.
- Phison PS3110-S10 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.
- Chip-off on Phison PS3110-S10 is possible on older unencrypted variants but still requires reversing the controller-specific XOR scrambling, page order, and metadata, which depends on tooling we do not currently have for this controller.
Frequently Asked Questions
Can software recover data from a dead Phison PS3110-S10?
Why not use chip-off recovery on Phison SSDs?
Does Rossmann recover data from Phison PS3110-S10 drives?
Can you recover deleted files from a Phison PS3110-S10 SSD?
Other Phison Controllers
Phison PS3111-S11
SATA · Kingston A400, PNY CS900 (some variants)
Phison PS5012-E12
NVMe Gen3 · Corsair Force MP510, Sabrent Rocket NVMe
Phison PS5016-E16
NVMe Gen4 · Corsair Force MP600, Sabrent Rocket 4.0
Phison PS5018-E18
NVMe Gen4 · Corsair MP600 Pro/XT, Sabrent Rocket 4 Plus
Phison PS5021-E21T
NVMe Gen4 · Sabrent Rocket 2230, Corsair MP600 Mini/Core
Phison PS5027-E27T
NVMe Gen4 · Micron P310 2280, Timetec Gaming SSD (Gen4)
Have a Phison PS3110-S10 drive?
We do not currently offer in-lab recovery for Phison PS3110-S10 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.