At 4:10 PM +0930 10/26/07, Tim wrote: >Tim: >>> Today I noticed the following in my log file, but I >>> haven't yet explored any further about it: >>> >>> --------------------- Smartd Begin ------------------------ >>> >>> >>> /dev/sda : >>> Usage: Load_Cycle_Count (193) changed to >>> 99, >>> Usage: Temperature_Celsius (194) changed to >>> 220, 203, 189, 183, 253, 220, 189, 196, >>> >>> **Unmatched Entries** >>> Drive: DEVICESCAN, implied '-a' Directive on line 18 of file >>>/etc/smartd.conf >>> Problem creating device name scan list >>> Device /dev/sda: ATA disk detected behind SAT layer >>> Try adding '-d sat' to the device line in the smartd.conf file. >>> For example: '/dev/sda -a -d sat' >>> >>> ---------------------- Smartd End ------------------------- >>> >>> Despite what it says. To the best of my knowledge, my HDD is actually a >>> SATA drive, and the motherboard pretends its PATA. > >Tony Nelson: >> It did't say anything about SATA or PATA, only about ATA behind SCSI SAT >>layer. > >Ah... Well, if it'd used the word SCSI, I would have had a hint to >follow (in that message, itself). ;-) > >Looking through /var/log/messages, with the current simple DEVICESCAN >option set in the configuration file (and nothing else), I see entries >like this: > >Oct 26 13:33:32 suspishus smartd[2609]: Opened configuration file >/etc/smartd.conf >Oct 26 13:33:32 suspishus smartd[2609]: Drive: DEVICESCAN, implied '-a' >Directive on line 18 of file /etc/smartd.conf >Oct 26 13:33:33 suspishus smartd[2609]: Configuration file >/etc/smartd.conf was parsed, found DEVICESCAN, scanning devices >Oct 26 13:33:33 suspishus smartd[2609]: Problem creating device name scan list >Oct 26 13:33:33 suspishus smartd[2609]: Device: /dev/sda, opened >Oct 26 13:33:33 suspishus smartd[2609]: Device /dev/sda: ATA disk detected >behind SAT layer >Oct 26 13:33:34 suspishus smartd[2609]: Try adding '-d sat' to the >device line in the smartd.conf file. >Oct 26 13:33:34 suspishus smartd[2609]: For example: '/dev/sda -a -d sat' >Oct 26 13:33:34 suspishus smartd[2609]: Device: /dev/sda, opened >Oct 26 13:33:35 suspishus smartd[2609]: Device: /dev/sda, not found in >smartd database. >Oct 26 13:33:35 suspishus smartd[2609]: Device: /dev/sda, is SMART >capable. Adding to "monitor" list. >Oct 26 13:33:35 suspishus smartd[2609]: Monitoring 1 ATA and 0 SCSI devices >Oct 26 13:33:36 suspishus smartd[2611]: smartd has fork()ed into >background mode. New PID=2611. >Oct 26 14:03:33 suspishus smartd[2611]: Device: /dev/sda, SMART Usage >Attribute: 194 Temperature_Celsius changed from 250 to 203 >Oct 26 14:33:33 suspishus smartd[2611]: Device: /dev/sda, SMART Usage >Attribute: 194 Temperature_Celsius changed from 203 to 183 >Oct 26 15:33:33 suspishus smartd[2611]: Device: /dev/sda, SMART Usage >Attribute: 194 Temperature_Celsius changed from 183 to 177 > >So I presume I don't really need to customise the file any further, it >appears to be reading data from the drive, as it is (it's found a drive, >it's monitoring 1 drive, and showing some values associated with that >drive). Yes. In my case, without the change smartd monitored 0 devices, so the change was needed. -- ____________________________________________________________________ TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx> ' <http://www.georgeanelson.com/>
