2 minutes ago, mikeyosm said:

version of UNRAID?

Version: 6.8.3 Pretty fresh install, just got it a few days ago.

45 minutes ago, Hkup859 said:

Version: 6.8.3 Pretty fresh install, just got it a few days ago.

try 6.9rc2 - newer linux kernel supports more mobo's

18 minutes ago, mikeyosm said:

try 6.9rc2 - newer linux kernel supports more mobo's

That did the trick! I now see a list of sensors in the dynamix system temp plug in. Thank you very much for your help!

 

If you don't mind helping with one more thing. There's a lot of sensors here and I only understand what a few are. Which ones should I use for cpu and motherboard temperature monitoring? 

 

Thanks again for your help! 

12 minutes ago, Hkup859 said:

That did the trick! I now see a list of sensors in the dynamix system temp plug in. Thank you very much for your help!

 

If you don't mind helping with one more thing. There's a lot of sensors here and I only understand what a few are. Which ones should I use for cpu and motherboard temperature monitoring? 

 

Thanks again for your help! 

https://www.linux.com/topic/desktop/advanced-lm-sensors-tips-and-tricks-linux-0/

Take a look at that, should help.

1 minute ago, mikeyosm said:

https://www.linux.com/topic/desktop/advanced-lm-sensors-tips-and-tricks-linux-0/

Take a look at that, should help.

Perfect, thanks! 

On 1/8/2021 at 12:01 PM, mikeyosm said:

I'm getting permission denied in autofan plugin.... Any ideas why? The plugin is detecting my sensor chip nct6683 OK.

 

<br /><b>Warning</b>:  file_get_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>43</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>46</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>49</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6683.2592/hwmon/hwmon3/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br />/sys/devices/platform/nct6683.2592/hwmon/hwmon3/fan2_input

 

Does anyone know what the issue might be please?

Hi folks,

I ended up inadvertently running into an issue with the fan speed plugin over the weekend that I thought might be important to report. It's worth pointing out that the fan plugin worked perfectly for several months. My motherboard is a Supermicro C9Z390-PGW, the driver loaded is coretemp nct6775.

I've been putting off a BIOS update for several months, so I finally took the time to shut the server down and take care of it. After booting everything back up, I discovered that the UnRAID GUI would stop working (crash) a few seconds after the boot process finished. Docker, VMs, network shares, etc., all continued working, and only the GUI would crash. Digging through the logs, I traced the problem back to the auto fan plugin. It seems that, for some reason, the plugin was causing the GUI to crash. I managed to remove the plugin using the console, and after doing so, the GUI started up again. I suspect that the BIOS update somehow changed the path to a hardware resource that the plugin didn't correctly handle.

 

I'm not sure what the scripts that make up the plugin look like, but it might be worth adding a check at start-up to handle any exceptions that might be thrown if allocated resources are missing. The plugin worked as expected after re-installation.

 

I hope this helps!

Edited January 12, 20215 yr by juchong

Hello, everyone. I have a problem that was caused by the system temp plugin (I think). 

• Motherboard: Supermicro X8DTL-6F
• CPU: Dual Intel Xeon X5680
• Unraid version: Latest stable (6.8, I think)

I installed this plugin almost two years ago and it worked great. About a year ago, it stopped working. I tried to re-detecting the drivers (it found one) and I was able to get the CPU temp to show, but my motherboard was now showing a negative number and I could no longer see any fan stats.

 

Today, I tried to fix this issue. I did some Googling and I came across this article in the unraid wiki. I followed the steps in the "older versions" (at the time, I thought this meant older hardware. I now know this means older unraid version) and after completing step 7, I logged into the GUI with my phone (I did the steps before while using a monitor and keyboard connected directly to the server) and tried to load the drivers. I clicked on detect and it pulled in 5 different drivers (coretemp, i5500_temp, jc42, w83627ehf, and w83795). I clicked on save and then tried to select the sensors from the drop-down menus. While I was doing this, the page tried to load and failed. I went back to the keyboard and mouse and tried pressing enter to get a response, but the system was frozen. 

 

I reset the server using the reset button on the front of my case and let it boot. I logged into the GUI again and it froze while trying to load the dashboard. I shut down the server by holding the power button on the front of the case and then turned it back on. I logged into the GUI again and I was able to get to the settings page, and then it froze again. At this point, I shut the server back down and I pulled the flash drive. I put it into my laptop to view the most recently modified files. 

 

This is where I stand now. Can someone offer some assistance, please? I would really like to not lose all of my data. I can pull information from the flash drive and upload here if it will be helpful, but I don't know what to even upload. Since the system locks up, I cant really pull the logs either. Please help!

 

