Dynamix - V6 Plugins


Recommended Posts

32 minutes ago, rbojanssen said:

I have some problems with the S3 Sleep plugin. It's a bit too eager to put the system into sleep.... ;-)

 

I have execute function on Sleep but no matter what options (Wait for array or Monitor Disks outside) I select it wil ALWAYS put computer to sleep after the Extra Delay after array inactivity.

 

My disks spin down after 30 mins. Extra delay is set to 5 mins. No matter if the array is active or not it puts my server to sleep after 5 mins. I tried enabling and disabling the "Wait for array inactivity" and select all of the array disks in "Monitor disks outside the array" but after 5 mins, computer goes to sleep.

 

Tried re-install but results are the same.

The disk activity checker function is broken in the current unRAID version.  No one knows when or if it will get fixed.

Link to comment
18 minutes ago, Bob@unraid said:

so the only way is got to the recent unraid version before the update to the current version?

 

Thanks

I think you'd need to go back to 6.11.X.  But that's not recommended.  I would try to make use of the network activity monitor or time of day exclusions.

Link to comment
On 1/31/2024 at 4:19 PM, Marc_G2 said:

The disk activity checker function is broken in the current unRAID version.  No one knows when or if it will get fixed.

Thx for the answer. It worked before indeed, I really depend on it. I'll try the network activity monitor, does it respect the 30 mins wait or is that only for array status?

 

Sleep settings.png

Link to comment

running 2024.01.05 (my birthday!) and unraid 6.12.6 and in the system stats tab, the storage graph shows 26 disks, 

image.png.382ede6ca0cb9c25b6cd86945d3f8ac6.png

 

But I have 45 disks, 44 of them are in a ZFS pool. 

 

1. can I do something to update the disks

2. does the graph speeds represent 26 or 45 disks as it is? (If it represents all of them, I dont care that it says 26)

 

Link to comment
On 1/31/2024 at 3:19 PM, Marc_G2 said:

The disk activity checker function is broken in the current unRAID version.  No one knows when or if it will get fixed.

Hi

 

i have made a few improvements to the S3 sleep plugin. One of them is that the disk activity checker is now fixed.

 

I have implemented the features mainly for myself. Therefore, not everything is 100% tested. If I find some time and the TVHeadend integration is ok for @bonienl I will do a PR. Feel free to use my fork that solves the disk activity problem until @bonienl solves the problem.

 

@bonienl See here for the fix: https://github.com/chriss158/dynamix/commit/98213df2c70ab4ee7f08475148ff31b51e677d67

 

i have made the following improvements.

- Check if a recording is currently running in TVHeadend or TVheadend is running a subscription (Live TV)
- Wake up the server when a TVHeadend recording is scheduled
- Custom wake-up times for the server, for example to wake up the server for a backup or the parity check
- Before shutdown/sleep, check whether the next wake-up time is within a defined time (15 minutes). If so, the shutdown/sleep is canceled
- Changed the option "Extra delay after inactivity" so that it runs not only after the inactivity of the array, but after all checks.

- Add check for running processes. e.g. backup script, wget, cp, rclone etc.

 

You can get the plugin from my forked repository: https://raw.githubusercontent.com/chriss158/dynamix/master/unRAIDv6/dynamix.s3.sleep.plg

 

For each new option there is an explanation when you click on the option.

 

grafik.thumb.png.fc9e599e6b70ba1be93dbd1306e6c44f.png

 

 

 

The TVheadend implementation is based on the work of https://github.com/git-developer/autosuspend

So thanks to him :D

 

 

Edited by chriss158
  • Thanks 2
Link to comment

Thanks for your work, sounds great but how do we download/install your forked version? When I follow your link on GitHub, the readme says not to download the Zip, but the links to the s3sleep plugin (like all the others) returns a 404 error.

Link to comment
57 minutes ago, spl147 said:

Excatly, I could have said that straight away :D

 

  

2 hours ago, Manni01 said:

Thanks for your work, sounds great but how do we download/install your forked version? When I follow your link on GitHub, the readme says not to download the Zip, but the links to the s3sleep plugin (like all the others) returns a 404 error.

Ignore the readme. The readme is copied/forked from the original repository

 

 

Edited by chriss158
  • Like 1
Link to comment

Hi every one, i am experince few problem since few days

When ever i sleep my server and after i resume , is starting weak procedures and then is going to sleep again before i could even access to web ui ,at this point i need to weak again but when is awke the connection of et0 is only 10mb from 1000 mb and my 10gb card is down.

Same time during the wake process just freeze 

 

 

image.png.37e976ca2516cf197bbd27b0dff03863.png

This is the log during the first wake process 

 

 

 

 

Is same one can help me on this.

 

image.thumb.png.c86b0ef01e82c639caee5260eae3c695.png

 

 

 

 

 

 

zeus-diagnostics-20240214-1335.zip

Edited by simo241
Link to comment

Does de Cache Dirs plugin contain the script or is it just a front end and I need to add that manually before installing this?

 

And would the Share Floor plugin interfere with it? As it needs to scan the directories? So it'd be scanning the indexes kept in ram?

 

Thanks!

Edited by Sptz87
Link to comment

Looking at updating the dynamix auto fan plugin.

 

Is there a way to call drives from the unassigned plugin? or a way I can say ignore them or add them to the list to be user excluded?

 

Currently they are being included under data disk and this then affects fan speed & noise while I sleep. Think others would enjoy a fix too.

 

