Dynamix - S3 Sleep


Recommended Posts

Yeah that would be great. I got slammed with work while your were on vacation anyhow. I am wrapping things up today, so I should be able to get to those logs.

I've finally got work projects under control. I now have time to dig and and get the necessary logs. Okay, syslog zipped and attached. I had just chosen to disable the S3 plugin and hit apply, when the webGUI became unusable. Then I grabbed the syslog and my sleep config file.

log.zip

Link to comment
  • Replies 117
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Here is a new syslog where I uninstalled all the Dynamix plugins except; plugin control and WebGUI. After doing so, I then enabled the sleep plugin and pressed Apply. I still got the error message at the bottom of the screen. This time the WebGUI did not lock up though.

 

The s3_sleep.log only contains lines tell me if drives are idle or not. No real debugging info.

Mon Aug 25 10:42:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:43:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:44:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:45:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:46:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:47:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:48:36 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:49:36 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:50:36 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:51:36 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:52:10 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:52:17 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:53:17 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:54:17 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 10:55:17 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle
Mon Aug 25 13:10:59 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:11:59 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:12:59 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:13:59 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:14:59 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:16:00 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:17:00 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:18:00 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:19:00 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:20:27 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:20:39 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle
Mon Aug 25 13:21:39 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle

 

 

syslog.zip

Link to comment

I had it once that the s3 script (and subsequently the GUI) was hanging while reading "/proc/mdcmd". Not sure why it happened and can't reproduce it.

 

When the GUI is hanging you might want to check if the S3 script is running, and kill it so see if the GUI starts responding again.

Link to comment

Thanks. I'll try that. Any ideas about the odd error message I see at the bottom of the Sleep plugin page when I hit Apply?

 

Uhoh, looks like a good time to test it. I just hit Apply again in order to see the error at the bottom of the screen and the webGUI just hung.

 

I killed the s3 script using "s3_sleep -q", but the gui is still hung. Nothing new is in the syslog.

 

 

Link to comment

Thanks. I'll try that. Any ideas about the odd error message I see at the bottom of the Sleep plugin page when I hit Apply?

 

Uhoh, looks like a good time to test it. I just hit Apply again in order to see the error at the bottom of the screen and the webGUI just hung.

 

Sorry what error message are you referring to ?

Link to comment

This one.

Warning: implode(): Invalid arguments passed in /usr/local/emhttp/update.sleep.php on line 13

 

Also see above. I tired killing the script but my GUI is still hung. I still have access to the tower using my iKVM or telnet and everything else is working, but the weGUI will not respond.

Link to comment

Can you show the content of your s3 configuration file (see example below) ?

 

root@vesta:~# cat /boot/config/plugins/dynamix/dynamix.s3.sleep.cfg

service="0"

checkHDD="-a"

timeout="30"

interval="3"

port="bond0"

checkTCP=""

idle="0"

login="-L"

pingIP=""

stopDay="0,6"

stopHour=""

dhcpRenew=""

forceGb=""

setWol=""

preRun=""

postRun=""

debug="0"

exclude=""

excludeList=""

options=""

root@vesta:~#

Link to comment

Here you go:

 

service="1"

checkHDD="-a -c"

timeout="30"

interval="3"

port="eth0"

checkTCP=""

idle="0"

login=""

pingIP=""

stopDay=""

stopHour=""

dhcpRenew=""

forceGb=""

setWol=""

preRun=""

postRun=""

debug="3"

exclude=""

excludeList=""

options="-C 1 -a -c -m 30 -e eth0 -D 3"

Link to comment

There is a coding error, need to look further into that (php is trying to perform an 'implode' action on a wrong variable type). This error happens only when you have disks outside the array.

 

Probably GUI is hanging now on this particular PHP script, unfortunately I don't have an easy way to stop this, other then rebooting your system, sorry.

 

(some corrections to make my answer sensible)

Link to comment
  • 1 month later...

Don't you think S3 should supported by default in Unraid?

Official support would be limited to a small list of known working hardware combinations. It would be very difficult, or impossible to fully support all the possible combinations of motherboards with various BIOS updates, HBAs, and network cards that each have their own quirks about S3. I think at the moment Tom doesn't want to deal with certifying components for unraid builds, other than the ones he sells. It's a never ending cycle of new parts and BIOS upgrades to deal with.

 

I think the basic issue is that server grade parts are typically used in an always on environment, so most parts that have lots of available SATA ports aren't designed with S3 in mind.

Link to comment
  • 1 month later...

I got both my servers to sleep/wake about a month ago after a few hardware changes. I set them both to sleep after 30 mins of inactivity. It was working great.

Recently my TV Show server won't go to sleep after a period of inactivity but my Movie server does. Where do I start in troubleshooting this?

Link to comment

Look at the main page to see which drives are still spun up. Also look a the syslog.

If all drives are spun down, look to see if you enabled the check for logins or network connectivity.

 

I got both my servers to sleep/wake about a month ago after a few hardware changes. I set them both to sleep after 30 mins of inactivity. It was working great.

Recently my TV Show server won't go to sleep after a period of inactivity but my Movie server does. Where do I start in troubleshooting this?

Link to comment

Hmm, the 7th drive 'sdg' is being read constantly. Other drives have a few thousand reads tops but sdg is on 850,000 reads after booting up two hours ago and not stopping.

I have had problems shutting down the server because drive 7 wouldn't unmount and had to force it. Could the drive be on its way. Nothing else seems to point to a drive fault.

Link to comment
  • 6 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.