LOOPMDS

after nerdpack has been deprecated i seem to have lost the ability to control array fan on my Gigabyte a520i AC motherboard. i installed phython3 plugin. but i seem to have lost the ability to control the fan speed. can anybody help? --------------------------------------------------------------- sensors-detect : # sensors-detect version 3.6.0 # System: Gigabyte Technology Co., Ltd. A520I AC [-CF] # Kernel: 6.6.68-Unraid x86_64 # Processor: AMD Ryzen 5 5500GT 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 0x8689 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. root@UNRAID:~# sensors it8689-isa-0a40 Adapter: ISA adapter in0: 1.18 V (min = +0.00 V, max = +3.06 V) in1: 2.02 V (min = +0.00 V, max = +3.06 V) in2: 2.00 V (min = +0.00 V, max = +3.06 V) in3: 2.00 V (min = +0.00 V, max = +3.06 V) in4: 996.00 mV (min = +0.00 V, max = +3.06 V) in5: 900.00 mV (min = +0.00 V, max = +3.06 V) in6: 1.37 V (min = +0.00 V, max = +3.06 V) 3VSB: 3.31 V (min = +0.00 V, max = +6.12 V) Vbat: 3.22 V fan1: 1630 RPM (min = 0 RPM) Array Fan: 530 RPM (min = 0 RPM) temp1: +36.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +38.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp3: +44.0°C (low = +127.0°C, high = +127.0°C) sensor = AMD AMDSI temp4: +20.0°C (low = +0.0°C, high = +127.0°C) sensor = thermistor temp5: +38.0°C (low = +0.0°C, high = -124.0°C) sensor = thermistor MB Temp: +42.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor intrusion0: ALARM gigabyte_wmi-virtual-0 Adapter: Virtual device temp1: +36.0°C temp2: +38.0°C temp3: +44.0°C temp4: +20.0°C temp5: +38.0°C temp6: +42.0°C k10temp-pci-00c3 Adapter: PCI adapter CPU Temp: +44.9°C amdgpu-pci-0600 Adapter: PCI adapter vddgfx: 1.24 V vddnb: 999.00 mV edge: +35.0°C PPT: 13.00 W acpitz-acpi-0 Adapter: ACPI interface temp1: +16.8°C temp2: +16.8°C nvme-pci-0500 Adapter: PCI adapter Composite: +41.9°C (low = -40.1°C, high = +83.8°C) (crit = +87.8°C) Sensor 1: +62.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +36.9°C (low = -273.1°C, high = +65261.8°C)

i Agree, would prefere more documentation to what it actually does, automatic updates ? does it show if an update requires reboot? etc. i like the idear to patch, but i would love to se better documentation and insight into the options and functions.

this did work on my primary Unraid server. But on my backup Unraid server it wont start, and i get no real error in log See log. (first Remove , then reinstall.) i even tried to delete the controlr.conf after remove) May 16 10:19:02 UNRAID2 root: plugin: controlr.plg removed May 16 10:23:02 UNRAID2 root: plugin: creating: /boot/config/plugins/controlr/controlr-v2024.05.11a.tgz - downloading from URL https://github.com/jbrodriguez/controlr/releases/download/v2024.05.11a/controlr-v2024.05.11a.tgz May 16 10:23:09 UNRAID2 root: plugin: checking: /boot/config/plugins/controlr/controlr-v2024.05.11a.tgz - MD5 May 16 10:23:10 UNRAID2 root: plugin: creating: /boot/config/plugins/controlr/controlr.cfg - from INLINE content May 16 10:23:10 UNRAID2 root: plugin: creating: /boot/config/plugins/controlr/controlr.env - from INLINE content May 16 10:23:10 UNRAID2 root: plugin: running: anonymous May 16 10:23:10 UNRAID2 root: plugin: creating: /tmp/controlr-chkconf - from INLINE content May 16 10:23:10 UNRAID2 root: plugin: running: /bin/bash /tmp/controlr-chkconf May 16 10:23:10 UNRAID2 root: plugin: controlr.plg installed May 16 10:23:22 UNRAID2 autofan: Highest disk temp is 42C, adjusting fan speed from: 219 (85% @ 0rpm) to: 189 (74% @ 0rpm) May 16 10:23:24 UNRAID2 ool www[12097]: /usr/local/emhttp/plugins/controlr/scripts/start May 16 10:23:24 UNRAID2 sudo: root : PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/bash -c 'env PORT=2378 SHOW_UPS=true /usr/local/emhttp/plugins/controlr/controlr --port 2378' May 16 10:23:24 UNRAID2 sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) May 16 10:23:24 UNRAID2 sudo: pam_unix(sudo:session): session closed for user root Then i discoveren that the /boot/config/plugins/controlr/controlr.env file was much larger (24B) on the backup unraid server. so i deleted the file on backup unraid server and started the controlr plugin from settings menu. and it worked. As far as i can see on my primary unraid server the file has no real content and is only 1B of size. Hope this can help others.

fixed it for me aswell... thx

