Open Yabgu opened 4 months ago
Hi @Yabgu,
You can use f3write
/ f3read
to check this drive. Since the drive must hold all the data to pass, it cannot escape this test. You can use the parameters --start-at=NUM
and --end-at=NUM
to instruct f3write
to gradually add files.
f3probe has to be used with f3write / f3read.
I have tried this tool which I compiled from the master branch, on a scam nvme disk and it runs as below:
I know this drive does not have 4TB for sure. How do I know it? Because I tried to use it. Here is how it goes: When I start using this as a disk with Steam, it starts to download files and the first few gigabytes it had normal stat SSD speed like 500 MB/sec and then it switches to 2MB/sec write speed. If you patiently wait for more data to be written, which took me a day, it eventually gets to the point of wiping all your data. I guess they are getting better at scamming and it is now even worse because this disk is useless. Even if you reduce the capacity, eventually it will wipe itself like a time bomb.
If you have any suggestions on detecting this type of disk? I can help testing new detection mechanisms on this disk,
The disk in question looks like this: scam ssd