Managed to get Unraid to S3 Sleep, but will not wake up

[umirza85]

Im using 5.0-rc8a, and i just recently installed simple features as I was trying to find a way to get the server to sleep and this command (echo 3 >/proc/acpi/sleep) from this WOL tutorial wasnt working (http://lime-technology.com/wiki/index.php/Setup_Sleep_(S3)_and_Wake_on_Lan_(WOL)) Using simple features the sleep command to get to S3 sleep worked perfectly and Im able to sleep the server, but can only bring it back with the button on the server. In my BIOS I've tried all settings (been doing this for about 12 hours now) and I cant get the server to turn on with the magic packet. The onboard Gbe NIC card has flashing lights while the system is in sleep mode but it just doesnt turn on. Is there something that I could be possibly missing in Unraid that could help? and just for an fyi my card does support wake on lan, it has the g when i run the ethtool.

 

Any help would really be appreciated, ive been doing this all day and searching like a mad man trying so any thing that could help. I use DD-WRT built in magic packet application to send the packet so i know its going through since it shows the server. I am using an Asus P5AD2-e premium motherboard

[warhead]

Do you have a live miniXP cd/usb? I've seen weird issues where devices don't work correctly until you use the Windows drivers to enable that particular feature ( in this case, WOL ).

I have a Dell laptop that everytime I turn off bluetooth in linux, I'd have to boot back into windows in order to turn it back on. If you don't have a live windows setup, try plugging in an old hard disk and run a miniXP install off that with the correct driver for your LAN card and enable WOL and disable any type of power management for the card

[umirza85]

I'll give that a shot and report back thanks for the advice.

[umirza85]

I booted up into windows and went to the adapter settings and made sure wake from sleep/power off was on, and also wake on settings had "Magic Packet & Test Pattern" selected. I tested the WOL from sleep and from powered off in windows and it turned my computer back on in both instances. I then went to power management and turned off all the settings (allow this computer to shut down this device etc....) then shut it down.

 

When I switched back to the unraid server and put the computer to sleep it still wouldnt turn back on with the magic packet, i needed to use the physical button to turn it on.The lights on the ethernet connection are on and flashing while the systems in sleep and powered off state - i just dont know why it wont wake the Unraid server. Is there something else that I need to change within Unraid?

 

Edit:

So i booted up with my windows hard drive, then shut down the computer. Took out the hard drive and connected the unraid drives back. sent the WOL packet and the computer started up. Then using simple features i put the computer to S3 sleep. Sending the WOL packet at this point did not start the server back up. Could unraid be changing some sort of setting, or maybe shutting down the NIC when it powers down/goes to sleep?

[kricker]

I had a similar situation with an older Shuttle motherboard with an onboard NIC. WOL worked in windows, but not in Unraid. I think it was a Realtek NIC. When I switched to a Supermicro mobo, I no longer had issues. It works great under Unraid. I tried all kinds of things to try to fix the old one including chaning BIOSs. Nothing worked. Eventually I killed it with a bad flash and had no choice but to replace it.

 

Sent from my LG-LS855 using Tapatalk 2

 

 

[umirza85]

I have dual onboard NICs Ive tried on both and same story they WOL only from windows. They are Marvel NICs. I can see the light flashing while the system is in sleep or off. And when I send the magic packet i see the lights flash everytime i click. Could it be they way unraid (or the sleep script) shuts down the interface? that its not telling it to be on the lookout for a packet? Maybe if i play around with it enough I'll break mine also  then I can justify getting a new one. Ive spent 3 days trying to figure this out, maybe its time to give up.