Anyone else having an issue with Disk Stats display looking squished. The bars in the graph are only a 1/8th of an inch tall and are so close together that the disk labels are overlapping. This is a brand new install of unRaid version 6.12.10 with dynamix Systems Stats version 2024.01.05. I apologize if this has been asked before but It didn't show up in my search.

Mine looks like this:

Is it just me or others are unable to connect Unraid Connect? I can't manage my NAS remotely. It simply just don't connect but shows connecting in un infinity loop. 

Does anyone has any idea about it?

Edited June 20, 20242 yr by Imran Khan

My System Temp plugin has been broken for some time, finally I understand where it's getting the information from and why it was blank. Basically if your lists are all blank but worked before it's likely because your sensors.conf has an error.

Run # sensors

If there is no errors, it's something else, if there is errors, vi into /etc/sensors.d/sensors.conf and check for a line like:

chip "nzxtsmart2-hid-#-#"

It could be corsair or some other fan type you tried to enable on the plugin.

Remove the hid-#-# part so it's like this:

chip "nzxtsmart2-*"

Change all that are like that, and save!
Now it should work (works for me at least)!

 

Link to known issue:

https://github.com/lm-sensors/lm-sensors/issues/369

Edited June 24, 20242 yr by PSteward

New build running 6.12.10 community, with Dyamix System temp 2023.02.04b. Build has i5-12600K CPU & MSI MPG B760I Edge MB. 
Current driver detection for system temp is showing coretemp nct6683. In the drop down for the CPU temp and MB temp its not clear which item is the temp for the CPU vs MB and what some of the other items are.
Any guidance?

Can please someone fix the "autofan" script?

/usr/local/emhttp/plugins/dynamix.system.autofan/scripts/autofan

    if [[ $SLEEPING -eq 0 ]]; then
      if [[ $DISK == /dev/nvme[0-9] ]]; then

the "-eq 0" is wrong here. Should be "-ne" because the temp of the hdd/nvme is not read out if it is NOT sleeping.

 

So please PLEASE change it to 

 

    if [[ $SLEEPING -ne 0 ]]; then
      if [[ $DISK == /dev/nvme[0-9] ]]; then
        CURRENT_TEMP=$(smartctl -n standby -A $DISK | awk '$1=="Temperature:" {print $2;exit}')


[...]

 

Thanks a lot.

Would save me so much heated nvmes

2 minutes ago, d3nny said:

Can please someone fix the "autofan" script?

/usr/local/emhttp/plugins/dynamix.system.autofan/scripts/autofan

    if [[ $SLEEPING -eq 0 ]]; then
      if [[ $DISK == /dev/nvme[0-9] ]]; then

the "-eq 0" is wrong here. Should be "-ne" because the temp of the hdd/nvme is not read out if it is NOT sleeping.

 

So please PLEASE change it to 

 

    if [[ $SLEEPING -ne 0 ]]; then
      if [[ $DISK == /dev/nvme[0-9] ]]; then
        CURRENT_TEMP=$(smartctl -n standby -A $DISK | awk '$1=="Temperature:" {print $2;exit}')


[...]

 

Thanks a lot.

Would save me so much heated nvmes

Submit a pull request! You can also edit your version locally

1 hour ago, spl147 said:

Submit a pull request! You can also edit your version locally

it's not maintained anymore by bergware. So pull request via github is senseless. Last update is more than a year.

Right now it's maintained by unraid itself.

 

Changing the file locally doesn't help after reboot.

8 minutes ago, d3nny said:

it's not maintained anymore by bergware. So pull request via github is senseless. Last update is more than a year.

Right now it's maintained by unraid itself.

 

Changing the file locally doesn't help after reboot.

Fork the repo, make changes and install the plugin from your fork, this is not rocket science.

Im having a problem with the integrated "trim" plugin, I created a thread as its somewhat detailed. Ive linked to it below.

The issue im having is the scheduled trim, is performing a trim on a HDD, that is alone in a pool designated for use by Frigate to store CCTV Footage. 

Frigate works perfectly fine, until the scheduled trim runs, and causes "no space available" errors in the container. 

In the thread below i dove into the script somewhat, and found it checks for if a drive is a spinning drive or SSD, but its still running the trim on the HDD anyway.

Any input on how i can prevent the trim from being performed on this particular drive?
 

 

Anyone willing to catch me up on the Dynamic S3 Sleep plugin?

 

I am trying to figure out why the plugin is completely ignoring a parity check running. I've set it up like this (see screenshot). Am I missing something?

 

Today, i got an EMail from my unraid-server with this content:

 

Event: Fix Common Problems - Horus Subject: Errors have been found with your server (Horus). Description: Investigate at Settings / User Utilities / Fix Common Problems Importance: alert

 

* **Old version of SSD Trim Schedule**

* dynamix.cache.dirs.plg Not Compatible with Unraid version 6.12.9

 

What the hell is this again?

Is this important? I dont see any functional problems...

