Intel 600p SSDPEKKF256G7H NVMe PCIe: wrong capacity 1073MB

[SOSdonnees]

Hi there,

Receive an Intel 256GB NVMe PCIe M.2 2280 SSD, model SSDPEKKF256G7H.
HP P/N: 910595-01
Firmware: HP01

The SSD is detected by `sudo nvme list`as:

Code:

Node              SN                    Model                   Namespace    Usage               Format            FW Rev
----------------  --------------------  ----------------------  ---------  --------------------  ----------------  ----------
/dev/nvme0n1      1234   010008A000001  SM2260                  1           1.07 GB / 1.07 GB    512   B +  0 B    1095


The controller is:

Code:

SMI
N07T96.00
S LLUT
TW 1639 40


My understanding is that this is the Hewlett Packard OEM version of the Intel 600p series, even if there is no mention of 600p on the sticker.
Datasheet: https://www.thailand.intel.com/content/dam/www/public/us/en/documents/product-briefs/ssd-600p-brief.pdf

As we can see, the `nvme list`command correctly returns the controller name SM2260 as "Model", a wrong capacity (1.07 GB) instead of 256GB, and a wrong serial number (unless it is possibly thus of the controller ?).

This SSD seems using an Intel modified version of the Silicon Motion SM2260 (SMI instead of SM on chip), with 256-bit AES encryption (according to the datasheet for the 600p series).

As the 1073 MB (1.07GB) can be cloned at full speed of 287 MB/s, I assume the MCU is ok and a problem with the NAND, probably the translator tables.
This situation seems quite similar to the one of this old topic: https://forum.hddguru.com/viewtopic.php?f=10&t=38762

The SSD is like the one in this topic, but visusally in good condition and without missing component:
https://forum.hddguru.com/viewtopic.php?f=10&t=40472

The list of supported PC-3000 SSD Systems by Acelab includes SSD from several brands using SM2260, but not for Intel.

I didn't try a reflow, nor checking voltages so far, as a firmware issue sounds to me more likely.
Components are tiny. Measurement of voltages would be possible but difficult.

For firmware issues, my understanding is that this SSD model is still not supported nowadays. Can someone confirm?

Maybe is data recovery though NAND off still possible, but I'm not sure because of the 256-bit AES encryption.

[Lardman]

AFAIK - Intel are about as recovery friendly as samsung. The controller is obviously fine as it appears to have dropped into safe mode. I'd check the nand power rails if everything looks good you're dead in the water if it's a firmware issue

[img]

Hi!

I have an exact same SSD with the same size (1024GB - 2097151 LBAs) and behavior (actually 2 of them: a failing one and one for reference or as a donor) but it probably fallen from the desk (in a laptop).

Is the AES-256 encryption key stored in the NAND in readable format if no ATA password set?

What if I move (reball) the ripped off NANDs to the donor board with a good contoller (if I don't want to spend a lot of time with repairing the ripped pads)? Can the other controller read the NANDs without PC3000 modification?

[suricate.ch]

That's not gonna work.

[img]

That's not gonna work.

Thank you for your answer!