3 ms·
Have you found cases where "f3probe --destructive" didn't work for you?
by axiolite 2y ago
Have you found cases where "f3probe --destructive" didn't work for you?
- dspillett 2y agoNot first hand, though I've used tools of similar intent and found the quick heuristics, while usually very good, not 100% reliable, and for storage I want to be sure not almost certain. Note that I was warning about quick tests, I'll have to try “f3probe --destructive” on something next time I have some playtime to see whether I'd consider that quick! Of course, it could be much quicker than the full capacity write some tools use to find a defective or deceptive drive¹² but quicker and quick aren't the same. If a quick test says the drive is fake then it is, and many fakes can be detected these ways, but it takes more to convincingly state a drive isn't fake. -- [1] Only a little over true capacity should be needed for that, in the case where writes to anywhere up to capacity will work (which is common as creating a filesystem more complex than FAT/exFat often requires activity similar to what quick write/read heuristics do).