Updated to 6.9.1 as well and everything runs smoothly.

As I can see the issue is resolved for everyone, so will be tagging this topic as solved.

Now on 6.9.2.

 

Issue not solved. Still not spinning down due to read SMART ..

May 19 13:23:56 Stacker emhttpd: read SMART /dev/sdh
May 19 13:24:02 Stacker emhttpd: read SMART /dev/sdi
May 19 13:24:11 Stacker emhttpd: read SMART /dev/sdl
May 19 13:24:17 Stacker emhttpd: read SMART /dev/sdm
May 19 13:48:48 Stacker emhttpd: spinning down /dev/sdf
May 19 13:48:53 Stacker emhttpd: spinning down /dev/sdm
May 19 13:54:27 Stacker emhttpd: spinning down /dev/sdl
May 19 13:54:42 Stacker emhttpd: spinning down /dev/sdg
May 19 13:56:36 Stacker emhttpd: spinning down /dev/sdi
May 19 13:57:18 Stacker emhttpd: spinning down /dev/sdk
May 19 14:00:15 Stacker emhttpd: read SMART /dev/sdg
May 19 14:00:15 Stacker emhttpd: read SMART /dev/sdl
May 19 14:00:20 Stacker emhttpd: read SMART /dev/sdb
May 19 14:00:36 Stacker emhttpd: read SMART /dev/sdf
May 19 14:02:49 Stacker emhttpd: spinning down /dev/sdh
May 19 14:08:13 Stacker emhttpd: read SMART /dev/sdh
May 19 14:08:26 Stacker emhttpd: read SMART /dev/sdm
May 19 14:08:26 Stacker emhttpd: read SMART /dev/sdk
May 19 14:08:34 Stacker emhttpd: read SMART /dev/sdi
May 19 14:17:13 Stacker emhttpd: spinning down /dev/sdb
May 19 14:26:34 Stacker emhttpd: spinning down /dev/sdg
May 19 14:31:02 Stacker emhttpd: read SMART /dev/sdg

Not solved for me either on 6.9.2

 

May 19 01:08:08 Tower emhttpd: spinning down /dev/sdk
May 19 01:08:08 Tower emhttpd: spinning down /dev/sdl
May 19 01:11:00 Tower emhttpd: spinning down /dev/sdh
May 19 01:13:06 Tower emhttpd: read SMART /dev/sdj
May 19 01:13:06 Tower emhttpd: read SMART /dev/sdl
May 19 01:13:07 Tower emhttpd: read SMART /dev/sdk
May 19 01:13:17 Tower emhttpd: read SMART /dev/sdh
May 19 01:28:37 Tower emhttpd: spinning down /dev/sdh
May 19 01:29:47 Tower emhttpd: spinning down /dev/sdj
May 19 01:30:17 Tower emhttpd: spinning down /dev/sdk
May 19 01:41:51 Tower emhttpd: spinning down /dev/sdl
May 19 02:01:18 Tower emhttpd: read SMART /dev/sdl
May 19 02:01:28 Tower emhttpd: read SMART /dev/sdh
May 19 02:01:38 Tower emhttpd: read SMART /dev/sdj
May 19 02:20:57 Tower emhttpd: spinning down /dev/sdj
May 19 02:20:57 Tower emhttpd: spinning down /dev/sdh
May 19 02:20:57 Tower emhttpd: spinning down /dev/sdl
May 19 02:27:40 Tower emhttpd: read SMART /dev/sdl
May 19 02:42:42 Tower emhttpd: spinning down /dev/sdl
May 19 04:10:57 Tower emhttpd: read SMART /dev/sdl
May 19 04:11:07 Tower emhttpd: read SMART /dev/sdh
May 19 04:25:59 Tower emhttpd: spinning down /dev/sdl
May 19 04:26:09 Tower emhttpd: spinning down /dev/sdh
May 19 04:36:15 Tower emhttpd: read SMART /dev/sdl
May 19 04:36:33 Tower emhttpd: read SMART /dev/sdh
May 19 04:51:25 Tower emhttpd: spinning down /dev/sdl
May 19 04:52:23 Tower emhttpd: read SMART /dev/sdj
May 19 05:01:32 Tower emhttpd: spinning down /dev/sdh
May 19 05:07:25 Tower emhttpd: spinning down /dev/sdj
May 19 06:14:14 Tower emhttpd: read SMART /dev/sdl
May 19 06:52:09 Tower emhttpd: spinning down /dev/sdl

 