Edit: Brief update. I decided to power up the server amd take a look in the BIOS for any leads. When I load into the BIOS, it is very slow and gets to the point where it becomes unresponsive. I am going to try and re-flash the BIOS and see what happens. 

Edited January 14, 20215 yr by Richamc01
Update

Is there a way to get the Auto Fan Control plugin to ignore unassigned device drives? I have an SSD there which runs hotter than the regular mechanical drives so the fan is spinning at a higher RPM than I need.

6 hours ago, remati said:

Is there a way to get the Auto Fan Control plugin to ignore unassigned device drives? I have an SSD there which runs hotter than the regular mechanical drives so the fan is spinning at a higher RPM than I need.

if the UAD devices are not in the dropdown list to exclude prolly not

may again a general question, after playing around and asking here, its only to control via hdd temps, ok.

 

Now, when i disabled now all fan controls in the plugin and uninstalled it, possible that the fans are still runing in the last state this plugin had ? and not using the default bios values ...

 

Do i need to reboot the server to drop it for real ? or may missed something ?

Hello, I have a problem with the sleep plugin.
My server just won't sleep either manually or automatic.
This is what my log says:
 

Jan 18 21:35:29 Tower s3_sleep: Enter sleep mode
Jan 18 21:35:29 Tower s3_sleep: Enter sleep state now
Jan 18 21:35:29 Tower kernel: PM: suspend entry (deep)
Jan 18 21:35:49 Tower kernel: PM: Syncing filesystems ... done.
Jan 18 21:35:49 Tower kernel: Freezing user space processes ...
Jan 18 21:35:49 Tower kernel: Freezing of tasks failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
Jan 18 21:35:49 Tower kernel: find D 0 18764 18763 0x00000004
Jan 18 21:35:49 Tower kernel: Call Trace:
Jan 18 21:35:49 Tower kernel: ? __schedule+0x4ef/0x548
Jan 18 21:35:49 Tower kernel: schedule+0x65/0x6e
Jan 18 21:35:49 Tower kernel: request_wait_answer+0xec/0x1d4
Jan 18 21:35:49 Tower kernel: ? wait_woken+0x6a/0x6a
Jan 18 21:35:49 Tower kernel: __fuse_request_send+0x78/0x7e
Jan 18 21:35:49 Tower kernel: fuse_readdir+0x16f/0x5af
Jan 18 21:35:49 Tower kernel: ? cp_new_stat+0x14b/0x17a
Jan 18 21:35:49 Tower kernel: iterate_dir+0x9a/0x12e
Jan 18 21:35:49 Tower kernel: ksys_getdents64+0x8e/0x106
Jan 18 21:35:49 Tower kernel: ? compat_filldir+0x102/0x102
Jan 18 21:35:49 Tower kernel: __x64_sys_getdents64+0x11/0x14
Jan 18 21:35:49 Tower kernel: do_syscall_64+0x57/0xf2
Jan 18 21:35:49 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 18 21:35:49 Tower kernel: RIP: 0033:0x152610072047
Jan 18 21:35:49 Tower kernel: Code: Bad RIP value.
Jan 18 21:35:49 Tower kernel: RSP: 002b:00007ffd96b18fa8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9
Jan 18 21:35:49 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000455b00 RCX: 0000152610072047
Jan 18 21:35:49 Tower kernel: RDX: 0000000000008000 RSI: 0000000000455b00 RDI: 0000000000000006
Jan 18 21:35:49 Tower kernel: RBP: ffffffffffffff80 R08: 0000000000000030 R09: 0000000000000001
Jan 18 21:35:49 Tower kernel: R10: 0000000000000100 R11: 0000000000000293 R12: 0000000000455ad4
Jan 18 21:35:49 Tower kernel: R13: 0000000000000000 R14: 0000000000455ad0 R15: 0000000000449ed0
Jan 18 21:35:49 Tower kernel: OOM killer enabled.
Jan 18 21:35:49 Tower kernel: Restarting tasks ... done.
Jan 18 21:35:49 Tower kernel: PM: suspend exit
Jan 18 21:35:49 Tower s3_sleep: Wake-up now
Jan 18 21:35:49 Tower s3_sleep: Wake-up from sleep mode

There is a task that refuses to sleep but how do I know which task it is?

 

On 1/19/2021 at 7:41 AM, abra8c said:

Hello, I have a problem with the sleep plugin.
My server just won't sleep either manually or automatic.
This is what my log says:
 

