Intel 600p 1GB Fix (SM2260 Bug) | Rossmann Group

No Data, No Fee

Guarantee

2.49M+

Subscribers

4.9

1,837+ Google Reviews

Since 2008

Established

Repairs on Video

Full Transparency

As Featured In

BBC News CBC News ABC Australia Wall Street Journal Business Insider Vice Fast Company 404 Media

Written by

Louis Rossmann

Founder & Chief Technician

Updated 2026-03-20

What You Are Seeing

The failure follows a consistent pattern across all Intel 600p variants (128 GB SSDPEKNW128G8, 256 GB SSDPEKNW256G8, 512 GB SSDPEKNW512G8, 1 TB SSDPEKNW010T8) and the OEM Pro 6000p. The system locks up or throws an INACCESSIBLE_BOOT_DEVICE blue screen. After reboot, BIOS detects the drive but shows 1,024 MB or 1,073 MB capacity instead of the actual size. Windows Disk Management labels it RAW or Uninitialized. In some cases, Windows misinterprets the geometry and displays a 2 TB "GPT Protective Partition."

Common symptoms

●BIOS shows "INTEL SSDPEKNW" with 1 GB or 1.07 GB capacity
●Disk Management shows unallocated RAW device at 1,024 MB
●BSOD INACCESSIBLE_BOOT_DEVICE followed by capacity loss
●Drive not detected at all on some motherboards

What not to do

✗Do not initialize, format, or partition the drive in Disk Management
✗Do not run Intel SSD Toolbox, Solidigm Storage Tool, or any firmware updater
✗Do not run chkdsk, Disk Drill, EaseUS, or any recovery software
✗Do not repeatedly power-cycle; each boot stresses the SM2260 controller logic

SM2260 Controller Architecture

The Intel 600p uses a Silicon Motion SM2260 controller, a dual-core ARM processor with an 8-channel NAND interface. Intel paired it with three 384-Gbit 32-layer 3D TLC NAND packages on a single-sided M.2 2280 PCB. Because the M.2 form factor limits physical space, the 8-channel controller operates in an asymmetric 6-channel configuration. This exotic geometry complicates translator rebuilds because the physical page layout does not follow standard SM2260 reference designs.

The SM2260 uses LDPC (Low-Density Parity-Check) error correction and dynamically allocates a portion of the TLC NAND as pseudo-SLC write cache to maintain burst write performance. Firmware, flash translation layer tables, bad block maps, and wear-leveling metadata are stored in a reserved service area on the same NAND that holds user data. When any of these modules become unreadable, the controller cannot boot.

Why the drive reports exactly 1 GB

When the SM2260 detects catastrophic translator damage or loses 3.3V power to the NAND array, it triggers a hardware fail-safe called ROM mode. The controller halts NAND access to prevent further degradation and presents only its base bootloader footprint to the NVMe host interface. That footprint enumerates as 1,024 MB (1 GB) or 1,073 MB (1.07 GB). The controller is functional; the failure is in the firmware stored on NAND, not in the silicon itself.

Why Software Recovery Is Impossible

Forum threads recommend running consumer recovery software or partition rebuild tools on an Intel 600p stuck at 1 GB. This cannot work. The SM2260 in ROM mode has physically disconnected the NAND arrays from the NVMe command interface. The operating system sees a 1 GB block device with no file system, no partition table, and no user data. Software tools scan an empty 1 GB void.

Clear rule: if the Intel 600p shows 1 GB in BIOS, no software on any operating system can access the NAND. Recovery requires hardware-level access to the SM2260 controller through engineering test points. Power the system down, remove the M.2 drive, and contact a lab with a PC-3000.

Chip-off recovery (desoldering the NAND packages and reading them in a chip programmer) also fails on the 600p. The SM2260 enforces hardware-level AES-256 encryption. The encryption key is bound to the original controller die. Extracting raw NAND yields only ciphertext with no way to derive the key. The data must be decrypted by the original SM2260 through PC-3000 safe mode.

PC-3000 Recovery Procedure for the SM2260

Recovery uses the PC-3000 Portable III with its dedicated Silicon Motion NVMe module. The procedure has four stages. The drive is never connected through a standard M.2 slot until the firmware is stabilized.

Power Rail Verification

