bonienl

It is a bit confusing, but the "Icon=<name>" refers to a 48x48 logo which resides in the "images" folder. <name> can be anything you like. The small icons in the title headers (tabs) are 16x16 icons, which reside in the "icons" folder. The file names to be used are the title header without spaces and all lowercase. And images/icons are in .png format ...

I am having this issue also Does the file /boot/config/plugins/dynamix/dynamix.cfg exist ? And what is the content of that file ?

You may want to run the "check for updates" feature under plugins. System Stats has been updated to version 2014.12.01, let me know your results.

Can you post or send me your "disks array" content, see Tools -> Vars. I don't have a cache pool myself, and it will help in making the correction.

LOL. The included filetree.js is already modded to allow selection of file extensions, but any good ideas can be merged

Notice: You must be running unRAID version 6.9 or later to use these plugins The easiest way of installing plugins is thru Community Applications. This is an apps installation manager developed by Squid and needs to be installed separately. The alternative way of installing an optional plugin is from the Plugin page in the WebGui and use the tab Install Pugin. The URLs of the optional plugins as mentioned below can be copied and pasted in the install box. Available Dynamix plugins Active Streams shows in real-time any open SMB and AFP network streams. This allows instant view of who is accessing the server - either by IP address or name - and see what content is opened. Optionally streams can be stopped from the GUI. Cache Dirs keeps folder information in memory to prevent unnecessary disk spin up. Dynamix builds a GUI front-end to allow entering of parameters for the cache_dirs script which is running in the background. S3 Sleep defines the conditions under which the system will go to S3 sleep mode. It also adds an unconditional 'sleep' button on the Array Operation page. System Info shows various details of your system hardware and BIOS. This includes processor, memory and sub-system components. System Stats shows in real-time the disk utilizations and critical system recources, such CPU usage, memory usage, interface bandwidth and disk I/O bandwidth. System Temp shows in real-time the temperature of the system CPU and motherboard. Temperatures can be displayed in Celsius or Fahrenheit. Your hardware must support the necessary probes, and additional software drivers may be required too. This plugin requires PERL, this package needs to be installed on Unraid versions lower than 6.11 System AutoFan allows automatic fan control based on the system temperature. High and low thresholds are used to speed up or speed down the fan. This is a new plugin and still under development. Schedules is a front-end utility for the built-in hourly, daily, weekly and monthly schedules. It allows the user to alter the schedule execution times using the GUI. See Settings -> Scheduler -> Fixed Schedules. System Buttons adds an one-click button to the header which allows for instant sleep, reboot, shutdown of the system or array start/stop. Local Master supports detection of the local master browser in an SMB network. It will display an icon in the header at the top-right when unRAID is elected as local master browser. Under SMB Workgroup settings more information about the current elected local master browser is given. SSD TRIM allows the creation of a cronjob to do regular SSD TRIM operations on the cache device(s). The command 'fstrim -v /mnt/cache' is executed at the given interval. This plugin is now built-in with Unraid version 6.11.0 and higher File Integrity Real-time hashing and verification of files stored on the data disks of the array. This plugin reports on failed file content integrity and detects silent file corruption (aka bit-rot). WARNING: USING THIS PLUGIN ON DISKS FORMATTED IN REISERFS MAY LEAD TO SYSTEM INSTABILITY. IT IS RECOMMENDED TO USE XFS. SCSI Devices updates the udev persistent storage devices rules file (courtesy of bubbaQ), which allows proper naming of SCSI attached disks. Please by aware that after installation of this plugin, it might be necessary to re-assign disks due to their changed names! Date Time adds an interactive world map to the date and time settings. This allows the user to simply click on his/her country and select the corresponding time zone. In addition the world map highlights the countries in the currently selected time zone. Stop Shell adds a script which gets invoked when the array is stopped. This script looks for any open shells in /mnt/... and terminate them. This ensures the array can be stopped. Be aware that automatic terminating of open shells may lead to data loss if an active process is writing to the array. Day Night automatically toggles between a day theme and a night theme. Based on the sunrise and sunset times of your location. Share Floor creates a cronjob to do a regular scan on user shares and change the minimum share floor value according to the largest file found in the share. Factory Reset resets the system to default settings and let it start like a new installation. Optionally array and pool assignments can be preserved. In either case USER DATA IS NEVER LOST Installation URLs (copy & paste) Active Streams - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.active.streams.plg Cache Dirs - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.cache.dirs.plg S3 Sleep - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.s3.sleep.plg System Info - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.info.plg System Stats - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg System Temp - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.temp.plg System AutoFan - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.autofan.plg Schedules - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.schedules.plg System Buttons - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.system.buttons.plg Local Master - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.local.master.plg SSD TRIM - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.ssd.trim.plg File Integrity - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.file.integrity.plg SCSI Devices - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.scsi.devices.plg Date Time - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.date.time.plg Stop Shell - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.stop.shell.plg Day Night - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.day.night.plg Share Floor - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.share.floor.plg Factory Reset - https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.factory.reset.plg gridrunner aka Spaceinvader One has made a very nice video tutorial about several Dynamix plugins. A recommended watch when you like to learn more. You like my Dynamix plugins?