Jan 18 21:35:29 Tower s3_sleep: Enter sleep mode
Jan 18 21:35:29 Tower s3_sleep: Enter sleep state now
Jan 18 21:35:29 Tower kernel: PM: suspend entry (deep)
Jan 18 21:35:49 Tower kernel: PM: Syncing filesystems ... done.
Jan 18 21:35:49 Tower kernel: Freezing user space processes ...
Jan 18 21:35:49 Tower kernel: Freezing of tasks failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
Jan 18 21:35:49 Tower kernel: find D 0 18764 18763 0x00000004
Jan 18 21:35:49 Tower kernel: Call Trace:
Jan 18 21:35:49 Tower kernel: ? __schedule+0x4ef/0x548
Jan 18 21:35:49 Tower kernel: schedule+0x65/0x6e
Jan 18 21:35:49 Tower kernel: request_wait_answer+0xec/0x1d4
Jan 18 21:35:49 Tower kernel: ? wait_woken+0x6a/0x6a
Jan 18 21:35:49 Tower kernel: __fuse_request_send+0x78/0x7e
Jan 18 21:35:49 Tower kernel: fuse_readdir+0x16f/0x5af
Jan 18 21:35:49 Tower kernel: ? cp_new_stat+0x14b/0x17a
Jan 18 21:35:49 Tower kernel: iterate_dir+0x9a/0x12e
Jan 18 21:35:49 Tower kernel: ksys_getdents64+0x8e/0x106
Jan 18 21:35:49 Tower kernel: ? compat_filldir+0x102/0x102
Jan 18 21:35:49 Tower kernel: __x64_sys_getdents64+0x11/0x14
Jan 18 21:35:49 Tower kernel: do_syscall_64+0x57/0xf2
Jan 18 21:35:49 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 18 21:35:49 Tower kernel: RIP: 0033:0x152610072047
Jan 18 21:35:49 Tower kernel: Code: Bad RIP value.
Jan 18 21:35:49 Tower kernel: RSP: 002b:00007ffd96b18fa8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9
Jan 18 21:35:49 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000455b00 RCX: 0000152610072047
Jan 18 21:35:49 Tower kernel: RDX: 0000000000008000 RSI: 0000000000455b00 RDI: 0000000000000006
Jan 18 21:35:49 Tower kernel: RBP: ffffffffffffff80 R08: 0000000000000030 R09: 0000000000000001
Jan 18 21:35:49 Tower kernel: R10: 0000000000000100 R11: 0000000000000293 R12: 0000000000455ad4
Jan 18 21:35:49 Tower kernel: R13: 0000000000000000 R14: 0000000000455ad0 R15: 0000000000449ed0
Jan 18 21:35:49 Tower kernel: OOM killer enabled.
Jan 18 21:35:49 Tower kernel: Restarting tasks ... done.
Jan 18 21:35:49 Tower kernel: PM: suspend exit
Jan 18 21:35:49 Tower s3_sleep: Wake-up now
Jan 18 21:35:49 Tower s3_sleep: Wake-up from sleep mode

There is a task that refuses to sleep but how do I know which task it is?

 

I have fixed it, the dynamix cach dir plugin has caused this problem.

On 1/18/2021 at 10:40 PM, alturismo said:

may again a general question, after playing around and asking here, its only to control via hdd temps, ok.

 

Now, when i disabled now all fan controls in the plugin and uninstalled it, possible that the fans are still runing in the last state this plugin had ? and not using the default bios values ...

 

Do i need to reboot the server to drop it for real ? or may missed something ?

Yes you need to reboot so the BIOS can take control of the fans again. 

 

6 hours ago, exist2resist said:

Yes you need to reboot so the BIOS can take control of the fans again. 

 

i figured it meanwhile and rebooted, after trying with a sleep which ended up in a bad crash after wake, but i guess was too much sleep while running VM's and so on ...

Thanks for all the hard work and great plugins!

 

I just upgraded my mobo to something that supports fan control. I have been setting up autofan and really like this, I did have a few suggestions that would make setup much easier.

 

1: It would be really nice if it could display the RPM of the selected fan in real time once selected in the menu. Makes it easier to identify which fan it is controlling.

 

2: Once the fan is identified, it would be REALLY nice to be able to label the fan in both speedfan and system temp.

 

3: Allow for the temp sensor to be selected so you can control off of more then just the drive temps. For example I have a 10GB nic that likes to overheat when used heavily and reports temps in unraid, it would be nice to ramp the fan that blows on it up when needed instead of having to keep it high.

Ok, so I got auto fan dialed in but when restarting the server it does not start working unless I manually go into it and change a setting and press apply.

 

How do I set it to start automatically?

Hello - I'm new to unraid and just getting everything setup. How do I know which of the various listed line items represents my "mainboard temperature"? Is it AUXTIN3, PECI Agent 0 or something else? I had to reboot to get the "coretemp" ones listed, otherwise when I installed the app it only showed CPUTIN, AUXTIN3 and PECI Agent O

 

 

