darkside40

Had the same troubles with it and modified it by myself: @bonienlI dont know if that was ever fixed but would be interested in the info.

The Sleep Plugin causes trouble for quit some time. A while ago i have posted a modified version here which works really good for me: https://lime-technology.com/forums/topic/34889-dynamix-v6-plugins/?do=findComment&comment=653280

Should be. After a reboot you should see Script Version 3.0.6.1 on the S3 Sleep settings page.

Here you can find the modified script: https://pastebin.com/knv869Aq The modifications are done between line 233-236, just commenting out the new check and adding the old style activity check from 3.0.4. I have also added an archive which includes the plg (because you need to change the md5sum of the txz after repackaging) and the txz with the script version mentioned above. Ignore the config, you will only need the plg and the txz. For me it works, wouldnt take any guarantee if it does for you. It is just a really ugly hacky fix till bonienl has the time to make an official fix, because the 3.0.6 didnt work for me most of the time. sleep.tar.gz

Okay i just changed the script by myself using the HDD Disk active check method form 3.0.4. Works perfect till now.

Hi bonienl, is there any intermediate fix for the problem with the S3 Script? Maybe a downgrade to the old algorithm to determinate if a disk is spun down or a way to make the hdparm check optional?

But when i read the code of the plugin right it is used side by side with the check of the Disk I/O stats which are compared. Which was the method also use in 2017/05/12 Version of the script. So would it be possible to make hdparm check optional?

Without Cache Disk included. Also put the Debug Log on and the script is complaining about ongoing activity in the disks that are shown as spindown in the Main Page, but hdparm showse them as active/idle. Checking with lsof there are no open files on the disks which block the script. Btw what was the reason the hdparm check was included?

Yes and if i manually Spin Down all drives via the Main page everything works as expected. The Problem seems to be that unRaid or hparm sometimes i not really spiining down drives, or the hdparm output is worng, i dont know. hdparm shows spin down drives as active, which cause the insomnia of the S3 sleep script.

Another night where my unRaid did not went to sleep as expected. hdparm showed one drive as active idle, white balled in the Main Tab of unRaid but showing the temps. Any idea how we could resolve this? Seems that i am not the only one that has such problems. The older Version of the Script that is use under 6.3.5 worked.

Since upgrading to unRaid 6.4.1 the S3 Sleep script, which i also upgraded does not work correctly anymore. The problem seems to be that the newer Version of the Script also checks the hdparm output on the disks, but unRaid is not always able to put disks correctly into standby or that hdparm is not able to recognize it correctly. So spin down disks are sometime shown as active/idle and the Script does not sleep the Server. I think we already had such au problem last year, resulting in reverting back to a previous Version of the script. Would it be possible to make the hdparm check optional?

The ffmpeg Version in this docker does not support VAAPI Transcoding. So no Hardware Transcoding. I think that is an issue which has been working on. If you want you could try a docker by linuxserver.io which should support Transcoding. Dont know how stable that work: https://hub.docker.com/r/linuxserver/emby/

+1 for the VAAPI support. Any more info what is the specific problem with that? When i recall it right, the Plex Docker can already do hardware transcoding. Correct me if i am wrong.

Same here. Tried it a couple of minutes ago, but no change. The broken version still shows as up-to-date. Is there any cache that needs to be deleted?

Hi bonienl, would it be possible to revert back to the last version of the script, until the problem with the new version is solved?

No its one of my Array disk, btw now it is SDB. I also tried the Custom commands method which you described, unfortunately that locked up the WebGui. Is there any way to revert back?

Got the same problem like b0mb. Yesterday i have updated to the latest S3 Sleep Version. From that point on my unRaid does not go to sleep anymore. Started the S3 Sleep debug it shows that there is ongoing activity on SDD. In the main it shown spun down but with temps displayed. I have also tried executing /usr/local/sbin/mdcmd spindown but the problem remains. Anyway to revert back to the last version of S3 sleep?

Really thanks for that great tutorial. I am just about to convert all my disks from ReiserFS to XFS. Unfortunately it takes about 24hrs to copy over 4TB of data from one drive to another. Write speeds never really rocked on unRaid

Maybe somebody has the same problem. Since some days i cant sync my folder because Syncthing is complaining: "home disk has insufficient free space". But this cannot be. The folder resides on my cachedrive with 600GB of free space.

Do yourself a favour and use the Community Applications Plugins: http://lime-technology.com/forum/index.php?topic=40262.0 Makes unRaid Docker Life a breeze, instead of messing around with template repos.

You find the forked-daapd.conf inside the config folder. If it is empty the path in the docker config might be wrong or it is a permission problem. For example when you created the folder via terminal as user root and user nobody which runs the docker cant wright to that folder. Also the UID and GID looks messed up in the log. You should start from scratch and add the Container using Community Applications Plugin.

Okay solved it by myself. On unRaid you have to set ipv6=no in the forked-daapd.conf because unRaid does not support ipv6. Maybe it would be a good idea to take that setting as default, because it is easier for most to enable it than to have a not working forked-daapd and have to search for that failure.

Hi i just tried to switch from Sparklyballs daapd to the ls.io dappd but i wont come up sayin it could not bind to Port 3689. These are the Log File entries which keep repeating. Any Idea? [2016-01-03 19:26:55] [ LOG] main: Forked Media Server Version 23.3 taking off [2016-01-03 19:26:55] [ LOG] main: mDNS init [2016-01-03 19:26:55] [ LOG] mdns: Avahi state change: Client running [2016-01-03 19:26:55] [ LOG] db: Now vacuuming database, this may take some time... [2016-01-03 19:26:56] [ LOG] db: Database OK with 403 active files and 6 active playlists [2016-01-03 19:26:57] [ LOG] raop: Couldn't make timing socket: Address family not supported by protocol [2016-01-03 19:26:57] [ LOG] raop: Couldn't make control socket: Address family not supported by protocol [2016-01-03 19:26:57] [FATAL] httpd: Could not bind :::3689 [2016-01-03 19:26:57] [FATAL] main: HTTPd thread failed to start [2016-01-03 19:26:57] [ LOG] main: Player deinit [2016-01-03 19:26:57] [ LOG] scan: Scanned 200 files... [2016-01-03 19:26:58] [ LOG] main: Spotify deinit [2016-01-03 19:26:58] [ LOG] main: File scanner deinit [2016-01-03 19:26:58] [ LOG] main: Cache deinit [2016-01-03 19:26:58] [ LOG] main: Worker deinit [2016-01-03 19:26:58] [ LOG] main: Database deinit [2016-01-03 19:26:58] [ LOG] main: mDNS deinit [2016-01-03 19:26:58] [ LOG] main: Exiting.

Anybody already got an up-to-date Ampache docker? @breakline: For an PXE Server you don't need a Docker. You can simply install the dnsmasq package for Slack 14.1 x64 and use an appropriate config file for it. I use it that way myself.

Thanks for the hint. Never checked that.