This is with Telegraf/Grafana stopped.  I am testing with some dockers down at given times to see if I can find a culprit, but so far no luck.

Anyone found a solution to this issue? My disk's also not going into spin down mode. I also think it worked with previous releases. 

Same issue here on a fresh 6.9.2 install with only 2 drives and 1 share:

 

Jul 11 19:09:02 Hannibal emhttpd: spinning down /dev/sdb
Jul 11 19:09:04 Hannibal emhttpd: spinning down /dev/sdc
Jul 11 19:12:23 Hannibal emhttpd: read SMART /dev/sdb
Jul 11 19:13:13 Hannibal emhttpd: read SMART /dev/sdc

6.9.2

turned off all VM and docker.

 

Jul 11 23:16:39 M17 emhttpd: spinning down /dev/sde
Jul 11 23:17:28 M17 emhttpd: read SMART /dev/sde
Jul 11 23:32:04 M17 emhttpd: spinning down /dev/sde

 

same problem here. the disk is format in GPT instead of MBR, this is the only difference compare to other sleeping disks

Unraid 6.9.2

 

Hey, i also have the problem that my disks are not spinning down. Even if i spin them down manual, they will spin up 5 sek later.
Tryed turning off all vm and docker. Also looked with the Plugin File Activity but there is nothing reading or writing.

In the logs of the drive i see the SMART scan right after the spindown.
Jul 16 14:26:27  emhttpd: read SMART /dev/sdc
Jul 18 23:39:28  emhttpd: spinning down /dev/sdc
Jul 18 23:39:31  emhttpd: read SMART /dev/sdc
Jul 18 23:39:51  emhttpd: spinning down /dev/sdc
Jul 18 23:39:54  emhttpd: read SMART /dev/sdc
Jul 18 23:43:37  emhttpd: spinning down /dev/sdc
Jul 18 23:43:45  emhttpd: read SMART /dev/sdc
Jul 18 23:50:11  emhttpd: spinning down /dev/sdc
Jul 18 23:50:28  emhttpd: read SMART /dev/sdc

This is something I noticed recently as well... my disks never spin down unless I initiate it manually. Open files shows no shares accessed, only cache... hddtemp disabled from grafana-unraid-stack docker.

 

I checked Disk Settings and Default spin down delay: is set to Never.

I have not touched this setting at all! does never mean, never spin disk down or 0 mins delay to spin down.

Could that be something enabled by default since 6.9.2?

Never means no automatic spin downs.   

16 hours ago, itimpi said:

Never means no automatic spin downs.   

Thanks, no wonder my disks are not automatically spinning down.

Is Never the default value? I just changed it to 3 hours and will test and report back overnight.

What does everyone else set this as? 1 hr, 4, hrs...

42 minutes ago, Juzzotec said:

Thanks, no wonder my disks are not automatically spinning down.

Is Never the default value? I just changed it to 3 hours and will test and report back overnight.

What does everyone else set this as? 1 hr, 4, hrs...

 

Not sure there is a perfect answer    Quite a few disk controllers suspend any other I/O while spinning up a drive which can cause temporary freezing in video streaming so you have to balance this against power savings of more frequent spindowns. 

  

Running both 6.9.2 and 6.10.0-rc1 and having the same issue, disabled all Docker containers, disabled Auto Fan and still having this issue. My disks are SAS if it's relevant.

 

They do spin down at the 15 min mark (as I have them configured) and then, few moments later, spin up again. I was playing with suggestion on this thread and noticed that after removing Auto Fan, seemed like it worked, my disks stayed spin down for a good minute or two and then they started again, in the logs, I could see:

 

Aug 29 05:48:49 Tower emhttpd: spinning down /dev/sde
Aug 29 05:48:49 Tower SAS Assist v0.86: Spinning down device /dev/sde
Aug 29 05:50:30 Tower kernel: sd 1:0:3:0: [sde] tag#786 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Aug 29 05:50:32 Tower emhttpd: read SMART /dev/sde

 

the time for the `emhttpd: read SMART /dev/sde` corresponds exactly to the time my disks spun up again, so it is possible that the UI is actually causing this issue?

3 hours ago, yorch said:

the time for the `emhttpd: read SMART /dev/sde` corresponds exactly to the time my disks spun up again, so it is possible that the UI is actually causing this issue?

this is due to ui detecting disk is spun up.

 

what model disks do you have?

