Jump to content

darkside40

Members
  • Posts

    517
  • Joined

  • Last visited

Posts posted by darkside40

  1. Hi there,

    i need to test some scripts for compability using unRaid 6.9. I have a License for my Main unRaid Server but i dont want to use it as testing rig.

    Is there any developer version of unRaid apart from the trial Keys which i could make use of to have an spare unRaid Server here for testing?

    That version could be limited in runtime etc. that would be no issue. How do other devs test? Or do they all buy spare unRaid Licenses?

     

    With unRaid 5 that was no problem because there was a free Version of unRaid.

  2. I have gfjardims preclear script install and dont have the error message regarding S3 Sleep.

    Btw the Error Message which JustinChase posted is the same like in the screenshot i have posted. 

  3. 3 hours ago, bastl said:

    Updated the sleep plugin and the UD stopped showing devices @bonienl

    I'am currently on 6.8.3.

     

    Edit:

    Removing the "S3 sleep plugin" brought back all devices in UD.

     

    Edit2:

    I can reproduce the issue be reinstalling the plugin fresh from the community apps. UD devices will dissapear.

    A friend of mine has the same problem and send me an screenshot with the failure.photo_2020-04-02_13-31-45.thumb.jpg.ff2c33277fd64b298511eba2150a5f8d.jpg

  4. 17 hours ago, pluginCop said:

    Because of the monster nature of this particular thread, it's rather hard to gather what exactly is happening.

     

    Is it fair to say that Dynamix S3 Sleep is for all intents and purposes non-functional (and has been since 2018)?  In looking through the code change that was posted earlier, it would appear that the routine that is determining whether or not the drive(s) are idle is completely broken?  Right / Wrong?

     

    Is there still a usage case for this plugin putting your server to sleep even if the drive(s) are still active?

    Simple problem was that with particular Raid Adapters the normal determination if the drives are spun up or down via the I/O statistics did not work.

    So there was a patch with version 3.0.3 which included an activity check via hdparm, which was not reliable for me. I have reported it and it was removed. Later on it was added again with the same consequences, the HDD's seemed to be spun down in the Webif, but the script did not send the server to sleep. So i removed that check again.

    For me being able to determinate if the if the array is quite so now data is written to it etc. is mandatory for this plugin.

    The other option are nice to have.

     

    I dont know how many people are out there having the same problem like me, but based on this thread here i am not alone.

    I will keep my modified version of the script because i know it works.

  5. You must calculate the MD5 hash of the new txz and add edit that in the plg. Than reboot your server and you should use the edited script.

    Btw i can download the attache file without any issues.

    • Like 1
  6. On 2/4/2020 at 1:06 PM, Healadin said:

    Hello,

    I have installed S3 Sleep a while ago (almost 2 months now) and my Unraid never went to sleep as far as I know. My config plugin config is in the attached screen. I also have running duckdns and OpenVPN docker container (I think that might be the problem?). No idea, to be honest, but I would like to use the sleep mode (it consumes around 75 Watts).

     

    Also I am wondering if its possible to wake it up over VPN or at all? But I doubt it.

    Screenshot from 2020-02-04 12-59-59.png

    The sleep plugin is know for being defunctional for quite some people since the last update nearly two years ago.

    You could give this a try:

     

    • Thanks 1
  7. Having the same issue since switching to unRaid 6.8.0.

    I have an Ubuntu 18.04 based machine which mounts 5 shares of the unRaid. Running unRaid 6.7.0 those mount where rock stable, also surviving when the unRaid goes to sleep and wakes up hours later.

    What i have read in some Forums actively switching the Samba Protocol version to 1.0 could solve the problem. I will try that now. 

  8. When the Debug mode shows no ethernet traffic and the drives are definately spun down than that could be a bug introduced in one of the last versions of the S3 Sleep Plugin. I think the root course was the integration of hdparm in the process of determinating if a drive is spun down.

    I patched that out and since then the script works as expected and reliable.

    I know that some people have that problem, but the script was never reverted back, althought i mentioned that problem some times here.

  9. On 11/13/2018 at 6:07 AM, Walter S said:

    I have a question with the S3 Sleep plugin.  The issue I have is when I set it to “Wait for array inactivity” “Yes, exclude cache”  It still refuses to go to the sleep mode.  I noticed, on the main page with all drives spun down a Temp for one or more of the drives stays and doesn’t turn to *.  Could this be why the system thinks it still up and not inactive? Preventing it from going to sleep.

     

    335703380_Screenshot_2018-11-12ServerMain.thumb.png.32e5d31e0c1d71208230aff7216f9d03.png

    Any thoughts would be helpful.

    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.

     

  10. 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

  11. 12 hours ago, bilben1 said:

    Thanks for the modified script. I am also giving it a try. I disabled sleep for the moment. I installed the .txz file into the dynamic.s3.sleep folder on the flash drive and copied the .plg file overwriting the existing .plg file on the flash drive and restarted the plugin. Is that all that has to be done?

     

     

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

  12. 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

  13. On 11.4.2018 at 8:02 AM, bonienl said:

     

    Sorry, I don't have time right now to look into this, and have to keep it on my todo list.

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

    Works perfect till now.

  14. On 12.3.2018 at 1:22 PM, bonienl said:

    I'll put this on my todo list. Had several (failed) attempts in the past, and need a good review of the approach to take.

     

    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?

  15. 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?

    • Upvote 1
  16. 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?

  17. 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.

×
×
  • Create New...