September 22, 20169 yr Hi, As everything was working well with 6.1.9 I waited until the next stable Unraid version to upgrade to. Apart from some hickups, everything is running fine again, except S3_Sleep. It appears as if the shutdown script is not executed, because it says "Shutdown system now" and then nothing happens. See part of the log: Sep 22 21:22:26 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:22:26 Stacker s3_sleep: Extra delay period running: 1 minute(s) Sep 22 21:23:26 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:23:26 Stacker s3_sleep: Extra delay period running: 0 minute(s) Sep 22 21:23:26 Stacker s3_sleep: Check TCP/SSH/TTY/IP activity Sep 22 21:23:26 Stacker s3_sleep: Communication state is idle Sep 22 21:23:26 Stacker s3_sleep: Shutdown system now Sep 22 21:23:26 Stacker s3_sleep: System woken-up. Reset timers Sep 22 21:24:26 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:24:26 Stacker s3_sleep: Extra delay period running: 1 minute(s) Sep 22 21:25:26 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:25:26 Stacker s3_sleep: Extra delay period running: 0 minute(s) Sep 22 21:25:26 Stacker s3_sleep: Check TCP/SSH/TTY/IP activity Sep 22 21:25:26 Stacker s3_sleep: Communication state is idle Sep 22 21:25:26 Stacker s3_sleep: Shutdown system now Sep 22 21:25:26 Stacker s3_sleep: System woken-up. Reset timers Sep 22 21:26:26 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:26:26 Stacker s3_sleep: Extra delay period running: 1 minute(s) Sep 22 21:27:27 Stacker s3_sleep: All monitored HDDs are spun down Sep 22 21:27:27 Stacker s3_sleep: Extra delay period running: 0 minute(s) Sep 22 21:27:27 Stacker s3_sleep: Check TCP/SSH/TTY/IP activity Sep 22 21:27:27 Stacker s3_sleep: Communication state is idle Sep 22 21:27:27 Stacker s3_sleep: Shutdown system now Sep 22 21:27:27 Stacker s3_sleep: System woken-up. Reset timers Please help to resolve, because this is really just a media server, only woken up to watch something after which it should shutdown automatically. Note: pushing the sleep button, the system indeed goes to sleep (but due to some incompatibilities it will not wake up from sleep). Fortunately, shutdown did the job perfectly.
September 23, 20169 yr Same issue waking from sleep after 6.2 upgrade. WOL does seem to wake server but GUI is unresponsive. On an AMD FX processor. 6.1 was fine though.
September 23, 20169 yr Author No it has nothing to do with the CPU. The behaviour of not waking from sleep was already with 6.1.9, because of the SAS controller card not detected and thus the array not started. But I had no problem with it, because I just had s3_sleep have it shutdown, after which I could WOL it. But now - since the upgrade to 6.2 - it is not shutting down anymore automatically. Manually shutting down and WOL'ing is working fine. In my opinion the shutdown script or powerdown script is not called or found from s3_sleep.
September 24, 20169 yr I had the same problem after upgrading from 5.something to 6.2. You are right in assuming that the sleep script doesn't find the powerdown script. After finding out how to modify a plugin with some trial and error (Is there any documentation about the correct procedure to set up a plugin for unRAID 6?) I came up with this solution. It calls the powerdown script using the full path. Please install it from here: https://raw.github.com/rgls/dynamix/master/unRAIDv6/dynamix.s3.sleep.plg and try if it solves your problem as well. You'll have to uninstall the original version before installing this one.
September 25, 20169 yr Glad I could help. The patch has now been applied to bergware's original version. Don't forget to switch back to his version in order to receive further updates.
Archived
This topic is now archived and is closed to further replies.