March 3, 20179 yr Hi, I have a happy UnRAID system except for one thing: wake-on-lan basically doesn't work properly. Here's the symptom: If I put it to sleep from the Main page, then I can reliably wake it again by sending the appropriate magic WoL packet. If the server goes to sleep by itself, it does not respond to the WoL packet. Instead I have to prod it back into life by tapping the power button. Most annoying when the server is in an out-of-the way place. Here's what I have installed: UnRAID 6.2.4 Dynamix Sleep plugin 3.0.4 Dynamix is configured to use sleep mode; exclude 10:00-13:00 and 17:00-23:00 (I rather hoped this meant the server would automatically wake during these periods); wait 60 minutes after array inactivity; wait for < 100kbps ethernet traffic; not wait for user inactivity; use WoL option 'g' before sleep. The output from 'ethtool eth0' includes "Supports Wake-on: pumbg" and "Wake-on: g". I've set Dynamix Sleep to log what it's doing and here's what I see: Mar 2 00:01:53 Tower s3_sleep: Enter sleep state now Mar 2 00:01:53 Tower kernel: PM: Syncing filesystems ... done. Mar 3 15:15:02 Tower kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. Mar 3 15:15:02 Tower kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Mar 3 15:15:02 Tower kernel: Suspending console(s) (use no_console_suspend to debug) Mar 3 15:15:02 Tower kernel: sd 6:0:0:0: [sdd] Synchronizing SCSI cache Mar 3 15:15:02 Tower kernel: sd 6:0:0:0: [sdd] Stopping disk Mar 3 15:15:02 Tower kernel: serial 00:07: disabled Mar 3 15:15:02 Tower kernel: serial 00:07: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: parport_pc 00:05: disabled Mar 3 15:15:02 Tower kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache Mar 3 15:15:02 Tower kernel: sd 2:0:0:0: [sdc] Stopping disk Mar 3 15:15:02 Tower kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache Mar 3 15:15:02 Tower kernel: sd 1:0:0:0: [sdb] Stopping disk Mar 3 15:15:02 Tower kernel: PM: suspend of devices complete after 1529.904 msecs Mar 3 15:15:02 Tower kernel: PM: late suspend of devices complete after 0.247 msecs Mar 3 15:15:02 Tower kernel: pcieport 0000:00:1c.4: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: pcieport 0000:00:1c.3: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: PM: noirq suspend of devices complete after 10.732 msecs Mar 3 15:15:02 Tower kernel: ACPI: Preparing to enter system sleep state S3 Mar 3 15:15:02 Tower kernel: PM: Saving platform NVS memory Mar 3 15:15:02 Tower kernel: Disabling non-boot CPUs ... Mar 3 15:15:02 Tower kernel: smpboot: CPU 1 is now offline Mar 3 15:15:02 Tower kernel: ACPI: Low-level resume complete Mar 3 15:15:02 Tower kernel: PM: Restoring platform NVS memory Mar 3 15:15:02 Tower kernel: Enabling non-boot CPUs ... Mar 3 15:15:02 Tower kernel: x86: Booting SMP configuration: Mar 3 15:15:02 Tower kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2 Mar 3 15:15:02 Tower kernel: cache: parent cpu1 should not be sleeping Mar 3 15:15:02 Tower kernel: CPU1 is up Mar 3 15:15:02 Tower kernel: ACPI: Waking up from system sleep state S3 Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: pcieport 0000:00:1c.4: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: PM: noirq resume of devices complete after 11.295 msecs Mar 3 15:15:02 Tower kernel: PM: early resume of devices complete after 0.149 msecs I have very little idea of what's really going on here, but those "System wakeup enabled by ACPI" followed by "System wakeup disabled by ACPI" messages look suspicious to me. If anyone could offer some advice in words of few syllables (assume you're talking to someone who knows nothing!) that would be very kindly received.
March 3, 20179 yr I also have very little knowledge of S3 sleep but it looks to me like the "System wakeup disabled by ACPI" happens as the server is resuming from sleep. I would say the message Mar 3 15:15:02 Tower kernel: ACPI: Low-level resume complete marks when the server beings waking up from sleep.
March 5, 20179 yr Author To add insult to injury, the problem appears intermittent. I just tried WoL and it worked (as it sometimes does). I have no idea why it isn't reliable.
March 6, 20179 yr If the issue is intermittent this might be relevant http://www.tomshardware.com/answers/id-3163253/wake-lan-working-intermittently.html
March 15, 20179 yr Author It's the weirdest thing. I write about the problem here and *poof*, it mysteriously vanishes... Thanks everybody for the advice, anyway.
Archived
This topic is now archived and is closed to further replies.