On 22/10/14 18:24, Srdjan Todorovic wrote:
Hi fellow ALUGgers,
Started getting fsck errors on a drive, ran smartctl -t long and smartctl -a.
[SNIP]
Is the drive cooked?
I don't know - sorry.
Why does the self test execution status report all is ok? Why does offline data collection status report without error? Why is the overall status PASSED?
I'm not entirely sure about this, but is this because SMART tools and fsck are not necessarily testing the same thing?
fsck is checking the integrity of the file system. SMART reports any hardware errors and information on the disk. Hardware errors will probably result in errors in the file system, but errors in the file system are not necessarily caused by hardware errors. Is it possible that a machine suffers a power outage in mid-write could end with file system corruption.
Whatever, if funds allow, if in doubt, replace it. At the very least, back it all up.
Good luck. Steve