I just updated my unRaid from 4.5 to 4.5.6. I have two WD drives that are not part of the array. In my go script I set these drives spindown time using hdparm -S, but they never spindown automatically. Even when I try and envoke a spindown hdparm -y /dev/sdx, they still stay active.

 

I did not have this problem in 4.5. What could have changed to cause this? How can I debug this? This is a big enough problem for me to go back to 4.5.

 

Many Thanks!

 

UPDATE:

 

After some searching I found some information that might be relevant. unRaid v4.5.6 is running hdparm v8.6. I found this page and this page that point to a bug in hdparm.

 

I also found the last poster here which says he solved his spindown problem by changing the Advanced Power Management value.

...I found that spindown time (-S) is affected by the Advanced Power Management facility (-B). For -Bn where n>128, spindown time is ignored. I found the disc had an APM value of 254 so set it to 127 and tried -S12, result spindown now works again. Well it works in that the disc spins down, need to check whether it spins down after spin up without having re-issued the command...

 

I decided instead of messing with the drive I would update hdparm first. I used http://slackware.osuosl.org/slackware-13.1/slackware/a/hdparm-9.27-i486-1.txz and tired hdparm -y /dev/sdx again. The drive now shows as to be spun down I reissued the hdparm -S 241 /dev/sdx (30min). This spun the drive up. I waited ~30min and it worked 

 

Should this be updated for unRaid 4.5.7?

Send an email off to Tom and let him know about the issue with hdparm in 4.5.6.  He can make sure to include an update in 4.5.7 and/or 5.x

UPDATE:

 

After some searching I found some information that might be relevant. unRaid v4.5.6 is running hdparm v8.6. I found this page and this page that point to a bug in hdparm.

 

I also found the last poster here which says he solved his spindown problem by changing the Advanced Power Management value.

...I found that spindown time (-S) is affected by the Advanced Power Management facility (-B). For -Bn where n>128, spindown time is ignored. I found the disc had an APM value of 254 so set it to 127 and tried -S12, result spindown now works again. Well it works in that the disc spins down, need to check whether it spins down after spin up without having re-issued the command...

 

I decided instead of messing with the drive I would update hdparm first. I used http://slackware.osuosl.org/slackware-13.1/slackware/a/hdparm-9.27-i486-1.txz and tired hdparm -y /dev/sdx again. The drive now shows as to be spun down I reissued the hdparm -S 241 /dev/sdx (30min). This spun the drive up. I waited ~30min and it worked 

 

Should this be updated for unRaid 4.5.7?

 

Link added to Best of the Forums here

 

Thanks kapperz!

Send an email off to Tom and let him know about the issue with hdparm in 4.5.6.  He can make sure to include an update in 4.5.7 and/or 5.x

I've created a package in unMENU for the newer hdparm.  You can install it from there too.

 

I agree, an e-mail to Tom is appropriate to let him know of the bug in the older hdparm.

I sent Tom an email a little while ago, but haven't heard anything.

 

One note, drives that are not part of the array need to have their suspend time set again after coming out of S3 sleep.

 

Thanks prostuff

I know this is an old thread but I suppose this is no longer an issue?!  The info in unmenu might need to be updated as a result since it is somewhat misleading.  Otherwise, if it's still an issue then it would be good to know.  Thanks.