Why do I get the feeling that - when I run counterfeit tests on these - that they will not come back as true 400gb drives?
Surely they wouldn’t do that to us, just sell us fake SD cards. Woot only sells the finest of goods that Thunderthighs personally vets.
Nope, I don’t vet. These came from Amazon. We’ll cross our fingers.
I got one and I have the same feeling. I don’t see how, but hopefully, they’ll be true to what’s advertised.
to be fair, it doesn’t claim a 400 GB capacity. 400GB is just the color lol
Boy… that’s what I always want to hear from my retailers! 
Yeah… but does it taste purple?
Gee… color me surprised:
derek@laptop:~$ sudo f3probe --destructive --time-ops /dev/sdb
F3 probe 7.0
Copyright (C) 2010 Digirati Internet LTDA.
This is free software; see the source for copying conditions.WARNING: Probing normally takes from a few seconds to 15 minutes, but
it can take longer. Please be patient.Bad news: The device `/dev/sdb’ is a counterfeit of type limbo
You can “fix” this device using the following command:
f3fix --last-sec=65013513 /dev/sdbDevice geometry:
Usable size: 31.00 GB (65013514 blocks)
Announced size: 400.10 GB (839065600 blocks)
Module: 512.00 GB (2^39 Bytes)
Approximate cache size: 31.00 MB (63488 blocks), need-reset=no
Physical block size: 512.00 Byte (2^9 Bytes)Probe time: 6’11"
Operation: total time / count = avg time
Read: 13.03s / 131380 = 99us
Write: 5’57" / 576029 = 620us
Reset: 384.7ms / 2 = 192.3ms
My surprise is that it’s at least a 32 GB card instead of an even smaller one.
Hmmmm. Feel free to reach out to Woot! Customer Service.
From a browser, use the Woot! Customer Service form.
In the Woot! App, choose Account from the bottom navigation and then Support.
Note: Woot! Customer Service replies go to the email address on your Woot! account, not your Amazon login email if used/different.
I did. Thanks. I just wanted everyone else to know exactly what they were getting.
Think of how many things I could queue up to print with 400GB of storage space…
How long did this take? I’m doing a test now, it’s taking hours.
Also, I couldn’t format it to NTFS for some reason. Any ideas?
If you do the full write/read test, yeah… it takes forever. If you run the command I used [sudo f3probe --destructive --time-ops /dev/sdb (or wherever your drive is)] this runs a truncated test that only takes about 15 minutes on a drive this size.
Once you run that test, it will present you with a command to “fix” the drive. When you run that command, what it does is creates a partition on the drive of the actual, usable size. You should be able to then format that partition any way you want, either through the command line or gparted.
I will try f3probe as well. I just checked the tool I’m using.
It’s done writing, and now it’s doing the verification. Whole process is not over yet, but it does show that this, in fact, is only 30GB usable.
Screenshot:
Logs:
Warning: Only 409634 of 409636 MByte tested.
The media is likely to be defective.
29.2 GByte OK (61261111 sectors)
15.1 GByte DATA LOST (31869641 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
15.1 GByte corrupted (31869641 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x000000074d8a6e00
Expected: 0x000000074d8a6e00
Found: 0xca7bb2a600853756
H2testw version 1.3
Oh… you’re running H2testw. under windows I presume? I don’t know if/think that f3 runs on anything but linux and I am not familiar with H2testw. I do know that the full f3 test wanted to take hours, though, so that sounds about right.