bergware / dynamix Goto Github PK

So, I have a system running coretemp for CPU temperatures and an nct7904 chipset for system monitoring over i2c.

After using the webui to populate things by first detecting and then loading the drivers, the dropdowns populate correctly; the output of "sensors" from a command line can be seen below:

root@redacted:~# sensors
nct7904-i2c-0-2e
Adapter: SMBus I801 adapter at 0580
in1:          +1.04 V
in2:          +1.04 V
in3:          +1.49 V
in4:          +1.24 V
in5:          +1.23 V
in6:          +0.65 V
in7:          +1.84 V
in8:          +0.60 V
in9:          +1.79 V
in10:         +1.79 V
in11:         +1.21 V
in12:         +1.21 V
in13:         +1.21 V
in14:         +1.21 V
in15:         +3.31 V
in16:         +3.17 V
in20:         +3.32 V
fan1:        4623 RPM
fan2:        1788 RPM
fan3:           0 RPM
fan4:           0 RPM
fan5:        2428 RPM
fan6:        2385 RPM
fan8:           0 RPM
temp1:        +39.9°C
temp2:        +57.2°C
temp3:        +56.0°C

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +57.0°C  (high = +83.0°C, crit = +93.0°C)
Core 0:        +51.0°C  (high = +83.0°C, crit = +93.0°C)
Core 1:        +49.0°C  (high = +83.0°C, crit = +93.0°C)
Core 2:        +53.0°C  (high = +83.0°C, crit = +93.0°C)
Core 3:        +50.0°C  (high = +83.0°C, crit = +93.0°C)
Core 4:        +50.0°C  (high = +83.0°C, crit = +93.0°C)
Core 5:        +51.0°C  (high = +83.0°C, crit = +93.0°C)
Core 8:        +49.0°C  (high = +83.0°C, crit = +93.0°C)
Core 9:        +52.0°C  (high = +83.0°C, crit = +93.0°C)
Core 10:       +52.0°C  (high = +83.0°C, crit = +93.0°C)
Core 11:       +51.0°C  (high = +83.0°C, crit = +93.0°C)
Core 12:       +52.0°C  (high = +83.0°C, crit = +93.0°C)
Core 13:       +52.0°C  (high = +83.0°C, crit = +93.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Package id 1:  +57.0°C  (high = +83.0°C, crit = +93.0°C)
Core 0:        +51.0°C  (high = +83.0°C, crit = +93.0°C)
Core 1:        +51.0°C  (high = +83.0°C, crit = +93.0°C)
Core 2:        +50.0°C  (high = +83.0°C, crit = +93.0°C)
Core 3:        +49.0°C  (high = +83.0°C, crit = +93.0°C)
Core 4:        +53.0°C  (high = +83.0°C, crit = +93.0°C)
Core 5:        +48.0°C  (high = +83.0°C, crit = +93.0°C)
Core 8:        +50.0°C  (high = +83.0°C, crit = +93.0°C)
Core 9:        +48.0°C  (high = +83.0°C, crit = +93.0°C)
Core 10:       +51.0°C  (high = +83.0°C, crit = +93.0°C)
Core 11:       +47.0°C  (high = +83.0°C, crit = +93.0°C)
Core 12:       +49.0°C  (high = +83.0°C, crit = +93.0°C)
Core 13:       +53.0°C  (high = +83.0°C, crit = +93.0°C)

After setting Package id 0 for CPU, temp2 for Motherboard and Fan2 for the Array fan, the lists become unpopulated, and running "sensors" again results in the following:

root@redacted:~# sensors
Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 10: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 12: Undeclared bus id referenced

The contents of sensors.conf at this point is as follows:

root@redacted:~# cat /etc/sensors.d/sensors.conf
# sensors
chip "nct7904-i2c-0-2e"
ignore "fan3"
chip "nct7904-i2c-0-2e"
ignore "fan4"
chip "nct7904-i2c-0-2e"
ignore "fan8"
chip "coretemp-isa-0000"
label "temp1" "CPU Temp"
chip "nct7904-i2c-0-2e"
label "temp2" "MB Temp"
chip "nct7904-i2c-0-2e"
label "fan2" "Array Fan"

The bus id "seems correct" based on the original output of sensors. Reading the manual, I decide to just use "nct7904*" which resulted in a "mostly" working scenario, where the CPU temperature and Motherboard temperature did work, but the fan speed did not. I have not been able to identify a way to get fan speed to work.

I'm not sure if this is caused by an upstream issue with LM_SENSORS or the way you are parsing the outputs for the creation of the sensors.conf file.

Anyways, hopefully there is enough detail here to resolve this.

I really like the Dynamix docker plugin on my unRAID os. Is it possible to install this on other machines not running unRAID?

noticed the other day that the autofan page is mostly missing. cannot start or configure or anything at all. this is not a new install. i have been using this plugin since the begining.

im on 6.3.0 RC5

Just as the title says. Files written to the cache are not handled by the "Automatically protect new and modified files" feature when they are moved to disk.

This is because, when the Unraid Mover runs, a partial file is created on the disk. After the move is complete, this file.partial is then moved to the original file name on the disk. Therefore, inotifywait does not see the move as a close_write, but rather a moved_to.

I have tested and fixed this on my dev server. PR inbound.

[[ -n $HDD ]] && SLEEPING=sdspin ${DISK}; echo $? || SLEEPING=hdparm -C ${DISK}|grep -c standby

This line is giving me trouble. (sorry for the formatting).
Apparently this never worked properly for me as hdparm always returns unknown status, which counts as not standby, and thus I did not notice.

The issue now is, that sdspin returns 1 for my HDDs (they never spin down) and 25 for my nvme (whatever this is supposed to mean) and thus all drives are excluded from the max temp calculation.

I understand there is little you can do about that (aside from maybe a config option to ignore the state of the disk; commenting this line fixed my issues).

What I would like very much is a check if all disks are excluded, because as it is now, all fans are set to 0 if no temp is read. This of course causes issues.

There is already a post on the support forum about this, so I guess multiple people are affected.

I have a problem regarding the cache_dirs script.

Background: I have a pretty large SMB share that I have running on a remote and addad as such to my unraid.

Problem: The cache_dirs script does not allow me in the GUI Configuration to exclude /mnt/remotes, only existing/defined shares.
I just want to use the remote share in my unraid services and not reshare them. Currently the script also runs for said remoted and thus generates an enormous abmount of traffic while indexing/caching/recaching millions of dirs/files over the internet.

Possible Solution(s): Add a yes/no Flag or a include/exclude selection for remote shares (as for user mounts)

Hi there,
could you please patch out (or make it optional) the hdparm check which was introduced in the last version of the S3 Sleep Plugin. It does not work reliable leaving the Server running most of the time.
For my self i patched it out long time ago and it works without any problem also in conjunction with a Raid Adapter.
I mentioned that also some times on the forums but never got a reply for that.

I did a full check with Unraid Update Assistant and it said everything was fine.
I did the upgrade but in Plugins- i see and error Dynamix-Wireguard error.
How can i fix this issue please?

Hi,

when I try to run "detect" in the auto fan I receive some errors:

Warning: file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm3_enable): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 40

