On Sat, 2004-08-28 at 19:12, Brian Fahrlander wrote:
> And for the last 2-3 years or so, I've been running smartd on it.
> Nothing but the lockups and the need for fsck ever gave me any warning.
> Nothing in the syslog, other than the nightly notifiction that some
> obscure byte in smartd had changed. Shouldn't I have had _some_
> notification? Isn't this what smartd was designed to identify?
>
> Just thinking out loud...as I run "chkconfig smartd off"...
I'm surprised it worked at all on a drive that old but if
you don't take a logfile entry about a change as a warning
what do you expect?
---
Les Mikesell
les@xxxxxxxxxxxxxxxx
