SATA Disk/SSD Temperature missing

According to this netdata documentation you add the following line to usr/lib/netdata/conf.d/python.d/smart_log.conf:

The tooltip for the Smart service Check Interval should also probably say something about not going above 30mins or 60 mins

Firstly a HUGE thank you to who has just spent about an hour looking at this (despite me being a free user!!!!!) - and it now appears to be working.

It appears to be due to one or both of the following settings in the Systems Settings / Services / Smart settings:

1. Check interval - was set to 60 - but the SmartMonitoringTools require an interval <= 30 mins.

2. Power mode - set to sleep (when I was previously considering spinning down the HDDs overnight) but tooltip says it must be set to “Never”.

Anyway, changing these made it work.

That said, I suspect that it was item 1. of the two - because the Smart service settings are for the Smart service (which collects the data) rather than the SmartMonitoringTools service (which processes the data) and the data was being collected for all disks despite having Power mode set to sleep.

So, my primary concern - actual monitoring of the HDD temps in order to be warned about bearings overheating - is resolved. It would be beneficial for other users if either the 30 mins max interval was removed or the UI prevented the Check Interval to be set to more than 30.

My secondary and quite minor concern is that the USB SSD is not showing in graphs despite the SMART data being collected. But I can certainly live without that.

Once again - a HUGE thank you to Muhammad for his help (and patience).

4pm works for me. Sending credentials in a few mins.

P.S. I am assuming you mean Microsoft Teams - if yo mean something else please provide details.

does 4 PM GMT today works for you and if yes - please share teamviewer creds to my email a few minutes before 4 PM GMT..do let me know though please that the timing works for you

This is why I stated the time of my comment - so that you could compare it with the local time of the comment as reported by Jira and calculate accordingly. I am in Western European Time which is the same as the UK and is GMT (for the next few weeks anyway).