|
Hi all,
Looking for advice on a Phison E12 NVMe in what looks like the classic failsafe / read-only state.
Drive: Greenliant ArmourDrive 960 GB, M.2 2280 NVMe (industrial line), Phison PS5012-E12 (PCI 1987:5012), firmware GECE1BB3 (Greenliant build, not the retail ECFM line).
History: ext4 data drive in an NVIDIA Jetson Orin Nano on a drone, recording camera video at about 120 MB/s. The drone crashed and power was cut mid-write. On the next boot the drive came up in this state.
State now, identical on every power-up, both in the Jetson's M.2 slot and through a JMicron JMS581 USB bridge (smartctl -d sntjmicron): - Identify OK: correct model, serial and firmware. NVMe 1.3, OACS 0x0017 (no namespace management). - TNVMCAP 960 GB, UNVMCAP 960 GB: no namespace. - SMART: Critical Warning 0x09 (spare below threshold, media read-only), Available Spare 0 % (threshold 5 %), temperature stuck at 30 C, Power Cycles 1, Power On Hours 0, all data counters 0. - Every read to NSID 1 fails with status 0x4016, Invalid Namespace or Format.
Not done: no MPTool, no firmware update, no format / sanitize / namespace creation, no vendor commands. Only identify, SMART / error logs and read attempts. The drive is stored unpowered now.
Questions: 1. Is this the standard E12 translator-loss case for PC-3000 SSD, and is a Greenliant firmware build likely to make it harder? 2. Would anyone with PC-3000 SSD take it as a one-off job for a modest fee? My budget is limited, and I only need one recording session (tens of GB), not the whole drive. I'm in California.
Photos of both sides attached. PCB 96-201-0005A, labels dated 2019-09-24, DRAM SK hynix H5AN4G6NBJR. The NAND package markings aren't legible in my photos; I can take closer ones if needed.
Thanks
| Attachments: |

2.jpg [ 302.28 KiB | Viewed 180 times ]
|

1.jpg [ 292.58 KiB | Viewed 180 times ]
|
|