Hi,

 

I want to put my server in S3 sleep state through the user script available in unmemu, but it states /proc/acpi/sleep file missing.

 

Checked my s3 state in bios and is activated.

Checked my wake on lan option in bios and is activated.

Checked wake on lan option in eth0 config and is set to "g".

What am I missing here ?

 

/proc/acpi/sleep is not used anymore. Try

echo -n mem > /sys/power/state

Doesn't work,

 

when using the command as proposed, the server just shuts down, no means to wakeit up again (eept power switch of course).

Hmm,

 

I've noticed that the nic on the mobo is a realtek (8111 in particular).

I've read on the forum that there where some problems with WOL on realtek nic's with unraid, but that these should be resolved in rc16c.

Is this the case for all realtek nic's or is the 8111 still known to pose problems ?

I really could use some help here, since i'm a complete linux noob

 

Today tried another mobo (h2000m) with a temporary unraid rc16c  with s3 sleep with the  command, and it gets even worse, when running the  echo -n mem > /sys/power/state and now I get the message "file or directory not found".

With my socket 775 mobo with realtek nic, the mobo justs shuts down instantly rsulting in parity check afterwards.

Installing the simplefeatures package results in pc hanging at boot procedure on acpi process (unraid doesn't boot anymore)

 

 

Thx,

 

Before writing "mem" to /sys/power/state , try reading from it:

cat /sys/power/state

If mem is not listed there, then that particular mobo/cpu doesn't support suspend to "mem", and you shouldn't be echoing "mem" to /sys/power/state

 

Update:

On mobo 1 (amd server)

only "freeze" and "standby" seem to be listed. Pity since wol can be set in mobo bios and can even be activated in nic bios.

Would setting acpi from 2.0 to 3.0 in bios change anything ?

If I understand well, If the "mem" option under /sys/power/state isn't present I shouldn't bother trying to get the mobo to s3 sleep state, this incompatibilty could be due to mobo,nic or cpu ?

I've included a full syslog on this mobo to see which may cause incomptibility, maybe a nic driver related problem (broadcom nic's) ?

 

On mobo2 (old socket 775)

"freeze" and "sleep" are present

so this board should be working ?

though the echo mem > /sys/power/state returns a blank black screen.

 

You could also see if you can get something with:

grep -i s3 /var/log/syslog

 

The grep command returned the following resulton the amd setup:

kernel DMI empty empty/s3992

kernel ACPI exeption AE_NOT_FOUND, while evaluating sleep state

 

The grep command on the intel setup returned the following

kernel acpi supports s0 s3 s5

additionally it lists 3 of my hard drives

 

so this board should be working, what could be going wrong ?

the echo mem > /sys/power/state returns a blank black screen, server powers completely off, and when restarted a parity check is required.

 

 

 

If I can't bring any of the boards that I actually have, to sleep then I will be forced to buy something else, as for now I consider s3 sleep a must have priority for my unraid array since it's really hard to find really power efficient and performant always on hardware

So in the worst case scenario can anyone recommend a mobo/cpu combo that actually supports s3 mem sleep with unraid rc16c?

 

 

 

 

syslog-2013-08-10.txt

Ive managed to make some progress with the socket 775 combo.

 

After manually spinning down the disks in unraid and executing the echo -n mem > /sys/power/state command the pc goes to what I think s5 state since no leds are powered on, neither does the nic blink in anyway ( on my windows machines s3 state leaves power button and nic leds blinking.

 

Some tuning in bios revealed that power on after suspend on pci-express device needed to be enabled for the wol magic pakket to be working. This cause the omboard nic seems to be a pci-e device.

 

Wol magic pakket now turns the pc back on (al fans running), but it doesn't seem to boot my unraid array (blank screen with blinking cursor).

 

I don't know what to be looking at next, maybe some other bios setting that prevents booting up properly ?

 

Wol magic pakket now turns the pc back on (al fans running), but it doesn't seem to boot my unraid array (blank screen with blinking cursor).

 

I don't know what to be looking at next, maybe some other bios setting that prevents booting up properly ?

I see this same issue with any build after Unraid RC 12a. There is an old post/thread about this and so far no solution that I am aware of.

The issue with some realtek nic's should have been resolved in rc16c according to this topic.

 

http://lime-technology.com/forum/index.php?topic=27786.0

 

Problem seems to be resolved for realtek 8111E nic's

 

In my case (realtek 8111B) the problem persists.

 

'kricker'

As I've looked at your previous topic I do have two power states present which are 'freeze' and 'mem' , it's as you described the server seem to wake from s3 mem to freeze state, but never boots the unraid software.

My NIC is Intel so the realtek "fix" means nothing for my system.

 

If I ever get time, I need to read more about the "freeze" state and see if there is a way to disable it and figure out why "mem" does not show up as a state in newer builds of unRaid. Is it a kernel , driver or unRaid software issue.

Update to my sleep situation. Hint...I have success!

http://lime-technology.com/forum/index.php?topic=28055.msg271555#msg271555