NOT fully read

[SampsonF]

Sorry if this has been covered in documents.

I am running version 8.0 compile from source downloaded here, against a single rotating HDD mounted as .

#sudo f3-8.0/f3read -p 1 dangerous/ &

I got 'NOT fully read due to "Input/output error"', but no corrupted / changed / overwritten.

Does that mean f3read cannot continue to read the file (due to interface reset, etc) so continue to the next one. But so far for the bytes able to read, there are no errors.

Another question:

• when f3read reporting corrupted / changed / overwritten, will f3read tell me the byte offsets that the error occurred?

some files showing errors

Validating file 460.h2w ... 312321/ 0/ 0/ 0 - NOT fully read due to "Input/output error" Validating file 461.h2w ... 2097152/ 0/ 0/ 0 Validating file 462.h2w ... 2097152/ 0/ 0/ 0 Validating file 463.h2w ... 2097152/ 0/ 0/ 0 Validating file 464.h2w ... 1323875/ 0/ 0/ 0 - NOT fully read due to "Input/output error" Validating file 465.h2w ... 2097152/ 0/ 0/ 0 Validating file 466.h2w ... 2097152/ 0/ 0/ 0 Validating file 467.h2w ... 1651647/ 0/ 0/ 0 - NOT fully read due to "Input/output error" Validating file 468.h2w ... 2097152/ 0/ 0/ 0 Validating file 469.h2w ... 1671071/ 0/ 0/ 0 - NOT fully read due to "Input/output error"

[AltraMayor]

Your understanding is right, the message NOT fully read due to "Input/output error" means that f3read cannot continue reading the file, so it goes on to the next file.

f3read doesn't report the byte offsets of corrupted, changed, or overwritten sectors. Given that f3read works on a filesystem, this information only has meaning for the filesystem. If you want to identify blocks, you should use f3brew, which accesses block devices directly.