-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An unexpected surprise #217
Comments
You've got a better deal than the vast majority of the people who buy fake cards. |
For sure. The cards were actually part of this kit: https://www.aliexpress.com/item/1005003575285528.html One of the two cards was sent to me as a replacement for an actual 16 GB one that died almost immediately. |
Okay, but... why, and how? Is there a catch? |
@ElonSatoshi, the cards have more capacity (~30GB) than the painted information suggests (16GB). This is likely due to a mistake made by the person who made fake cards. The catch is that these cards are probably not reliable. |
Can that happen if they aren't even fake? I once bought a pack of, if I recall correctly, 3 16GB PNY USB drives from Walmart. When I plugged one in, I found out it was 32GB. And yeah, one of them got bricked. But I'm not sure how much of it was it being unreliable, and how much of it was me plugging 2 USB drives into one hub and unplugging/plugging one while the other was being written to. I'm going to be very careful/avoid USB hubs in the future when I don't want to risk bricking one. |
Yes, but it is very unlikely since manufacturers are way more organized than scammers. |
I bought a lot of 100 MicroSD cards of 1GB, the sticker says 1GB, but the capacity is real 4GB on all of them. Testing data retention on them with write-once-read-many pattern right now. |
Not an issue, just wanted to share an unexpected result.
SD card 1
SD card 2
Turns out both SD cards have a real capacity of almost 30 GB, despite the (fake) SanDisk sticker claiming 16 GB.
Differences between the two cards:
The text was updated successfully, but these errors were encountered: