Dynamix - V6 Plugins

bonienl

By bonienl
in Plugin Support

Recommended Posts

Recommended

Posted by Zonediver,

Its not broken, just "vice versa" 😉 You can fix this. If the sleep plug-in is active, you can enter all drives (which you want to monitor) under "Monitor disks outside array:" There is something "the other way around" - but it is working 😉👍 It seems the plugin does not recognise the array correctly (last update from 6.2020)      
Recommended by Squid
  • Confused
  • Thanks

3 reactions

Go to this post
  • Replies 4k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

bonienl
bonienl

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 develope

bonienl
bonienl

It has been some time since I visited the Unraid forums. Due to health issues I had to take a break, and unfortunately this break took way longer than anticipated. But I am back and will sta

bonienl
bonienl

Today has been a productive day   I have updated several Dynamix plugins, mainly bug fixes. Please check your plugins to get the updates.

Posted Images

bonienl Veteran

bonienl

Posted
  • Author
Posted
7 minutes ago, JCM said:

The "stats" page is constantly refreshing. I cant click on anything because it reloads every 0,5s or so.

Verision 2023.02.14 on Unraid Version: 6.11.5

 

Are you using Safari on an iPad?
In the above case Safari tries constantly to translate the page, hence the constant refreshes.

 

This doesn’t happen with Safari on macOS, and the problem is solved when updating the iPad to version 16.4

 

Link to comment
JCM Noob

JCM

Posted
Posted

Interesting.

I don't use any antivir plugins in my browser and the adblocker is disabled for the unraid page. I also tried it in an private firefox session without any plugin enabled but with the same behavior. If you need more information, please ask.

Link to comment
Spitko Noob

Spitko

Posted
Posted (edited)

Some notes on getting a corsair commander pro working. I needed to go this route since my Asus mobo didn't offer any PWM control out of the box.

1) The fan control plugin does not properly detect it; you'll get errors when you try to get the fan list. You can work around this though by manually specifying it. For example, in my case I have PWM controller set to corsaircpro - pwm1 (this is detected properly) and the PWM fan manually set to /sys/class/hwmon/hwmon2/fan1_input. Change the fan and hwmon numbers to match your device.

2) Trying to specify a fan from the cpro in the system temp program completely breaks the interface and indeed the entire sensors command. To get it working again, modify sensors.conf and change corsairpro-hid-3-2 (or similar) to just be corsairpro-*. Ref this github issue: https://github.com/lm-sensors/lm-sensors/issues/369 

As a note, this needs to be re-applied every reboot; I presume there's a way to fix this properly but unsure.

Edited by Spitko
formatting
Link to comment
jjthepirate Noob

jjthepirate

Posted
Posted

Anyone know how to disable the Autofan plugin altogether? I enabled it to test things out and now I can't get it to stop controlling my fans... I wanna go back to the motherboard controlling my fans so I can avoid the constant ramping up/down. Seems the plugin is still controlling my fans even after disabling/re-enabling and deleting the plugin.

 

Specs:

 

CPU: Ryzen 9 5900x

Mobo: Asrock Taichi x570

Unraid version: 6.9.11

Link to comment
alturismo Mentor

alturismo

Posted
Posted
2 hours ago, jjthepirate said:

Seems the plugin is still controlling my fans even after disabling/re-enabling and deleting the plugin.

to be sure

 

disable your settings for each fan you setted up (usually not necessary)

uninstall the plugin

remove the following folder from your flash drive (usually not necessary)

image.png.d0a9ae28717d9716af7b88fa96188c18.png

 

and finally, reboot, once your system took over the control most likely your BIOS wont take over until a reboot,

i guess here you stuck ... just a guess ;)

 

sidenote, to check if autofan is still doing something, you should see syslog entries ... just sa note and sample 

