Temperature on Seagate disks not shown


12 posts in this topic Last Reply

Recommended Posts

Thanks for the tip. Strange that the default is set to 30 minutes. Is there any additional stress that polling significantly more often (e.g. every 60 seconds) could cause? I guess my question could be rephrased as, is polling SMART causing the drive to perform any additional work out of its ordinary SMART health monitoring?

Link to post
4 hours ago, realies said:

Thanks for the tip. Strange that the default is set to 30 minutes. Is there any additional stress that polling significantly more often (e.g. every 60 seconds) could cause? I guess my question could be rephrased as, is polling SMART causing the drive to perform any additional work out of its ordinary SMART health monitoring?

It had trouble with certain drives (Seagate in particular) when pulling smart reports while disk was getting heavy I/O with preclear. In fact my worst drive experience ever happened with such a drive that was running on a non-motherboard controller. Maybe was a bad drive all along, but I was pretty convinced it was related to the smart reports and since stuck with motherboard ports and limiting smart reports. And I've never had anything like the wonky symptoms I saw from that drive that I returned for exchange.

 

Would be nice if guI had an option to trigger a reread of the attributes when you specifically wanted them to refresh. Otherwise, you might leave it an.infrequent internal.

Link to post

A problem (in the past) was that quering SMART information could interfere with the normal operation of the disk. This was mostly noticable when a parity check was done and parity check times could go up considerably when (too) many SMART queries were done at the same time.

 

The default value of 30 minutes was taken from a recommendation of smart tools, but in practise this is quite a long interval to see results in *near* real-time. In general it is safe to lower the interval to a couple of minutes. Making the interval too short may again have impact on the normal operation of the disk though.

 

The GUI reads the information obtained by the emhttp daemon, it doesn't query the disks directly itself.

 

Link to post
6 hours ago, bonienl said:

The default value of 30 minutes was taken from a recommendation of smart tools

One note here is that smartmontools creates a CSV record for every processed disk so 30 minutes is a reasonable interval to create long-term logging.

 

When relating to a GUI I think 5 minutes would be a reasonable interval.

Link to post
  • 1 year later...

Just for the sake of Murphy's law while assuming a cooling problem of some sort (ambient) and one or more drives would run hot.

How long do you want your drives to run hot before a notice is generated? 

I know it is a bit far fetched but that is the time frame I personally like to work with.

Have set my Tunable (poll_attributes) to 3 minutes. Only hope that is not too long.

Link to post
  • 1 year later...

Hi All

I Have same related problem here with my Seagate’s disks (SAS Server Drives With Raid Controller card ) not displaying Temp stats ?  but was working fine before new update to Unraid 6.9.1

Was there any changes made in the update that may have change value or any work around to fix this as temp is important summer is round the corner and don’t what my drives to get to hot losing the ability to monitor them is concerning 

any advise will help .

 

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.