The sorting of pages is done alphabetically, if you want pages to appear in a different order then a sequence number needs to be added to the menu reference. For example you have the files A.page B.page C.page These are shown in the sequence A, B, C If you want to show them in the sequence C, B, A (as an example), do the following: In file A.page Menu="parent:3" In file B.page Menu="parent:2" In file C.page Menu="parent:1" "parent" is the name of the menu under which these pages will be shown.

Do sensors -u You get something similar like below: nct6776-isa-0290 Adapter: ISA adapter SYSTIN: temp1_input: 32.000 temp1_max: 0.000 temp1_max_hyst: 0.000 temp1_alarm: 1.000 temp1_type: 4.000 temp1_offset: 0.000 CPUTIN: temp2_input: 41.000 temp2_max: 80.000 temp2_max_hyst: 75.000 temp2_alarm: 0.000 temp2_type: 4.000 temp2_offset: 0.000 AUXTIN: temp3_input: 36.000 temp3_max: 80.000 temp3_max_hyst: 75.000 temp3_alarm: 0.000 temp3_type: 4.000 temp3_offset: 0.000 Instead of the names SYSTIN and CPUTIN use the "tempX" reference, so in my case: sensors.conf contains (also note the 'wildcard' in the chip name): chip "nct6776-isa-*" label temp1 "MB Temp" label temp2 "CPU Temp"

Yeah, this is a known bug. It has been corrected for v6, but needs to be ported to v5 as well.

Indeed no worries on that last 'yes' (this is reset upon reboot). Add the following to your "go" file and reboot your system # Add temperature modules modprobe coretemp modprobe w83627ehf /usr/bin/sensors -s After reboot do a "sensors" command and create your sensors.conf file as per wiki.

Tried "setsid" but it holds plugin installation, like when executing the command directly. The "at" approach makes the plugin installation continue.

I ran in exactly the same issue, plugins which need to start a background process get stuck upon installation. This was working previously under v5 when plugins were installed directly from the CLI. The proposal of dlandon is working, but I find it a bit cumbersome, ideally I like to have the one liner working again, so the example above really should be just the line: /etc/rc.d/rc.snap start

The plugin dependency which exists in Dynamix comes from the fact that the Dynamix webGui adds several javascript libraries which do not exist in the stock webGui. The same is true for additional API functionality to store and retrieve settings. The optional Dynamix plugins rely on these libraries and API calls to function properly, hence a check is performed by each optional plugin to see whether the Dynamix webGui is present. This system can only work when the Dynamix webGui is installed before any other plugin.

Your explanation is right. A system plugin gets installed before a user plugin. This becomes important when a dependency exists and certain plugins (e.g. Dynamix webGui) need to be installed first to create the correct foundation for other plugins to operate. Other than that there are no differences between both in terms of execution or privileges.

First I like to propose a simplification in the "plugin" installer script and *not* store any -stale- plugins, just forget/ignore older plugin versions. I think that is less confusing for the end-user. Next, I would like to make a feature request to the "plugin" manager which allows plugins to be installed as "system plugin", meaning they get installed in the directory '/boot/plugins' instead of '/boot/config/plugins'. To make this work an additional attribute can be introduced, see example below <?xml version='1.0' standalone='yes'?> <!DOCTYPE PLUGIN [ <!ENTITY name "webGui"> <!ENTITY author "Bergware"> <!ENTITY version "3.0.0"> <!ENTITY category "Core Functionality"> <!ENTITY pluginURL "https://raw.github.com/..."> ]> <PLUGIN name="&name;" author="&author;" version="&version;" category="&category;" pluginURL="&pluginURL;" system="true"> The new attribute 'system' defaults to 'false' but can be set to 'true' to have the plugin installation changed. This requires an update to the "plugin" installer script, for example: // register successful install // absence of "configfile" attribute indicates normal plugin; presence indicates a VM plugin $configfile = plugin("configfile", $plugin_file, $error); if ($configfile === false) { // Bergware change: add user or system plugin selection $system = plugin("system", $plugin_file, $error); $target = $system === false ? "/boot/config/plugins/$plugin" : "/boot/plugins/$plugin"; if ($target != $plugin_file) copy($plugin_file, $target); symlink($target, "/var/log/plugins/$plugin");

With the current large sized hard disks it is almost obligatory to do a pre-clear, having your array unprotected for an extended period of time when adding or changing disks, simply isn't acceptable.

Thanks RobJ for creating this. I have updated the OP. It is also possible to get PERL installed using the system-temp plugin file. People need to edit the PLG file and change the wording "no-install" into "do-install" at the appropriate line, you may want to add this installation possibility.

True, but any array related activities should be started/stopped based on the event system which exists now. Modifying the go file programmably is not very flexible, the better way is to use the plugin system.

It looks like you don't have any modules/probes installed at all, which are required for your hardware. You can run sensors-detect, but this requires installation of the perl package to make it run (see inside the PLG file).

Whatever webGui is chosen, it all comes down whether emhttp stays alive or not ...

I am not using sensors.conf myself, but could it be simply a syntax issue? Did you try using quotes or double-quotes ? The unix style of escaping a space is to proceed it with a slash '\' character, maybe that works ?

When you do the sensors command from a telnet session, do you see the modified names ?

Renaming is done using the sensors.conf file, perhaps you can post what you have tried so far.

For the moment I stick to the lm-sensors approach, but keep this open for future enhancement.

It would be great indeed if past experiences/solutions can be brought in this topic, it will surely make it easier for others in their 'quest'. Thanks