Fixed server's "insomnia" -now missing recordings?

[timg11]

Somewhere along the line with Windows Updates, one of them changed something that caused the server to never sleep when idle.

I used "POWERCFG /LASTWAKE" to determine the NIC was the cause.
In the system log, I saw sleep transitions, then 1 second later it woke up.

Under the NIC properties, Power Management Page,
"Allow this device to wake the computer" was checked, but "Only allow a magic packet to wake" was not. I checked "only allow magic packet to wake".
(Note - I sometimes use WOL with magic packet to remotely wake the system for backup or management tasks, and of course the HD-300 uses WOL to wake the server)

Now the SageTV server is sleeping when idle. I'm monitoring it's state with another system that logs when it pings or does not ping.

It wakes in time for shows, but does not record them. If I manually record the favorite that was supposed to be recording, the UI shows two instances of the favorite recording. Other shows that were supposed to be recording on other sources will also start recording once I manually start something recording. However, if I then try to play one of the shows while they are recording, SageTV hangs.

I have to reboot the server to get things running properly again.

Can anyone provide guidance on how to diagnose this situation? I'd rather not have to disable sleep and run the server 24/7.

[timg11]

Crickets... I'm back disabling sleep and running 24/7 for now until I can learn more. So maybe it's just my system?

Could anyone confirm that they have a Windows 10 64 bit system running as a SageTV server, that is able to reliably wake to record shows and enter sleep when idle and not recording?

[Striker:WG]

Sorry, I'm running a Sage docker on an Unraid server that's on 24/7.

When I did run a Windows server it doubled as my main payback system as well and was also on 24/7.

[trk2]

I run Windows 10 64 bit with working sleep. I had problems getting it to work correctly but I didn't experience the issues you're describing. It's been years since I fixed it but I do remember having to configure Windows to only use the S3 sleep state, disabling hybrid sleep, and disabling fast startup.

[timg11]

Originally Posted by trk2

I run Windows 10 64 bit with working sleep. I had problems getting it to work correctly but I didn't experience the issues you're describing. It's been years since I fixed it but I do remember having to configure Windows to only use the S3 sleep state, disabling hybrid sleep, and disabling fast startup.

Thanks - I only have S3 sleep available according to POWERCFG, and fast startup is already disabled. I have not disabled hybrid sleep. I'll try that.

I have these settings in the Ethernet driver:
Advanced EEE - Disabled
Energy Efficient Ethernet - Disabled
Green Ethernet - Disabled
Power Saving Mode - Enabled
Shutdown WOL - Enabled
Wake on Magic Packet - Enabled
Wake on Magic Packet when sys... - Enabled
Wake on Pattern Match - Enabled
WOL and Shutdown link speed - 10 mbps

These settings for Ethernet Power Management tab.
Allow the computer to turn off this device to save power - Unchecked
Allow this device to wake the computer - Unchecked
Only allow a magic packet to wake the computer - Checked

The last two items are grayed out when the first is unchecked. The setting "Allow this device to wake the computer" prevents sleep because apparently any LAN packet will wake the computer, so it sleeps only for a fraction of second. I'm not sure why that configuration would be useful in the real world.

The computer is waking from SageTV's wake timers now, but it is ignoring WOL from Magic Packet from HD300 or other computers running wolcmd.exe.

[trk2]

Have you checked the BIOS? Some motherboards have a setting to enable WOL in the BIOS (typically in power management or peripheral config).

[timg11]

Originally Posted by trk2

Have you checked the BIOS? Some motherboards have a setting to enable WOL in the BIOS (typically in power management or peripheral config).

WOL used to work, and I haven't changed anything in the BIOS since I built the system. But I did check to see if there is something relevant. Anything look like it would interfere with WOL?




I had to look up some of the items:
PEG ASPM: PCI Express Graphics
PCH ASPM: Allows you to configure the ASPM mode for both CPU side and Chipset side of the DMI link. (DMI = Desktop Management Interface or Direct Media Interface? )
DMI ASPM: Allows you to configure the ASPM mode for both CPU side and Chipset side of the DMI link.

[timg11]

After trial and error of many settings, I found a configuration where Wake On Lan works.

I'm documenting the settings here in case it helps anyone: