I'm curious about what tool[s] you use for "simply taking a report a day for each disk and when disks act up I see if the bad sectors count are rising on one of the disks". [I do not agree with the 'less than useful' classification of smartd. Did you really see situations where your just-look-at-the-bad-blocks strategy did reveal some imminent catastrophe but smartd did _not_? [I was thinking about opening another thread for this, but stepped back then again.] Thank you! În vin., 16 aug. 2024 la 19:21, Roger Heflin <rogerheflin@xxxxxxxxx> a scris: > > Someone seems to have added it to setup a snmp config. It is > unlikely you want an snmp config/install, its only use is for external > monitoring via the network (without ssh access) and is for the most > part not being used much anymore. > > You might do a man smartd.conf and see if there is an option to > disable snmp config completely. > > I also disable smartd because generally it is less than useful (I have > had too many "your disk is going to fail soon" notifications where the > disk stopped working >3 years later--so the warning was useless, I > have also had disks fail that smartd did not ever report as failed). > Generally I view its reliability is so bad the tool is actually WORSE > than useless since it scares you with incorrect warnings, and fails to > report real (usually bad sector issues) correctly. > > I replace it with simply taking a report a day for each disk and when > disks act up I see if the bad sectors count are rising on one of the > disks. > > > On Fri, Aug 16, 2024 at 10:33 AM Robert McBroom via users > <users@xxxxxxxxxxxxxxxxxxxxxxx> 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. > > > > -- > > _______________________________________________ > > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue > -- > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