Warning: file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm3_enable): failed to open stream: Permission denied in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 42

Warning: file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm3_enable): failed to open stream: Permission denied in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 50
/sys/devices/platform/nct6687.2592/hwmon/hwmon3/fan3_input

Posted in the unraid forum https://forums.unraid.net/topic/34889-dynamix-v6-plugins/?do=findComment&comment=957341

thank you in advance.

Unraid 6.9.2
Perl installed using NerdPack
Had 2021.06.25 installed, tried upgrading and got same error.
Uninstalled 2021.06.25, rebooted server, tried fresh install, same error.

Install screen:

plugin: installing: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.system.temp.plg
plugin: downloading https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.system.temp.plg
plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.system.temp.plg ... done
plugin: run failed: /bin/bash retval: 2

Updating Support Links

How to reproduce:

1 - create file on disk, export hashes
2 - change file contents from smb share, export hashes
3 - hashes are the same which causes the modified file to be reported as corruption

This obviously doesn't happen when the file is modified within the unraid e.g. with nano.

Is this a known issue?

auto fan speed does not start when multiple config files present:

https://forums.unraid.net/topic/34889-dynamix-v6-plugins/page/121/?tab=comments#comment-959047

user: TexasUnraid

I'm on unraid 6.6.7, latest autofan plug-in.
The Auto Fan plug-in doesn't exclude my nvme cache drive. It runs much hotter than a hdd, so my fan speed is now always 'set by that same drive'

