hi,

is my assumption right, that somethings spin up/down my disks every 30minutes?

today morning i woke up and heard that the disks are spinning, and they should not since i havent used the server in any way.

here are some log entries:

Dec 26 04:01:45 unRAID kernel: mdcmd (152): spindown 0
Dec 26 04:01:45 unRAID kernel: mdcmd (153): spindown 1
Dec 26 04:31:27 unRAID kernel: mdcmd (154): spindown 0
Dec 26 04:35:29 unRAID kernel: mdcmd (155): spindown 1
Dec 26 05:05:41 unRAID kernel: mdcmd (156): spindown 0
Dec 26 05:05:42 unRAID kernel: mdcmd (157): spindown 1
Dec 26 05:30:51 unRAID kernel: mdcmd (158): spindown 0
Dec 26 05:30:51 unRAID kernel: mdcmd (159): spindown 1
Dec 26 06:01:34 unRAID kernel: mdcmd (160): spindown 0
Dec 26 06:01:35 unRAID kernel: mdcmd (161): spindown 1
Dec 26 06:31:16 unRAID kernel: mdcmd (162): spindown 0
Dec 26 06:31:17 unRAID kernel: mdcmd (163): spindown 1
Dec 26 07:01:29 unRAID kernel: mdcmd (164): spindown 0
Dec 26 07:01:30 unRAID kernel: mdcmd (165): spindown 1
Dec 26 07:31:41 unRAID kernel: mdcmd (166): spindown 0
Dec 26 07:31:42 unRAID kernel: mdcmd (167): spindown 1
Dec 26 08:01:24 unRAID kernel: mdcmd (168): spindown 0
Dec 26 08:01:24 unRAID kernel: mdcmd (169): spindown 1
Dec 26 08:31:36 unRAID kernel: mdcmd (170): spindown 0
Dec 26 08:31:36 unRAID kernel: mdcmd (171): spindown 1
Dec 26 09:01:18 unRAID kernel: mdcmd (172): spindown 0
Dec 26 09:01:19 unRAID kernel: mdcmd (173): spindown 1
Dec 26 09:31:31 unRAID kernel: mdcmd (174): spindown 0
Dec 26 09:31:31 unRAID kernel: mdcmd (175): spindown 1

it seems like every 30minutes somethings turning my disks on?

here are my diagnostics:

unraid-diagnostics-20181226-1135.zip

 

hope you can help me.

greetings

Million possible reasons, including

• One of your VMs exists on array (domains share exists on the cache and on disk1 -> mover can't do anything while the VMs are running)
• One or more of your docker applications are scanning / indexing your media

Installing Active Streams or Open Files might help you to determine what's going on

36 minutes ago, Squid said:

One of your VMs exists on array (domains share exists on the cache and on disk1 -> mover can't do anything while the VMs are running)

According to his diagnostics, system and domains both exist on cache and disk1.

 

Go to Settings - Docker and disable. If using VMs, do same in Settings - VM Manager.

Go to Main - Array Operations and Move Now. When done

Reenable docker (and VMs).

13 minutes ago, trurl said:

According to his diagnostics, system and domains both exist on cache and disk1.

 

Go to Settings - Docker and disable. If using VMs, do same in Settings - VM Manager.

Go to Main - Array Operations and Move Now. When done

Reenable docker (and VMs).

Yeah, that could be a reason.

yesterday i recreated my docker image.

i will give it a try!

 

EDIT: i guess that was the problem. but why is the newly created docker image on disk1 and not the cache? it is set to "prefer".

oh, i think i know whats the problem.

a night or two ago i was getting the message that my cache is 99% full, and after a minute or so it was solved by itself.

can anybody see this in my diagnostics? i was kinda curious but as i woke up everything was normal. it was about 3.55am.

 

EDIT: i probably found it by myself.

i assigned windows10 a additional 500gb vdisk and its trying to move it to my ssd cache, which is also 500gb.

so he will try to move it, it will fail, and it stays on disk1.

 

 

Edited December 26, 20187 yr by Danny08