Michael wrote: > On Monday, 2 November 2020 05:08:14 GMT Dale wrote: >> Howdy, >> >> I did a KDE update so I switched to boot runlevel and back to default. >> I noticed that a service didn't start and it was smartd. Not exactly >> critical but it does monitor my hard drives. When I try to restart it, >> I get this using the -v option. >> >> >> root@fireball / # /etc/init.d/smartd start -v >> * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh >> /etc/init.d/smartd start >> * Starting smartd ... >> * start-stop-daemon: fopen `/run/smartd.pid': No such file or directory >> * Detaching to start `/usr/sbin/smartd' ... >> * start-stop-daemon: failed to start `/usr/sbin/smartd' >> * Failed to start >> smartd >> >> [ !! ] >> * ERROR: smartd failed to start >> root@fireball / # >> >> >> I've tried re-emerging the smartmontools package, I've tried the zap >> option as well, in case my recent power supply blow up left some cruft >> behind. I also googled but can't find this problem. It seems tho that >> the pid file should maybe be in /var instead of /run. I'm not sure if >> it was moved recently or what. >> >> Anyone know how to fix this? Or run into this before? >> >> Thanks. >> >> Dale >> >> :-) :-) > The pid file hasn't moved here on a stable system: > > $ ls -la /run/smartd.pid > -rw------- 1 root root 5 Nov 2 08:22 /run/smartd.pid > > This is what syslog reveals: > > ... smartd[3669]: smartd has fork()ed into background mode. New PID=3669. > ... smartd[3669]: file /run/smartd.pid written containing PID 3669 > > What do you see in your syslog as you try to start it?
It has this. Nov 2 09:38:28 fireball smartd[20975]: smartd 7.1 2019-12-30 r5022 [x86_64-linux-5.6.7-gentoo] (local build) Nov 2 09:38:28 fireball smartd[20975]: Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org Nov 2 09:38:28 fireball smartd[20975]: Opened configuration file /etc/smartd.conf Nov 2 09:38:28 fireball smartd[20975]: Configuration file /etc/smartd.conf parsed. Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sda [SAT], opened Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sda [SAT], WDC WD1600AAJS-00YZCA0, S/N:WD-WCAYU4389620, WWN:5-0014ee-1ad79c1b3, FW:01.03B01, 160 GB Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sda [SAT], found in smartd database: Western Digital Caviar Blue Serial ATA Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sda [SAT], enabled SMART Attribute Autosave. Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sda [SAT], enabled SMART Automatic Offline Testing. Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list. Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sdc [SAT], opened Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sdc [SAT], WDC WD60EZRZ-00GZ5B1, S/N:WD-WXJ1H26HUAL2, WWN:5-0014ee-2633c4309, FW:80.00A80, 6.00 TB Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sdc [SAT], found in smartd database: Western Digital Blue Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sdc [SAT], enabled SMART Attribute Autosave. Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sdc [SAT], enabled SMART Automatic Offline Testing. Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sdc [SAT], is SMART capable. Adding to "monitor" list. Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sde [SAT], opened Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sde [SAT], SAMSUNG HD753LJ, S/N:S1PWJ1KS305193, WWN:5-0024e9-001308c31, FW:1AA01117, 750 GB Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sde [SAT], found in smartd database: SAMSUNG SpinPoint F1 DT Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sde [SAT], enabled SMART Attribute Autosave. Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sde [SAT], enabled SMART Automatic Offline Testing. Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sde [SAT], is SMART capable. Adding to "monitor" list. Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sdf [SAT], opened Nov 2 09:38:28 fireball smartd[20975]: Device: /dev/sdf [SAT], not ATA, no IDENTIFY DEVICE Structure Nov 2 09:38:28 fireball smartd[20975]: Unable to register ATA device /dev/sdf [SAT] at line 91 of file /etc/smartd.conf Nov 2 09:38:28 fireball smartd[20975]: Unable to register device /dev/sdf [SAT] (no Directive -d removable). Exiting. Nov 2 09:38:28 fireball /etc/init.d/smartd[20974]: start-stop-daemon: failed to start `/usr/sbin/smartd' Nov 2 09:38:28 fireball /etc/init.d/smartd[20950]: ERROR: smartd failed to start root@fireball / # It appears it doesn't like that sdf is no longer there. I commented out that line in the conf file and now it starts. Since I do move drives on rare occasions, is there a way to make it just recognize a drive that is there but ignore any that have been removed? After all, things are hot plugable nowadays. I might add, I have a sdk that is a external drive. Actually, two drives share sdk since they are never connected at the same time. Even tho I sometimes test it manually, I would like it to notify me if it receives some sort of a SMART error. This is the relevant conf part, leaving out the commented out lines for sure. /dev/sda -a -d sat -o on -S on -s (S/../.././12|L/../../6/12) -m root /dev/sdb -a -d sat -o on -S on -s (S/../.././12|L/../../6/12) -m root /dev/sdc -a -d sat -o on -S on -s (S/../.././12|L/../../6/12) -m root /dev/sdd -a -d sat -o on -S on -s (S/../.././12|L/../../6/12) -m root /dev/sde -a -d sat -o on -S on -s (S/../.././12|L/../../6/12) -m root #/dev/sdf -a -d sat -o on -S on -s (S/../.././12|L/../../6/12) -m root All other lines appear to be commented out except that. I notice it has -d on all those even tho the logs say it doesn't. Something missing? Maybe there is a better setting for all this?? Thanks much. Dale :-) :-)