25 minutes ago, Zonediver said:

* **Old version of SSD Trim Schedule**

Make a dummy change in the TRIM Scheduler and apply, that will updated it to the current script.

3 minutes ago, JorgeB said:

Make a dummy change in the TRIM Scheduler and apply, that will updated it to the current script.

Thanks for this hint - done 👍

2 hours ago, icezolation said:

Anyone willing to catch me up on the Dynamic S3 Sleep plugin?

 

I am trying to figure out why the plugin is completely ignoring a parity check running. I've set it up like this (see screenshot). Am I missing something?

 

Please also have a look at my fork for the sleep plugin. It fixes some stuff and adds some features.

 

Have a look here:

 

37 minutes ago, jojo345 said:

Toggle/choose all your drives under "Monitor disks outside array", might help to resolve this problem.

 

p.s.

Execute function: "enable" !?

Added my parity drive to the "Monitor disks outside array" and will test that out. Thank you. Just find it a bit weird that the plugin doesn't wait for sleep/shutdown when a parity check is running.

"Execute function" - yes, I disabled it when I noticed that the server was shutdown during the night because of the Dynamic S3 Sleep.

3 minutes ago, icezolation said:

Added my parity drive to the "Monitor disks outside array" and will test that out. Thank you. Just find it a bit weird that the plugin doesn't wait for sleep/shutdown when a parity check is running.

"Execute function" - yes, I disabled it when I noticed that the server was shutdown during the night because of the Dynamic S3 Sleep.

I think the problem here is, that the disk activity checker is broken with the current sleep version. The plugin does not correctly check if a disk is active. Therefore the plugin decides to goto sleep, because no disk activity.

 

This is also fixed in my fork.

System Temp has a small bug in it which causes the plugin startup script to delete sensors-detect on Unraid 7 betas.

 

# Remove sensors-detect script (Unraid 6.7 and earlier)
source /etc/unraid-version
version=${version:2:2}
if [[ $((${version/./}*1)) -lt 8 ]]; then
  rm -f /usr/sbin/sensors-detect
fi

 

As the above only checks the minor version number, it's evaluating 0 as less than 8 and deleting the script.

 

And once the script is deleted, the plugin can't find any sensors, identify, nor load their drivers .

Edited July 8, 20241 yr by Espressomatic

On 6/30/2024 at 12:00 AM, d3nny said:

it's not maintained anymore by bergware. So pull request via github is senseless. Last update is more than a year.

Right now it's maintained by unraid itself.

Could the @unraid team please reflect this on the plugin's "about"? Also, I'd be very happy, if this could be incorporated: https://github.com/lm-sensors/lm-sensors/issues/167 I have exactly that chip, but since the driver, outlined there, is not available fan control does not work for me. Thanks.

Edited July 10, 20241 yr by amix
fix and additional info

On 7/8/2024 at 10:14 PM, Espressomatic said:

System Temp has a small bug in it which causes the plugin startup script to delete sensors-detect on Unraid 7 betas.

 

# Remove sensors-detect script (Unraid 6.7 and earlier)
source /etc/unraid-version
version=${version:2:2}
if [[ $((${version/./}*1)) -lt 8 ]]; then
  rm -f /usr/sbin/sensors-detect
fi

 

As the above only checks the minor version number, it's evaluating 0 as less than 8 and deleting the script.

 

And once the script is deleted, the plugin can't find any sensors, identify, nor load their drivers .

Looks like there is a PR to fix this
https://github.com/bergware/dynamix/pull/91
but how do we get the sensors-detect script under /usr/sbin back after it's deleted? It is supplied by Unraid and does not come with the Plugin 

9 hours ago, Centurio said:

Looks like there is a PR to fix this
https://github.com/bergware/dynamix/pull/91
but how do we get the sensors-detect script under /usr/sbin back after it's deleted? It is supplied by Unraid and does not come with the Plugin 

For now you can do that, execute the command once and it will be fixed for now:

**REMOVED**

 

PR is already merged, please update the plugin, reboot your servers and it will work as usual.

On 7/9/2024 at 11:12 PM, amix said:

I have exactly that chip, but since the driver, outlined there, is not available fan control does not work for me. Thanks.

Did you already try to install the driver from CA:

(please remove all custom things that you maybe applied to the syslinux command line)

On 7/5/2024 at 10:04 AM, icezolation said:

Anyone willing to catch me up on the Dynamic S3 Sleep plugin?

 

Install the Version 3.0.10 and done.

All newer versions are not working properly...

15 hours ago, ich777 said:

Did you already try to install the driver from CA:

(please remove all custom things that you maybe applied to the syslinux command line)

Holy Moses, there is an addon for that! Thanks so much! I will try asap. Should I remain silent, that will only mean, that I am happy ;-D.

Fan Auto Control ignores my cache-drive temp? (UnRaid 6.12.10, Plugin 2023.02.05a)

 

Didn't exclude it from the drives-list.

would also be happy if the fans didn't just go to 0 🤔