Custom Query (1096 matches)


Show under each result:

Results (40 - 42 of 1096)

Ticket Resolution Summary Owner Reporter
#341 worksforme smartd tries to send Email even though it was not configured to do so. a_user


I am using smartmontools/smartd 6.2 on Fedora 20. My smartd.conf file looks like this (all other lines are just empty or comments):

DEFAULT -H -s S/../../1/20 -p -f -l error -l xerror -n standby,q /dev/sda -i 197 -i 198 -W 5,32,38 -s L/../01/./21 DEVICESCAN -W 10,37,42

smartd itself is started by systemd with this command line:

/usr/sbin/smartd -n -q never

I have 4 different disks attached to this computer (/dev/sda, /dev/sdb, /dev/sdc, /dev/sdd). At the time /dev/sdb and /dev/sdc got hotter than 37 degree Celsius smartd tried to start /usr/bin/esmtp to send an email. I didn't configure smartd to send any email (not using the -m or -M options). Am I missing something or does smartd behave wrong?

Additional info: although /dev/sdd has some uncorrectable sectors it is only logged to syslog, not to mail (as expected/configured). Seems like just the last line is incorrectly interpreted.

#77 wontfix smartd to include fma on opensolaris somebody grooverdan

opensolaris has a fault management architecture. smartd has the detection capability to report faults into this architecture.

There is a simple API for reporting faults.

detailed documentation for this is available:

#520 wontfix smartd should provide socket interface ballock

smartd has knowledge of the state of all the hard drives in the system, and as such it is a perfect abstraction layer between the hardware and services or software that would make use of such information.

Unfortunately, although it is a daemon, it currently behaves in a cron-like fashion, by querying the HDD at specified intervals and optionally sending emails when a fault is detected.

My proposal is to add a Unix socket interface to smartd so that the last-checked HDD state and drive inventory can be queried from external software. I am proposing a simple query interface: 1-line command, 1-line response.

What smartd should provide on the socket:

  • a hello, I am running message; smartd version string included
  • a command to shut down
  • a command to reload the configs
  • a command to provide internal daemon statistics, like daemon runtime, etc

For the drive data that should also be:

  • a command to enumerate the drives monitored by smartd
  • a command to provide SMART variables for the specified drive (including SCSI/ATA specifics)

Optionally, these might make sense too:

  • a command to get/change device settings (-g -s in smartctl)
  • a command to deal with self-tests, SMART-GPT logs
Note: See TracQuery for help on using queries.