hi everyone first post , I have got everything running well with the latest rc.

only issue I have is using the simplefeatures i configure it to sleep, it works once i can WOL no problem but then the second time it goes in to sleep the hd's spin down and monitor goes off but the cpu and fans are still running. I am unable to do anything but power it down and restart it. I have searched and found a solution but I can't figure out how to apply it to unraid can someone help? here is what is posted his motherboard is identical to mine.

 

 

Under Linux, my computer freezes while trying to "sleep". The strange thing is, it works fine the first time my computer sleeps after I boot it up. The second time around, however, my monitor fails to power down, several of the fans in my case continue spinning, and then my computer becomes completely unresponsive.

 

This issue happens under the following distros:

 

Ubuntu 10.10 x64

Ubuntu 10.10 32-bit

Peppermint Ice

Ubuntu 10.04.1 x64

Mint Debian

OpenSuse 11.3 x64

 

This issue does *not* happen under Windows!

 

I've tried changing just about every setting possible in my BIOS. I loosened the memory timings, tried enabling and disabling 64-bit hardware memory remapping, and I tried disabling Cool N Quiet.

 

My rig:

 

Opteron 165

Asus A8N-E (Nforce 4 motherboard)

4gb DDR ram

8800GTS 320mb

 

I also tried pulling out my memory sticks and running with just one stick of ram. This did nothing to solve the problem.

 

If any of you have any insight into this problem I would really appreciate it!

 

TIA

 

*edit*

 

I've solved this problem by adding "acpi_sleep=old_ordering" to my boot/grub/grub.cfg file. You need to put it after the kernel near where it usually says "quiet splash".

 

It turns out this is a bug in the Linux kernel since 2.6.22.

 

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/347150

 

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/210543

I can't get a syslog because unraid becomes unresponsive , is there a way that unraid will save the syslog before over righting it? or just not over right at all?