February 1, 201511 yr I have an assortment of drives on this server. My 2 TB data WDC WD20EARS never spin down. I will probably just replace these 2 2TB drives with a 4 TB HGST the next time one goes on sale. Anything anyone would like me to provide while these are still in my machine?
February 1, 201511 yr Are you sure the drives are set to spin down? This can be changed individually ... if these drives have somehow inadvertently been changed that could explain why they're not spinning down. Also, do you have any add-ons that are using these drives for their data store? That could also explain this. Finally, do you have Cache Dirs installed -- if so, do these two drives happen to have a very large # of files on them that could result in Cache Dirs doing a continual refresh? [if that happens to be the case, then modify the parameters for Cache Dirs so it's not caching the troublesome folders]
February 2, 201511 yr Author 1 - no autostart, 1 hour spindown delay, each disk set to use default 2 - neither would spin down with no data on them, now 1 of the 2 has data (but is going through a new config/parity rebuild) 3 - one of the needed add-ons! at this point, no. This will be added after each share has a fully robocopy from my main server. the only add-ons at this point are unmenu (for ups/clean powerdown, and screen).
February 2, 201511 yr Interesting that they don't spin down. You can't try this now (during the parity sync) ... but when that's done, see if they spin down okay when you click the button to spin down the drives.
February 2, 201511 yr Community Expert I have seen this but it only seems to affect the last data drive. Before I added a 5th data drive, my 4th drive would not spin down on its own, but I could spin it down by clicking the button and it would stay spun down. Now that I have added a 5th data drive, this behaviour has shifted to it. My 4th and 5th drive are 3TB, and parity, 1, 2, and 3 are 4TB. During my monthly parity check, drive 4 spun down after the parity check had got beyond 3TB as it should, but drive 5 didn't. This drive is a WD 3TB Red just like drive 4 and all of the others are also WD Red drives, so it doesn't seem to have anything to do with the drive model, just the position in the array. Also, drive 5 is currently empty and not included in any share, so there is definitely nothing accessing it. Anyway, not a big deal, and I think jonp mentioned somewhere that they may have a fix for this forthcoming. Just thought I would share my experience. This behaviour or something like it has spawned a number of threads.
February 2, 201511 yr Sometimes you need to shutdown (I usually powerdown) a server after adding a drive so it spins down properly.
February 2, 201511 yr did you upgrade the dynamix to 2015.01.21? There is a known issue. http://lime-technology.com/forum/index.php?topic=36527.msg349680#msg349680
February 2, 201511 yr Community Expert did you upgrade the dynamix to 2015.01.21? There is a known issue. http://lime-technology.com/forum/index.php?topic=36527.msg349680#msg349680 Yes
February 2, 201511 yr Author 1 - manual spin down indicates that they do spin down but after a few moments they start spinning again. This is when they are in the array (i know out of array does not autospin down sadly). 2 - plugin dynamix updated and system restarted - issue appears to be gone. - thanks
Archived
This topic is now archived and is closed to further replies.