Michel Machado

There's a stage of the algorithm of `f3probe` that it knows that (1) the drive being tested is fake and (2) a possible usable size of the drive (i.e. a...

About drive 2. `f3probe` will report a drive is damaged anytime when there are repeated I/O errors. Drive 3. This drive is interesting because it passed `f3probe`'s test at least...

> @AltraMayor - I'm not sure if the 1st tested drive is really fake, because I've already tested it with f3write/f3read and I don't remember any of the drives returning...

Hi @milangfx, `f3probe` is reporting the drive as "damaged" because it gets I/O errors when it writes to some location in the drive. This last conclusion about the write operation...

Hi @FreezeHeat, I agree with your conclusion that you have a good drive that is failing since the drive can hold most of its announced size. While it's possible that...

Some filesystems support what you want, and, on those filesystems, you may find more than one way to do it. The following link shows an example for ext4: https://sysadmin.compxtreme.ro/check-and-mark-badblocks-on-ext4-partitions/ In...

Hi @whitslack, Flakyflash meets the demands of some of the users of F3, so I'm open to a pull request to add a brief description and link to it in...

F3 returns an error when it cannot report on the tested drive. That is, F3 does not try to interpret the output of its report. Although I'm suspicious of the...

Hi @pravorskyi, I'm not familiar with SonarQube, but I'm open to integrating with it, so I can gradually learn it. Can you implement the integration using GitHub actions? If so,...

I remember that a user published years ago an image with some tools that included among them F3, but I can't remember his name. I'm going to leave this issue...