I have the following issue:

 

All my disks are set to spin down after 15 minutes, which is working for all but my third array disk. This also keeps my Parity disk spun up, so I am looking for a way to change this.

 

The disk in Question is a small 3Tb WD Drive.

 

I have double checked (using lsof /mnt/disk/*), Open Files Plugin and Active Streams and can thus verify:

-No process is accessing disk3

-No network share on disk3 (or any smdb share in general) is being accessed

 

neither /mnt/user nor /mnt/disk3 is in use.

 

When I manually spin down my array all disks go grey, but after merely 10ish seconds the third disk (and parity) spin up again.

 

I have moved my "disk3" content to the cache drive and set the according shares to cache only, also unchecking disk3 as the linked disk, which is why NOTHING should actually access the disk in question.

 

Any idea what I can do to overcome this behavior?

syslog.txt

I am now officialy a sad potato  :'(

I am now officialy a sad potato  :'(

 

What is that WD drive plugged into?  (MB or a SATA card)  You might try using a MB socket for it.  (IF you are using a SATA cards with that drive on it, you might swap with another drive in the array and see if the problem follows.)

 

Also check the temperatures and see if it really looks like the disk is spinning.  If you can possibly get to the drive, try to feel (or listen) to detect if it is actually rotating. 

 

Sometimes, it seems like there is some 'house cleaning' that occurs when the array is first started.  I assume that you have waited to long enough so that this event is not what you are seeing. 

Thanks for the rich suggestions 

 

Ill try this once at home and will report back

One more thing.  There are two places where you can set the spin down delay.  The first one is for all of the disks and that can be found (as you probably have discovered) on the 'Settings' >> 'Disk Setting' page.  The second one is a place to set the spin down time for each disk.  That is found from the 'Main' page. You click on the disk name in the 'Device' column and look on the 'Settings' tab on that page.  (I don't know which setting takes precedence!  'Default' should be the setting unless you have another reason for some other setting.)

double-checked that one through openvpn.. My disks are all default. I have set my delay to one hour now (was less before) and have set cache-dirs to only cache my plex library.. maybe there were to many folders for it to cache properly.

I have the following issue:

 

All my disks are set to spin down after 15 minutes, which is working for all but my third array disk. This also keeps my Parity disk spun up, so I am looking for a way to change this.

 

The disk in Question is a small 3Tb WD Drive.

 

I have double checked (using lsof /mnt/disk/*), Open Files Plugin and Active Streams and can thus verify:

-No process is accessing disk3

-No network share on disk3 (or any smdb share in general) is being accessed

 

neither /mnt/user nor /mnt/disk3 is in use.

 

When I manually spin down my array all disks go grey, but after merely 10ish seconds the third disk (and parity) spin up again.

 

I have moved my "disk3" content to the cache drive and set the according shares to cache only, also unchecking disk3 as the linked disk, which is why NOTHING should actually access the disk in question.

 

Any idea what I can do to overcome this behavior?

 

I want to believe you    that absolutely nothing is writing to Disk 3, but you said the Parity disk is also spinning up!  The *only* thing that makes the parity drive spin up on its own is a write to a data disk.  And if Disk 3 is the only disk that's spinning then *something* is writing to Disk 3!  The Parity drive does not care about the spin state of any drive, only whether a write has been performed.

 

That *something* must be very sneaky!

I know that, but my ninja-like

lsof /mnt/disk3*

-spamming skills have yet to find the process in question...

 

Seriously though, neither the Open Files Plugin, nor my repeated shell promts have yieled any result..

 

But you are right. Parity would sleep on Read operations..

But you are right. Parity would sleep on Read operations..

Unless its in the same spin up group as another drive that needed to be spun up to do the read.

 

Then it would spin up with the other disk(s) but sleep under its own settings.

Unless its in the same spin up group as another drive that needed to be spun up to do the read.

 

Then it would spin up with the other disk(s) but sleep under its own settings.

 

That requires spin-up groups to be enabled, which is disabled by default.

Unless its in the same spin up group as another drive that needed to be spun up to do the read.

 

Then it would spin up with the other disk(s) but sleep under its own settings.

 

That requires spin-up groups to be enabled, which is disabled by default.

Ah I always thought it was the reverse.  Spinup groups disabled utilized whatever spinup groups unRaid detected, and by enabling it allowed you to create your own groups.  Guess I should read the help text.