Mar 30 02:32:06 AlsServer autofan: Highest disk temp is 32C, adjusting fan speed from: 100 (39% @ 2830rpm) to: 120 (47% @ 2824rpm)
Mar 30 02:36:57 AlsServer emhttpd: spinning down /dev/sdc
Mar 30 02:37:11 AlsServer autofan: Highest disk temp is 0C, adjusting fan speed from: 120 (47% @ 2818rpm) to: OFF (0% @ 2818rpm)

 

Link to comment
Daaadou Noob

Daaadou

Posted
Posted (edited)

Hello, 

I have installed the plugin to help me manage the fan speed in regards to HDD temp but the plugin is not finding any of the fan. 
My motherboard is an Asrock H670 mITX and the fans are Noctuas' with the PWM feature. 

PWM feature is activated in the BIOS. 

I have the latest version of Unraid and the plugin is up to date. It is probably the PWM controller from the mobo which is not recognized?

 

Do you know if there is a trick to get fan control to recognize the fans plugged in chassis fan 1 on this mobo? 
Thank you in advance, 

Edited by Daaadou
Link to comment
Dimebag Noob

Dimebag

Posted
Posted
On 4/6/2023 at 12:45 PM, Daaadou said:

Hello, 

I have installed the plugin to help me manage the fan speed in regards to HDD temp but the plugin is not finding any of the fan. 
My motherboard is an Asrock H670 mITX and the fans are Noctuas' with the PWM feature. 

PWM feature is activated in the BIOS. 

I have the latest version of Unraid and the plugin is up to date. It is probably the PWM controller from the mobo which is not recognized?

 

Do you know if there is a trick to get fan control to recognize the fans plugged in chassis fan 1 on this mobo? 
Thank you in advance, 

 

Same problem (?) here. In my case i have a intel DQ77MK with 2 Artic P8 PWM PST. But the plugin doesn't recognize then unfortunately:

 

af14155e898fc7c7bb725396c2c87da9.png

Link to comment
Dimebag Noob

Dimebag

Posted
Posted (edited)

I think i got it. After install the "system temp plugin" he was able to detected and download the drivers for my MB as you can see.

 

https://i.imgur.com/WLh0GLO.png

 

After that, the dynamix could see my 3 pwm fans (CPU + other 2).

 

https://i.imgur.com/0WOZbgP.png

 

But my question now: How do I know which fan it is? I don't want target my cpu fan for 40º for example and screw it up.

 

EDIT: I just figure out. Pwm2 is the cpu fan. Problem solved. :)

Edited by Dimebag
Link to comment
TIE Fighter Rookie

TIE Fighter

Posted
Posted (edited)
On 3/23/2023 at 8:26 AM, daTroll said:


On my side, the status says “Running” in green. On your suggestion, because the Sleep plugin is no longer working also in my system, I changed the first setting to Disabled. This changed the status to “Stopped” in orange, and like you I seem to recall this is what it said in the past (before the most recent update) as well. I changed the setting back to Sleep, but going to sleep it does not. 🤷‍♂️ I’m sure I haven’t touched any configuration since it was working, except for installing a few updates including the latest Sleep plugin.

Same for me aswell s3 sleep plugin do not put the server to sleep.

So this is a new setup, Unraid 6.11.5, just installed all the plugins i normaly use and put settings for sleep in the plugin but just realised last night that it doesent go to sleep. 

Any fix for this?

@bonienl

megatron-diagnostics-20230410-1659.zip

Edited by TIE Fighter
Link to comment
Kasjo Noob

Kasjo

Posted
Posted (edited)

For me the s3 sleep plugin is still broken. (Unraid 6.11.5)

I currently use the Fork from Bjorn.
https://blog.sengotta.net/dynamix-s3-sleep-script-fork-fuer-unraid/

Main Problem on my side is, the TCP activity counter in this current version is not working at all. 


Second Problem is, the "outside Array" Feature still wont see my nvmes. It was working when it was included in the updates the first time, since then, not anymore. 

 

I Backuped the Bjorn Plugin just in case because the main forum (Kodinerds.net) from this guy seems to be offline since weeks and i was able to get it from is github. 

 