other people reported similiar issues with nvme cache drives. I tried disable/reanable. remove the exclude settings, etc. but still. In the log, it always shows that my hotest temp is the excluded nvme drive. (When I had a sata ssd cache, it was working fine)
Any idea?

Thanks!

I just installed Dynamix System Stats on 6.11.1. It properly shows real-time data but any option for historical info shows a blank graph.

All my hard disks are encrypted, and Unraid leaves no traces of the files on these disks exposed.

Currently, file integrity files are being exported to the USB disk. This happens in plain text, storing the file names in plain form.

Deleting the integrity files on the USB disk deletes them logically but not physically. Therefore, the content of these files can be recovered making the file names on my encrypted disks visible.

Request:
Allow the user to specify which folder to export the files to, e.g. /root to keep them in memory only so that user can store them elsewhere, or allow the user to download them as e.g. a ZIP file from within the browser.

Would it be possible to change lines 39 and 40 in SystemTemp.php from

if ($val[0]!='-') $set[] = "<i class='fa fa-snowflake-o' title='Processor' style='margin:0 6px 0 12px'></i>".my_temp($val[0], $_POST['unit'], $_POST['dot']);
if ($val[1]!='-') $set[] = "<i class='fa fa-snowflake-o' title='Mainboard' style='margin:0 6px 0 12px'></i>".my_temp($val[1], $_POST['unit'], $_POST['dot']);

to

if ($val[0]!='-') $set[] = "<i class='fa fa-snowflake-o' title='Processor' style='margin:0 6px 0 12px'></i>".my_temp($val[0], $_REQUEST['unit'], $_REQUEST['dot']);
if ($val[1]!='-') $set[] = "<i class='fa fa-snowflake-o' title='Mainboard' style='margin:0 6px 0 12px'></i>".my_temp($val[1], $_REQUEST['unit'], $_REQUEST['dot']);

This will have no side effect but will allow me direct access to http://TOWER/plugins/dynamix.system.temp/include/SystemTemp.php?unit=C&dot=. so i can pull it in to Home Assistant etc. Unfortunately HA doesn't support POST on it's scrape sensor.

I already currently modify this file to do that but it would be nice to just have this change implement.

I am thinking of adding a setting where the server won't go to sleep when someone is streaming from Plex. Just wondering whether this feature would be considered useful and would be accepted into the plugin.

Asking because there wouldn't be much use for me making this custom when it will be removed with every update of the plugin.

I have a SuperMicro X9DRi-F with three fans plugged into fan headers 1-3 and two fans plugged into fan headers 5 and 6. No fan is plugged into header 4. When booting the system the BMC reports Fan 4 as N/A. I have had no issues with this for several weeks. After installing System Temp with Perl and setting it to monitor the fans, after several minutes the system fans spin up to max. Checking the BMC it appears that Fan4 is now reported as "Lower non-recoverable" and has set an alarm. After rebooting the fan header is set back to N/A but after UnRaid boots this is once again set to "Lower non-recoverable" and the server fans spin up to maximum. The driver loaded is "coretemp nct7904".

When scanning the array for fans it finds 5 fans and after adding them the fans are listed as fans 1-5. Is it possible that this fan listed as 4 is triggering the BMC to believe that the fan 4 header should be populated? Is the driver that's loaded possibly doing this someway during polling for available fans?