function data_disks($disk) {
  return $disk['type']=='Data' && strpos($disk['status']??'','_NP')===false;

 

221593945_Screenshot2024-02-19at01_07_01.thumb.png.efe10bb37f0522e98f984a1f9085dc52.png

Link to comment

I am lost trying to get CPU temp to run on Gigabyte 550i Aorus pro, CPU Ryzen 5600G

So far I have K10 and it87 drivers running

This is my sensors detect

# sensors-detect version 3.6.0
# System: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX [Default string]
# Kernel: 6.1.64-Unraid x86_64
# Processor: AMD Ryzen 5 5600G with Radeon Graphics (25/80/0)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8688
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM aux hw bus 1 (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.

 

This is what I have from sensors. Really just CPU is missing, or CPU is single k10 temp sensor?

1.png.be74cdf8959f707ec8c647652b5deb99.png

Can you help me please to fix this issue?

Link to comment

I have an issue with auto fan. It looks like upon boot it's not detecting anything. I've set the fans I want to control to 100% in the bios PWM. When I run a "Detect" it detects it correctly, I set my values. If I reboot it shows 0% yet its running at 100%

 

1445502053_CleanShot2024-02-22at18_40.22@2x.png.537ac6bdc6b3ee4195a91b9a5b9f4bbb.png

 

If I go back to Auto Fan and try to change any value and save this happens and it also goes missing from System Temp plugin.

 

2144678985_CleanShot2024-02-22at18_42.21@2x.png.99823d3c69fc71203ecadfb7bfe3de90.png

 

Any idea what's up? This is using the IT87 driver on a gigabyte board

Edited by Sptz87
Link to comment
On 2/20/2024 at 9:03 PM, J05u said:

I am lost trying to get CPU temp to run on Gigabyte 550i Aorus pro, CPU Ryzen 5600G

So far I have K10 and it87 drivers running

This is my sensors detect

# sensors-detect version 3.6.0
# System: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX [Default string]
# Kernel: 6.1.64-Unraid x86_64
# Processor: AMD Ryzen 5 5600G with Radeon Graphics (25/80/0)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8688
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM aux hw bus 1 (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.

 

This is what I have from sensors. Really just CPU is missing, or CPU is single k10 temp sensor?

1.png.be74cdf8959f707ec8c647652b5deb99.png

Can you help me please to fix this issue?

did you actually read the output? the answers you seek are in the output!

 

Trying family `ITE'... Yes

Found unknown chip with ID 0x8688

 

Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check https://hwmon.wiki.kernel.org/device_support_status for driver status.

 

 

Edited by spl147
Link to comment
2 hours ago, Sptz87 said:

I have an issue with auto fan. It looks like upon boot it's not detecting anything. I've set the fans I want to control to 100% in the bios PWM. When I run a "Detect" it detects it correctly, I set my values. If I reboot it shows 0% yet its running at 100%

 

1445502053_CleanShot2024-02-22at18_40.22@2x.png.537ac6bdc6b3ee4195a91b9a5b9f4bbb.png

 

If I go back to Auto Fan and try to change any value and save this happens and it also goes missing from System Temp plugin.

 

2144678985_CleanShot2024-02-22at18_42.21@2x.png.99823d3c69fc71203ecadfb7bfe3de90.png

 

Any idea what's up? This is using the IT87 driver on a gigabyte board

whats the output of sensors detect?

Link to comment
21 minutes ago, spl147 said:

whats the output of sensors detect?

 

Not on my PC atm but it was fan2 pwm, so the correct one. But it fixed itself. Took 5 minutes for the sensor to reappear at the bottom and it's reacting accordingly. Bit weird it took a while but not gonna complain :)

Link to comment
8 hours ago, spl147 said:

did you actually read the output? the answers you seek are in the output!

 

Trying family `ITE'... Yes

Found unknown chip with ID 0x8688

 

Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check https://hwmon.wiki.kernel.org/device_support_status for driver status.

 

 

So I left without temp monitoring, not perfect.

Link to comment
18 hours ago, Sptz87 said:

 

Not on my PC atm but it was fan2 pwm, so the correct one. But it fixed itself. Took 5 minutes for the sensor to reappear at the bottom and it's reacting accordingly. Bit weird it took a while but not gonna complain :)

 

The main issue now is this:

 

134176298_CleanShot2024-02-23at15_24.04@2x.png.96ec15d7595dcda3ab94dfdae50fe2a4.png

 

It's showing the percentage number next to the PWM1 instead of PWM2 yet it's PWM2 that's being affected. PWM1 (CPU Fans) are fully controlled by bios curve. This is how my settings look:

 

Fan/PWM1 disabled:

 

1193539655_CleanShot2024-02-23at15_25.59@2x.thumb.png.79af0c66b6fe714c2ffce48f2175ce20.png

 

Fan2/PWM2 Enabled:

 

298503445_CleanShot2024-02-23at15_26.21@2x.thumb.png.10058d95fb42a6a2a7abe54b21c2bcb5.png

Edited by Sptz87
Link to comment
1 hour ago, spl147 said:

You have the wrong fan selected

 

That was my first thought as well but the one on the right is the one being affected by the changes I make. I can literally see it if I change anything. Yet the % parenthesis is showing on the left. Which is the CPU fans. I know 100% be cause I didn't the hdd fans connected to the mobo header before. 

Edited by Sptz87
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.