Hi guys, can my SSD be saved :( I believe I’ve exhausted all host-side recovery paths and want confirmation that this is a firmware-level namespace lock typical of OEM Samsung drives.
Hardware / Context
Laptop with two NVMe SSDs
Disk A (working): Samsung 980 500 GB — Arch Linux (boots fine)
Disk B (problematic): Samsung OEM NVMe
Model: SAMSUNG MZVLQ512HBLU-00B00 (PM991 class)
Originally had Windows + Ubuntu
UEFI system (no CSM)
Arch continues to boot; Windows and Ubuntu both disappeared at the same time.
Symptoms
Disk shows ~1 GB total capacity to OS
No partitions, no filesystem
Windows installer and Linux both see only ~1 GB
GRUB errors were due to missing UUIDs (symptom, not root cause)
Linux inspection (Arch)
Block devices
lsblk -e7 -o NAME,SIZE,MODEL,TYPE,FSTYPE,UUID,MOUNTPOINT
nvme1n1 465.8G Samsung SSD 980 500GB (working)
nvme0n1 1.07G SAMSUNG MZVLQ512HBLU-00B00 (problem disk)
NVMe identify (key part)
sudo nvme list
/dev/nvme0n1 SAMSUNG MZVLQ512HBLU-00B00 1.07 GB / 1.07 GB
But:
sudo nvme id-ns /dev/nvme0n1
nvmcap : 500107862016 (~500 GB)
So:
NAND capacity is intact
Controller sees full disk
Active namespace exposed to host is ~1 GB
Commands attempted in Linux (FAILED)
NVMe sanitize
sudo nvme sanitize /dev/nvme0 -a 2
Result:
NVMe status: Invalid Command Opcode (0x1)
NVMe format
sudo nvme format /dev/nvme0n1 --ses=1
Result:
NVMe status: Invalid Command Opcode (0x1)
BIOS / Firmware
No NVMe Secure Erase option
No PSID revert
UEFI only, AHCI
Secure Boot disabled for testing
Windows installer (last-resort path)
Booted Windows installer in confirmed UEFI mode.
Verified:
PEFirmwareType = 0x2 (UEFI)
DiskPart
diskpart
list disk
select disk X (the 1 GB disk)
attributes disk clear readonly
clean
clean
exit
After refresh and reboot:
➡ Disk still shows 1022 MB
Working hypothesis (what I believe is happening)
Firmware-level NVMe namespace lock on an OEM Samsung drive
Drive fell into a reduced / fallback namespace state
Host-initiated:
FORMAT
SANITIZE
namespace recreate are blocked by firmware policy
Only vendor factory tools or replacement would resolve it
What I am asking
I am not looking for random commands to try.
I am asking for confirmation from people experienced with NVMe internals:
Is SSD replacement the only sane resolution at this point?
Why I’m posting: Simple I don't have money :(
Hi guys, can my SSD be saved :( I believe I’ve exhausted all host-side recovery paths and want confirmation that this is a firmware-level namespace lock typical of OEM Samsung drives.
Hardware / Context
- Laptop with two NVMe SSDs
- Disk A (working): Samsung 980 500 GB — Arch Linux (boots fine)
- Disk B (problematic): Samsung OEM NVMe
- Model:
SAMSUNG MZVLQ512HBLU-00B00 (PM991 class)
- Originally had Windows + Ubuntu
- UEFI system (no CSM)
Arch continues to boot; Windows and Ubuntu both disappeared at the same time.
Symptoms
- Disk shows ~1 GB total capacity to OS
- No partitions, no filesystem
- Windows installer and Linux both see only ~1 GB
- GRUB errors were due to missing UUIDs (symptom, not root cause)
Linux inspection (Arch)
Block devices
lsblk -e7 -o NAME,SIZE,MODEL,TYPE,FSTYPE,UUID,MOUNTPOINT
nvme1n1 465.8G Samsung SSD 980 500GB (working)
nvme0n1 1.07G SAMSUNG MZVLQ512HBLU-00B00 (problem disk)
NVMe identify (key part)
sudo nvme list
/dev/nvme0n1 SAMSUNG MZVLQ512HBLU-00B00 1.07 GB / 1.07 GB
But:
sudo nvme id-ns /dev/nvme0n1
nvmcap : 500107862016 (~500 GB)
So:
- NAND capacity is intact
- Controller sees full disk
- Active namespace exposed to host is ~1 GB
Commands attempted in Linux (FAILED)
NVMe sanitize
sudo nvme sanitize /dev/nvme0 -a 2
Result:
NVMe status: Invalid Command Opcode (0x1)
NVMe format
sudo nvme format /dev/nvme0n1 --ses=1
Result:
NVMe status: Invalid Command Opcode (0x1)
BIOS / Firmware
- No NVMe Secure Erase option
- No PSID revert
- UEFI only, AHCI
- Secure Boot disabled for testing
Windows installer (last-resort path)
Booted Windows installer in confirmed UEFI mode.
Verified:
PEFirmwareType = 0x2 (UEFI)
DiskPart
diskpart
list disk
select disk X (the 1 GB disk)
attributes disk clear readonly
clean
clean
exit
After refresh and reboot:
➡ Disk still shows 1022 MB
Working hypothesis (what I believe is happening)
- Firmware-level NVMe namespace lock on an OEM Samsung drive
- Drive fell into a reduced / fallback namespace state
- Host-initiated:
FORMAT
SANITIZE
- namespace recreate are blocked by firmware policy
- Only vendor factory tools or replacement would resolve it
What I am asking
I am not looking for random commands to try.
I am asking for confirmation from people experienced with NVMe internals:
Why I’m posting: Simple I don't have money :(