Hi there,

i have a problem with the automatic disk spin down in unRaid.

 

Sometimes one of my disks which is attached to my Adaptec 1430SA Raid adapter does not get spun down correctly. I can see this when i take a look at the web interface. The disk is shown as spun down but the temperature is reported. When i look at the output of hdparm -C of the disk it is shown as active/idle not as standby.

 

Strange thing is  that if i "spin up" the disk from the Web Interface and then use the Web Interface to spin it down it always works.

The disk is than reported as "standby" by hdparm.

 

How can this be. Does the Webif and the automatic spindown use different commands to spin down the disks or where to search for the failure. I just switch from an Asmedia 2 Port controller card to the 1430SA, both showed the same behaviour.

 

The problem for me is that with this failure the S3 Sleep command does not work correctly.

 

Any help would really be appricated.

Does nobody have an idea?

Have exactly the same Problem since a few days and my S3-sleep dosnt work "properly" anymore.

It seems that the S3 sleep script is broken - developer dosnt answer on my PM so i have no idea how to fix this 

What i do is i spin up all drives over the button "SpinUp" and then push the Button "SpinDown". This is syncing all disk and the Temps are no longer reported.

In this condition my server go to sleep till the next wakeup where everything is in confusion again.

After a wakeup when i do a hdparm -C /dev/sdg it says "active/idle" and NOT "standby"

In my case it is adequate (after a wakup) to push 1x SpinUp and then 1x SpinDown. It syncs (or something) the disks and the S3 script is working again.

Doing hdparm -C again showns now "standby" - strange thing 

 

I remember - bevore v6.1.9 - the sys did an automatic spin up of all disks when the sleep event occur.

Since v6.1.9 this dosnt happen anymore so they made either a change in the software or it is a bug.

 

Hi there,

i have a problem with the automatic disk spin down in unRaid.

 

Sometimes one of my disks which is attached to my Adaptec 1430SA Raid adapter does not get spun down correctly. I can see this when i take a look at the web interface. The disk is shown as spun down but the temperature is reported. When i look at the output of hdparm -C of the disk it is shown as active/idle not as standby.

 

Strange thing is  that if i "spin up" the disk from the Web Interface and then use the Web Interface to spin it down it always works.

The disk is than reported as "standby" by hdparm.

 

How can this be. Does the Webif and the automatic spindown use different commands to spin down the disks or where to search for the failure. I just switch from an Asmedia 2 Port controller card to the 1430SA, both showed the same behaviour.

 

The problem for me is that with this failure the S3 Sleep command does not work correctly.

 

Any help would really be appricated.

 

You might want to report this as a bug or defect. It sounds like an issue that is going to need Lime-Tech to look into / fix.

A workaround is to spin up all disks after waking from sleep by adding this:

for disknum in 0 `ls /dev/md* | sed "sX/dev/mdXX"`; do /root/mdcmd spinup $disknum; done

into the "Custom commands after wake-up:" field.

 

IMHO its not the best solution, as it spins up disks I don't want to access, too. But it works, so give it a try.

Reporting this error to Limetech is a great idea. Maybe they find a fix to the root cause.

 

Thanks for this but in my case its not always working - somtimes this code spin up all drives and sometimes not.

Can i copy this code "as is" or do i need some changes?

 

EDIT: Did some tests - after wakeup, all disks are spun down - so what can i do?