Custom Query (1414 matches)

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

When scanning for devices, smartd uses the FreeBSD cam subsystem to iterate through all of the devices on the system. When it encounters a SATA port multipler (e.g., /dev/pmp0) it sends commands to that device that eventually timeout. This delays boot by several minutes on a large system.

Running "smartd -q onechceck" produces errors like this for each port multiplier encountered,

Device: /dev/pmp8, opened (pass53:mvsch10:0:15:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 00 (pass53:mvsch10:0:15:0): CAM status: ATA Status Error (pass53:mvsch10:0:15:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (pass53:mvsch10:0:15:0): RES: 51 04 00 00 00 00 00 00 00 00 00 (pass53:mvsch10:0:15:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 01 00 (pass53:mvsch10:0:15:0): CAM status: Command timeout Device: /dev/pmp8, not ATA, no IDENTIFY DEVICE Structure Unable to register ATA device /dev/pmp8

These devices should be avoided on FreeBSD. The attached patch avoids them when running "smartd -d onecheck" but it is not clear if that is sufficient or even the right place to make such a change.

Attached is an {open}solaris service definition. The configure script should alter some of the path names but otherwise should work flexibly.

An make install target could do something like:

	cp smartd.xml /var/svc/manifest/site/
	chown root:sys /var/svc/manifest/site/smartd.xml
	svccfg -v import /var/svc/manifest/site/smartd.xml

Documentation could say run 'svcadm enable smartd' to get it running

I'm still getting this error. I'm running out of time to debug it. Tips welcome.

svc:/system/smartd:default (SMART monitoring)
 State: maintenance since June  9, 2010 01:54:26 PM EST
Reason: Start method failed repeatedly, last exited with status 10.
   See: http://sun.com/msg/SMF-8000-KS
   See: man -M /usr/share/man -s 1M smartd
   See: man -M /usr/share/man -s 4 smartd.conf
   See: /var/svc/log/system-smartd:default.log
Impact: This service is not running.

/var/svc/log/system-smartd:default.log

[ Jun  9 13:52:06 Rereading configuration. ]
[ Jun  9 13:54:26 Executing start method ("/usr/sbin/smartd -q never"). ]
[ Jun  9 13:54:26 Method "start" exited with status 10. ]
[ Jun  9 13:54:26 Executing start method ("/usr/sbin/smartd -q never"). ]
[ Jun  9 13:54:26 Method "start" exited with status 10. ]
[ Jun  9 13:54:26 Executing start method ("/usr/sbin/smartd -q never"). ]
[ Jun  9 13:54:26 Method "start" exited with status 10. ]