Netac NV5000 TenaFe TC2200 errors

[vanyassia]

1) DEVICE:
Netac NV5000, 500GB, M.2 NVMe. Controller presumably TenaFe TC2200 (not visually
confirmed — board under heatsink with "warranty void if removed" seal).

Hardware ID seen before failure (old Windows log):
PCI\VEN_1F40&DEV_0001&SUBSYS_02801D89&REV_00
PCI\VEN_1F40&DEV_0001&CC_010802

2) BRIDGE USED FOR DIAGNOSTICS: JMicron JMS583
VID: 152D / PID: 0583, fw jm583_00_02_01_04
Shows as "JMicron Generic SCSI Disk Device" / "JMicron Generic 0214"

3) FAILURE CAUSE:
Drive stopped being detected after RAM overclocking instability errors on the
motherboard (not the SSD itself overclocked — system RAM OC caused instability,
drive failed to be detected afterward).

4) TEST RESULTS:
Windows: Disk Management asks to initialize, "No Media" / can't read size.
R-Studio: "JMicron Generic 0214", size field empty.
DMDE: "Disk unavailable".
Linux dmesg: Sense Key Hardware Error, ASC=0x44 ASCQ=0x81, Read Capacity failed,
0 logical blocks.
smartctl: "Test Unit Ready [medium or hardware error (serious)]"
Identical error across Windows/Linux/macOS.

5) J2 SHORTING TEST:
Shorted contacts labeled J2 on the board (no documentation, guesswork — J2 is one
of several unlabeled pads near the controller). After shorting, Tenafe NVME flash
id v0.11a utility returns:

Model: Merak Nvme Ssd Controller
Fw: c1bc3e90
Size: 1 MB [0.0 GB]
LBA Size: 512

Without shorting J2, the same utility returns "Identify error!" with no response
at all. So J2 shorting does change something, but Read Capacity/actual sector
reads still fail — drive still shows 0 usable blocks/bytes in every OS.

Is "Merak Nvme Ssd Controller" / 1MB actually a genuine ROM/boot mode, or just the
controller's standard firmware-panic fallback identity (as seen in a similar
Kingston case on Tom's Hardware forums)? If it IS a real ROM mode entry — what's
the next step to dump NAND/FTL from here?

Data matters, zero budget for professional recovery (student). Board photos
(without breaking warranty seal) available on request.

[Lukas]

5) J2 SHORTING TEST:
Shorted contacts labeled J2 on the board (no documentation, guesswork — J2 is one
of several unlabeled pads near the controller). After shorting, Tenafe NVME flash
id v0.11a utility returns:

Model: Merak Nvme Ssd Controller
Fw: c1bc3e90
Size: 1 MB [0.0 GB]
LBA Size: 512

Is "Merak Nvme Ssd Controller" / 1MB actually a genuine ROM/boot mode, or just the
controller's standard firmware-panic fallback identity (as seen in a similar
Kingston case on Tom's Hardware forums)? If it IS a real ROM mode entry — what's
the next step to dump NAND/FTL from here?

Yes, shorting the pins returns the correct controller identification data.
The TC controller is not supported by commercial tools, so in-house solutions are the only option.

Data matters, zero budget for professional recovery (student).

In that case, you must accept data loss.

[Hardcore Games]

The SSD has a 5 year warranty so try that. Make a backup of important data, never assume any disk or SSD is perfect.