6 hours ago, SimonF said:

this is due to ui detecting disk is spun up.

 

what model disks do you have?

Thanks for your reply.. This is what I have:

 

ST33000650SS

HUS726060AL5210

DKS2D-H3R0SS

 

Is there a log somewhere that tells when disks spun down and up?

7 hours ago, yorch said:

 

Thanks for your reply.. This is what I have:

 

ST33000650SS

HUS726060AL5210

DKS2D-H3R0SS

 

Is there a log somewhere that tells when disks spun down and up?

Yes the syslog, but it may be the spindown is not working correctly or the checking of its status and hence why the system is doing the read SMART to get drive temps.

 

It looks like its trying to send an ATA command to the SAS drive, suggest you post output of the commands below on the SAS helper plugin page.

 

Does it happen with all drives?

 

Unraid uses the following to spin down and the second command is the status, could you run for each drive?

 

/usr/local/sbin/sdspin /dev/sdx down

echo $?

/usr/local/sbin/sdspin /dev/sdx

echo $?

 

sdparm -ip di_target /dev/sdx

On 8/30/2021 at 9:21 AM, SimonF said:

Unraid uses the following to spin down and the second command is the status, could you run for each drive?

 

/usr/local/sbin/sdspin /dev/sdx down

echo $?

/usr/local/sbin/sdspin /dev/sdx

echo $?

 

sdparm -ip di_target /dev/sdx

 

What exactly do you mean by this? You have posted 5 commandlines. Rather confusing. The sdparm command does not state anything about drives being spun down or not, or at least I don't see it..

10 hours ago, fluisterben said:

/usr/local/sbin/sdspin /dev/sdx down

echo $?

/usr/local/sbin/sdspin /dev/sdx

echo $?

these will run the commands and show status to validate if they spin down and status.

 

10 hours ago, fluisterben said:

sdparm -ip di_target /dev/sdx

This is used to identify SAS drives

This is still an issue. My disks keep spinning up almost immediately after spinning them down, which, barely any even do when asked.

This used to not be the case, with the exact same hardware and software config. Something is waking them up, and it costs us a ridiculous amount of power. In fact, the reason I noticed this issue, is because we wanted to know what changed in our power consumption. Turned out it was the unraid server.

10 hours ago, fluisterben said:

This is still an issue. My disks keep spinning up almost immediately after spinning them down, which, barely any even do when asked.

This used to not be the case, with the exact same hardware and software config. Something is waking them up, and it costs us a ridiculous amount of power. In fact, the reason I noticed this issue, is because we wanted to know what changed in our power consumption. Turned out it was the unraid server.

Can you post diags?

Rather than the SMART Read either spinning the disks up or preventing them from spinning down, I believe it's Plex do it instead and the SMART Reads are just happening because the disks are already spinning.

Edited October 15, 20214 yr by BoutTime

2 hours later and no spin-ups and no SMART Reads.....

 

Hi there, i had the same issue and I fixed it by moving docker's virtual disk from array to cache. The app reeded always on the array so the disk was always spin up.

Hello, having the same issue, my disks are not spinning down even if i spin them down manualy, they will spin up 5 seconds later.
Tryed turning off all dockers, Using Unraid 6.9.2,

 

Nov 17 20:12:24 NAS emhttpd: spinning down /dev/sde

Nov 17 20:12:24 NAS emhttpd: spinning down /dev/sdb

Nov 17 20:12:24 NAS emhttpd: spinning down /dev/sdf

Nov 17 20:12:24 NAS emhttpd: spinning down /dev/sdc

Nov 17 20:18:31 NAS emhttpd: read SMART /dev/sdb

Nov 17 20:18:31 NAS emhttpd: read SMART /dev/sdf

Nov 17 20:18:31 NAS emhttpd: read SMART /dev/sdc

Nov 17 20:19:00 NAS emhttpd: read SMART /dev/sde

1 minute ago, Pedro Ferreira said:

Tryed turning off all docker

Did you actually disable docker in Settings? 

 

Attach Diagnostics to your NEXT post in this thread. 

@trurl thanks for taking the time to reply, here is the Diagnostics, please keep in mind that i'm kind of a noob with computers.

no i didn´t knew that was possible to disable dockers in the Settings, i usualy go to the docker tab and stop them one by one, i only have 3 instaled.

 

nas-diagnostics-20211118-1933.zip

Edited November 26, 20214 yr by Pedro Ferreira