Extremely frequent SMART checks


13 posts in this topic Last Reply

Recommended Posts

Hi guys, are SMART checks super frequent now under 6.9.0 or is something else a likely culprit here?  My log is pretty much this now - spin down, read smart, spin down, wait 30 mins, rinse and repeat.  Is that normal?  I used to have disks sleep for a very long time.

 

image.png.a70f6358f21f6418c823856edc55da65.png

Link to post
10 minutes ago, Pillendreher said:

Not really. I'm on 6.9.1 and my disks still wake up due to a smart reading:

 

grafik.png.3b099ef25b36ef6fceb1caf6302538fd.png

 

 

I suspect something else is waking up the drive, Unraid notices and then does SMART to get temp.

 

 

Link to post
4 hours ago, SimonF said:

I suspect something else is waking up the drive, Unraid notices and then does SMART to get temp.

 

 

I've suspected that as well, but I don't think there is anything. I'm not running any monitoring software on my Unraid server.

Edited by Pillendreher
Link to post

Yeah, I have been wondering about this too.

 

Mar 12 12:02:55 unRAID emhttpd: spinning down /dev/sdn
Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdg
Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdw
Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdd
Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdt
Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sde
Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdu
Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdr
Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sds
Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdq
Mar 12 12:02:58 unRAID emhttpd: spinning down /dev/sdp
Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdm
Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdj
Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdh
Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdf
Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdv
Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdo
Mar 12 12:03:02 unRAID emhttpd: spinning down /dev/sdi
Mar 12 14:06:20 unRAID nmbd[11338]: [2021/03/12 14:06:20.406871,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Mar 12 14:06:20 unRAID nmbd[11338]:   *****
Mar 12 14:06:20 unRAID nmbd[11338]:   
Mar 12 14:06:20 unRAID nmbd[11338]:   Samba name server UNRAID is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.15
Mar 12 14:06:20 unRAID nmbd[11338]:   
Mar 12 14:06:20 unRAID nmbd[11338]:   *****
Mar 12 14:41:42 unRAID emhttpd: read SMART /dev/sdj
Mar 12 15:26:55 unRAID emhttpd: read SMART /dev/sdh
Mar 12 16:09:26 unRAID emhttpd: read SMART /dev/sdi
Mar 12 16:10:19 unRAID emhttpd: read SMART /dev/sdw
Mar 12 16:11:08 unRAID emhttpd: read SMART /dev/sdu
Mar 12 16:12:35 unRAID emhttpd: read SMART /dev/sdf
Mar 12 16:12:46 unRAID emhttpd: read SMART /dev/sde
Mar 12 16:13:23 unRAID emhttpd: read SMART /dev/sdd
Mar 12 16:13:42 unRAID emhttpd: read SMART /dev/sdq
Mar 12 16:13:57 unRAID emhttpd: read SMART /dev/sdp
Mar 12 16:14:24 unRAID emhttpd: read SMART /dev/sdt
Mar 12 16:14:42 unRAID emhttpd: read SMART /dev/sds
Mar 12 16:15:34 unRAID emhttpd: read SMART /dev/sdr
Mar 12 16:16:03 unRAID emhttpd: read SMART /dev/sdv
Mar 12 16:17:54 unRAID emhttpd: read SMART /dev/sdg
Mar 12 16:52:49 unRAID emhttpd: read SMART /dev/sdn
Mar 12 16:55:00 unRAID emhttpd: read SMART /dev/sdm
Mar 12 16:55:00 unRAID emhttpd: read SMART /dev/sdo
Mar 12 17:11:09 unRAID emhttpd: spinning down /dev/sdu
Mar 12 17:12:47 unRAID emhttpd: spinning down /dev/sde
Mar 12 17:14:00 unRAID emhttpd: spinning down /dev/sdp
Mar 12 17:14:27 unRAID emhttpd: spinning down /dev/sdt
Mar 12 17:14:45 unRAID emhttpd: spinning down /dev/sds
Mar 12 17:14:53 unRAID emhttpd: spinning down /dev/sdd
Mar 12 17:15:51 unRAID emhttpd: spinning down /dev/sdr
Mar 12 17:16:22 unRAID emhttpd: spinning down /dev/sdf
Mar 12 17:16:29 unRAID emhttpd: spinning down /dev/sdw
Mar 12 17:16:29 unRAID emhttpd: spinning down /dev/sdq
Mar 12 17:16:36 unRAID emhttpd: spinning down /dev/sdi
Mar 12 17:17:55 unRAID emhttpd: spinning down /dev/sdg
Mar 12 17:18:20 unRAID emhttpd: spinning down /dev/sdv
Mar 12 17:39:46 unRAID emhttpd: spinning down /dev/sdj
Mar 12 17:41:18 unRAID emhttpd: read SMART /dev/sdj
Mar 12 17:47:23 unRAID ool www[32538]: /usr/local/emhttp/plugins/dynamix/scripts/notify 'smtp-init'
Mar 12 17:56:21 unRAID emhttpd: spinning down /dev/sdm
Mar 12 17:56:21 unRAID emhttpd: spinning down /dev/sdn
Mar 12 17:56:21 unRAID emhttpd: spinning down /dev/sdo
Mar 12 17:56:24 unRAID emhttpd: read SMART /dev/sdv
Mar 12 17:56:57 unRAID emhttpd: read SMART /dev/sdi
Mar 12 17:57:13 unRAID emhttpd: read SMART /dev/sdr
Mar 12 17:57:43 unRAID emhttpd: read SMART /dev/sde
Mar 12 17:57:59 unRAID emhttpd: read SMART /dev/sdg
Mar 12 17:58:30 unRAID emhttpd: read SMART /dev/sdp
Mar 12 17:58:44 unRAID emhttpd: read SMART /dev/sdw
Mar 12 17:59:05 unRAID emhttpd: read SMART /dev/sdf
Mar 12 18:00:05 unRAID emhttpd: read SMART /dev/sdu
Mar 12 18:00:16 unRAID emhttpd: read SMART /dev/sdt
Mar 12 18:00:49 unRAID emhttpd: read SMART /dev/sdd
Mar 12 18:01:10 unRAID emhttpd: read SMART /dev/sdq
Mar 12 18:02:56 unRAID emhttpd: read SMART /dev/sds
Mar 12 19:00:21 unRAID emhttpd: read SMART /dev/sdn
Mar 12 19:03:21 unRAID emhttpd: spinning down /dev/sdg
Mar 12 19:04:27 unRAID emhttpd: spinning down /dev/sdt
Mar 12 19:04:57 unRAID emhttpd: spinning down /dev/sdu
Mar 12 19:05:09 unRAID emhttpd: spinning down /dev/sdq
Mar 12 19:05:12 unRAID emhttpd: spinning down /dev/sds
Mar 12 19:05:31 unRAID emhttpd: spinning down /dev/sde
Mar 12 19:06:00 unRAID emhttpd: spinning down /dev/sdp
Mar 12 19:06:04 unRAID emhttpd: spinning down /dev/sdd
Mar 12 19:06:10 unRAID emhttpd: spinning down /dev/sdr
Mar 12 19:06:13 unRAID emhttpd: spinning down /dev/sdk
Mar 12 19:06:31 unRAID emhttpd: spinning down /dev/sdw
Mar 12 19:06:52 unRAID emhttpd: spinning down /dev/sdv
Mar 12 19:07:01 unRAID emhttpd: spinning down /dev/sdh
Mar 12 19:07:03 unRAID emhttpd: spinning down /dev/sdf
Mar 12 19:07:08 unRAID emhttpd: spinning down /dev/sdi
Mar 12 19:07:11 unRAID emhttpd: spinning down /dev/sdj
Mar 12 19:11:23 unRAID emhttpd: read SMART /dev/sdk
Mar 12 19:23:44 unRAID ool www[4095]: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init'
Mar 12 19:27:41 unRAID ool www[5874]: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init'
Mar 12 19:42:11 unRAID ool www[24315]: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init'
Mar 12 20:00:22 unRAID emhttpd: spinning down /dev/sdn
Mar 12 20:41:34 unRAID emhttpd: read SMART /dev/sdj
Mar 12 20:42:54 unRAID emhttpd: read SMART /dev/sdv
Mar 12 21:51:09 unRAID emhttpd: spinning down /dev/sdj
Mar 12 22:11:40 unRAID emhttpd: spinning down /dev/sdk

 

Link to post
9 hours ago, Pillendreher said:

I've suspected that as well, but I don't think there is anything. I'm not running any monitoring software on my Unraid server.

 

Do you have file activity plugin installed? This may provide an overview of any files are being open at the same times.

 

I know you are not using SAS drives but if you install doron's plugin it has a smartctl wrapper that you can set to debug and it will post an entry in the log if you add debug=true to the script.

 

Other things that where causing spin ups before 6.9.1 where processes that used smartctl i.e. telegraf checking disk temps etc. I know you said you don't run any of these monitoring tools and the use of smartctl shouldn't be the cause now.

 

Other plugins may be using hdparm which could cause spin ups. If you want to post diags I can have look to see if there is anything obvious. 

Link to post
2 hours ago, SimonF said:

 

Do you have file activity plugin installed? This may provide an overview of any files are being open at the same times.

 

I know you are not using SAS drives but if you install doron's plugin it has a smartctl wrapper that you can set to debug and it will post an entry in the log if you add debug=true to the script.

 

Other things that where causing spin ups before 6.9.1 where processes that used smartctl i.e. telegraf checking disk temps etc. I know you said you don't run any of these monitoring tools and the use of smartctl shouldn't be the cause now.

 

Other plugins may be using hdparm which could cause spin ups. If you want to post diags I can have look to see if there is anything obvious. 

 

These are my currently installed plugins:

 

grafik.thumb.png.c0ac7020baf298aafdcaa011f26201a3.png

 

The only User script I'm running is an undervolting script for my Intel CPU. I also user Docker images, but none of them actually utilize HDDs unless I tell them to.

 

Is there any way to debug the smart reading? Ie can I pinpoint the source for the smart request?

Link to post

The one the system uses in /usr/local/sbin and its call smartctl_type. But I dont think its this one.

 

Doesn't S3 Sleep check disks? I think there was a issue with that, but I believe there was fix/update yesterday.

 

Only way to know for sure is that you need to have a wrapper around the commands or trace when the command is used but I am not sure how to do trace part.

 

doron's SAS Helper installs a smartctl wrapper where you can a line to the script to enable debug messages to the syslog.

 

 

Link to post
18 hours ago, SimonF said:

What version are you running?

 

17 hours ago, SimonF said:

 

Do you have file activity plugin installed? This may provide an overview of any files are being open at the same times.

 

I know you are not using SAS drives but if you install doron's plugin it has a smartctl wrapper that you can set to debug and it will post an entry in the log if you add debug=true to the script.

 

Other things that where causing spin ups before 6.9.1 where processes that used smartctl i.e. telegraf checking disk temps etc. I know you said you don't run any of these monitoring tools and the use of smartctl shouldn't be the cause now.

 

Other plugins may be using hdparm which could cause spin ups. If you want to post diags I can have look to see if there is anything obvious. 

All my info is in my sig if you need it, version 6.9.1.

 

I was running the file activity plugin, but I actually turned it off to test if this was causing the issue.  Not surprisingly it's not the file activity plugin.  With file activity running, it does not show any files being accessed either.  The only thing is that the log says SMART is checked and the drive is spun down.

 

craigr

Link to post

Well hold on.  I had rebooted earlier today and the drives had only had the SMART read once since then.  I just restarted File Activity and each drive, one by one, is getting spun up and SMART read.  This will require further investigation so I'll play with it.

 

craigr

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.