SSD Controller Technical Reference
Innogrit IG5236 (Rainier) Controller Reference
The Innogrit IG5236 (codenamed Rainier) is a premium 8-channel Gen4 NVMe controller with onboard DRAM. When the controller suffers a firmware exception, it drops its OEM identity and reverts to its factory silicon descriptor MN-5236 with capacity shrinking to 2.1GB or 2MB. A deeply ingrained firmware instability under sustained mixed I/O causes buffer overflows that crash the controller into this permanent ROM state. 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.
Innogrit IG5236 (Rainier) is not on the current PC-3000 SSD supported-controller list
Innogrit IG5236 (Rainier) 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.
Innogrit IG5236 (Rainier) Specifications
| Manufacturer | Innogrit |
| Interface | NVMe Gen4 |
| NAND Types | 3D TLC |
| DRAM Cache | Yes |
| Channels | 8 |
| PC-3000 Support | Supported (Active Utility) |
| Chip-Off Viability | Not viable (AES-256 hardware encryption) |
AES-256 hardware encryption makes chip-off not viable. PC-3000 SSD Extended supports Innogrit controllers. 8-channel architecture with onboard DRAM.
Affected SSD Models
The Innogrit IG5236 (Rainier) 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 | ADATA XPG Gammix S70 Blade | NVMe Gen4 |
| 2 | HP FX900 Pro | NVMe Gen4 |
| 3 | Acer Predator GM7000 | NVMe Gen4 |
| 4 | Mushkin Redline Vortex | NVMe Gen4 |
Common Failure Modes and Symptoms
Each failure mode below describes a specific way the Innogrit IG5236 (Rainier) 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.
- Firmware exception / BSoD trigger
Early firmware revisions on drives using this controller caused Windows BSoD (KERNEL_DATA_INPAGE_ERROR) under sustained mixed workloads. The drive may enter read-only mode or become unresponsive after the crash.
- Windows BSoD during file operations
- Drive enters read-only mode
- SMART reports pending sector count increase
- Power loss recovery loop
After an unclean shutdown, the controller enters a recovery cycle that can take 30+ seconds. If interrupted by the user power cycling again, FTL corruption results. Repeated power cycling during this window makes the drive permanently undetectable.
- Drive takes 30+ seconds to enumerate after power loss
- Repeated power cycling makes drive undetectable
- Drive not seen in BIOS after multiple reboots
- MN-5236 firmware panic
When the controller suffers a firmware exception under heavy workloads, it drops its OEM identity (ADATA, HP, Mushkin) and reverts to its factory silicon descriptor MN-5236. The reported capacity shrinks to 2.1GB or 2MB. The drive causes severe BIOS hang-ups and Windows BSODs before entering this permanent ROM state.
- Drive shows as MN-5236 in BIOS
- Capacity dropped to 2.1GB or 2MB
- System hangs in BIOS with drive connected
- BSODs preceded by drive instability under load
How Is Data Recovered from a Failed Innogrit IG5236 (Rainier) 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.
- Innogrit IG5236 (Rainier) 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 Windows BSoD during file operations, Drive enters read-only mode, SMART reports pending sector count increase are useful to recognize, but on this controller they do not unlock a tooling path we can offer in-lab.
- Innogrit IG5236 (Rainier) 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.
- Innogrit IG5236 (Rainier) 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 Innogrit IG5236 (Rainier)?
Why not use chip-off recovery on Innogrit SSDs?
Does Rossmann recover data from Innogrit IG5236 (Rainier) drives?
Can you recover deleted files from a Innogrit IG5236 (Rainier) SSD?
Have a Innogrit IG5236 (Rainier) drive?
We do not currently offer in-lab recovery for Innogrit IG5236 (Rainier) 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.