unraided

Ok, I'll have to try that. What is better, using the s3.sh script or the the s2ram? I cannot determine what is best. My concern which one syncs the parity and data drives before suspending the system and which one is better for less power consumption? Also, is their a already compiled s2ram package for unraid? my aim is to have the server power on/off without any physical invention, use magic packet to power on and power off via script.Thanks.

I was interested in this s3.sh script, see below: #!/bin/bash #http://lime-technology.com/wiki/index.php?title=Setup_Sleep_(S3)_and_Wake_on_Lan_(WOL) drives="/dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf dev/sdh" timeout=5 count=5 while [ 1 ] do hdparm -C $drives | grep -q active if [ $? -eq 1 ] then count=$[$count-1] else count=$timeout fi if [ $count -le 0 ] then # Do pre-sleep activities sleep 5 # Go to sleep /bin/sync /boot/config/beep-down echo 3 > /proc/acpi/sleep # Do post-sleep activities ethtool -s eth0 speed 1000 ethtool -s eth0 wol gp # Force a DHCP renewal (shouldn't be used for static-ip boxes) #/sbin/dhcpcd -n /boot/config/beep-up sleep 5 count=$timeout fi # Wait a minute echo COUNT $count sleep 60 done but when I try to run it, I get a "/boot/config/s3.sh: /bin/bash^M: bad interpreter: No such file or directory" error. The s3 file has full ugo+rwx access: -rwxrwxrwx 1 root root 806 Mar 6 21:07 s3.sh* I've tried to run it in the 'go' script and I get that message, if I evoke it in ./bin/bash /boot/config/s3.sh or if I run it like this ./boot/config/s3.sh. Any reason why it doesn't work? Thanks.