Im not really sure what happened after i upgraded to rc12. Ive always had simplefeatures installed with the sleep plugin and ive never had an issue with my array going to sleep x amount of time after the drives spin down. Now when I turn on sleep and set it to sleep 15mins after drive inactivity the server never sleeps. Does anybody else have ths issue or know why the sleep function stopper working?

 

I can use sleep from the simpleFeatures main menu and it puts my server to sleep so i know that sleep does work.

 

Thanks

I had to change the disk spindown to 15 mins on one of my disks as it wasn't picking up the default.

This was in a previous version though. No idea if it's been fixed and possibly unfixed...

Worth a try anyway.

Just doing a parity check, will change spin-down time from 'default' to '15 mins' for all disks manually and see if that makes a difference. Though Ive noticed that on default, and setting the global spin-down time to 15mins that all my disks are spun-down since the green ball is flashing. But its worth a shot I guess.

Ive upgraded to the latest rc15. Within simpleFeatures it says ive got "s3_sleep version: 2.1.0" and I have

- 'Wait for array inactivity' to 'Yes'

- 'Extra delay after array inactivity' to '1'.

- 'Wait for network inactivity' to 'No'

- 'Wait for user login inactivity' to 'No'

 

I manually spin down the drives and wait but the server wont shutdown. Doing it this way to test sleep used to work everytime but for some reason since rc12 its stopped working. I can manually put the server to sleep and it goes to sleep/wakes up perfectly - not sure why Unraid wont send the sleep command?

 

I tried changing the spin down times in the actual disk, then also changing them back to 'use default' which is 15 mins - but that shouldnt matter since when I refresh the page even after 20 mins its showing the drives as asleep.

 

Also does it matter if I have a drive attached thats not in the array? I am using that as a backup?

Also i enaled debugging for the sleep plugin - here is the log:

 

Jun 16 13:05:40 Tower logger: /usr/sbin/rpc.nfsd 8

Jun 16 13:05:40 Tower logger: /usr/sbin/rpc.mountd

Jun 16 13:05:40 Tower mountd[19356]: Kernel does not have pseudo root support.

Jun 16 13:05:40 Tower mountd[19356]: NFS v4 mounts will be disabled unless fsid=0

Jun 16 13:05:40 Tower mountd[19356]: is specfied in /etc/exports file.

Jun 16 13:05:40 Tower emhttp: shcmd (278): /usr/local/sbin/emhttp_event svcs_restarted

Jun 16 13:05:40 Tower emhttp_event: svcs_restarted

Jun 16 13:06:40 Tower logger: s3_sleep: Disk activity detected. Reset all counters

Jun 16 13:06:42 Tower s3_sleep: ==============================================

Jun 16 13:06:42 Tower s3_sleep: command-args=-q

Jun 16 13:06:42 Tower s3_sleep: action mode=sleep

Jun 16 13:06:42 Tower s3_sleep: check array=no

Jun 16 13:06:42 Tower s3_sleep: exclude cache=-

Jun 16 13:06:42 Tower s3_sleep: check network=no

Jun 16 13:06:42 Tower s3_sleep: check device=

Jun 16 13:06:42 Tower s3_sleep: check SSH=no

Jun 16 13:06:42 Tower s3_sleep: check TTY=no

Jun 16 13:06:42 Tower s3_sleep: version=2.1.0

Jun 16 13:06:42 Tower s3_sleep: ----------------------------------------------

Jun 16 13:06:42 Tower s3_sleep: killing s3_sleep process 19271

Jun 16 13:06:42 Tower s3_sleep: ==============================================

Jun 16 13:06:42 Tower s3_sleep: command-args=-C 1 -a -m 1 -e eth0 -F -w g -D 1

Jun 16 13:06:42 Tower s3_sleep: action mode=sleep

Jun 16 13:06:42 Tower s3_sleep: check array=yes

Jun 16 13:06:42 Tower s3_sleep: exclude cache=-

Jun 16 13:06:42 Tower s3_sleep: check network=no

Jun 16 13:06:42 Tower s3_sleep: check device=

Jun 16 13:06:42 Tower s3_sleep: check SSH=no

Jun 16 13:06:42 Tower s3_sleep: check TTY=no

Jun 16 13:06:42 Tower s3_sleep: version=2.1.0

Jun 16 13:06:42 Tower s3_sleep: ----------------------------------------------

Jun 16 13:06:42 Tower s3_sleep: s3_sleep process ID 20139 started, To terminate it, type: s3_sleep -q

Jun 16 13:06:42 Tower logger: s3_sleep: Disk activity detected. Reset all counters

Jun 16 13:06:51 Tower emhttp: Spinning down all drives...

Jun 16 13:06:51 Tower kernel: mdcmd (37): spindown 0

Jun 16 13:06:52 Tower kernel: mdcmd (38): spindown 1

Jun 16 13:06:53 Tower kernel: mdcmd (39): spindown 2

Jun 16 13:06:54 Tower kernel: mdcmd (40): spindown 3

Jun 16 13:07:42 Tower logger: s3_sleep: Disk activity detected. Reset all counters

Jun 16 13:08:42 Tower logger: s3_sleep: Disk activity detected. Reset all counters

I think i've solved this issue, though it raises another one.

 

I had an extra drive in the system that was attached & precleared but not part of the array. I figured maybe it was that disk that was making activity on the system. I removed that 'hot spare' and then voila the simplefeature sleep script worked perfectly....now all I have to figure out is how to wake the system back up

 

Does anybody know what that extra drive was showing activity? I thought since its outside of the array it would never really be spun up.

The s3_sleep script will check drives outside the array for disc activity. If a preclear was running, it wouldn't be nice if the sever went to sleep. If no process is accessing the drive it should spin down and the script should sleep the server.

 

If the drive doesn't spin down for whatever reason, the system would'nt sleep. Or if the drive reports a state the script doesn't recognize as  spun down, the system would'nt sleep either.

 

I have a ssd that always reports active and therefore prevents sleep when installed.