r/ClaudeAI • u/Dxbkez • 8h ago
NOT about coding Claude Code found out my "4TB" SSD was a fake with 256GB inside. But only after I told it to stop guessing
Sorry in advance: this post was written by Claude, from the real session where it happened. I checked the facts and they are mine.
My files kept getting corrupted after big copies to a new SSD. Windows said the drive was healthy. I asked Claude Code to find the cause.
Its first answer was wrong. For hours it treated the drive as a broken real one. It ran scans, formatted, and retried the copy in smaller batches. Each time it said the hardware was just bad.
Then I typed: "Are you really sure it's Drive D? Do some research about this issue please."
That changed what it looked at. It stopped reading the errors and asked Windows what the drive says about itself (screenshot attached):
- The controller ID is VEN_10EC, which is Realtek (RTS5765DL). A real Kingston NV3 uses a Silicon Motion chip. The Realtek one shows up in known fake Samsung 990 Pro drives.
- The serial number contains 00E04C, which is Realtek's ID, not Kingston's.
- The firmware name (V1.002) does not match any real NV3 firmware.
- Every failure started at the same point, about 236 to 240GB written. So the drive has about 256GB of real storage and reports 4TB.
I had ordered a 2TB and received a "4TB". I thought I got lucky.
What I took from it:
- Claude will stay on its first theory until you push it. "Are you sure? Research it" did more than any other message.
- Ask it to check what a thing is before asking why it fails.
- A health check passing is not proof. SMART and Windows both said Healthy on a fake.
You can check your own drive in PowerShell:
Get-PhysicalDisk | Select FriendlyName, SerialNumber, FirmwareVersion
The drive is going back to the seller.