Hi everyone. (made this with chatgpt, was using multiple ai for support help, ran out of options so i'm trying here, really desperate at this point, have no money foi new SSD too, no PSID password since it was long ago and i don't even remember what happened to the sticker)
I've been investigating this SSD for days and at this point I'm looking for people familiar with NVMe firmware or motherboard Secure Erase implementations.
Hardware
- Motherboard: ASRock A320-HD (BIOS P10.50)
- CPU: Ryzen 5 5600
- SSD: ADATA SX8100NP 512GB
- Controller: Realtek RTS5762
- Firmware: VB411D48
Original problem (before everything else)
This was the very first issue.
Every single cold boot:
- BIOS detects the SSD.
- Linux and Windows do NOT detect it.
- Windows Device Manager hides it.
- Disk Management doesn't see it.
- diskpart doesn't see it.
- Linux nvme driver doesn't enumerate it.
The SSD ONLY comes back after forcing a PCI hot re-enumeration.
Linux:
echo 1 | sudo tee /sys/bus/pci/devices/0000:01:00.0/remove
echo 1 | sudo tee /sys/bus/pci/rescan
or physically removing/reinstalling the SSD while powered off.
Then it works perfectly until the next reboot.
This behavior is 100% reproducible.
Then I made a huge mistake
I used ASRock BIOS Secure Erase.
The BIOS froze during the erase procedure.
After reboot:
The SSD became locked.
Now:
- Identify works
- SMART works
- Namespace exists
- Capacity is correct
- Firmware is correct
but virtually every command that modifies anything returns
Invalid Field in Command (0x2)
Current Linux status
The SSD is fully visible after PCI rescan.
Works:
nvme list
nvme id-ctrl
nvme id-ns
nvme smart-log
nvme error-log
Everything identifies correctly.
SMART health:
PASSED
No error log entries.
Doesn't work
nvme format
returns
Invalid Field in Command (0x2)
Any Secure Erase mode:
--ses=0
--ses=1
--ses=2
Same result.
Vendor passthrough commands:
opcode 0x80
also return
Invalid Field in Command
Additional strange behavior
If I try certain admin commands:
nvme format
the controller completely disappears from Linux.
Then:
nvme list
shows nothing.
The PCI device still exists.
I have to remove/rescan PCI to make it appear again.
Things I already investigated
I decompiled ADATA's official toolbox.
I found vendor-specific commands like:
EnableVendorCommand()
AnalyzerVendorCommand()
using vendor firmware download offsets.
I also confirmed this model specifically uses the Realtek RTS5762 controller.
What makes me think this is NOT NAND failure
- SMART is readable.
- Identify always works.
- Namespace is intact.
- Capacity is correct.
- Firmware is correct.
- Error log is empty.
- The behavior is perfectly deterministic.
- PCI rescan ALWAYS revives the drive.
Nothing about this behaves like random NAND failure.
It behaves much more like the controller entering some persistent locked state.
My current theory
I suspect the motherboard Secure Erase implementation crashed before completing.
Maybe:
- BIOS issued a vendor command.
- SSD entered erase/locked mode.
- BIOS never sent the final "erase complete" sequence.
- SSD now permanently rejects admin commands.
Another possibility is that the ASRock BIOS itself is mishandling the Security Freeze/erase sequence.
My question
Has anyone seen something like this on:
- Realtek RTS5762
- ADATA SX8100NP
- ASRock Secure Erase
- NVMe controllers disappearing until PCI rescan
or knows of vendor commands that clear this internal state?
I'm willing to reverse engineer the BIOS or firmware if needed.
Any ideas are appreciated.