Screenshot 2023-04-13 141326.png

Screenshot 2023-04-13 141128.png

tower-diagnostics-20230413-1423.zip

Edited by Kasjo
add diagnostics
Link to comment
Zonediver Community Regular

Zonediver

Posted
Posted

I have a problem with the new version 3.0.11

When i push the sleep button, some disk spin up (?) and i got this at the syslog:

  

Apr 14 14:27:37 Horus s3_sleep: version=3.0.11
Apr 14 14:27:37 Horus s3_sleep: ----------------------------------------------
Apr 14 14:27:37 Horus s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi
Apr 14 14:27:37 Horus s3_sleep: excluded disks=nvme0n1 nvme1n1 sda
Apr 14 14:27:37 Horus s3_sleep: ----------------------------------------------
Apr 14 14:27:37 Horus s3_sleep: s3_sleep process ID 18435 started, To terminate it, type: s3_sleep -q
Apr 14 14:30:28 Horus s3_sleep: Enter sleep mode
Apr 14 14:30:28 Horus kernel: PM: suspend entry (deep)
Apr 14 14:31:21 Horus kernel: Filesystems sync: 0.017 seconds
Apr 14 14:31:21 Horus kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Apr 14 14:31:21 Horus kernel: OOM killer disabled.
Apr 14 14:31:21 Horus kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
Apr 14 14:31:21 Horus kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 14 14:31:21 Horus kernel: sd 7:0:5:0: [sdi] Synchronizing SCSI cache
Apr 14 14:31:21 Horus kernel: sd 7:0:5:0: Power-on or device reset occurred
Apr 14 14:31:21 Horus kernel: sd 7:0:4:0: [sdh] Synchronizing SCSI cache
Apr 14 14:31:21 Horus kernel: sd 7:0:4:0: Power-on or device reset occurred
Apr 14 14:31:21 Horus kernel: sd 7:0:3:0: [sdg] Synchronizing SCSI cache
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: [sdf] Synchronizing SCSI cache
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: Power-on or device reset occurred
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: attempting task abort!scmd(0x0000000080da7ace), outstanding for 10235 ms & timeout 60000 ms
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: [sdf] tag#5185 CDB: opcode=0x1b 1b 00 00 00 01 00
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: handle(0x0009), sas_address(0x4433221104000000), phy(4)
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: enclosure logical id(0x500605b006af7450), slot(7) 
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: task abort: SUCCESS scmd(0x0000000080da7ace)
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: attempting device reset! scmd(0x0000000080da7ace)
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: [sdf] tag#5185 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: handle(0x0009), sas_address(0x4433221104000000), phy(4)
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: enclosure logical id(0x500605b006af7450), slot(7) 
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: device reset: FAILED scmd(0x0000000080da7ace)
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: attempting target reset! scmd(0x0000000080da7ace)
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: [sdf] tag#5185 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: handle(0x0009), sas_address(0x4433221104000000), phy(4)
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: enclosure logical id(0x500605b006af7450), slot(7) 
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: target reset: SUCCESS scmd(0x0000000080da7ace)
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: Power-on or device reset occurred
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: attempting host reset! scmd(0x0000000080da7ace)
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: [sdf] tag#5185 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: sending diag reset !!
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: diag reset: SUCCESS
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: LSISAS2308: FWVersion(20.00.07.00), ChipRevision(0x05), BiosVersion(07.39.02.00)
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: sending port enable !!
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: port enable: SUCCESS
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: search for end-devices: start
Apr 14 14:31:21 Horus kernel: scsi target7:0:0: handle(0x0009), sas_addr(0x4433221100000000)
Apr 14 14:31:21 Horus kernel: scsi target7:0:0: enclosure logical id(0x500605b006af7450), slot(3)
Apr 14 14:31:21 Horus kernel: 	handle changed from(0x000e)!!!
Apr 14 14:31:21 Horus kernel: scsi target7:0:1: handle(0x000a), sas_addr(0x4433221101000000)
Apr 14 14:31:21 Horus kernel: scsi target7:0:1: enclosure logical id(0x500605b006af7450), slot(2)
Apr 14 14:31:21 Horus kernel: 	handle changed from(0x000d)!!!
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: handle(0x000b), sas_addr(0x4433221104000000)
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: enclosure logical id(0x500605b006af7450), slot(7)
Apr 14 14:31:21 Horus kernel: 	handle changed from(0x0009)!!!
Apr 14 14:31:21 Horus kernel: scsi target7:0:4: handle(0x000c), sas_addr(0x4433221106000000)
Apr 14 14:31:21 Horus kernel: scsi target7:0:4: enclosure logical id(0x500605b006af7450), slot(5)
Apr 14 14:31:21 Horus kernel: scsi target7:0:5: handle(0x000d), sas_addr(0x4433221107000000)
Apr 14 14:31:21 Horus kernel: scsi target7:0:5: enclosure logical id(0x500605b006af7450), slot(4)
Apr 14 14:31:21 Horus kernel: 	handle changed from(0x000b)!!!
Apr 14 14:31:21 Horus kernel: scsi target7:0:3: handle(0x000e), sas_addr(0x4433221105000000)
Apr 14 14:31:21 Horus kernel: scsi target7:0:3: enclosure logical id(0x500605b006af7450), slot(6)
Apr 14 14:31:21 Horus kernel: 	handle changed from(0x000a)!!!
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: search for end-devices: complete
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: search for end-devices: start
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: search for PCIe end-devices: complete
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: search for expanders: start
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: search for expanders: complete
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: mpt3sas_base_hard_reset_handler: SUCCESS
Apr 14 14:31:21 Horus kernel: mpt2sas_cm0: host reset: SUCCESS scmd(0x0000000080da7ace)
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: Power-on or device reset occurred
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: attempting task abort!scmd(0x0000000080da7ace), outstanding for 50171 ms & timeout 60000 ms
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: [sdf] tag#5185 CDB: opcode=0x1b 1b 00 00 00 01 00
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: handle(0x000b), sas_address(0x4433221104000000), phy(4)
Apr 14 14:31:21 Horus kernel: scsi target7:0:2: enclosure logical id(0x500605b006af7450), slot(7) 
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: task abort: SUCCESS scmd(0x0000000080da7ace)
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: Power-on or device reset occurred
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: Power-on or device reset occurred
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: [sdf] Sense Key : 0x6 [current] 
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: [sdf] ASC=0x29 ASCQ=0x0 
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: PM: dpm_run_callback(): scsi_bus_suspend+0x0/0x11 returns -5
Apr 14 14:31:21 Horus kernel: sd 7:0:2:0: PM: failed to suspend async: error -5
Apr 14 14:31:21 Horus kernel: PM: Some devices failed to suspend, or early wake event detected
Apr 14 14:31:21 Horus kernel: OOM killer enabled.
Apr 14 14:31:21 Horus kernel: Restarting tasks ... done.
Apr 14 14:31:21 Horus kernel: random: crng reseeded on system resumption
Apr 14 14:31:21 Horus kernel: video LNXVIDEO:00: Restoring backlight state
Apr 14 14:31:21 Horus kernel: PM: suspend exit
Apr 14 14:31:21 Horus s3_sleep: Wake-up from sleep mode

 

I can't put the server to sleep anymore...

So, how can i get back the older "working" version of this plugin?

I think it was 3.0.8 or so...

Link to comment
Zonediver Community Regular

Zonediver

Posted
Posted (edited)
On 4/13/2023 at 2:17 PM, Kasjo said:

Second Problem is, the "outside Array" Feature still wont see my nvmes. It was working when it was included in the updates the first time, since then, not anymore.

 

How did you fix the problem with the NVMe's?

I have the same issue...

Edited by Zonediver
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.

×
Go to topic listing