After a wakeup or a boot, all HDDs have the status "active/idle" but it should be "standy" (checked over hdparm -C).

This prevents the Server to go to sleep properly next time even when the disks are spun down.

 

Workaround: After boot/wakeup its necessary to spin up all disks "by hand"

After this procedure, all disk which go to sleep have the proper status "standby"

 

Boring thing because this must be done "by hand" 

Can some of the Devs check this problem or set it to the Bug-List?

 

Thanks for your help

After a wakeup or a boot, all HDDs have the status "active/idle" but it should be "standy" (checked over hdparm -C).

This prevents the Server to go to sleep properly next time even when the disks are spun down.

 

Workaround: After boot/wakeup its necessary to spin up all disks "by hand"

After this procedure, all disk which go to sleep have the proper status "standby"

 

Boring thing because this must be done "by hand" 

Can some of the Devs check this problem or set it to the Bug-List?

 

Thanks for your help

If you check out the S3 sleep thread, you'll see that it's a known issue, and the solution is to use its before sleep scripting ability to spin up all of the drives

I saw it, but it dosnt work when i put something in this fields... 

The Sys ignores everything in this fields.

What is the "proper" String to spin up the disks?

Use the following line in Custom commands after wake-up:

hdparm -y $(ls /dev/sd*|grep '[a-z]$') >/dev/null 2>&1

This will put all disks in standby mode after wake-up (works for me).

 

Ps. Sleep mode isn't officially supported by Limetech, chances for corrections regarding sleep issues are slim...

Thanks for this hint - will try it 

EDIT: Nice - its working!!!! 

 

Thanks again bonienl