Comment Re:28 files in 6 years is a hardware defect (Score 1) 396
Bad RAM could have corrupted the file as it was being written to disk. The file is corrupted all along, but not the disk/filesystem's fault
Or the file could have been corrupted in RAM on read, and would actually be fine if read on a working machine.
Or the disk has been replaced in those 6 years and the file was corrupted during the copy because of bad RAM
There are lots of possibilities for the file to get corrupted that don't involve the disk or filesystem.
Or the file could have been corrupted in RAM on read, and would actually be fine if read on a working machine.
Or the disk has been replaced in those 6 years and the file was corrupted during the copy because of bad RAM
There are lots of possibilities for the file to get corrupted that don't involve the disk or filesystem.