Edit: when I check my motherboard, it shows CPU as ~32C and motherboard as ~39C so I assume AUXTIN3 is the motherboard. I have my BIOS chassis (i.e. HDD) fan curves set to monitor the motherboard temperature. Should I change this to monitor the CPU temperature? Is there a way to have the fans monitor individual hard drives instead?

Edited January 25, 20215 yr by DrivePool9015

System Temp can't support the B550 mainboard and cpu 4600GE, press detect, there is no drive detected.

7 hours ago, vzro said:

System Temp can't support the B550 mainboard and cpu 4600GE, press detect, there is no drive detected.

I had this happen at first after I swapped from a intel motherboard. I pressed detect and it got nothing but then I rebooted and it worked after rebooting. I think it was trying to load the coretemp and it failed (there was a message on bootup). Although I am on B450.

Edited January 27, 20215 yr by TexasUnraid

I had been using the Dynamix S3 Sleep plugin for a while and all worked well for me, but recently having upgraded Unraid I am finding that when watching Plex, the plugin does not detect this and still shuts down. I have tried turning on to wait for network inactivity now as well as array inactivity to make it more strict, but before I did not need this and just had it set to check for array inactivity. Has anything changed with recent unraid versions affecting functionality? I basically want it to only shutdown from midnight onwards if it detects nothing is being watched.

 

EDIT: Adjusted settings and seems to be working ok now. I turned on the option for waiting for network inactivity, but had to set it to more than zero, for it to work. i.e. I think it was around 10Kb (the smallest amount not zero) and then things worked ok. 

Edited February 5, 20215 yr by jaybee
more info

Quick question about Dynamix S3 Sleep from me as well.

 

My hardware is:

CPU: Ryzen 7 1700

M.Board: MSI x470 Gaming Plus

 

 

Recently I have installed S3 Sleep plugin and tried to use it, triggering sleep manually so far.  There are no issues in going into sleep, however when I woke up Unraid (using physical power button) dockers and VMs were crashed, as well as the array. Parity check was automatically started, however in order to have VMs and Dockers working normal I had to reboot Unraid.

 

Is there any chance to have S3 sleep working on Ryzen and MSI mainboard? Could it be hardware issue or Unraid configuration perhaps?

Hi !

Is there a way to add a condition to prevent sleep based on UPS consumption ?

 

My problem is : I use the S3 sleep pluging to automatically put my server to sleep. It checks if no VM is runnig by pinging them. BUT, If I'm in a OS update process, the VM is not responding to the ping, so the S3 sleep pluging puts the server to sleep. Crashing my update process.

 

Graphic cards are passed through my VM resulting in more power consumption when active. I thought that by checking if the UPS power is below a certain value, the plugin could be "sure" that no VM is running.

 

But maybe there is a smarter solution with virsh ?

Hi bonienl,

 

first post in the Forums, lets see how I fare.

 

I've been playing around with a few of your plugins and noticed some things in one of them:

 

Specifically the Autofan:

Im using an old Supermicro X8DTN+, the plugin is able to recognize the correct fan input and pwm device (In case of the X8DTN+ there are 8 Fan headers and they seem to all be controlled by one pwm controller: w83795adg). So far so good.

 

Problem that i've experienced was that I was wondering why the fans were always going full throttle, even though the plugin kept changing the Input values. Found out a while later. The actual script doing the work ( /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/autofan ) has a nice variable called PWM_HIGH which is set to a standard of 255. In case of the "w83795adg" that max pwm input seems to be around 150. Now it made sense why the fans always ramped up to full speed, since that value is used to calculate how the fans are set. Changed that manually in the above mentioned script and look here, now the fans are properly controlled. But I am quite sure that the setting is gone after a reboot (since its created via the *.tgx from the plugin). I don't want to modify that since that modification will be gone if there is an update from your side.

Do you think you could add the setting for that to the settings page? Could also be interesting for people that want to limit the max speed of their fans for noise reasons.

Until then I'll maybe write a small script for myself to correct that after booting.

 

 

Another issue I noticed was that after a reboot the status of the Autofan plugin is "stopped" (which is true..no running process)... If I go into the settings and select the pwm controller it says enabled...to actually get it running I have to selected "disable" then "enable" again and apply. Then the plugin / script actually starts working. Workaround for myself is a small userscript that checks if autofan is running (pgrep) and executes the "rc.autofan start" if not. Scheduled that every 5 minutes, so after latest 5 minutes the Autofan kicks in.

Have yet to figure out why it is not started after a reboot. Any idea?

 

Thats all for for now. Hope this helps in further development.

 

Regards

-MaNIaC-

I believe my UNRAID is being spammed:
root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: uninitialized csrf_token

 

I received this on another forum post:

Is it expected to have connections from the US, the UK, Russia, Kazakstan, Lithuania, ?

Unraid is not hardened and is not supposed to face the Internet directly.

 

What can I do to stop this?