SSD Shows Up as Not Initialized?
Do Not Initialize It
When Windows shows an SSD as Not Initialized, Unknown, or Unallocated, do not click Initialize Disk. Initializing writes a fresh partition table to the first sectors of the drive.
Our SSD data recovery service handles both the logical partition case and the controller firmware case in our Austin, TX lab.
Why Does My SSD Say Not Initialized?
Windows shows an SSD as Not Initialized when it reads the first sectors of the drive and finds no partition table it recognizes. The prompt is a symptom, not a diagnosis. The same dialog appears whether the partition metadata was lost, a USB enclosure failed, or the controller itself stopped working.
That range matters because the fixes are opposite. A drive with a healthy controller and a missing partition table needs a logical recovery that reads past the damage. If the controller's in a firmware panic, the drive needs firmware-level work. Cancel the dialog first, then figure out which failure you have.
What Initialize Disk Writes to Your SSD
- Initialize as MBR
- Windows writes a fresh Master Boot Record to Logical Block Address 0, the first sector of the drive. That record includes an empty partition table. Whatever partition layout described your old volume at LBA 0 is overwritten with a blank one.
- Initialize as GPT
- Windows writes a Protective MBR (partition type 0xEE) to LBA 0, the primary GPT header to LBA 1, and the partition entry array after that header.
Two Different Failures Sit Behind the Same Prompt
The Not Initialized dialog covers two failures with opposite fixes. When the SSD is healthy, reports its correct capacity and real model name, and has a missing or corrupt partition table, you need a logical, file-system recovery. If it reports 0 bytes or a placeholder capacity, the controller is in a firmware panic and needs firmware-level work.
Open Disk Management and Device Manager and read the capacity and model name before doing anything else.
Correct capacity, real model name
The drive shows up at its full size, but Windows labels it Not Initialized, Unallocated, or RAW.
When the drive is healthy and its GPT or MBR is missing or corrupt, the job is a logical, file-system recovery. An engineer reads past the missing partition table, rebuilds the volume structure, and extracts the files. File-system recovery runs From $250.
0 bytes, placeholder size, or SATAFIRM S11
The drive reports 0 bytes, a tiny capacity like 2MB, a wrong model string, or the identifier SATAFIRM S11. Windows still prompts you to initialize, but this is a controller firmware panic, not a partition problem.
This needs firmware-level work. On the controller families PC-3000 SSD supports, we upload a loader into the drive's RAM and rebuild the translator. See SSD shows 0GB or wrong capacity for the full walkthrough.
The SATAFIRM S11 string is worth a note because it is specific. That identity is hardcoded only into the Phison PS3111-S11 SATA controller; a failing Silicon Motion or Marvell drive instead sits in a busy hang or reports its own raw silicon descriptor, not SATAFIRM. If your drive shows that exact string, the SATAFIRM S11 firmware fix page covers the controller-specific recovery. Firmware recovery runs $600–$1,200 for SATA and $900–$1,200 for NVMe.
USB-C M.2 Enclosure Bridge Chip Failures
When the drive is an M.2 NVMe SSD living in an external USB-C enclosure, the enclosure itself is a suspect before the drive is. Inside the case sits a USB-to-NVMe bridge controller that translates USB storage commands into NVMe.
Find out whether it's the enclosure or the drive that failed before you give up on the drive.
- Remove the drive from the enclosure. Open the case and take the bare M.2 SSD out.
- Connect it to a direct PCIe path. Seat the drive in an internal motherboard M.2 slot, or use a known-good M.2 adapter you trust, so the drive talks to the host over PCIe instead of through the failed bridge.
- Re-check Disk Management. If the drive now shows its correct capacity and model, the enclosure was the fault and you can copy the data off. If it still reports Not Initialized, 0 bytes, or a placeholder size, the failure is on the drive.
A drive that reads normally on a direct connection tells you the enclosure was the problem. A drive that still fails on a direct PCIe path has a real fault, and the capacity it reports routes you back to the two-failure split above. For NVMe drives that do not appear at all, see NVMe SSD not detected in BIOS, and our NVMe recovery page covers which controller families are recoverable.
CHKDSK and Recovery Software on a Not Initialized SSD
Don't run CHKDSK or consumer recovery software on an SSD that's throwing errors. CHKDSK works at the file system layer, over standard drive commands. It can't reach a controller stuck in a firmware panic, so it does nothing useful on a panicked drive.
What to Do With a Not Initialized SSD
If the SSD holds data you need, secure the hardware before you touch the software. These steps keep the drive in the state a lab can work with.
- Cancel the Initialize Disk dialog. Do not initialize, format, or let a partition tool write a new layout. Each of those writes to the start of the drive.
- Read the capacity and model name. If the drive reports 0 bytes, a placeholder capacity, or a wrong string, that points to a firmware panic.
- Rule out the enclosure. If the drive is in a USB-C enclosure, retest it on a direct internal connection before assuming the SSD failed.
- Do not run CHKDSK or recovery software. No repair tools, no partition rebuilders, no firmware updates. Each one writes to a drive you want left untouched.
- Power down and get an evaluation. Leave the drive off and send it for a free evaluation. We tell you which failure it is and quote before any work begins.
How We Recover an Uninitialized SSD
We start by figuring out which of the two failures your drive has. A logical recovery is software work on a drive with a healthy controller. A firmware recovery is firmware-level work on the controller. Both happen in-house at our Austin lab.
- 1
Identify the Failure
We read what the drive reports about itself. If it reports 0 bytes or a placeholder, the controller is in a firmware panic.
Free evaluation - 2
Logical Path: Read Past the Missing Map
For a healthy controller, we image the drive, then reconstruct the volume structure past the missing or corrupt partition table and parse the file system to extract the files.
No diagnostic fee - 3
Firmware Path: Revive the Controller
For a firmware panic on a controller family PC-3000 SSD supports, we upload a loader into the drive's RAM and rebuild the translator so we can image the drive.
In-house at the Austin lab - 4
Image the Drive
We extract the logical sectors to a destination drive in the lab.
No data, no charge
On the controller families it supports, PC-3000 SSD is the tool that reaches a panicked controller. It talks to a live controller over the SATA or NVMe interface. It does not read desoldered NAND chips; that is a separate hardware path. For a healthy drive with a missing partition table, none of that is needed, which is why identifying the failure first keeps the logical cases in the lower price tier.
What Recovery Costs for an Uninitialized SSD
Cost follows the failure. A logical partition or file-system recovery on a healthy drive runs From $250. A controller firmware panic runs $600–$1,200 for SATA and $900–$1,200 for NVMe.
| What the drive reports | Failure | Recovery tier |
|---|---|---|
| Correct capacity and real model name on a healthy drive. Not Initialized, Unallocated, or RAW | Logical partition or file-system loss | File-system recovery, From $250 |
| 0 bytes, placeholder capacity, wrong model, or SATAFIRM S11 (SATA) | Controller firmware panic | Firmware recovery, $600–$1,200 |
| NVMe drive reporting 0 bytes or a placeholder | Controller firmware panic (NVMe) | NVMe firmware recovery, $900–$1,200 |
Rush service adds +$100 rush fee to move to the front of the queue. We give you a firm quote before work starts. It's no data, no charge, and there's no diagnostic fee. Full ranges live on our pricing page.
Dying SSD Data Recovery at Rossmann Repair
Common Questions
Should I click Initialize Disk on my SSD?
My SSD shows its correct size and model name but says Not Initialized. What does that mean?
My SSD reports 0 bytes or shows SATAFIRM S11 and asks me to initialize. Is that the same problem?
My NVMe drive in a USB-C enclosure shows Not Initialized. What should I check first?
How much does it cost to recover an uninitialized SSD?
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 maintain drive integrity. This approach allows us to serve clients nationwide with consistent technical standards.
Localized Clean Zone
Open-drive work is performed in a 0.02 micron ULPA-filtered laminar clean bench.
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
Our engineers review all lab protocols to maintain 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 showing the bench rather than just describing it. Open-drive work runs on a 0.02 micron ULPA-filtered laminar clean bench, and we filmed it.
See the particle counter test at the benchSince 2008
Established
As Featured In
Related services
Related Guides
Full SSD recovery service overview
The controller firmware panic sibling case
Phison PS3111-S11 controller firmware panic
When the drive does not appear at all
The hardware we use for firmware-level recovery
Transparent cost breakdown
Do not initialize. Get a diagnosis first.
We separate a logical partition problem from a controller firmware panic and recover each the right way. Free evaluation, firm quote, no data no charge.