Got a new SSD, heard about fakes, a tool to verify size?

Hardware Hub Storage
1

Hi All,

I’ve just bought a Samsung 980 Pro from Amazon and heard that Amazon has a problem with fake products even from reputable sellers since Amazon pools inventory.

I’m familiar with crystal disk mark for verification of speeds but is there a tool to verify that the drive’s reported disk size is correct?

(I’m on windows)

2

Fill it up, if the the data you copied first disappears then it’s fake

3

Samsung has tools for their SSDs probably would validate it that way.

2 Likes
4

The tool is named Samsung Magician, I use it for my Samsung SSD’s, both SATA and NVMe devices.

1 Like
5

Is there an app for this for linux (or at least platform agnostic) and maybe for non-samsung products as well? I really dont want to do this manually…

6

like a single pass of badblocks?

or like dd if=/dev/radom of=/dev/sdx and wait for it to run out of space?

(but neither varify previous writes weren’t just overwritten?)

7

Well, badblocks would likely work:

mkfs.ext4 -vcc /dev/sdb

Or to be sure… mount the file system, write random files until full, and be sure all but the last (partial) file matches. e.g.:

pv -fcN gen -Ss 50G /dev/urandom | mbuffer -m 1M -o rand.$(date +%s) -H -q -Q -l /dev/stdout | grep -v ^summary: | sed -e "s/^md5 hash: //" -e "s/$/  rand.$NUM/" | tee -a md5sums &>/dev/null &

Then check with: md5sum -c md5sums

1 Like
8

quick and dirty…
a text file.
fill it with zero’s making it few 10mb in size.
(easily done with cut and paste)
save then copy paste that file into the same folder… it will incriment the name if you keep both files.
just repeat the past till you have a around 100.
zip that folder and create 10 copies
zip them all together. rinse and repeat if you want really big files 1-4gigs. (dont go over 4 gigs for speed sake).
copy that file over to your drive incrementing the name each time.

eventually you will run out of space and will be told you dont have enough room on the destination.
see how many big files you copied over … more than likely it will be the correct amount.

9

See a lot of advice here that assumes the drive reports the proper file size and file sectors.

No, this is not necessarily the case. If it is a fake the drive will either:

  1. Overwrite it by cutting off the last n bits in the address (e.g. bitmasking)
  2. Send everything above a certain threshold to /dev/null, or
  3. only have a small buffer that repeats the last x bytes.

One easy way to test this is to create two to four partitions, equally large. Write 1 GB of Random data to each partition, md5 the sum and keep writing to one partition at a time until full. In theory this should immediately catch 1 and 2. For 3, you need to write about 64 GB of data before you can validate the results.

10

Made for memory cards but work for discs too. f3 - Fight Flash Fraud — f3 8.0 documentation

2 Likes
11

This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.