Re: Updated on UDMA BadCRC errors + subsequent problems (was: Is it safe to ignore UDMA BadCRC errors?)

[Jonathan Kamens]

John Bradford writes:

 > Maybe not - the most common cause I've seen for that message in the
 > logs is trying to access S.M.A.R.T. information when S.M.A.R.T. is
 > disabled.
 > 
 > I.E. the error should be reproducable with:
 > 
 > # smartctl -d /dev/hda
 > # smartctl -a /dev/hda
 > 
 > Are you sure you weren't trying to get S.M.A.R.T. info from the
 > drive at the time the error was logged?

My smartctl wants "-s off" rather than "-d", but other than that,
you're correct, that sequence of commands does ause the same error to
appear in the logs.  But why/how would SMART be disabled on the drive?
I've been running smartd on the drive for weeks with no errors of this
sort, and I fail to see how SMART would suddenly be disabled on the
drive with no action on my part, so it seems more likely that some
other condition caused the error.

Thanks,

  jik
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/