Run a fuller check to verify
For users who prefer a thorough, traditional diagnostic run that tests every sector of the usable file system, the combination of f3write and f3read provides an exhaustive alternative modeled on the original h2testw process.
This two-step process functions at the file system level rather than the raw device level. Consequently, users supply the command with the drive’s active mount point—the directory where the device is accessed within the file system hierarchy, commonly structured as /media/username/DRIVE—rather than the raw /dev/ device node used by f3probe.
After confirming the active mount point through lsblk or a file manager, the write phase is initiated from the terminal:
f3write /media/device/
The utility systematically generates 1GB test files containing predictable data sequences, labeled sequentially in the format N.h2w, until the remaining free space on the drive is completely filled. A progress indicator tracks data throughput and estimated completion times. Because every megabyte of free space must be written to disk, this phase can take several hours on slower or large-capacity drives.
Once the write operation concludes, the verification phase is launched by pointing f3read at the identical mount directory:
f3read /media/device/
During this pass, f3read examines each generated test file, comparing the data retrieved from the flash memory against the original patterns written during the first phase. If the storage device is legitimate, all sectors pass without incident. If the drive is counterfeit, any sectors that the controller discarded, wrapped around, or overwrote will immediately surface as damaged, corrupted, or missing data blocks in the terminal report. Once testing is complete, users simply delete the generated .h2w test files to restore standard storage availability.
And if the drive is fake?
Discovering that a newly purchased memory card or flash drive possesses only a fraction of its advertised capacity leaves consumers with distinct practical and technical choices. From a consumer perspective, retaining original transaction receipts, packaging, and order confirmations is critical. A failed F3 diagnostic report provides clear, undeniable documentation of counterfeit goods, which can be leveraged to dispute charges, request immediate refunds, or file formal vendor complaints through marketplace buyer protection policies.
From a technical perspective, users who cannot secure a refund or who simply wish to repurpose the hardware can deploy the f3fix utility. By applying the parameters generated during an f3probe diagnostic scan, f3fix configures a modified partition table that restricts drive usage exclusively to the physical boundary of genuine storage cells. This prevents the operating system from attempting to write beyond the physical capacity of the flash chips, effectively eliminating the silent data loss caused by loopback overwriting.
However, system administrators and storage analysts caution against relying on salvaged counterfeit drives for important work. Flash memory controllers that have been deliberately reprogrammed to defraud consumers are typically paired with the lowest tier of factory-rejected, substandard NAND silicon. These components are prone to premature degradation, controller lockups, and unrecoverable read errors, meaning that even when downsized to their true capacity, counterfeit drives remain deeply unreliable for any critical storage needs.
