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?
signature.asc
Description: This is a digitally signed message part.
