Hi,

I recently have issues waking up from S3. I'm not sure what's causing this, but I believe it might be related to recent UnRaid updates.
Sometimes (not always, say 1 out of 3 times) the system doesn't wakeup from sleep properly.

All my containers are running just fine and are accessible through the reverse proxy I run (traefik, also as a container). However UnRAID's webui and SSH are not responding.

This morning it happened again, and I had setup syslog to write to my array to debug this and set the sleep plugin to debug log.

Attached is the log run. I don't see anything out of the ordinary (I believe, no expert on this) except for this line;

br0: carrier lost

The docker containers I run do not use this bridge/network but once I created myself (which could explain why I can access my containers but maybe!? not unraids webui, although I'm unsure whether it uses this bridge to communicate).

In the logs you find this line when I woke up the system;

Jun 5 06:16:19 GotGeeks s3_sleep: Wake-up now

At the end of the log you see I've shutdown the system in order to reboot it (could not restart, since I couldn't access SSH or the webgui)

I'm not 100% confident that it's an UnRaid issue since I also recently updated my BIOS/UEFI (which is a piece of **** on this board, had many issues with it already).

Any advice or help would be greatly appreciated. And if I missed out on some information that might help diagnose this issue, please tell me.

Thanks in advance

Edited June 10, 20251 yr by joz

you may need a wake on lan or secondary script to stop/start (Restart) dockers when s3 wakes up and leaves the power states...

as the dockers still try to run when palced in to idel lose network and error out when this occurs... I honestly wouldn't use sleep and disable sleep on unraid. let the disk spin down be your sleep like state to save power/electric costs.

some bios options have setting when the device enter s3 trying to engage s5 and adational memry / parts can become corupted. form time counters and other settings like fast startup taht can corrupt ram.

Unraid sits in ram so I don't advise the use of sleep / Wake on Lan...
Double check soem bios settings turn off s5 / s4 use s3 only and turn off fast startup. double check usb power when asleep to make sure there is no los to usb drive access as well...

review:

Set up Wake-on-LAN (WOL) | Unrai...

Set up Wake-on-LAN (WOL) | Unraid Docs

You can set up the Unraid server to wake up from a shutdown or sleep state by sending what is known as a magic packet over the network. A magic packet is a special data packet that contains the tar...

Setup Sleep (S3) and Wake on Lan...

Setup Sleep (S3) and Wake on Lan (WOL) | Unraid Docs

The following are my notes for setting up my Unraid server to sleep to