Before touching firmware, we verify the 3.3V power rail to the NAND array. The Intel 600p uses a load switch between the M.2 connector's 3.3V supply and the NAND packages, controlled by the SM2260's enable pin. If the load switch has failed or its soft-start capacitor is shorted, the NAND receives no power. The SM2260 controller still enumerates over NVMe but cannot see any flash. In these cases, micro-soldering the load switch or bypassing the failed component restores NAND power before firmware work begins.

Safe Mode Test Point Bridging

The SM2260 has specific engineering test points on the PCB that force the controller into safe mode when shorted during power-on. Safe mode bypasses the corrupted firmware on NAND entirely; the controller boots from internal ROM and accepts commands from PC-3000 without attempting to load its flash-based firmware. The test point locations differ by PCB revision (Intel used at least two board layouts across the 600p production run). Shorting the wrong pads on the wrong revision will not work and risks damage to the controller.

On the bench: After bridging, PC-3000 detects the SM2260 in safe mode and uploads a custom loader (LDR) directly into the controller's volatile SRAM. This gives the SM2260 a temporary operating system that can address the NAND without relying on the corrupted firmware modules stored in the service area.

Virtual Translator Reconstruction

The flash translation layer (FTL) maps logical block addresses to physical NAND pages. On the 600p, the asymmetric 6-channel layout means the physical page distribution does not follow standard 8-channel patterns. PC-3000's Silicon Motion module reads the raw NAND, extracts surviving metadata from page headers and block sequence numbers, and reconstructs a virtual translator in system RAM. This process does not write to the NAND.

Decrypted Imaging

With the virtual translator built, PC-3000 commands the SM2260 to decrypt and serve user data through its AES-256 engine. We image the entire drive sector-by-sector to a known-good destination, then verify files against the original directory structure. The original SSD is never written to. Data is returned on your choice of media.

When the 1 GB Bug Has a Physical Cause

Not every 600p that reports 1 GB has firmware corruption. The SM2260 also enters ROM mode if it loses communication with the NAND array due to a physical power delivery failure. The Intel 600p routes 3.3V through a load switch before reaching the NAND packages. If the load switch output shorts to ground, or its soft-start capacitor fails, the NAND array powers down while the SM2260 continues to enumerate over PCIe. The controller detects no flash and reports its bare ROM footprint: 1 GB.

Distinguishing firmware-only failure from a load switch failure requires probing the power rails with an oscilloscope or multimeter before entering safe mode. If the 3.3V rail to the NAND is missing or unstable, board-level repair comes first. After restoring power, the firmware may or may not be intact; some drives recover immediately once NAND power is restored, while others need the full translator rebuild.

Load switch repair adds the cost of micro-soldering and a donor component, moving the total from the firmware tier ($900 to $1,200) to the advanced rebuild tier ($1,200 to $1,500).

Intel 600p vs. 660p: Different Controllers, Different Procedures

The naming similarity between the Intel 600p and Intel 660p causes confusion. They share no controller or NAND architecture.

Specification	Intel 600p	Intel 660p
Controller	Silicon Motion SM2260	Silicon Motion SM2263
NAND type	32-layer 3D TLC	64-layer 3D QLC
Channels	8-channel (6-channel active)	4-channel
Interface	PCIe 3.0 x4 NVMe	PCIe 3.0 x4 NVMe
Encryption	AES-256 (controller-bound)	AES-256 (controller-bound)
PC-3000 module	SM2260 NVMe	SM2263 NVMe (distinct loaders)
Failure signature	1 GB / 1.07 GB unallocated	0 GB / not detected

The firmware loaders, translator algorithms, and test point locations are entirely different between these two controllers. Applying SM2263 procedures to an SM2260 (or vice versa) will fail. Both are recoverable through our NVMe recovery service, but the engineering approach is distinct.

Affected Intel 600p Models

Intel 600p Series

SSDPEKNW128G8 (128 GB), SSDPEKNW256G8 (256 GB), SSDPEKNW512G8 (512 GB), SSDPEKNW010T8 (1 TB). M.2 2280, single-sided PCB. All use SM2260 controller with 32-layer TLC NAND.

Intel Pro 6000p (OEM)

The Pro 6000p is the OEM variant shipped in Dell, HP, and Lenovo laptops. Same SM2260 controller and NAND. Same 1 GB firmware failure. Same recovery procedure.

If your Intel NVMe drive shows a different failure pattern (0 GB, not detected, wrong model name), it may use a different controller. The Intel 660p uses SM2263; the Intel 670p uses SM2265. See all Intel SSD models we recover or call (512) 212-9111 with your model number.

NVMe SSD Recovery Pricing

Intel 600p SM2260 recovery: $900 to $1,200 (firmware only) or $1,200 to $1,500 (if load switch micro-soldering is required). Free evaluation, firm quote, no data recovered = no charge.

Service Tier	Price	Description
Simple CopyLow complexity	$200	Your NVMe drive works, you just need the data moved off it Functional drive; data transfer to new media Rush available: +$100
File System RecoveryLow complexity	From $250	Your NVMe 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
Circuit Board RepairMedium complexity – PC-3000 required	$600–$900	Your NVMe 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)
Firmware RecoveryMedium complexity – PC-3000 required	$900–$1,200	Your NVMe 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
PCB / NAND SwapHigh complexity – precision microsoldering and BGA rework50% deposit	$1,200–$1,500	Your NVMe 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

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.

All tiers: Free evaluation and firm quote before any paid work. No data, no fee on all tiers (NAND swap requires a 50% deposit because donor parts are consumed in the attempt).

Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost. All prices are plus applicable tax.

Compare our published pricing to industry-wide data recovery costs. Large labs typically quote $1,500 to $3,000+ for NVMe firmware work and do not publish prices upfront.

Frequently Asked Questions

Why does my Intel 600p show 1GB or 1.07GB unallocated?

The SM2260 controller detected critical firmware corruption or translator damage and entered ROM mode, a hardware fail-safe. In ROM mode, the controller disconnects from the NAND flash array and exposes only its base bootloader footprint to your system BIOS. That footprint enumerates as 1,024 MB or 1,073 MB. Your data is physically intact on the TLC NAND; the controller lost the firmware it needs to read it.

Can data recovery software fix the Intel 600p 1GB bug?

No. When the SM2260 drops into ROM mode, the operating system has zero access to the NAND arrays. Software tools like R-Studio, Disk Drill, or EaseUS scan only the 1GB void the controller presents. There is no volume to scan, no file system to parse, and no sectors to read. Recovery requires PC-3000 vendor-level commands issued directly to the controller through hardware test points.

Is chip-off recovery possible on the Intel 600p?

No. The SM2260 enforces hardware-level AES-256 encryption. The encryption key is bound to the specific controller die. Desoldering the 32-layer TLC NAND packages and reading them in a chip programmer yields only ciphertext. The original controller must be revived through PC-3000 safe mode bridging to decrypt the data on-the-fly during extraction.

How much does Intel 600p data recovery cost?

The SM2260 firmware bug requires PC-3000 intervention with translator reconstruction, which falls in our firmware recovery tier at $900 to $1,200. If the 3.3V load switch also needs micro-soldering repair, the price moves to $1,200 to $1,500 (advanced rebuild). Free evaluation, firm quote before paid work, no data recovered means no charge.

What SSD Recovery Customers Say

4.9 across 1,837+ verified Google reviews

May 10, 2020

“I consulted Rossmann Repair Group for data recovery services. A new IT client was recently referred to me, because his main computer crashed and his business database went offline as a result. It turned out that the computer crashed because its main storage, a 500 GB Solid State Hybrid Drive, failed. That part was easy - replace it with a new 1 TB SSD and reinstall Windows along with the software he uses. However, the data on the SSHD was critical and would have meant serious problems for his business if he didn't get that back. That's where Rossmann Repair Group came in.”

Shomari Hohn

View on Google

July 24, 2024

“Went in to ask if they could retrieve my SSD from my Surface Pro 4 for me and they gave me a good rate, but was still a bit too expensive for me. So, they let me use their equipment for about an hour until I was able to fish it out myself and recover my data.”

Aravind Udayakumar

View on Google

November 17, 2021

“Sent in a SSD for data recovery for a client of mine. Data was recovered! What else can I say. Thank you.”

David Dachenhaus (DDock)

View on Google

February 2, 2026

“Amazing place! Super friendly and knowledgeable people! I have a LaCie Rugged Pro SSD that stopped mounting. It turns out the enclosure was the problem, not the SSD itself. They helped diagnose the issue and offered solutions—all free of charge. Great experience, and I highly recommend them! 😊”

Ludwig JonssonLaCie

View on Google

Read all 1,837+ reviews