September 1, 201312 yr Hi guys i having a peculiar problem where my server doesn't go to s3 Sleep once i initiate it ( i am currently testing with the latest version 5, and also as barebones as possible (only added simplefeatures base and S3 sleep packages). I initially thought it was my cache drive and other plugins causing the issue, but after eliminating each, the issue still remains. the server goes missing on the network for about 2/3 minutes, but doesn't physically power down. Looking at the syslog, it seems like it is complaining about some of the drives. some of the entries : ata9.00: failed command: STANDBY IMMEDIATE PM: Device 10:0:0:0 failed to suspend async: error 134217730 sd 10:0:0:0: [sdc] START_STOP FAILED sd 9:0:0:0: [sdb] Stopping disk Sep 1 13:27:24 Storage kernel: PM: Some devices failed to suspend now some entries refer to ata9, some to sd9 / sd10 and some to sdb/sdc confusing part is that sdb is disk 11 on the gui, and sdc disk 10... will somebody please be able to assist in pointing out how i could determine which drives is a possible cause, so that i can try moving / swapping them around in order to determine if it is a drive and/or controller issue? regards Neo_X 20130901_syslog.txt.txt
September 1, 201312 yr I also just upgraded to 5.0 final and now I'm trying to get the s3 sleep functionality back. It seems /proc/acpi/sleep is no longer included with the latest unraid distro. That's what I was using to sleep my 4.7 servers. I like to put my servers to sleep when not in use to save power and reduce noise. I don't have any answers/solutions yet but I am searching...
September 1, 201312 yr This might work, it's from about a month ago... http://lime-technology.com/forum/index.php?topic=28834.0
September 2, 201312 yr This might work, it's from about a month ago... http://lime-technology.com/forum/index.php?topic=28834.0 Thanks for the link! I was able to get my 5.0 servers to sleep by manually entering the following at the command prompt: echo -n mem > /sys/power/state They also wake up successfully via network magic packet. Now I'll need to see if I can somehow incorporate the above command into an automated sleep script that puts the server into S3 sleep after X amount of inactivity.
November 13, 201312 yr Hi guys i having a peculiar problem where my server doesn't go to s3 Sleep once i initiate it ( i am currently testing with the latest version 5, and also as barebones as possible (only added simplefeatures base and S3 sleep packages). I initially thought it was my cache drive and other plugins causing the issue, but after eliminating each, the issue still remains. the server goes missing on the network for about 2/3 minutes, but doesn't physically power down. Looking at the syslog, it seems like it is complaining about some of the drives. some of the entries : ata9.00: failed command: STANDBY IMMEDIATE PM: Device 10:0:0:0 failed to suspend async: error 134217730 sd 10:0:0:0: [sdc] START_STOP FAILED sd 9:0:0:0: [sdb] Stopping disk Sep 1 13:27:24 Storage kernel: PM: Some devices failed to suspend ... I am seeing this same situation on one of the unraid systems I maintain. Did you ever figure this out?
Archived
This topic is now archived and is closed to further replies.