This new lock is pretty hard to see locked(green). in the standard Green color theme the lock is very har to see unless you know where to look. i suggest changing the color somewhat to improve visibility...og adding it to Display setting and let user decide color....

your absolutely right. sorry... i missed that option completely. thx

i do, in main menu. Add Remote Share. but i cant change destination for "copy" i only se local shares.

is it possible to add remote shares as destination?

i fixed it by doing : mysql -u root -p and SET GLOBAL log_bin_trust_function_creators = 1; verify it works, then and then adding below in the "custom.cnf" log_bin_trust_function_creators = 1

using latest version of "linuxserver/mariadb" for my Zabbix. Zabbix Server "zabbix/zabbix-server-mysql:latest" failed to updgrade Database When i try to upgrade Zabbix to 6.2 from 6.0.5 docker i get below error in Zabbix Server log from "Zabbix Server" Log: --------------------- 7:20220705:141509.188 completed 48% of database upgrade 7:20220705:141509.189 [Z3005] query failed: [1419] You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) [create trigger hosts_insert after insert on hosts for each row insert into changelog (object,objectid,operation,clock) values (1,new.hostid,1,unix_timestamp())] 7:20220705:141509.189 database upgrade failed 7:20220705:141509.191 database could be upgraded to use primary keys in history tables. -------------------------------------------- im no db expert. so if anybody knows hoiw to fix this. never seen this problem before. i updated from 5.x to 6.0.5 with no trouble.

reported as known Bug.

i get an "hostfile_replace_entries" error when ssh from my primary unraid server "TOWER" to my backup unraid server "testTOWER" or the other way around... ----TOWER--- root@TOWER:~/.ssh# ssh [email protected] (testTOWER) Load key "/root/.ssh/id_rsa": invalid format hostfile_replace_entries: link /root/.ssh/known_hosts to /root/.ssh/known_hosts.old: Operation not permitted update_known_hosts: hostfile_replace_entries failed for /root/.ssh/known_hosts: Operation not permitted Last login: Fri Jun 3 13:50:54 2022 from IP.IP.IP.IP Linux 5.15.43-Unraid. ------- ----testTOWER---- root@testTOWER:~/.ssh# ssh [email protected] (TOWER) hostfile_replace_entries: link /root/.ssh/known_hosts to /root/.ssh/known_hosts.old: Operation not permitted update_known_hosts: hostfile_replace_entries failed for /root/.ssh/known_hosts: Operation not permitted Last login: Fri Jun 3 12:30:27 2022 from IP.IP.IP.IP Linux 5.14.15-Unraid. ---------- i run 6.10.0 rc2 on TOWER and and 6.10.2-rc3 on testTOWER i used ssh-keygen to create keys on both and user ssh-copy-id to ensure keys are on both. and this worked before i upgraded to 6.10.2-rc3 from 6.10.0 stable on testTOWER server. if i ssh from my windows pc to each i get no error (keys from that is on both servers. anybody else seen this issue?

i get the same errors in the log. running UNRAID 6.10.0 RC2

Hi Dev. Thanks for a nice product. possible to get the "NUT - Network UPS Tools" plugin supported for UPS? load and status support. support forum post: https://forums.lime-technology.com/topic/60217-plugin-nut-v2-network-ups-tools/

my wallet cant connect. chia wallet show : ------ Connection error. Check if the wallet is running at 9256. You can run the wallet via: chia start wallet ------ i restarted the docker twice. and its in sync.

update i enabled "Typical" in BIOS for "Power Supply Idle Control" and its been stable since.

try plugin tips and tweaks and set "CPU Scaling Governor" to performance and look at this thread. https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/page/2/ this video : perhaps it helps? let me know what helped you 🙂 running a ryzen 1600x myself.

i just disabled xmp altogether for a while

i tried update bios to latest. and will try to append rcu_nocbs=0-11 if that does not work. thx for input

hi guys i need help. my unraid server crashes or reboots once or twice a day. i have not much running at the moment - No vm's only select dockers. - vacation time. 🙂 i tried installing mcelog , but apparently my cpu is not supported. can anyone help please? unraid-diagnostics-20210715-2134.zip

i could come up with a few things Try new psu In the tweak settings try performance settings away from default “on demand” flash bios on motherboard try new vm, fresh installs and see if same crash occur

i Get the same error... and then the docker stops.. what changed in this last update? have been running this chia docker as harvester only for many days...

i think you are missing a step. my Guide: 1.) Telegram App: open chat "BotFather" 2.) Telegram App: write /newbot 3.) Telegram App: name Bot 4.) Telegram App: name username for the Bot 5.) Telegram App: now you should recieve a long text mssage in "BotFather" with access token. 6.) UNRAID: paste access token into Settings -> Notification -> Telegram -> access token field 7.) Telegram App: click on top link in chat that looks like t.me/<botname> 8.) Telegram App: click start in the new chat. and write /start to start the Bot. 9.) UNRAID: click the Test button in the Unraid UI 10.) UNRAID: set the "Available notifications" and "Notification entity" as required