March 10, 201016 yr Hi. Over night I noticed that my server didn't sleep as it would normally do. My server would normally placed any unused HDDs to sleep after 30mins, once all HDDs are asleep, it would then run the 's3.sh' script to sleep the whole server. All HDDs we're still active this morning as if their were all in use. The unraid main site indicated little read/writes to the drives, mainly one drive which might of been generated the night before as I was copying files to it. To my knowledge, all clients which connect to it was off. I rebooted the server via the unraid web site, it booted fine, after 30 mins, as usual all HDDs slept, the s3.sh script kicked in and the server fell asleep soon after. Im running 4.5.3 Pro. Any reason what caused all the disks not to sleep thus preventing the 's3.sh' script not to run?
March 10, 201016 yr The unraid main site indicated little read/writes to the drives, mainly one drive which might of been generated the night before as I was copying files to it. I think you answered your own question - something was accessing it.
March 11, 201016 yr Author Quote "To my knowledge, all clients which connect to it was off." unquote. Last I looked at it, a had a client copying files it it at about 9.30pm, and I scheduled that client to switch off when it was complete, which it did that just fine and completed the copying of files and the client switched off before 10pm. All clients which only connect to it were switched off, which doesn't explain why the servers HDDs were all still running. I discovered this at 5.30am this morning, so what it was way after the 30 mins which it would normally take, it was running like this for several hours. No I haven't really answered my question, but I should of gave more details on the subject though. Thanks. The unraid main site indicated little read/writes to the drives, mainly one drive which might of been generated the night before as I was copying files to it. I think you answered your own question - something was accessing it.
March 11, 201016 yr Quote "To my knowledge, all clients which connect to it was off." unquote. Last I looked at it, a had a client copying files it it at about 9.30pm, and I scheduled that client to switch off when it was complete, which it did that just fine and completed the copying of files and the client switched off before 10pm. All clients which only connect to it were switched off, which doesn't explain why the servers HDDs were all still running. No I haven't really answered my question, but I should of gave more details on the subject though. Thanks. The unraid main site indicated little read/writes to the drives, mainly one drive which might of been generated the night before as I was copying files to it. Are you using a cache drive? The mover script does its work in the middle of the night. I think you answered your own question - something was accessing it.
Archived
This topic is now archived and is closed to further replies.