June 3, 200818 yr Using v4.3 beta 6 my WD10EACS-00Z parity drive never spins down on its own but will spin down if I use the spindown button on the web interface. All the other drives in the unRAID server spin down after the specified activity timeout has elapsed. Anybody else using v4.3 beta 6 and one of these drives as parity seeing this? How can I debug this further?
June 3, 200818 yr I have 2 of those drives and after a reboot the drives spun down...before the reboot for some reason they wouldn't.
June 3, 200818 yr I have 2 of those drives and after a reboot the drives spun down...before the reboot for some reason they wouldn't. Same here. Bill
June 3, 200818 yr I've found after installing any sort of new drive a re-boot is usually required to get the drives to spin down. Once the drive has been added to the array, cleared, and had a file system added to it, re-boot your server and your drive should spin down.
June 4, 200818 yr I have a siimilar situation. I have a 3-disk array. The first disk (parity) is a Samsung HD753LJ (750 GB) and the other two are Hitachi HDT72505 (500 GB). The two smaller drives spin down just fine, but the parity drive keeps spinning and doesn't seem to stop unless I manually force it to. Any ideas? Not that it's the parity drive that refuses to spin down, just like the OP. Michael
June 4, 200818 yr Sometimes you have to set the spindown on purpose. Locate the /dev/sd? device (look on the Devices page). then do a manual hdparm command to see what the deal is. hdparm -I /dev/sd? where ? is the device character associated with the drive. hdparm -S241 /dev/sd? This should set spin down time to 30 minutes. Then see what happens. To force a spin down as a test do hdparm -y /dev/sd? The current power mode can be checked with hdparm -C /dev/sd? More info available here http://linux.die.net/man/8/hdparm
August 5, 200817 yr I have just installed a fresh 4.3.3 un-raid with two samsung disk (1TB and 750GB). Both disks are data disk, so there is no parity disk yet. Everything works fine, except spin down. None of the two disks are spinning down after 1 hour, which is set as a spin dwon delay. On the main screen, I can force the dirvers to spin down by the spin all drive button, and can wake them up without any problem. I try to do the rebooting, poweroff-poweron trick about 10 time, without luck. If I set the spin down delay using hdparm -Sx /dev/sdx, it is working as it should. Is it possible at any circumtances, that there is no other way to get it working, except manually set by hdparm and hack it into the go script?
August 5, 200817 yr You may have to reboot the server after adding new disks to an array to get the spindown to work. This was supposed to be fixed in a recent build, but I would try it anyway. It is also not clear if looking at the main page of the GUI (where the disk temp is shown) causes the spindown timer to be reset. I would try a full power down of the unRAID server, then power back up and let the machine sit unusued overnight. If the drives are not spun down in the morning, I'd capture a syslog and post. This is a common question when starting a new array. Obviously it is not something that most of us on the forum do very often. Please let us know what you find out.
August 5, 200817 yr Thank you for replying bjp999! My issue is, that I was already trying the rebooting, also with full power down for several times. Moreover, to avoid the issue, that the main page might reseting the spin down timer, I've not checked the drives on that page, but telnet in, and do a "hdparm -C /dev/sdx". The un-raid box is running without any activity from the morning, and it has not spinned down, up until now. Could you please help me on how to catch the syslog? Or should I still try something before? Or should I go for manual setting hdparm? Thanks for your help again!
August 5, 200817 yr Could you please help me on how to catch the syslog? Or should I still try something before? Or should I go for manual setting hdparm? Follow the troubleshooting link in my sig. You will find a section on how to capture the syslog.
August 5, 200817 yr After a lot of struggling and testing my findings are the following: - No way for me to get the disks spin down from the GUI. - I found my solution based on RobJ post, here: http://lime-technology.com/forum/index.php?topic=1006.0 - Based on his last post, I included "hdparm -Sx /dev/sdx" twice for each drive, still not working Than I put a sleep command before the second run of hdparm like this: /usr/sbin/hdparm -Sx /dev/sdb /usr/sbin/hdparm -Sx /dev/sdc sleep 15 /usr/sbin/hdparm -Sx /dev/sdb /usr/sbin/hdparm -Sx /dev/sdc where x is the corresponding time to spin down. In this way, I get it working. My conclusion is that the problem related to this twice needed command issue. I assume (based on the syslog), that Tom is using the same hdparm command to set spin down times, but this command is given out only once during default boot. I wonder why is it so different for me, because it seems that it works for most of the users in the default way.
August 6, 200817 yr I would like to refer you to a thread where there has been further discussion related to this problem, possibly similar to what you are experiencing. http://lime-technology.com/forum/index.php?topic=2212.msg16979#msg16979 It would be useful to have a little detail about your hardware, and to see your syslog after playing with spin down. One other point, are you seeing temps for the drives? If SMART is not enabled for the drive(s), then you might have similar behavior, as well as missing temps.
August 6, 200817 yr First of all, thank you all for your support! So, my config: Giga-byte GA-G33M-DS2R MB (ICH9R) with Celeron E1200 CPU 2 Data disk, yet without parity: SAMSUNG_HD103UJ (1000GB) and SAMSUNG_HD753LJ (750GB) AHCI, native SATA and S.M.A.R.T is enabled in the BIOS. Yes, I see the temps in the main page. And now, the most intresting finding of today: I mentioned before, when seting spin down time manually with hdparm, than it is working as it should. Well, just partially. It is only working, if I set spind down time at maximum 20 minutes. If I set it above, than never spin down. If I set it to 20 minutes, seems spin down always. My first thought was, that something on my netwotk try to read/ and or write to the disks, so I turned off everything on the LAN, no luck. Than I pulled out the LAN cable from the un-raid box, still no luck. Based on the aboves, it seems to me, that somehow the spin down timer is reseting between 20 and 30 minutes. The intresting thing is, that if something would like to access to disks, between 20 and 30 minutes, they should spin up, but once they spinned down at 20 minutes, they stayed in standby up until I try to access them via smb. Weird... If you still think based on the aboves, that there can be relevant info for you in the syslog, I can share with you. Could you please advise me what to look after all? Thank you!
August 6, 200817 yr First of all, thank you all for your support! So, my config: Giga-byte GA-G33M-DS2R MB (ICH9R) with Celeron E1200 CPU 2 Data disk, yet without parity: SAMSUNG_HD103UJ (1000GB) and SAMSUNG_HD753LJ (750GB) AHCI, native SATA and S.M.A.R.T is enabled in the BIOS. And now, the most intresting finding of today: I mentioned before, when seting spin down time manually with hdparm, than it is working as it should. Well, just partially. It is only working, if I set spind down time at maximum 20 minutes. If I set it above, than never spin down. If I set it to 20 minutes, seems spin down always. My first thought was, that something on my netwotk try to read/ and or write to the disks, so I turned off everything on the LAN, no luck. Than I pulled out the LAN cable from the un-raid box, still no luck. Based on the aboves, it seems to me, that somehow the spin down timer is reseting between 20 and 30 minutes. The intresting thing is, that if something would like to access to disks, between 20 and 30 minutes, they should spin up, but once they spinned down at 20 minutes, they stayed in standby up until I try to access them via smb. Weird... If you still think based on the aboves, that there can be relevant info for you in the syslog, I can share with you. Could you please advise me what to look after all? Thank you! What specific values are you using in the commands you entering to set the timeout? The numbering scheme is not intuitive. -S240 = 20 minutes -S241 = 30 minutes -S242 = 60 minutes -S243 = 90 minutes -S244 = 120 minutes -S245 = 150 minutes -S246 = 180 minutes -S247 = 210 minutes -S248 = 240 minutes -S249 = 270 minutes -S250 = 300 minutes -S251 = 330 minutes -S252 = 21 minutes -S253 = disk vendor defined between 8 and 12 hours -S254 = undefined, reserved -S255 = 21 minutes plus 15 seconds According to the hdparm manual page: -S Set the standby (spindown) timeout for the drive. This value is used by the drive to determine how long to wait (with no disk activity) before turning off the spindle motor to save power. Under such circumstances, the drive may take as long as 30 seconds to respond to a subsequent disk access, though most drives are much quicker. The encoding of the timeout value is somewhat peculiar. A value of zero means "timeouts are disabled": the device will not automatically enter standby mode. Values from 1 to 240 specify multiples of 5 seconds, yielding timeouts from 5 seconds to 20 minutes. Values from 241 to 251 specify from 1 to 11 units of 30 minutes, yielding timeouts from 30 minutes to 5.5 hours. A value of 252 signifies a timeout of 21 minutes. A value of 253 sets a vendor-defined timeout period between 8 and 12 hours, and the value 254 is reserved. 255 is interpreted as 21 minutes plus 15 seconds. Note that some older drives may have very different interpretations of these values. Joe L.
August 6, 200817 yr "-S240 = 20 minutes" is still OK, spin down at 20 minutes and stay standby until I try to reach the disk "-S241 = 30 minutes" is already not working, means if this value is set, then there is no spindown. Even after a whole night.
August 6, 200817 yr have you tried setting with the "-S241" parameter, then doing a power cycle. I.E. Full power down then power up. A restart may not suffice.
August 6, 200817 yr Yes, I have. It didn't helped. I found the following discussion in a fedora linux thread: http://fedoraforum.org/forum/archive/index.php/t-152576.html Is there any chance, that my problem is related to this in any way? But in this case, I would not understand, why is this only happen to me...
August 9, 200817 yr I cannot get trought this problem. I spent my all nights in the week in troubleshooting, than yesterday I tried in my desktop PC with completely different config (just the disks are the same), and the same happens. No spin down. What am I doing wrong? Or is it possible that my samsung disks are not compatible?
August 9, 200817 yr just fyi (not read whole thread) I have several of the following disks and they work perfectly. SAMSUNG_HD103UJ SAMSUNG_HD501LJ
August 10, 200817 yr I would still like to see a syslog. Also, get SMART reports for each disk, see http://lime-technology.com/wiki/index.php?title=FAQ#How_can_I_find_out_more_information_about_a_hard_drive.3F.
August 10, 200817 yr Hello RobJ, Here are the requested reports. (syslog, smartctl and hdparm reports for both drive) I have found a spare maxtor HDD, so there is a samsung HD753LJ and a maxtor 6Y200M0 attached now, instead of the two samsung. The maxtor disk is always spinning down, while the samsung not. Additionally I tested it in two completely different motherboard config, with this same disk, with the same results. It is really seems to me that something is now OK between samsung and un-raid, in spite of, what NAS repors above in his post. Or maybe it is a firmware issue? NAS, could you please check the firmware revision in your HD103UJ? Or is there any chance, that the free version is behaving differently, than the Plus and Pro version? (I assume NAS not using the free version)
August 10, 200817 yr an easier way for you to do this for rerference would be to use pastebin.com choosing the permanent storage option. No registration required.
August 10, 200817 yr an easier way for you to do this for rerference would be to use pastebin.com choosing the permanent storage option. No registration required. I am not really sure how to inject the pastebin url into my post. Shall I use the insert hyperlink option in this forum? Paralelly, could you please feedback me regarding to your HD103UJ firmware revision? Thank you!
Archived
This topic is now archived and is closed to further replies.