-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2005-10-15 at 08:11 -0700, Simon Roberts wrote:
I set up smartd to monitor the drives of my raid array a week or so ago. I created these entries in my smartd.conf file:
/dev/hde -H -l error -l selftest -s (S/../../2|4|6|7/02|L/../../1/01) -m simon,root -M test
I guess you copied that from my config ;-) /dev/hda -H -f -l selftest -l error -C 197 -U 198 -m cer -s (S/../../2|4|6|7/22|L/../../5/23) Ok, the -s (S/../../2|4|6|7/02|L/../../1/01) strings means: T MM DD d d d d HH Do the short test at 02 hours of Tuesdays, Thursdays, Saturdays and Sundays - on other days, do nothing. Do the long test at 01:00 hours of Mondays.
I get test messages when the system boots. However, if I manually poll the drives with smartctl -a, they don't show any record of having run any tests under this configuration. Normally, if I run a test manually, it shows up in a history list on the drive.
Your computer must be running at that hour and day. You should find messages like this at those times in /var/log/messages: Oct 14 23:10:26 nimrodel smartd[2724]: Device: /dev/hda, starting scheduled Long Self-Test. Oct 14 23:10:26 nimrodel smartd[2724]: Device: /dev/hdb, starting scheduled Long Self-Test. Oct 14 23:10:27 nimrodel smartd[2724]: Device: /dev/hdd, starting scheduled Long Self-Test. I don't find entries for short tests, but I can see them with smartctl -a By the way, you'd better make sure that the long test does not coincide with cron daily run. It works, of course, but much slower. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDVljNtTMYHG2NR9URAhUUAKCJdXaPVwwYe2Kq3Eiu0X7bpza2SACfcYph +cV2C1YquVq7x0EomVImKq4= =lsjX -----END PGP SIGNATURE-----