May 11, 20197 yr Wol was working fine in 6.6.7 and updated to 6.7.0 and Wol is not working. Restored back 6.6.7 and WOL started to work again. No settings are changed prior to update and no new plugins were installed. Sent from my iPad using Tapatalk
May 11, 20197 yr Author Yes the ethernet link is active and when i restore back to 6.6.7 WOL is woking.
May 14, 20197 yr You may try check by "ethtool eth0" or enable WOL by "ethtool -s eth0 wol g" Edited May 14, 20197 yr by Benson
May 18, 20197 yr Same problem with 6.7 (no WOL) and ethtool eth0 says pumbg for 'Supports wake-on' and g for Wake-on. Pushing the power button did wake up the system.
May 18, 20197 yr 24 minutes ago, drcos said: Same problem with 6.7 (no WOL) and ethtool eth0 says pumbg for 'Supports wake-on' and g for Wake-on. Pushing the power button did wake up the system. Pls confirm the link still active after shutdown If still not work, pls perform some test 1. Completely power off PSU for 1 min 2. Power on / Plug in power, then confirm the link still active 3. WOL, it must work ( Y / N ? ), If not, check BIOS setting. 4. Boot Unraid in safe mode no docker / VM, then shutdown, link still active, try WOL work or not. ( Y/ N ? ) Edited May 18, 20197 yr by Benson
May 18, 20197 yr Same issue here. Ever since upgrading to 6.7 WOL no longer works. WOL is enabled in BIOS, am running the latest BIOS version, and the only change done to my server is upgrading from 6.6.7 to 6.7 An an FYI the mainboard I am using is an Asus PRIME X370-A; network card is Realtek® RTL8111H.
May 18, 20197 yr 16 hours ago, Benson said: Pls confirm the link still active after shutdown How do you check this? With the system sleeping, neither LED on the ethernet port is on.
May 18, 20197 yr My port have LED on in shutdown, if no LED on that means no link, so NIC won't WOL. In some hardware when link speed was 10Mbps, LED would off, but mine will on. You also can check on router/switch side. As sereval case report, so I believe 6.7 have issue but clearly not everyone got this. We must rule out what turn off WOL. I suspect problem in shutdown phase which turn off WOL, but I can't reproduce. Edited May 18, 20197 yr by Benson
May 19, 20197 yr 10 hours ago, Benson said: My port have LED on in shutdown, if no LED on that means no link, so NIC won't WOL. In some hardware when link speed was 10Mbps, LED would off, but mine will on. You also can check on router/switch side. As sereval case report, so I believe 6.7 have issue but clearly not everyone got this. We must rule out what turn off WOL. I suspect problem in shutdown phase which turn off WOL, but I can't reproduce. My NIC LED is off when Unraid goes into Sleep mode.
May 19, 20197 yr Could this issue be related to https://wiki.archlinux.org/index.php/Wake-on-LAN#Realtek ?
May 19, 20197 yr 12 minutes ago, Jonathan Vella said: Could this issue be related to https://wiki.archlinux.org/index.php/Wake-on-LAN#Realtek ? Could you peform suggest test ? If step 3 fail, then check BIOS, turn off ERP, Deep sleep, CEC2019 ....... *** After each change, pls redo step 1-3 *** On 5/18/2019 at 10:30 AM, Benson said: If still not work, pls perform some test 1. Completely power off PSU for 1 min 2. Power on / Plug in power, then confirm the link still active 3. WOL, it must work ( Y / N ? ), If not, check BIOS setting. 4. Boot Unraid in safe mode no docker / VM, then shutdown, link still active, try WOL work or not. ( Y/ N ? ) Edited May 19, 20197 yr by Benson
May 19, 20197 yr So, if I execute "ethtool -s interface wol g" WOL works perfectly fine. Issue is how do I make it persistent since after every reboot i need to execute the same command line?
May 19, 20197 yr 33 minutes ago, Jonathan Vella said: So, if I execute "ethtool -s interface wol g" WOL works perfectly fine. Issue is how do I make it persistent since after every reboot i need to execute the same command line? You may add that in go file ( /boot/config/go ). But problem likely you haven't well set WOL in BIOS.
May 20, 20197 yr So I did add "ethtool -s eth0 wol g" (without quotes) to my go file however it does not work :-( Maybe I am doing something wrong. As to my BIOS settings being incorrect, I really doubt it - see attached image, there really isn't that much to configure and again this started to happen once i upgraded to 6.7
May 21, 20197 yr Author When I used the command WOL works for that instance and is not persistent. IAfter restart again WOL doesn't work. I read in here in other old thread to reset network settings to deleted the network.cfg file, I deleted the file and it made no difference for me. I had a flash backup of 6.6.7 where WOL was working, I added the few lines that were missing in the network.cfg in 6.7.0 and WOL is working.Sent from my iPhone using Tapatalk
May 21, 20197 yr 13 hours ago, harshakavuri said: When I used the command WOL works for that instance and is not persistent. IAfter restart again WOL doesn't work. I read in here in other old thread to reset network settings to deleted the network.cfg file, I deleted the file and it made no difference for me. I had a flash backup of 6.6.7 where WOL was working, I added the few lines that were missing in the network.cfg in 6.7.0 and WOL is working. Sent from my iPhone using Tapatalk I'm having the same problem, can you share the lines that you have added and solved this? Thanks.
May 21, 20197 yr Author 32 minutes ago, psychosb said: I'm having the same problem, can you share the lines that you have added and solved this? Thanks. Here you go, Please make a backup of your config/network.cfg file before making any changes # Generated settings: IFNAME[0]="br0" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BRNICS[0]="eth0" PROTOCOL[0]="ipv4" USE_DHCP[0]="yes" DHCP_KEEPRESOLV="no" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" SYSNICS="1" I have a single Realtek 8168 PCI Express Gigabit Ethernet. I don't have any VMs as of now and only few dockers. I am not sure if these settings will work for you or not and some of the settings might be different for you. I have a backup of the flash drive when WOL was working and I just used that. I haven't made any setting changes or installed any new plugins as well. With the above network.cfg file WOL is working again for me Whats weird is that after upgrading to 6.7.0 the network.cfg has just a few lines compared to the file in 6.6.7
May 21, 20197 yr This is weird. I have just downgraded to 6.6.7 and the WOL started to work again. I have compared the network.cfg from both versions and on my case the're the same. # Generated settings: IFNAME[0]="br0" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BRNICS[0]="eth0" DESCRIPTION[0]="Bridge" PROTOCOL[0]="ipv4" USE_DHCP[0]="yes" METRIC[0]="208" DHCP_KEEPRESOLV="no" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" MTU[0]="" SYSNICS="1"
May 21, 20197 yr Author That is weird my network.cfg file after upgrade to 6.7.0 # Generated network settings USE_DHCP="yes" IPADDR= NETMASK= GATEWAY= BONDING="yes" BRIDGING="yes" I thought that might be the problem and i changed the file
May 23, 20197 yr same issue for me here, after upgrading from 6.5.3 to 6.7.0. The board is an ASUS M5A78L-M Plus/USB3 running with Opteron 3350HE and ECC RAM, using onbaord NIC (Realtek RTL8111H) Sleep and WOL did work for literally years and several linux distros on that rig... The NIC apears to be powered down when in sleep...pushing the power button wakes up the system without any error. This used to work with 6.5.3 for about a year uptime, with several sleep/WOL cycles per week.
Archived
This topic is now archived and is closed to further replies.