From: Bruce A. <ba...@gr...> - 2003-04-02 15:17:35
|
> thank you for having replied in a such short time. Well I thought > smartd run some tests infact I coulnd't explain the existence of > smartctl except than reading attributes. It's also for running self-tests, and examining the self-test logs and ATA error logs. Although your main interest is in smartd, you should carefully read the smartctl manual page as well. > As you told I've to run > "smartctl -t long /dev/hda" by crontab...but what should be the most > right scheduling...I mean 4 hours or more? I'd suggest about once per week. > Doesn't this generate some > problems (conflicts) with the self test which is made by the hard > disk itself? (or the hard disk doesn't perform any kind of self > test?). Please read the smartctl manual page completely. It has a description of the different types of testing. > and smartctl updates the > attributes smartctl does not update the attributes. As it says in the manual page: smartctl does not calculate any of these values, it merely reports them from the S.M.A.R.T. data on the disk. > 2. smartd will read the updated attributes and will notify > what changed is. Another question....(sorry :o) ) I can't understand > when I should use the directive -S: > > > -S VALUE > > Enables or disables Attribute Autosave when smartd > > starts up and has no further effect. The valid > > arguments to this Directive are on and off. > > > > This is also a command line parameter we can find on using smartctl so > this seems I can use smartd instead of smartctl, but we have told that > these programs make different things...so I feel a little confused on > finding duplicated command line parameter/directive on both smartctl > and smartd.... :o( when using the one and the other? In fact you can use either smartctl or smartd to turn on the Attribute auto-save. It's there as a convenience in smartd. Cheers, Bruce |