December 5, 201411 yr solved as of beta 14b My drives don't seem to be staying spun down. I do see unRaid log of them spinning down but something is spinning them back up. I can force them down and they do spin down, but after an amount of time they come back up. I've not had this problem in the past. Only thing I've changed since switching to 12 is adding Dynamix System Temperature and install Cach_dir Dynamix Plugin vs just running it from my go script. For instance, here is my log up until I updated my APC plugin just a few minutes ago. Dec 5 05:32:02 NAS1 logger: mover finished Dec 5 06:00:38 NAS1 kernel: mdcmd (93): spindown 2 Dec 5 06:02:19 NAS1 kernel: mdcmd (94): spindown 0 Dec 5 06:02:20 NAS1 kernel: mdcmd (95): spindown 3 Dec 5 06:03:51 NAS1 emhttp: shcmd (22813): /usr/sbin/hdparm -y /dev/sdh &> /dev/null Dec 5 08:58:08 NAS1 kernel: mdcmd (96): spindown 4 This would lead me to believe they were spun down, however they are not, they were all spinning. On SNAP drive 1 KVM windows VM 1 Plex Docker Plugins APC UPS Dynamix Cache Directories SNAP Web Virtual Manager Libvirt Support Powerdown Package Dynamix System Temperature Dynamix webgui I just spun the drives down manually at 2:06pm and now at 2:16 all but drive 4 are spinning. I'm the only one here and wasn't accessing any files. Dec 5 14:06:07 NAS1 kernel: mdcmd (97): spindown 0 Dec 5 14:06:08 NAS1 kernel: mdcmd (98): spindown 1 Dec 5 14:06:08 NAS1 kernel: mdcmd (99): spindown 2 Dec 5 14:06:09 NAS1 kernel: mdcmd (100): spindown 3 Dec 5 14:06:09 NAS1 kernel: mdcmd (101): spindown 4 Dec 5 14:06:10 NAS1 emhttp: shcmd (25688): /usr/sbin/hdparm -y /dev/sdh &> /dev/null Only drive I would expect to be spinning is drive one where I have some torrents stored. Is there a way to track down what might be spinning these drives back up?
December 5, 201411 yr My drives don't seem to be staying spun down. I do see unRaid log of them spinning down but something is spinning them back up. I can force them down and they do spin down, but after an amount of time they come back up. I've not had this problem in the past. Only thing I've changed since switching to 12 is adding Dynamix System Temperature and install Cach_dir Dynamix Plugin vs just running it from my go script. For instance, here is my log up until I updated my APC plugin just a few minutes ago. Dec 5 05:32:02 NAS1 logger: mover finished Dec 5 06:00:38 NAS1 kernel: mdcmd (93): spindown 2 Dec 5 06:02:19 NAS1 kernel: mdcmd (94): spindown 0 Dec 5 06:02:20 NAS1 kernel: mdcmd (95): spindown 3 Dec 5 06:03:51 NAS1 emhttp: shcmd (22813): /usr/sbin/hdparm -y /dev/sdh &> /dev/null Dec 5 08:58:08 NAS1 kernel: mdcmd (96): spindown 4 This would lead me to believe they were spun down, however they are not, they were all spinning. On SNAP drive 1 KVM windows VM 1 Plex Docker Plugins APC UPS Dynamix Cache Directories SNAP Web Virtual Manager Libvirt Support Powerdown Package Dynamix System Temperature Dynamix webgui I just spun the drives down manually at 2:06pm and now at 2:16 all but drive 4 are spinning. I'm the only one here and wasn't accessing any files. Dec 5 14:06:07 NAS1 kernel: mdcmd (97): spindown 0 Dec 5 14:06:08 NAS1 kernel: mdcmd (98): spindown 1 Dec 5 14:06:08 NAS1 kernel: mdcmd (99): spindown 2 Dec 5 14:06:09 NAS1 kernel: mdcmd (100): spindown 3 Dec 5 14:06:09 NAS1 kernel: mdcmd (101): spindown 4 Dec 5 14:06:10 NAS1 emhttp: shcmd (25688): /usr/sbin/hdparm -y /dev/sdh &> /dev/null Only drive I would expect to be spinning is drive one where I have some torrents stored. Is there a way to track down what might be spinning these drives back up? This is happening for me too. Usually only a handful of drives but always the same ones. I have no plugins or anything else installed. Weird.
December 5, 201411 yr I am having the same problem, but it is only with 1 disk. Manual spin down works fine. Automatic spin down doesn't seem to spin down my disk 12. http://lime-technology.com/forum/index.php?topic=36596.0 Gary
December 5, 201411 yr What are your plex settings? How often do you have it set to access your library?
December 5, 201411 yr Drives not staying spun down here. I have updated the "Spinup group(s):" setting per drive so each is unique (had gotten jumbled over time with drive slot switching, etc). Currently they are all included in "Movies1" share, but only disk1 has any space on it. Plex is on cache drive.
December 5, 201411 yr Author What are your plex settings? How often do you have it set to access your library? If you're asking me, Plex is on an SSD (SNAP) drive outside the array.
December 5, 201411 yr I'm having issues where drives are spinning back up too. Nothing is accessing them. Sometimes I'll write data to cache and parity spins up. I haven't noticed any patterns yet. I'll try and see if I notice anything and report back.
December 5, 201411 yr Same here. I'll manually spin down all drives (besides cache) and then go to the cache drive to delete a file and it will pause for a second and spin up a drive before it will delete the file. It will do other random things too, I haven't seen a pattern.
December 5, 201411 yr Author Are you using cache_dirs? I am (as shown in my OP) but even disabled they spun back up. I thought that might be the issue, but apparently not.
December 5, 201411 yr Same here. One of my two disks in the array keeps spinning up. lsof /mnt/disk2 shows nothing accessing it yet it still stays spun up
December 5, 201411 yr Are you using cache_dirs? I am yes. I'm going to disable it when I get home from work and see what happens.
December 5, 201411 yr That's what I was going to suggest. I ran into an issue when booted in Xen and I assigned too little memory. Cache_dirs was constantly cycling through the drives. I ended up assigning memory to 4096M and it stopped.
December 5, 201411 yr That's what I was going to suggest. I ran into an issue when booted in Xen and I assigned too little memory. Cache_dirs was constantly cycling through the drives. I ended up assigning memory to 4096M and it stopped. This could be a big cause, I would suggest disabling cache_dirs to determine if this is the cause, Other then that, Maybe if people could post model numbers of the drives which continue to spin up. A test to determine if there is a drive interface issue would be to run hdparm -C /dev/sd? where ?=drive id. This is used by dynamix to determine spin status (as far as I remember from Tom and a scan of dynamix text). emhttp uses /usr/sbin/smartctl -n standby -A /dev/sd? So drive behavior may be different with hdparm vs smartctl (I'm taking a wild guessing stab at this).
December 5, 201411 yr My model is: WDC WD20EARS-00MVWB0 I have 2 others in my array and they spin down fine. No cache dirs either. Gary
December 5, 201411 yr Author This could be a big cause, I would suggest disabling cache_dirs to determine if this is the cause, Other then that, Maybe if people could post model numbers of the drives which continue to spin up. A test to determine if there is a drive interface issue would be to run hdparm -C /dev/sd? where ?=drive id. This is used by dynamix to determine spin status (as far as I remember from Tom and a scan of dynamix text). emhttp uses /usr/sbin/smartctl -n standby -A /dev/sd? So drive behavior may be different with hdparm vs smartctl (I'm taking a wild guessing stab at this). root@NAS1:/var/log# hdparm -C /dev/sdb /dev/sdb: drive state is: active/idle root@NAS1:/var/log# /usr/sbin/smartctl -n standby -A /dev/sdb smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.17.4-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 184 180 021 Pre-fail Always - 5758 4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3181 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 046 046 000 Old_age Always - 39626 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 69 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 26 193 Load_Cycle_Count 0x0032 125 125 000 Old_age Always - 227285 194 Temperature_Celsius 0x0022 121 115 000 Old_age Always - 29 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
December 5, 201411 yr What's needed are the models in question. The output of hdparm -C /dev/sd? and only the start of /usr/sbin/smartctl -n standby -A /dev/sd? Here's an example. I like to use /dev/disk/by-id because the drive model serial is there. root@unRAIDb:/# ls -l /dev/disk/by-id/ | egrep -v 'part|usb' total 0 lrwxrwxrwx 1 root root 9 Dec 4 01:48 ata-HGST_HDN724040ALE640_PK2334PCHX2DLB -> ../../sdc lrwxrwxrwx 1 root root 9 Dec 4 01:48 ata-HGST_HDN726060ALE610_NAG1D7TP -> ../../sdd lrwxrwxrwx 1 root root 9 Dec 3 22:54 ata-HGST_HDN726060ALE610_NAG1DEKP -> ../../sdb root@unRAIDb:# hdparm -C /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB: drive state is: active/idle root@unRAIDb:# hdparm -y /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB: issuing standby command root@unRAIDb:# hdparm -C /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB: drive state is: standby root@unRAIDb:# smartctl -n standby -A /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.17.4-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Device is in STANDBY mode, exit(2) root@unRAIDb:/usr/local/emhttp# hdparm -C /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB: drive state is: standby If you do the smartctl and get a full attribute listing with the ID# header, then don't post all that data at this time, Just post that you received a full attribute listing.
December 5, 201411 yr What are your plex settings? How often do you have it set to access your library? If you're asking me, Plex is on an SSD (SNAP) drive outside the array. Not where you have plex installed, but your setting on the plex web server. In other words do you have plex scan your library for changes every x hours? or is it set to constantly monitor your library and update it whenever it detects changes?
December 6, 201411 yr Author Not where you have plex installed, but your setting on the plex web server. In other words do you have plex scan your library for changes every x hours? or is it set to constantly monitor your library and update it whenever it detects changes? Ahh, yes its set to monitor constantly. But has been that way all along, no "setting" / "Process" changes other than moving cache_dir's to the Dynamix Plugin, and adding the Dynamix temperature plugin. (outside of the b12 changes themselves)
December 6, 201411 yr Author What's needed are the models in question. The output of hdparm -C /dev/sd? and only the start of /usr/sbin/smartctl -n standby -A /dev/sd? Here's an example. I like to use /dev/disk/by-id because the drive model serial is there. root@unRAIDb:/# ls -l /dev/disk/by-id/ | egrep -v 'part|usb' total 0 lrwxrwxrwx 1 root root 9 Dec 4 01:48 ata-HGST_HDN724040ALE640_PK2334PCHX2DLB -> ../../sdc lrwxrwxrwx 1 root root 9 Dec 4 01:48 ata-HGST_HDN726060ALE610_NAG1D7TP -> ../../sdd lrwxrwxrwx 1 root root 9 Dec 3 22:54 ata-HGST_HDN726060ALE610_NAG1DEKP -> ../../sdb root@unRAIDb:# hdparm -C /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB: drive state is: active/idle root@unRAIDb:# hdparm -y /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB: issuing standby command root@unRAIDb:# hdparm -C /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB: drive state is: standby root@unRAIDb:# smartctl -n standby -A /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.17.4-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Device is in STANDBY mode, exit(2) root@unRAIDb:/usr/local/emhttp# hdparm -C /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB /dev/disk/by-id/ata-HGST_HDN724040ALE640_PK2334PCHX2DLB: drive state is: standby If you do the smartctl and get a full attribute listing with the ID# header, then don't post all that data at this time, Just post that you received a full attribute listing. Attached is a copy of the picture in text. DriveSpin.doc
December 6, 201411 yr no cache_dirs installed. Plex (installed on cache) set to look for new once a day. I do manual update when I add movies usually. Sorry can't run hd debug right now
December 6, 201411 yr i have this same issue with HDD - WD WD2002FYPS i have 4 disk ST2000DM001 and 3 WD2002FYPS - i have spin down setup for 15 min - after this 15 min ST2000DM001 disk go to idle and WD2002FYPS stay active - they only go sleep after manual spin down from webGUI i have setup for all disk "use default" but i try change for WD disk manual per disk to 15 min or 30 min and test, after that again back to use default but nothing help - all time stay active ( dont go to idle from automat). i was try also delate super.dat file (but i dont know if this is connected) i must add - from beta12 im add 2x WD2002FYPS becuase on beta11a i have only 1 but sleep/idle for this one works fine on beta11
December 6, 201411 yr I also have this similar problem. the spindown issue confines to WD 2T green drive. I have cache dir on. This issue only after beta12.
Archived
This topic is now archived and is closed to further replies.