Though this old thread http://lime-technology.com/forum/index.php?topic=33619.msg309926#msg309926 had this issue along with other problems, I couldn't find a solution to being no video after unraid wakes from sleep.  Was doing it on v5 also.

S3 sleep is a complex and problematic thing, with numerous compatibility issues, and it's a wonder whenever it actually DOES work!  That must be why there's so little official support for it, unless the hardware and software is specified.  I've looked at syslogs where it worked, and it looks like numerous subsystems are broken(!), then slowly reset themselves and self-heal, hopefully enough to bring the whole system back to life.

 

Your hardware and software have to be compatible.  To give yourself the best chance of success, make sure your BIOS and addon card firmware is fully updated.  After that, you may have to upgrade hardware components.  Newer and better quality components are more likely to work.

Thanks for the reply and unfortunately my experience jives with yours.  I had years of my unraid's WOL and sleep not working, then suddenly it did!  But somewhere along the way I lost video on waking.

 

Now that I've just changed my mobo (to an old Gigabyte EP43-UD3L with the last firmware released) I'm back to starting over.  My WOL works but still the same no video on wake.  Additionally, I have a remote system that wakes my unraid by closing the circuit of the PC's power switch.  On this new setup it sometimes works but other times it does a hard reboot (which then triggers a parity check).  Still trying to fix that one and have played with the BIOS with little success.  It almost seems like if I manually press the GUI sleep button I can properly wake the unraid with the power switch, but if it sleeps due to my defined inactivity, the power button reboots. 

...  It almost seems like if I manually press the GUI sleep button I can properly wake the unraid with the power switch, but if it sleeps due to my defined inactivity, the power button reboots.

 

That would be weird, cause both use exactly the same command to put the system to sleep, though the button is unconditionally and there might be more activity while the system is put to sleep.

 

That would be weird, cause both use exactly the same command to put the system to sleep, though the button is unconditionally and there might be more activity while the system is put to sleep.

 

Agreed that there should be no difference on manual sleep vs automatic, but what do you mean there might be more activity while the system is put to sleep?  Thanks.

That would be weird, cause both use exactly the same command to put the system to sleep, though the button is unconditionally and there might be more activity while the system is put to sleep.

 

Agreed that there should be no difference on manual sleep vs automatic, but what do you mean there might be more activity while the system is put to sleep?  Thanks.

 

I meant disks may be running and may even have active I/O, or network transfers may be on going, in short the system is doing its thing