Raffaele BELARDI wrote: > Dale wrote: >> I went through this before and I haven't changed anything so not sure >> why it isn't working now. I decided to test smartd to make sure that it >> would send me a email if a drive developed a problem. I added -M test >> to the line, restarted smartd and got nothing. I mean nothing but >> crickets. Going to post relevant info that I know of. Here we go: > (snip) > >> When I check my email, I do get the test message. It seems to me that >> ssmtp is working but that smartd either isn't working or it is not >> getting to ssmtp somehow. >> >> Anyone see a reason this shouldn't be working? I'd really like a heads >> up if a drive is having "issues". >> > Any hints from the syslog? Here -M test seems to work fine. > > raffaele
Sorry. I forgot to include that. This is from when I restart smartd. Aug 4 04:46:45 fireball smartd[3610]: smartd received signal 15: Terminated Aug 4 04:46:45 fireball smartd[3610]: smartd is exiting (exit status 0) Aug 4 04:46:45 fireball smartd[7526]: smartd 6.4 2015-06-04 r4109 [x86_64-linux-3.18.7-gentoo] (local build) Aug 4 04:46:45 fireball smartd[7526]: Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org Aug 4 04:46:45 fireball smartd[7526]: Opened configuration file /etc/smartd.conf Aug 4 04:46:45 fireball smartd[7526]: Drive: DEVICESCAN, implied '-a' Directive on line 27 of file /etc/smartd.conf Aug 4 04:46:45 fireball smartd[7526]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices Aug 4 04:46:45 fireball smartd[7526]: Device: /dev/sda, type changed from 'scsi' to 'sat' Aug 4 04:46:45 fireball smartd[7526]: Device: /dev/sda [SAT], opened Aug 4 04:46:45 fireball smartd[7526]: Device: /dev/sda [SAT], WDC WD1600AAJS-00YZCA0, S/N:WD-WCAYU4389620, WWN:5-0014ee-1ad79c1b3, FW:01.03B01, 160 GB Aug 4 04:46:45 fireball smartd[7526]: Device: /dev/sda [SAT], found in smartd database: Western Digital Caviar Blue Serial ATA Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list. Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sdb, type changed from 'scsi' to 'sat' Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sdb [SAT], opened Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sdb [SAT], SAMSUNG HD753LJ, S/N:S1PWJ1KS305193, WWN:5-0024e9-001308c31, FW:1AA01117, 750 GB Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sdb [SAT], found in smartd database: SAMSUNG SpinPoint F1 DT Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list. Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sdc, type changed from 'scsi' to 'sat' Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sdc [SAT], opened Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sdc [SAT], ST3000DM001-1CH166, S/N:W1F4C31Q, WWN:5-000c50-06e7a0a7c, FW:CC29, 3.00 TB Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sdc [SAT], found in smartd database: Seagate Barracuda 7200.14 (AF) Aug 4 04:46:46 fireball smartd[7526]: Device: /dev/sdc [SAT], is SMART capable. Adding to "monitor" list. Aug 4 04:46:46 fireball smartd[7526]: Monitoring 3 ATA and 0 SCSI devices Aug 4 04:46:46 fireball smartd[7528]: smartd has fork()ed into background mode. New PID=7528. Aug 4 04:46:46 fireball smartd[7528]: file /run/smartd.pid written containing PID 7528 root@fireball / # It seems to start and begin monitoring but I don't see anything about it even trying to email anything. Thanks. Dale :-) :-)
