pluginCop

Members
  • Posts

    60
  • Joined

  • Last visited

Posts posted by pluginCop

  1. I've reviewed this thread, and there's nothing per se that warrants any further moderation / comments on this plugin AT THIS TIME.

     

    The error message on the screen during boot is a minor display aberration and completely harmless

     

    Array Not able to Stop -> this is a big deal, but a single instance reported doesn't justify any action being taken.

     

    Server not turning off displaying "Turning Off Swap".  While uninstalling the plugin may have fixed the issue for you, it is hard to properly diagnose this as I also have a server which doesn't run any VMs and also has this same issue.

     

     

    • Like 1
  2. 16 minutes ago, John_M said:

    Uneventful update from 6.8.2. Thank you.

     

    The Dynamix File Integrity plugin is still not Unraid 6.8 compatible (it tries and fails to run its scheduled check directly from the boot flash). I know it isn't the fault of this specific release and it has been mentioned in the support thread for that plugin but it still remains broken.

    Yeah, there is a comment within Apps regarding that.  If the plugin wasn't still functional in other respects, it would have been blacklisted from Apps completely.  But, IMHO background checking of the files is a very important aspect of the plugin and this should be fixed asap.

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

  4. 41 minutes ago, olehj said:

    I can of course consider make an option to disable update writes, but then features will be lost, or simply add a custom update time.

    This^^^ because the feedback from SMART would be an overlap from the built-in SMART monitoring unless the plugin is doing something else.

     

    The amount of writes varies quite wildly.  If I set up the plugin with all my drives (24), if they are all spinning, then there is ~300 writes per hour (2.6M / year) according to the dashboard.  If they're all spun down, that drops to ~20/hr

     

     

     

    (under my test it would have been ~64,000 over the 9 days)

     

     

     

     

  5. Just an FYI,

     

    CA's application feed is getting stricter on plugins.  The template for CA for this plugin references one URL which does not match the URL referenced within the plugin itself.

     

    This is a security issue because if / when the plugin updates, effectively a different plugin winds up getting installed from the one CA has listed (even though in this case they are identical, but due to the differing URLs they effectively are different plugins).

     

    Because of this the application feed is automatically blacklisting Corsair PSU until either the template or the plugin are fixed to point to the same URL

     

    If the GitHub repository simply changed where the plugin is stored, then the solution is to change the template to that new repository

     

    Fma965's Repository
    https://raw.githubusercontent.com/Fma965/corsairpsu-unraid/master/corsairpsu.plg:
            Fatal: Plugin URL on xml template does not match PluginURL in .plg (https://raw.githubusercontent.com/Fma965/corsairpsu-unraid/master/corsairpsu.plg vs https://raw.githubusercontent.com/Cyanlabs/corsairpsu-unraid/master/corsairpsu.plg)

  6. On 10/27/2019 at 12:19 PM, bonienl said:

    You are right.

    Need to correct that. Thanks

    Polite little bump - I'm sure you just forgot about this.

    # Generated file integrity check schedule:
    10 0 * * * /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /dev/null

     

    • Like 1
  7. 10 minutes ago, BRiT said:

    Well the previous versions of PreClear Plugin still did questionable things on 6.8 such as replacing libevents with years older versions, so it probably shouldn't even be listed on 6.8.

     

    Quote

    Bugs within applications can (and do) happen.  This is outside of the control of the moderators of CA.  Depending upon the circumstances, the application may be subject to moderation due to the bug.  This moderation may be mild or in the cases where the bug could cause data-loss severe resulting in the possible blacklisting of the application.  In most cases, the author is given time to rectify the bug before moderation happens.  Minor issues with any application will tend to not have any moderation applied.  As a general rule, it is recommended to always keep your applications (especially plugins and unRaid itself) up to date.  In the case of egregious software errors, the moderators of CA will err on the side of the user instead of the side of the author.

     

    • Thanks 1
  8. 2 hours ago, cybrnook said:
    
    unRAID version (6.8.1) not supported.
    plugin: run failed: /bin/bash retval: 1

    Being marked for deletion, and cannot reinstall on 6.8.1

    Confirmed.  Will however give @gfjardim time to fix this before any additional action is taken.

  9. 2 hours ago, dlandon said:

    In the next release of UD, I am separating out all the packages loaded currently by UD into a separate plugin called 'Unassigned Devices Plus'.  The packages removed from the base UD affect mounting of HFS+ and extFAT disks.  If you need to mount these formats, install the UD plus Plugin.

     

    The other package not installed any more in the base UD s 'parted'.  Parted is used for formatting and partition delete on disks.  If you need to do any formatting or deleting of partitions, install the UD Plus plugin.

     

    All disk formats supported by Unraid are supported in the base UD plugin.  The idea behind all this is the installation of packages into Unraid that are not used by the majority of users.  I am not a fan of installing a lot of packages into Unraid, especially packages that are not being used.  This also cuts down on the UD plugin installation time by not downloading and installing all those packages.

     

    The UD Settings page will indicate which features can not be enabled without the UD Plus plugin being installed.  Check the 'Help' on that page for further information.

    Would you like me to notify everyone with UD and FCP installed about this?  Should *hopefully* lessen the massive influx of support posts that will happen

  10. Not going to mark this as being incompatible with 6.8, but will put a comment on the app linking to the command.  Hopefully someone will post if / when the plugin has been updated to work out of the box.

  11. 31 minutes ago, poto2 said:

    The plugins are very much appreciated, but having functional issues with Unraid 6.7.2.

    AFAIK, there are no compatibility issues with the plugin and 6.7.x  Rather it's that not all combinations of hardware (due to a variety of factors, most outside of @bonienl's control) will work properly.  The apps tab does have a note on this plugin (and a few others) specifying this.

     

    If there is an actual compatibility issue with 6.7.x, then let me know

  12. 50 minutes ago, dabl said:

    These should be removed from Community Applications so others aren't misled into installing non-working plugins where support for them has been abandoned

    The issue isn't that the plugin doesn't work (it does).  The issue is that newer chipsets don't have the drivers included the kernel (in which case you bug Intel / AMD to do that) or that the sensors / sensors-detect scripts themselves have been abandoned (years ago actually).

     

    There are a number of work-arounds if you google things.  EG: On one of my older AMD boards I had to do this in the "go" file

     

    modprobe it87 force_id=0x8686

    as the it87 module was included in the kernel, but it didn't recognize the chipset id that my board was giving it.

     

    While I do understand your frustration with this, these issues are outside of the author's control.  But, I will add a note to the app stating that it does not work with all hardware combinations.