Here is a strange one. I decided to play around with the S3 sleep screen in unmenu. Tested it once and the server went to sleep fine. So decided to check the BIOS to make sure that WOL was enabled. So in the unraid menu, I stopped the array and hit the power down button. The server powers down and then immediately powers back up. Even weirder is now when I hit the S3 sleep button in unmenu it goes to sleep and immediately wakes back up. Didn't make any BIOS changes.

 

Any ideas? The server used to shutdown fine.

 

 

Here is a snip of my syslog when I now try to enable sleep:

 

http://pastebin.com/TKyupME8

Here is a strange one. I decided to play around with the S3 sleep screen in unmenu. Tested it once and the server went to sleep fine. So decided to check the BIOS to make sure that WOL was enabled. So in the unraid menu, I stopped the array and hit the power down button. The server powers down and then immediately powers back up. Even weirder is now when I hit the S3 sleep button in unmenu it goes to sleep and immediately wakes back up. Didn't make any BIOS changes.

 

Any ideas? The server used to shutdown fine.

 

 

Here is a snip of my syslog when I now try to enable sleep:

 

http://pastebin.com/TKyupME8

Get a new copy of the sleep button.  It was accidentally written to wake on any activity on the lan, not just WOL packets.

See here: http://code.google.com/p/unraid-unmenu/source/diff?spec=svn69&r=58&format=side&path=/trunk/85-unmenu_user_script_sleep&old_path=/trunk/85-unmenu_user_script_sleep&old=7

 

fixed on the 17th.

 

You may have a few unMENU files that need updating.  There have been continual fixes.  Once they are in place it might be easiest to just reboot to get your settings into place on the network port.

Get a new copy of the sleep button.  It was accidentally written to wake on any activity on the lan, not just WOL packets.

See here: http://code.google.com/p/unraid-unmenu/source/diff?spec=svn69&r=58&format=side&path=/trunk/85-unmenu_user_script_sleep&old_path=/trunk/85-unmenu_user_script_sleep&old=7

 

fixed on the 17th.

 

Thanks Joe, I went ahead and updated my sleep script. It did not solve my issue though. Still does the same thing, and it also does this when I actually try a power down in the unmenu main menu, machine reboots instead of powers down.

Get a new copy of the sleep button.  It was accidentally written to wake on any activity on the lan, not just WOL packets.

See here: http://code.google.com/p/unraid-unmenu/source/diff?spec=svn69&r=58&format=side&path=/trunk/85-unmenu_user_script_sleep&old_path=/trunk/85-unmenu_user_script_sleep&old=7

 

fixed on the 17th.

 

Thanks Joe, I went ahead and updated my sleep script. It did not solve my issue though. Still does the same thing, and it also does this when I actually try a power down in the unmenu main menu, machine reboots instead of powers down.

Did you also update the acpi handler script?  It too was updated as part of the powerdown package.

 

Joe L.

No, I did not, but after I did my last reply I decided to do a complete unmenu upgrade to the very latest so that should have updated it. Can't test at the moment since I had to power down the server and now for some reason it is doing a parity check, maybe I initiated it unintentionally but I'll let that finish and then test the power down and s3 script.

No, I did not, but after I did my last reply I decided to do a complete unmenu upgrade to the very latest so that should have updated it. Can't test at the moment since I had to power down the server and now for some reason it is doing a parity check, maybe I initiated it unintentionally but I'll let that finish and then test the power down and s3 script.

Since the old package.auto_install scripts were still in your /boot/packages directory you might still have the same problems.  They are not automatically updated just because you updated unMENU itself.  That will only occur if you disable them and then re-enable them.

 

Once your parity check finishes, disable the re-install on re-boot options in unMENU, then, stop the array, then reboot.

Once rebooted, you can re-enable whatever you like.

 

Sorry for any inconvenience.

 

Joe L.

Here is a strange one. I decided to play around with the S3 sleep screen in unmenu. Tested it once and the server went to sleep fine. So decided to check the BIOS to make sure that WOL was enabled. So in the unraid menu, I stopped the array and hit the power down button. The server powers down and then immediately powers back up. Even weirder is now when I hit the S3 sleep button in unmenu it goes to sleep and immediately wakes back up. Didn't make any BIOS changes.

 

Any ideas? The server used to shutdown fine.

 

 

Here is a snip of my syslog when I now try to enable sleep:

 

http://pastebin.com/TKyupME8

 

The exact same thing happend to me. Unplugging the ethernet stopped the symptom (not the problem).

 

In the forum somewhere I found this solution:

change the last line in "85-unmenu_user_script_sleep"

from

ethtool -s eth0 wol gp

to this:

ethtool -s eth0 wol g

 

edit: As far as I learned in this forum a parity check occurs e.g. after a "dirty" power down.

Just wanted to say thanks Joe, was able to get everything squared away and seems to be working as intended now.