I'm trying to set my server to wake on LAN, I've set the parameters as best as I know

ethtool -s eth0 wol g

and I can see the Wake-on: g

however after a cold boot it always goes back to Wake-on: d

and won't wake with a magic packet.

 

What am I doing wrong?

 

Regards

Stu

I'm trying to set my server to wake on LAN, I've set the parameters as best as I know

ethtool -s eth0 wol g

and I can see the Wake-on: g

however after a cold boot it always goes back to Wake-on: d

and won't wake with a magic packet.

 

What am I doing wrong?

 

Regards

Stu

It needs to be set in your motherboard BIOS.

I do nothing to enable it specifically, yet it shows as enabled when I use ethtool. (It is enabled in my BIOS)

[pre]

root@Tower:/boot# ethtool eth0

Settings for eth0:

        Supported ports: [ TP ]

        Supported link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supports auto-negotiation: Yes

        Advertised link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Advertised auto-negotiation: Yes

        Speed: 1000Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: on

        Supports Wake-on: umbg

        Wake-on: g

        Current message level: 0x00000007 (7)

        Link detected: yes

[/pre]

Hmm, as far as I can tell it is enabled on the MB. Though my bios is somewhat esoteric in these matters. ASRock K7VT4A Pro!

 

 

Try disabling unRAID by commenting out emhttp.  Boot, run ethtool, and shutdown with the *poweroff* script.  THis shoul dbe the way to test it, cause if you can't get it to work un this scenario, you mobo doesn't support it.  If it does work this way, then it with unRAID and work backwards from there.

 

When if I boot unRAID, and use the unRAID shutdown button, it turns off eth0, and it will NOT wake up from S5.... so I have to use a script to shut down the array, and halt the server.... you need to remove the -i from the halt command.

I'm trying to set my server to wake on LAN, I've set the parameters as best as I know

ethtool -s eth0 wol g

and I can see the Wake-on: g

however after a cold boot it always goes back to Wake-on: d

and won't wake with a magic packet.

 

What am I doing wrong?

 

Regards

Stu

 

stuartl, I have with my motherboard 915GM Speedster-FA4 same problem. But I am add bellow code to end of "go" script. Now WOL is working.

 

ethtool -s eth0 wol g

 

 

But if I power-off of my UnRaid server WOL is not work. This behavior is probably normal for my motherboard. If shutdown UnRaid server and not power-off than WOL is work.

 

stuartl, You may help this procedure.

if I power-off of my UnRaid server WOL is not work.

This behavior is probably normal for my motherboard. If shutdown UnRaid server and not power-off than WOL is work.

 

I thought this was normal behaviour.

There might be some bios options. I think in my bios I have POWER ON = LAST STATE.

I know I have an option to POWER ON BY PCI enabled.

How "cold" is your shutdown?  Are you killing power to the PSU or is it a "warm off" and the mobo still has power?

How "cold" is your shutdown?  Are you killing power to the PSU or is it a "warm off" and the mobo still has power?

 

I switch power off on PSU or unplug cord from power. Then not work WOL.

 

I have choice POWER ON in BIOS:

- Off

- On

- Former-Sts

 

I try change POWER ON in BIOS to Former-Sts.

Change to Former-sts not help me.

 

If I power off (unplug cord) and then power on (plug cord) LED on NIC is stay OFF.

If I only shutdown server and don't unplug cord then LED on NIC is stay ON.

 

Probably this is normal behavior for my mothenrboard.

You can not WOL when you disconnect the power and reconnect it. 

 

You can only WOL when the system is shut down programatically, leaving power to the NIC and leaving it plugged into the wall.

 

the option in the BIOS has to do with a power failure (i.e. disconnecting the power) ... after a power failure, should the computer 1) stay off, 2) turn on, or 3) go back to the state it was in when the power failed (off or on).... it will NOT go back to a "soft-off" state with the NIC powered up and ready to WOL.

You can not WOL when you disconnect the power and reconnect it. 

 

You can only WOL when the system is shut down programatically, leaving power to the NIC and leaving it plugged into the wall.

 

the option in the BIOS has to do with a power failure (i.e. disconnecting the power) ... after a power failure, should the computer 1) stay off, 2) turn on, or 3) go back to the state it was in when the power failed (off or on).... it will NOT go back to a "soft-off" state with the NIC powered up and ready to WOL.

 

I have another computers where WOL is working correctly. I disconnect  the power from PSU and reconnect - WOL is working.

On my motherboard in server WOL after disconnect the power from PSU WOL is not working.

This is difference.

Different motherboards have different capabilities.  If you have one what will WOL from a hard power off, it is a rarity...., and if that is what you need, buy more of them.