montr

I have the same problem. Here is the hardware: Motherboard: Gigabyte GA-D510UD NIC: Realtek RTL8111D No software plug-ins or customization with a 16GB flash and one 2TB HD. The sleep and wakeup has been working for years until I updated to the final UnRaid release 5.0. Sleep was working with 4.7 and all the 5.0 RC up to RC12aAiO. The computer will go to sleep and wakeup without any problems or need of rebooting at all. I installed the final V5.0 a week ago. I put to sleep using the command "echo -n mem >/sys/power/state" and send a magic packet to wakeup. The server wakeup but it is frozen, it will not even respond to a ping and the server show on my Asus router as offline. The only thing left is to turn it OFF by holding the power switch for 4 seconds. I tried many things like starting without shares or any customizations. No success, same problems. I reverted to RC12aAiO and everything is working fine. As suggested, I made a backup of my flash drive. Made it easy to go back to last known good software version.

As I describe in my post #2, I wake up the server from a Win7 PC that send a WOL to the server. The scheduled task wake up the Win7 PC first and then wakeup the server. One minute later, another task start the backup. On unRaid, I do not know a command that can do a wakeup. Another option is to schedule a wakeup from the BIOS if you have that option in your BIOS.

I have a GigaByte Atom D510 processor motherboard, 2GB RAM, 1 Seagate 1TB 5900RPM low-power (model:?), 120 mm fan and pico-supply. The S3 sleep to RAM and WOL works perfectly, no glitch with unraid 4.6 and now 4.7. I used the server is used only for backup. The server runs for about 15 mins everyday except for the first day of the month where is full image is done, about 3 hours. In sleep mode, the power consumption is about 2W. When running with drive spinning, the power consumption is about 30-32W.

First, I am new to Linux. I did not try to understand your change to original S3.sh. Here is how I use my server. The server is only use for backup and restore. The server is always asleep except that I have a task on a PC (Win 7 64b) at 1:59 AM everyday to wake up the server using WOL. At 2:00 AM, another task start the backup. If I need to use the server at other time, I have on my PC a icon that I click to send a WOL to the server. When the server is running and after the disk spin down, the server is sending a ping every minutes to the PC. If the PC is responding, the server is not allow to enter sleep. I included my S3.sh as an example my_s3.txt