May 31, 20215 yr Hi My unraid seems to be idle, I see in the syslog spin down command, but then I see read SMART entries and array awakes. May 31 21:15:52 Vault emhttpd: spinning down /dev/sde May 31 21:15:52 Vault emhttpd: spinning down /dev/sdf May 31 21:16:24 Vault emhttpd: spinning down /dev/sdg May 31 21:16:33 Vault emhttpd: spinning down /dev/sdi May 31 21:16:43 Vault emhttpd: spinning down /dev/sdj May 31 21:18:49 Vault emhttpd: read SMART /dev/sdb May 31 21:18:49 Vault emhttpd: read SMART /dev/sdc May 31 21:19:22 Vault emhttpd: read SMART /dev/sdd May 31 21:19:22 Vault emhttpd: read SMART /dev/sde May 31 21:19:22 Vault emhttpd: read SMART /dev/sdf May 31 21:19:30 Vault emhttpd: read SMART /dev/sdg May 31 21:19:41 Vault emhttpd: read SMART /dev/sdi May 31 21:19:51 Vault emhttpd: read SMART /dev/sdj May 31 21:26:30 Vault emhttpd: spinning down /dev/sdh May 31 21:29:39 Vault emhttpd: read SMART
May 31, 20215 yr dynamix.cache.dirs.plg - 2020.08.03 There's something in the support thread about not having it scan user shares (only disk shares) to prevent disk spinups incurring.
June 1, 20215 yr Author But this is something I discovered recently, could it be related to recent upgrade of unraid? I will remove dirs cache to see if it helps. Health of disks is more important
June 1, 20215 yr Author 9 hours ago, Squid said: dynamix.cache.dirs.plg - 2020.08.03 There's something in the support thread about not having it scan user shares (only disk shares) to prevent disk spinups incurring. Did not help: Jun 1 08:54:50 Vault cache_dirs: Stopping cache_dirs process 10494 Jun 1 08:54:51 Vault cache_dirs: cache_dirs service rc.cachedirs: Stopped Jun 1 08:59:32 Vault emhttpd: spinning down /dev/sdf Jun 1 08:59:43 Vault emhttpd: spinning down /dev/sdh Jun 1 08:59:54 Vault emhttpd: spinning down /dev/sdj Jun 1 09:02:41 Vault emhttpd: read SMART /dev/sdf Jun 1 09:02:52 Vault emhttpd: read SMART /dev/sdh Jun 1 09:03:02 Vault emhttpd: read SMART /dev/sdj Jun 1 09:21:31 Vault emhttpd: spinning down /dev/sdb Jun 1 09:21:31 Vault emhttpd: spinning down /dev/sdc Jun 1 09:21:53 Vault emhttpd: spinning down /dev/sdd Jun 1 09:21:53 Vault emhttpd: spinning down /dev/sde Jun 1 09:22:14 Vault emhttpd: spinning down /dev/sdg Jun 1 09:22:22 Vault emhttpd: spinning down /dev/sdi Jun 1 09:24:51 Vault emhttpd: read SMART /dev/sdb Jun 1 09:24:51 Vault emhttpd: read SMART /dev/sdc Jun 1 09:25:12 Vault emhttpd: read SMART /dev/sdd Jun 1 09:25:12 Vault emhttpd: read SMART /dev/sde Jun 1 09:25:21 Vault emhttpd: read SMART /dev/sdg Jun 1 09:25:31 Vault emhttpd: read SMART /dev/sdi Jun 1 09:32:32 Vault emhttpd: spinning down /dev/sdf Jun 1 09:32:43 Vault emhttpd: spinning down /dev/sdh Jun 1 09:32:54 Vault emhttpd: spinning down /dev/sdj Jun 1 09:35:42 Vault emhttpd: read SMART /dev/sdf Jun 1 09:35:52 Vault emhttpd: read SMART /dev/sdh Jun 1 09:36:03 Vault emhttpd: read SMART /dev/sdj For some reason, file activity does not work for me. When I click on 'start', the service stays in 'Stopped' status
June 1, 20215 yr Author I don't think this is folder caching. -- I disabled it, did not help - re-enabled, and enabled logs -- don't see the cache task running but I do see this again Jun 1 14:32:52 Vault emhttpd: read SMART /dev/sdb Jun 1 14:32:52 Vault emhttpd: read SMART /dev/sdc Jun 1 14:33:24 Vault emhttpd: read SMART /dev/sdd Jun 1 14:33:24 Vault emhttpd: read SMART /dev/sde Jun 1 14:33:24 Vault emhttpd: read SMART /dev/sdf Jun 1 14:33:35 Vault emhttpd: read SMART /dev/sdh Jun 1 14:33:45 Vault emhttpd: read SMART /dev/sdj disks are spinning down.. and then immediately spinning up. what is emhttpd? the GUI? Why does it access SMART? Does it spin up the disk?
June 1, 20215 yr Community Expert See if downgrading to v6.9.1 helps, there are some known issues with v6.9.2 and spin down.
June 1, 20215 yr Author 3 minutes ago, JorgeB said: See if downgrading to v6.9.1 helps, there are some known issues with v6.9.2 and spin down. this makes more sense to me, but I will wait then for the next version. Should I open a bug, or there is already an open one?
Archived
This topic is now archived and is closed to further replies.