On 8/17/24 9:20 AM, David King wrote:
On 8/17/24 00:37, Robert McBroom via users wrote:
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 n
> On 20 Aug 2024, at 17:04, Iosif Fettich wrote:
>
> 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 o
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-
On 8/17/24 00:37, Robert McBroom via users wrote:
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 fo
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]:
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/sm
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 t
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 conf
