On 8/16/24 11:00 PM, David King wrote:
On 8/16/24 11:32, Robert McBroom via users wrote:
Boot process f40 system stops for a long time with a problem with smartd. Seems to access the system drives and note that they are SMART capable. The following entries are in the journal
smartd[977]: Warning via /usr/libexec/smartmontools/smartdnotify to root produced>>
smartd[977]: No configuration file found at (null) or /etc/esmtprc
After multiple entries
smartd[977]: No configuration file found at (null) or /etc/esmtp
The files referenced are not in /etc. Don't see such files on a f39 system
What is the system looking to find and where can it be found.
esmtp is a mail transfer agent (MTA). Use "sudo dnf info esmtp" to see its Fedora package info. I know that on Fedora smartd is configured by default to send e-mail when it detects a problem on a disk. It may be that your system is configured to use esmtp to send mail and smartd has found a disk problem and is hanging when it tries to email you because esmtp is not configured properly. If that is the case then you would need to put the proper mail server, userid and password into file mentioned, /etc/esmtprc, to make it all work. Or, you could go into /etc/smartmontools/smartd.conf and change the configuration so it doesn't try to send emails.
To check to see if esmtp is actually the MTA your system is configured to use: "sudo alternatives --config mta"
To confirm that there is a disk problem that smartd is trying to notify you about: do "sudo smartctl --scan" to find the disk devices smart knows about and then do "sudo smartctl -a /dev/sdX" for one of the listed devices.
The only activated option in smartd.conf was
DEVICESCAN -H -m root -M exec /usr/libexec/smartmontools/smartdnotify -n standby,10,q
none of the email options were active but one could be hidden here.
Commented it out as I typically monitor the disks from the gnome-disk-utility application. Will do a boot to see.
Thanks David