While putting unRAID to an S3 sleep with the script works perfectly, the shutdown option doesn't work.
The powerdown script is never called due to problems with the search path.
(See https://lime-technology.com/forum/index.php?topic=52151.0)
I created a patched plugin for myself. The patched scripts calls the powerdown script using the full path.
You can find my version here:
plg file for installing: https://raw.github.com/rgls/dynamix/master/unRAIDv6/dynamix.s3.sleep.plg
the actual patch to the s3_sleep script: rgls@ebf1066

A pull request doesn't really make sense here, since you'll have to recreate the txz file.

Not sure who to report this to, so I'll start here. Nothing happens after clicking the UPDATE button.

The text boxes to enter folders and file extensions to exclude are too small. Expanding them who be helpful. Thanks!

I dont know if this is possible, but it would be usefull to minimzize windows such as the move or copy window.
This would be useful, because if one had to copy/move larger folders/files and therefore the window is in front for a prolonged period of time, its impossible to do anything in the webui in the meantime

On Unraid 6.9.2 the history stats for system stats is not working. At most it only seem to have ~24hours.

I guess this line is the problem

If you have a post wake up script which exits with 1 instead of 0 the condition is false, and it will execute system_down.

My last line of the post sleep script which is causing this issue uses the "Test" function, and this will set the exit code to 1.

test "$(date +%s -d "60 days ago")" -gt "$(mdcmd status | sed -n 's/sbSynced=//p')" && /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null

This executes the parity check if it was older than 60 days because crone schedule does not work if the system does sleep.

As per title really. I find this makes very little sense: if the drives are off, I would expect the fan to power down or spin at minimum speed.

I attach a screenshot of my configuration. When the drives spin, the speed seems to be managed correctly. It's hard to know anyway, since there is no log or information to verify what it is doing.

As the title says the link in the Readme.md isn't working.

I would like to prevent my system going to sleep when i am encoding files. This is entirely local, so i cannot prevent this by a network-check. However, the CPU usage is a good indicator.

Thanks!

Hi, does anybody like to have this feature?

https://github.com/BLAKE3-team/BLAKE3/releases/tag/1.0.0

Performance improvements are huge.

Do you like to get a pull request from me for this update? Or is already somebody working on it?
If somebody did evaluate and postponed this task, I would like to know the reason and reevaluate it.

Based on your feedback, I will share my work or keep it for myself.

since Feb 6th seeing non stop log noise from the plugin:

Feb  6 01:00:04 husky Plugin Auto Update: dynamix.system.stats.plg version 2023.02.05a does not meet age requirements to update
Feb  6 13:51:18 husky root: plugin: creating: /boot/config/plugins/dynamix.system.stats/dynamix.system.stats.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.system.stats.txz
Feb  6 13:51:21 husky root: plugin: checking: /boot/config/plugins/dynamix.system.stats/dynamix.system.stats.txz - MD5
Feb  6 13:51:21 husky root: plugin: running: /boot/config/plugins/dynamix.system.stats/dynamix.system.stats.txz
Feb  6 13:51:21 husky root: plugin: dynamix.system.stats.plg updated
Feb  6 13:52:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 13:53:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 13:54:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 13:55:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 13:56:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 13:57:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 13:58:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 13:59:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 14:00:02 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 14:01:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 14:02:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 14:03:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
Feb  6 14:04:01 husky  crond[1595]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null
...

Hello.
Since version 2023.02.19 the plugin is unable to detect any Network traffic on my Unraid server.

Also i cant select my nvme Cache drives to monitore aswell.

I tryed many restarts, reinstall and so an, non of them works.

Version 3023.02.05 was working for me, so dont know what to do.
I send you my Diagnostics, if that helps. Let me know if i can try something.

tower-diagnostics-20230222-2151.zip

I just recently got myself a NAS and i am running unraid 6.12.4
For some reason the plugin is just detecting my HDD's in the array and adjusting temperature according to them.
the plugin works perfectly in that use case however my nvme drives are usually the ones running hot under load, for some reason it does not take them into consideration.

Any way i can get autofan to detect the drives temps and adjust with them?
I've tried excluding all my HDD's to see if this solved the problem but it resulted in autofan reading the hottest temperature was 0 and turned off the fans.

I'm fairly new to this and any help is appreciated.

Alle the links to the plg are gooing to 404 even unraid gives back errors

Can you please fix

The Dynamix Local Master plugin's description says "Networks using Web Services on Devices (WSD) do not have a local master browser and use broadcast messaging to do host discovery"

However, the Unraid SMB settings page says "Select 'Yes' to enable WSD (WS-Discovery)"

Are these in fact two different services, or did one of them get the initialism wrong?

just work the first time and now nothing

unraid 6.5.0
plugins : 2018.03.18

here the available driver
coretemp nct7904

but my select are all empty

Model: Custom M/B: Supermicro - X9DR3-F CPU: Intel® Xeon® CPU E5-2690 v2 @ 3.00GHz HVM: Enabled IOMMU: Enabled Cache: 640 kB, 2560 kB, 25600 kB Memory: 64 GB Multi-bit ECC (max. installable capacity 192 GB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 100 Mb/s, full duplex, mtu 1500 eth1: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.14.26-unRAID x86_64 OpenSSL: 1.0.2n Uptime:

in console when i launch the command :
sensors Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 8: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 10: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 14: Undeclared bus id referenced sensors_init: Can't parse bus name

syslog has an entry like the following every minute:

crond[1587]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Looking at the script, it tries to execute sadc in /usr/lib64/sa, which is not there.

# ls -al /usr/lib64/sa
total 20
drwxr-xr-x  2 root root   120 Feb  6 08:51 ./
drwxr-xr-x 48 root root 26040 Feb  5 11:51 ../
-rwxr-xr-x  1 root root  1720 Nov  9 21:17 sa1*
-rwxr-xr-x  1 root root  1586 Nov  9 21:17 sa2*
-rwxr-xr-x  1 root root   605 Feb  5 11:51 sysstat*
-rwxr-xr-x  1 root root  6430 Feb  5 11:51 sysstat.ioconf*

I can't find sadc anywhere, though.

Unraid v6.11.5

Unraid Server 6.5.2 starts based on WOL. I have all my hard disks encrypted and the server never goes to sleep even though the S3 Sleep plugin 2018.02.04 used to work fine before.

Why?

As the s3 sleep plugin is "stopped", this might be related to me having encrypted my hard disks and they are not auto-decrypted on boot. I have to manually set the "Execute Function" to "Disabled & Apply", then choose "Shutdown & Apply". Then I can see the S3 Sleep job being started and the server will shut down.

Request:
The script should run regardless of the encryption status of the disks.

I have an Adaptec 51254 RAID controller allowing for 12 SATA ports.

Problem: Your S3 sleep plugin won't allow bringing the system to S3 if HDD activity should be evaluated.

HDD's cannot be spinned down via unraid UI or hdparm, the controller brings them back up immediately.

Solution is to not use each disk as JBOD but instead use them as individual arrays consisting of just one disk. For arrays spin down times can be defined in the controller menu and that works fine.

However - "hdparm -C" will never get the proper result, the disks are always "active" though they are off.

I had created some code to handle this before but found a better way around that on the web. Instead of relying on the state of the drive, check if there has been any IO happening. The following code works perfectly - it finds there is no activity on the disks regardless of their activity state.

I changed my code locally (repacked into txz and adjusted the MD5) and it works fine - should work well for all disks.

The code I'm using now:

HDD_activity() {
result=
if [[ $checkHDD == yes ]]; then
# Create a file on the ramdisk and cycle it to test for disk activity
( if [ ! -f /dev/shm/1 ] ; then touch /dev/shm/1 /dev/shm/2; fi ; mv /dev/shm/1 /dev/shm/2; cat /proc/diskstats > /dev/shm/1 ) >/dev/null 2>&1

for dev in ${array[@]}; do
  # Check if drive has been non idle since last run
  if [ "$(diff /dev/shm/1 /dev/shm/2 | grep $dev )" =  "" ]; then
    result=
  else
    result=1
    break;
  fi
done

fi

if [[ -n $result ]]; then
log "Disk activity on going: $dev"
echo $result
fi
}

I have set "Excluded folders and files" to exclude files with the extension "*.!qB".

But Dyamix File Integriy is still creating checksums for files with the extenion "*.!qB", and still verifying files.

Given that several smb connection exists from same host with different credential logins, all streams show the same username.

smbstatus -L

Samba version 4.17.12
PID     Username     Group        Machine                                   Protocol Version  Encryption           Signing              
----------------------------------------------------------------------------------------------------------------------------------------
6980    user1      users        192.168.3.3 (ipv4:192.168.3.3:60226)      SMB3_00           -                    partial(AES-128-CMAC)
6980    user2       users        192.168.3.3 (ipv4:192.168.3.3:60226)      SMB3_00           -                    partial(AES-128-CMAC)
6980    uster3        users        192.168.3.3 (ipv4:192.168.3.3:60226)      SMB3_00           -                    partial(AES-128-CMAC)

Locked files:
Pid          User(ID)   DenyMode   Access      R/W        Oplock           SharePath   Name   Time
--------------------------------------------------------------------------------------------------
6980         1005       DENY_NONE  0x120196    WRONLY     LEASE(RWH)       /mnt/user/ 
6980         1001       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /mnt/user/

Result in webgui:

HOST	USER	SHARE	TYPE	STREAM	PLAYTIME	SIZE	HALT
192.168.3.3	user2	xxx	0:04:13	4.25 GB	
192.168.3.3	user2	xxx	0:09:17	23 MB

Where the expected result is user1 and user2

Lookup seems to be ok:
https://github.com/bergware/dynamix/blob/f66d34fdb5a3183d8799a179b8a35cf7def75e1b/source/active-streams/include/StreamList.php#L57C24-L57C39

But the translation to users seems off.

Version: 2023.02.19
Unraid 6.12.8

With the "automatically protect new and modified files" functionality in the file integrity check plugin, if no exclusions are specified, everything ends up being excluded. As a result, the inotifywait daemon is rendered functionally inoperable.

PR on the way!

Hi

After update plugin to 2023.02.05a System Stats show only live data but not showing historical data eg last day etc (blank space)

Disk Stats working properly

Thank You for any response

Hello,

Those of us who want to change the text of the name of the fans from 'FAN 1', 'FAN 2'. etc in dashboard We do it with this code through custom.css and adding CSS in the theme engine plugin, since it seems that the FAN 3 tag does not come with the fan class and it is not impossible to change it.

Would it be possible to add that tag in the next version?

Thank you

</style>
<script>
document.addEventListener("DOMContentLoaded", function() {
    if ($(".fan:contains('FAN 1')").length) {
      $(".fan:contains('FAN 1')").text("CPU");
    }  
    if ($(".fan:contains('FAN 2')").length) {
      $(".fan:contains('FAN 2')").text("BOARD");
    }
    if ($(".fan:contains('FAN 3')").length) {
      $(".fan:contains('FAN 3')").text("BACKPLANE");
    }
        if ($(".fan:contains('FAN 4')").length) {
      $(".fan:contains('FAN 4')").text("BACK");
    }       
});
</script>
<style>

I'd like it to display multiple network graphs at the same time.

reflink, soft link and hard link are very useful when playing with PT, do we have a plan to support them?

After updating to autofan version 1.7 I get a parse error for pwm nct6796 when detecting the pwm fan:

Parse error: syntax error, unexpected ';', expecting ')' in /usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php on line 65

The preveous version worked well.

Version 2023.02.04a does not show plugin page settings.

SYSTEM TEMP

Warning: require_once(/usr/local/emhttp/plugins/dynamix.system.temp/include/Legacy.php): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(693) : eval()'d code on line 16

Fatal error: require_once(): Failed opening required '/usr/local/emhttp/plugins/dynamix.system.temp/include/Legacy.php' (include_path='.:/usr/local/emhttp') in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(693) : eval()'d code on line 16

Temperature readings worked until first reboot.

Using Unraid RC builds, Dynamix lightbox pop ups do not function on iOS devices once the text scrolls beyond the bottom of the lightbox (eg the update pop-up).

Right now when you finger to scroll through (for example) the update progress lightbox, the page behind the lightbox is what scrolls.

Would it be possible to add support so the s3_sleep script will check a file on the system for activity state before proceeding to sleep or shutdown? It would make the plugin a lot more flexible in terms of integrating with other services.
It can be a configurable filename and the file can contain a true/false flag or whatever the plugin needs.

I'm planning on pulling the plex activity stream count via api and in order to update the activity state, but there can be plenty of other ways to integrate with this.