FakeFlashTest does not run on Linux, and no compatibility trick turns a Windows-only freeware tool into a Linux one. Linux users do not need it to. The standard tool is F3, Fight Flash Fraud, open source, built for exactly this fraud, and available for Linux as well as macOS and Windows. Its main workflow is disarmingly simple: one command fills your drive with test files, a second command verifies them. Remember that shape: on Linux, the full test is two commands, f3write followed by f3read, plus a quicker probe for when you need a first signal.
The fraud those commands expose is a firmware lie. A fake drive’s hacked controller reports a small amount of real flash as a huge capacity. Linux, like every other system, believes the reported size until a test proves otherwise. Writes beyond the real capacity wrap around and overwrite older data, so a drive can list your files correctly while their contents are already destroyed, and overwritten data is usually unrecoverable. Filling the drive with known data and reading it all back is the definitive counter: either every test file verifies, or the drive was lying.
Installing F3 and identifying your drive safely
F3 is available in most distro repositories, and also via Homebrew on macOS if you work across both systems, so installation is normally a single package-manager step for the f3 package. Confirm f3write and f3read respond before you begin. Then comes the step that deserves your full attention: identifying the right device. List your block devices and mounts, note the test drive’s device name, size, and mount point, and compare them against what you physically plugged in. Our download page documents the Windows alternative for dual-boot machines, but on Linux the safety rule is universal: never point a fill test at a system disk, a backup disk, or any device you have not positively identified twice.
Back up the test drive first if it holds anything, because f3write fills the target volume. If several removable drives are attached, unplug the ones you are not testing so there is nothing to confuse. Use a good reader or port: a flaky connection that drops mid-test invalidates the run and wastes hours. These precautions take a minute and are the difference between a confident verdict and an expensive misunderstanding, especially on a machine that also holds your real backups.
Running the full test, and the quicker probe
Mount the drive, run f3write against its mount point, and let it write test files until the device is full. Then run f3read against the same mount point and let it verify everything. Read the summary carefully: F3 tells you how much was validated and whether data was corrupted. Corruption on verification is the fake signature: test data written later overwrote test data written earlier because the real capacity was far smaller than reported. A clean run means the capacity you tested behaved honestly. Give the job the time it needs; on large or slow media a full fill and verify is a long run, and interrupting it leaves you with no verdict at all.
F3 also offers f3probe, a quicker probe component. Treat it with the modesty its status deserves: it is described as experimental, and it is best used as a fast first signal, the Linux cousin of a quick screen, not as a substitute for the full f3write and f3read proof when a drive will hold important data or support a refund claim. That layered approach mirrors the Windows advice in FakeFlashTest vs H2testw and FakeFlashTest vs F3: screen quickly if you like, prove fully before you trust. For cards rather than sticks, the same commands apply through a reader, as in how to test a microSD card for fake capacity and how to test an SD card on a Mac.
After the verdict
If verification fails, preserve the terminal output with your order records, stop using the drive for anything that matters, and follow what to do next when a fake drive is confirmed. Do not let a reformat talk you into trusting it again; formatting changes the filesystem, not the hardware’s real capacity. If the drive passes fully, use it with normal backups and keep the result until the return window closes. For the complete cross-platform picture, see fake SD card test software for every platform, the best fake USB drive test tools, and the general method in how to test a USB flash drive for fake capacity. Linux gives you the full proof natively, in two commands, with no Windows machine required.
Testing cards, sticks, and second-hand drives
The same two-command proof covers every removable flash device you can mount: USB sticks, SD and microSD cards in a reader, and second-hand drives whose history you do not know. Second-hand media deserves the full test most of all, because a previous owner’s clean experience proves nothing about the capacity a full write will reach. If you test drives regularly, keep a short log of each device, its claimed size, its tested result, and the date. Patterns in that log, such as one seller’s drives failing repeatedly, are exactly the evidence that protects your next purchase and strengthens any dispute. A drive that passes fully can join your working kit with normal backups. A drive that fails should leave your kit entirely, however small its real capacity turns out to be, because storage that began as a deception has no safe second career holding anything you value.