ChirpyTurnip

I ran memtest a bunch of times a month or so back when the CPU decided to die. Everything passed....it is possible that now the RAM is having a problem, but I've also read in places that the Intel fix for the over voltage issue can also create problems. Some of the errors imply the MB has a problem, but as always it can be anything...which makes it so hard to diagnose when you don't have a stack of swappable parts. I posted here about the current problems I'm having.... The issues are intermittant....but they always show up....

Hi, I have a build based on a Core i7, the first CPU was a 13700K but it got replaced with a 14700K after it fell victim to the intel bug, but I'm still having problems, including crashes and kernel errors (and yes, I have the latest BIOS). It could now be a new fault related to the BIOS/CPU, or a MB, RAM, or HBA problem. I have no spare hardware so it is hard work trying to get it stable. At this point I'm getting really tired of fighting with it so I want out. I'll re-purpose the hardware for a PC running windows, if it gives me grief it can go back to store under warranty (they only understand windows). The question is - where do I go for my Unraid build? I run Plex and Jellyfin, the arr suite, two instances of Frigate (with external TPUs), and a bunch of other stuff.... The way I see it I have three options: Buy another system more or less the same (e.g. Core i7 again, different MB, 4x16GB RAM to make it easier to diagnose future problems etc). Pros - cost effective, easy to do. Cons - May well get the same problems again. Buy a new system based on the Core Ultra range with a Z890 chipset MB. Pros - no more voltage problems, power efficiency. Cons - Need to run Unraid 7 Beta, no support for iGPU transcoding so will need to buy an Intel Arc, possibly swapping one set of problems for another, pay a premium for bleeding edge, not a lot of community support. Change to AMD. Haven't run AMD for 20+ years as had bad experience in the Athlon days. Pros - probably cheaper, no intel crap. Cons - will need a solution for HW decoding (up to 5 parallel streams) so either a recommended graphics card or an ARC (I assume they work with AMD), and then Unraid 7. Thoughts? What would you do in my position? And if you pick an option, any recommended specs...especially if I need a graphics card for transcoding....I've not bought one for years. I can take any size MB....so there is no form factor limitation.... Any help gratefully accepted.

I'm glad you posted this. I'm having loads of problems with my Z790 system. The CPU died and got replaced under warranty, I now have the latest 'safe' BIOS but the system keeps throwing kernel errors and crashing. It could be memory, it could be the HBA, it could be the motherboard. Who knows? It is a nightmare and I can't swap components around as I simply don't have any spare components because I didn't buy two systems...like a normal person. Long story short a new PC might be the only way out of the current hole - it will be more cost/time effective than replacing one part after another. My whole beef is that I don't want to go to AMD, and I also don't want to go back to an i7 from the 14th gen as that pretty much puts me back where I am now. So I'm pretty darn stuck as Arrow lake is new (and I might be swapping one set of bugs for another) and it's not fully supported by Unraid (e.g. no transcoding). So I have no idea what to do now. Arrow Lake? Take my chances with the older generation with problems I'm already having? If I do go Arrow Lake I have to pay a premium an then buy an Arc GPU on top of that..... What to do? What to do?

More crashes.....diagnostics attached. In the log it did show that WireGuard was loading...but Wireguard is disabled.....? svalbard-diagnostics-20241120-1418.zip

It could be the network card(s), SAS Controller, motherboard, CPU.....is there any way to figure out which hardware item is causing the problem?

Just got home. Should have provided more details, but I was at work when I saw this and figured I'd post it and see what comes back. The time that this error occurred the system had already been running for 14 hours....so this isn't a boot issue....I'm also not running Wireguard (well....my GlueTun docker might be, but "unraid" isn't. This error is spontaneous - here is the preceding hours of log: Nov 19 02:19:03 Svalbard emhttpd: read SMART /dev/sdd Nov 19 02:49:35 Svalbard emhttpd: spinning down /dev/sdd Nov 19 02:49:37 Svalbard emhttpd: read SMART /dev/sdd Nov 19 03:20:09 Svalbard emhttpd: spinning down /dev/sdd Nov 19 03:20:10 Svalbard emhttpd: read SMART /dev/sdd Nov 19 03:50:44 Svalbard emhttpd: spinning down /dev/sdd Nov 19 03:50:46 Svalbard emhttpd: read SMART /dev/sdd Nov 19 04:21:18 Svalbard emhttpd: spinning down /dev/sdd Nov 19 04:21:21 Svalbard emhttpd: read SMART /dev/sdd Nov 19 04:22:19 Svalbard emhttpd: spinning down /dev/sdg Nov 19 04:53:01 Svalbard emhttpd: spinning down /dev/sdd Nov 19 04:53:03 Svalbard emhttpd: read SMART /dev/sdd Nov 19 05:23:36 Svalbard emhttpd: spinning down /dev/sdd Nov 19 05:23:37 Svalbard emhttpd: read SMART /dev/sdd Nov 19 05:45:43 Svalbard shfs: /usr/sbin/zfs create 'm2-cache/archive_backups_pembroke' 2>&1 Nov 19 05:46:21 Svalbard kernel: br-1d649d9c9840: port 1(veth34ae42a) entered disabled state Nov 19 05:46:21 Svalbard kernel: veth0ed63db: renamed from eth0 Nov 19 05:46:21 Svalbard kernel: br-1d649d9c9840: port 1(veth34ae42a) entered disabled state Nov 19 05:46:21 Svalbard kernel: device veth34ae42a left promiscuous mode Nov 19 05:46:21 Svalbard kernel: br-1d649d9c9840: port 1(veth34ae42a) entered disabled state Nov 19 05:46:21 Svalbard kernel: br-1d649d9c9840: port 1(vetha97eefb) entered blocking state Nov 19 05:46:21 Svalbard kernel: br-1d649d9c9840: port 1(vetha97eefb) entered disabled state Nov 19 05:46:21 Svalbard kernel: device vetha97eefb entered promiscuous mode Nov 19 05:46:21 Svalbard kernel: br-1d649d9c9840: port 1(vetha97eefb) entered blocking state Nov 19 05:46:21 Svalbard kernel: br-1d649d9c9840: port 1(vetha97eefb) entered forwarding state Nov 19 05:46:22 Svalbard kernel: eth0: renamed from veth39342eb Nov 19 05:46:22 Svalbard kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha97eefb: link becomes ready Nov 19 05:47:06 Svalbard kernel: br-1d649d9c9840: port 1(vetha97eefb) entered disabled state Nov 19 05:47:06 Svalbard kernel: veth39342eb: renamed from eth0 Nov 19 05:47:06 Svalbard kernel: br-1d649d9c9840: port 1(vetha97eefb) entered disabled state Nov 19 05:47:06 Svalbard kernel: device vetha97eefb left promiscuous mode Nov 19 05:47:06 Svalbard kernel: br-1d649d9c9840: port 1(vetha97eefb) entered disabled state Nov 19 05:47:06 Svalbard kernel: br-1d649d9c9840: port 1(vethbaf97ae) entered blocking state Nov 19 05:47:06 Svalbard kernel: br-1d649d9c9840: port 1(vethbaf97ae) entered disabled state Nov 19 05:47:06 Svalbard kernel: device vethbaf97ae entered promiscuous mode Nov 19 05:47:06 Svalbard kernel: br-1d649d9c9840: port 1(vethbaf97ae) entered blocking state Nov 19 05:47:06 Svalbard kernel: br-1d649d9c9840: port 1(vethbaf97ae) entered forwarding state Nov 19 05:47:07 Svalbard kernel: eth0: renamed from vethd0bd9b2 Nov 19 05:47:07 Svalbard kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbaf97ae: link becomes ready Nov 19 06:00:01 Svalbard Docker Auto Update: Community Applications Docker Autoupdate running Nov 19 06:00:01 Svalbard Docker Auto Update: Checking for available updates Nov 19 06:00:43 Svalbard Docker Auto Update: No updates will be installed Nov 19 06:31:26 Svalbard emhttpd: spinning down /dev/sdd Nov 19 06:31:28 Svalbard emhttpd: read SMART /dev/sdd Nov 19 07:00:01 Svalbard Plugin Auto Update: Checking for available plugin updates Nov 19 07:00:08 Svalbard Plugin Auto Update: tips.and.tweaks.plg version 2024.11.17a does not meet age requirements to update - 2 days old Nov 19 07:00:08 Svalbard Plugin Auto Update: Community Applications Plugin Auto Update finished Nov 19 07:00:30 Svalbard emhttpd: spinning down /dev/sde Nov 19 07:30:36 Svalbard emhttpd: spinning down /dev/sdd Nov 19 07:30:38 Svalbard emhttpd: read SMART /dev/sdd Nov 19 08:01:10 Svalbard emhttpd: spinning down /dev/sdd Nov 19 08:01:12 Svalbard emhttpd: read SMART /dev/sdd Nov 19 08:31:44 Svalbard emhttpd: spinning down /dev/sdd Nov 19 08:31:46 Svalbard emhttpd: read SMART /dev/sdd Nov 19 09:02:19 Svalbard emhttpd: spinning down /dev/sdd Nov 19 09:02:21 Svalbard emhttpd: read SMART /dev/sdd Nov 19 09:10:34 Svalbard kernel: ------------[ cut here ]------------ Nov 19 09:10:34 Svalbard kernel: kernel BUG at drivers/md/unraid.c:1617! Nov 19 09:10:34 Svalbard kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI Nov 19 09:10:34 Svalbard kernel: CPU: 19 PID: 12370 Comm: unraidd0 Tainted: P O 6.1.106-Unraid #1 Nov 19 09:10:34 Svalbard kernel: Hardware name: Gigabyte Technology Co., Ltd. Z790M AORUS ELITE AX/Z790M AORUS ELITE AX, BIOS F10 09/27/2024 After that nothing again....everything is just normal: Nov 19 09:10:34 Svalbard kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: </TASK> Nov 19 09:10:34 Svalbard kernel: ---[ end trace 0000000000000000 ]--- Nov 19 09:40:36 Svalbard emhttpd: spinning down /dev/sdj Nov 19 09:40:36 Svalbard emhttpd: spinning down /dev/sdh Nov 19 09:40:36 Svalbard emhttpd: spinning down /dev/sdf Nov 19 09:40:36 Svalbard emhttpd: spinning down /dev/sdi Nov 19 10:11:11 Svalbard emhttpd: spinning down /dev/sdd Nov 19 10:11:12 Svalbard emhttpd: read SMART /dev/sdd Nov 19 10:41:45 Svalbard emhttpd: spinning down /dev/sdd Nov 19 10:41:47 Svalbard emhttpd: read SMART /dev/sdd Nov 19 11:12:20 Svalbard emhttpd: spinning down /dev/sdd Nov 19 11:12:22 Svalbard emhttpd: read SMART /dev/sdd Nov 19 11:42:54 Svalbard emhttpd: spinning down /dev/sdd Nov 19 11:42:55 Svalbard emhttpd: read SMART /dev/sdd Nov 19 12:13:29 Svalbard emhttpd: spinning down /dev/sdd Nov 19 12:13:31 Svalbard emhttpd: read SMART /dev/sdd Nov 19 12:21:07 Svalbard emhttpd: read SMART /dev/sdh Nov 19 12:21:18 Svalbard emhttpd: read SMART /dev/sdg Nov 19 12:21:18 Svalbard emhttpd: read SMART /dev/sdf Nov 19 12:21:31 Svalbard emhttpd: read SMART /dev/sdj Nov 19 12:51:50 Svalbard emhttpd: spinning down /dev/sdd Nov 19 12:51:52 Svalbard emhttpd: read SMART /dev/sdd Nov 19 12:52:26 Svalbard emhttpd: spinning down /dev/sdh Nov 19 12:52:26 Svalbard emhttpd: spinning down /dev/sdf Nov 19 12:52:31 Svalbard emhttpd: spinning down /dev/sdj Nov 19 12:52:31 Svalbard emhttpd: spinning down /dev/sdg Nov 19 13:23:09 Svalbard emhttpd: spinning down /dev/sdd Nov 19 13:23:11 Svalbard emhttpd: read SMART /dev/sdd Nov 19 13:23:51 Svalbard emhttpd: read SMART /dev/sdh Nov 19 13:24:06 Svalbard emhttpd: read SMART /dev/sdj Nov 19 13:24:19 Svalbard emhttpd: read SMART /dev/sdf Nov 19 13:24:30 Svalbard emhttpd: read SMART /dev/sdi Nov 19 13:55:13 Svalbard emhttpd: spinning down /dev/sdd Nov 19 13:55:15 Svalbard emhttpd: read SMART /dev/sdd Nov 19 13:58:13 Svalbard emhttpd: spinning down /dev/sdi Nov 19 13:59:28 Svalbard webGUI: Successful login user root from 192.168.3.5 Nov 19 14:00:49 Svalbard emhttpd: spinning down /dev/sdf Nov 19 14:01:15 Svalbard emhttpd: spinning down /dev/sdh Nov 19 14:01:21 Svalbard emhttpd: spinning down /dev/sdj Nov 19 14:31:31 Svalbard emhttpd: spinning down /dev/sdd Nov 19 14:31:33 Svalbard emhttpd: read SMART /dev/sdd Nov 19 15:02:05 Svalbard emhttpd: spinning down /dev/sdd Nov 19 15:02:07 Svalbard emhttpd: read SMART /dev/sdd Nov 19 15:32:39 Svalbard emhttpd: spinning down /dev/sdd Nov 19 15:32:41 Svalbard emhttpd: read SMART /dev/sdd Nov 19 15:33:48 Svalbard emhttpd: read SMART /dev/sdh Nov 19 15:34:00 Svalbard emhttpd: read SMART /dev/sdj Nov 19 16:04:24 Svalbard emhttpd: spinning down /dev/sdd Nov 19 16:04:26 Svalbard emhttpd: read SMART /dev/sdd Nov 19 16:04:30 Svalbard emhttpd: spinning down /dev/sdj Nov 19 16:04:32 Svalbard emhttpd: spinning down /dev/sdh Nov 19 16:34:58 Svalbard emhttpd: spinning down /dev/sdd Nov 19 16:35:00 Svalbard emhttpd: read SMART /dev/sdd Nov 19 17:05:33 Svalbard emhttpd: spinning down /dev/sdd Nov 19 17:05:35 Svalbard emhttpd: read SMART /dev/sdd Nov 19 17:36:07 Svalbard emhttpd: spinning down /dev/sdd Nov 19 17:36:09 Svalbard emhttpd: read SMART /dev/sdd Nov 19 18:06:41 Svalbard emhttpd: spinning down /dev/sdd Nov 19 18:06:43 Svalbard emhttpd: read SMART /dev/sdd It's a bit weird. Parity check is on 45.5%, it will resume overnight.....other than happy. That brings me to the crash yesterday. The system went offline, the syslog shows thousands of these: Nov 18 18:43:18 Svalbard kernel: pcieport 0000:00:01.0: AER: Corrected error message received from 0000:01:00.0 Nov 18 18:43:18 Svalbard kernel: pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Nov 18 18:43:18 Svalbard kernel: pcieport 0000:01:00.0: device [10b5:8724] error status/mask=00000001/0000a000 Nov 18 18:43:18 Svalbard kernel: pcieport 0000:01:00.0: [ 0] RxErr Nov 18 18:43:19 Svalbard kernel: pcieport 0000:00:01.0: AER: Corrected error message received from 0000:01:00.0 Nov 18 18:43:19 Svalbard kernel: pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Nov 18 18:43:19 Svalbard kernel: pcieport 0000:01:00.0: device [10b5:8724] error status/mask=00000001/0000a000 Nov 18 18:43:19 Svalbard kernel: pcieport 0000:01:00.0: [ 0] RxErr Nov 18 18:43:20 Svalbard kernel: pcieport 0000:00:01.0: AER: Corrected error message received from 0000:01:00.0 Nov 18 18:43:20 Svalbard kernel: pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Nov 18 18:43:20 Svalbard kernel: pcieport 0000:01:00.0: device [10b5:8724] error status/mask=00000001/0000a000 Nov 18 18:43:20 Svalbard kernel: pcieport 0000:01:00.0: [ 0] RxErr Nov 18 18:43:22 Svalbard kernel: pcieport 0000:00:01.0: AER: Corrected error message received from 0000:01:00.0 Nov 18 18:43:22 Svalbard kernel: pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Nov 18 18:43:22 Svalbard kernel: pcieport 0000:01:00.0: device [10b5:8724] error status/mask=00000001/0000a000 Nov 18 18:43:22 Svalbard kernel: pcieport 0000:01:00.0: [ 0] RxErr Following a reboot, no more issues. I am pusszledified... I will upload the diagnostic once the parity check is finished. 🙂

HI, I see the below in my log: Nov 19 09:10:34 Svalbard kernel: kernel BUG at drivers/md/unraid.c:1617! Nov 19 09:10:34 Svalbard kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI Nov 19 09:10:34 Svalbard kernel: CPU: 19 PID: 12370 Comm: unraidd0 Tainted: P O 6.1.106-Unraid #1 Nov 19 09:10:34 Svalbard kernel: Hardware name: Gigabyte Technology Co., Ltd. Z790M AORUS ELITE AX/Z790M AORUS ELITE AX, BIOS F10 09/27/2024 Nov 19 09:10:34 Svalbard kernel: RIP: 0010:unraidd+0x1051/0x1140 [md_mod] Nov 19 09:10:34 Svalbard kernel: Code: 00 83 3d 83 50 00 00 03 7e 16 41 8b 56 98 89 e9 48 c7 c7 21 23 47 a0 48 8b 73 20 e8 82 7e 3f e1 41 f6 86 69 ff ff ff 02 75 02 <0f> 0b 48 8b 43 20 49 03 47 10 41 c7 46 b0 00 10 00 00 49 8b 56 10 Nov 19 09:10:34 Svalbard kernel: RSP: 0018:ffffc9000c36fdf0 EFLAGS: 00010246 Nov 19 09:10:34 Svalbard kernel: RAX: 0000000000000000 RBX: ffff88815a213658 RCX: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: RDX: 0000000000000000 RSI: ffffffff829f0720 RDI: ffff888146ea5e38 Nov 19 09:10:34 Svalbard kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8881479e4110 Nov 19 09:10:34 Svalbard kernel: R13: ffff88815a213850 R14: ffff88815a2138c8 R15: ffff8881395a12d8 Nov 19 09:10:34 Svalbard kernel: FS: 0000000000000000(0000) GS:ffff88907f8c0000(0000) knlGS:0000000000000000 Nov 19 09:10:34 Svalbard kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 19 09:10:34 Svalbard kernel: CR2: 0000148fe25b3010 CR3: 000000000420a005 CR4: 0000000000770ee0 Nov 19 09:10:34 Svalbard kernel: PKRU: 55555554 Nov 19 09:10:34 Svalbard kernel: Call Trace: Nov 19 09:10:34 Svalbard kernel: <TASK> Nov 19 09:10:34 Svalbard kernel: ? __die_body+0x1a/0x5c Nov 19 09:10:34 Svalbard kernel: ? die+0x30/0x49 Nov 19 09:10:34 Svalbard kernel: ? do_trap+0x7b/0xfe Nov 19 09:10:34 Svalbard kernel: ? unraidd+0x1051/0x1140 [md_mod] Nov 19 09:10:34 Svalbard kernel: ? unraidd+0x1051/0x1140 [md_mod] Nov 19 09:10:34 Svalbard kernel: ? do_error_trap+0x6e/0x98 Nov 19 09:10:34 Svalbard kernel: ? unraidd+0x1051/0x1140 [md_mod] Nov 19 09:10:34 Svalbard kernel: ? exc_invalid_op+0x4c/0x60 Nov 19 09:10:34 Svalbard kernel: ? unraidd+0x1051/0x1140 [md_mod] Nov 19 09:10:34 Svalbard kernel: ? asm_exc_invalid_op+0x16/0x20 Nov 19 09:10:34 Svalbard kernel: ? unraidd+0x1051/0x1140 [md_mod] Nov 19 09:10:34 Svalbard kernel: md_thread+0xf4/0x122 [md_mod] Nov 19 09:10:34 Svalbard kernel: ? _raw_spin_rq_lock_irqsave+0x20/0x20 Nov 19 09:10:34 Svalbard kernel: ? signal_pending+0x1d/0x1d [md_mod] Nov 19 09:10:34 Svalbard kernel: kthread+0xe4/0xef Nov 19 09:10:34 Svalbard kernel: ? kthread_complete_and_exit+0x1b/0x1b Nov 19 09:10:34 Svalbard kernel: ret_from_fork+0x1f/0x30 Nov 19 09:10:34 Svalbard kernel: </TASK> Nov 19 09:10:34 Svalbard kernel: Modules linked in: ipvlan wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha tun nft_compat nf_tables xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod tcp_diag inet_diag it87(O) hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs 8021q garp mrp bridge stp llc bonding tls r8125(O) zfs(PO) i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp zunicode(PO) zzstd(O) kvm_intel iosf_mbi drm_buddy i2c_algo_bit ttm btusb btrtl btbcm zlua(O) drm_display_helper btintel zavl(PO) kvm icp(PO) drm_kms_helper bluetooth drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 ecdh_generic sha1_ssse3 ecc ch341 aesni_intel usbserial zcommon(PO) crypto_simd intel_gtt Nov 19 09:10:34 Svalbard kernel: cryptd znvpair(PO) rapl spl(O) mei_pxp mei_hdcp intel_cstate gigabyte_wmi wmi_bmof mpt3sas intel_uncore nvme i2c_i801 agpgart mei_me i2c_smbus i2c_core ahci nvme_core mei libahci raid_class scsi_transport_sas syscopyarea sysfillrect sysimgblt fb_sys_fops thermal fan tpm_crb tpm_tis video tpm_tis_core tpm wmi backlight intel_pmc_core acpi_tad acpi_pad button unix [last unloaded: r8125(O)] Nov 19 09:10:34 Svalbard kernel: ---[ end trace 0000000000000000 ]--- Nov 19 09:10:34 Svalbard kernel: RIP: 0010:unraidd+0x1051/0x1140 [md_mod] Nov 19 09:10:34 Svalbard kernel: Code: 00 83 3d 83 50 00 00 03 7e 16 41 8b 56 98 89 e9 48 c7 c7 21 23 47 a0 48 8b 73 20 e8 82 7e 3f e1 41 f6 86 69 ff ff ff 02 75 02 <0f> 0b 48 8b 43 20 49 03 47 10 41 c7 46 b0 00 10 00 00 49 8b 56 10 Nov 19 09:10:34 Svalbard kernel: RSP: 0018:ffffc9000c36fdf0 EFLAGS: 00010246 Nov 19 09:10:34 Svalbard kernel: RAX: 0000000000000000 RBX: ffff88815a213658 RCX: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: RDX: 0000000000000000 RSI: ffffffff829f0720 RDI: ffff888146ea5e38 Nov 19 09:10:34 Svalbard kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8881479e4110 Nov 19 09:10:34 Svalbard kernel: R13: ffff88815a213850 R14: ffff88815a2138c8 R15: ffff8881395a12d8 Nov 19 09:10:34 Svalbard kernel: FS: 0000000000000000(0000) GS:ffff88907f8c0000(0000) knlGS:0000000000000000 Nov 19 09:10:34 Svalbard kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 19 09:10:34 Svalbard kernel: CR2: 0000148fe25b3010 CR3: 00000008cc37c006 CR4: 0000000000770ee0 Nov 19 09:10:34 Svalbard kernel: PKRU: 55555554 Nov 19 09:10:34 Svalbard kernel: ------------[ cut here ]------------ Nov 19 09:10:34 Svalbard kernel: WARNING: CPU: 19 PID: 12370 at kernel/exit.c:816 do_exit+0x87/0x923 Nov 19 09:10:34 Svalbard kernel: Modules linked in: ipvlan wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha tun nft_compat nf_tables xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod tcp_diag inet_diag it87(O) hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs 8021q garp mrp bridge stp llc bonding tls r8125(O) zfs(PO) i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp zunicode(PO) zzstd(O) kvm_intel iosf_mbi drm_buddy i2c_algo_bit ttm btusb btrtl btbcm zlua(O) drm_display_helper btintel zavl(PO) kvm icp(PO) drm_kms_helper bluetooth drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 ecdh_generic sha1_ssse3 ecc ch341 aesni_intel usbserial zcommon(PO) crypto_simd intel_gtt Nov 19 09:10:34 Svalbard kernel: cryptd znvpair(PO) rapl spl(O) mei_pxp mei_hdcp intel_cstate gigabyte_wmi wmi_bmof mpt3sas intel_uncore nvme i2c_i801 agpgart mei_me i2c_smbus i2c_core ahci nvme_core mei libahci raid_class scsi_transport_sas syscopyarea sysfillrect sysimgblt fb_sys_fops thermal fan tpm_crb tpm_tis video tpm_tis_core tpm wmi backlight intel_pmc_core acpi_tad acpi_pad button unix [last unloaded: r8125(O)] Nov 19 09:10:34 Svalbard kernel: CPU: 19 PID: 12370 Comm: unraidd0 Tainted: P D O 6.1.106-Unraid #1 Nov 19 09:10:34 Svalbard kernel: Hardware name: Gigabyte Technology Co., Ltd. Z790M AORUS ELITE AX/Z790M AORUS ELITE AX, BIOS F10 09/27/2024 Nov 19 09:10:34 Svalbard kernel: RIP: 0010:do_exit+0x87/0x923 Nov 19 09:10:34 Svalbard kernel: Code: 24 74 04 75 13 b8 01 00 00 00 41 89 6c 24 60 48 c1 e0 22 49 89 44 24 70 4c 89 ef e8 41 30 81 00 48 83 bb b0 07 00 00 00 74 02 <0f> 0b 48 8b bb d8 06 00 00 e8 43 2f 81 00 48 8b 83 d0 06 00 00 83 Nov 19 09:10:34 Svalbard kernel: RSP: 0018:ffffc9000c36fee0 EFLAGS: 00010286 Nov 19 09:10:34 Svalbard kernel: RAX: 0000000000000000 RBX: ffff8881533b0000 RCX: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: RDX: 0000000000000001 RSI: 0000000000002710 RDI: 00000000ffffffff Nov 19 09:10:34 Svalbard kernel: RBP: 000000000000000b R08: 0000000000000000 R09: ffffffff829573f0 Nov 19 09:10:34 Svalbard kernel: R10: 00003fffffffffff R11: ffff8890bfbc0ce6 R12: ffff888137fbf000 Nov 19 09:10:34 Svalbard kernel: R13: ffff8881533a6300 R14: 0000000000000002 R15: ffffffff820b3185 Nov 19 09:10:34 Svalbard kernel: FS: 0000000000000000(0000) GS:ffff88907f8c0000(0000) knlGS:0000000000000000 Nov 19 09:10:34 Svalbard kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 19 09:10:34 Svalbard kernel: CR2: 0000148fe25b3010 CR3: 00000008cc37c006 CR4: 0000000000770ee0 Nov 19 09:10:34 Svalbard kernel: PKRU: 55555554 Nov 19 09:10:34 Svalbard kernel: Call Trace: Nov 19 09:10:34 Svalbard kernel: <TASK> Nov 19 09:10:34 Svalbard kernel: ? __warn+0xab/0x122 Nov 19 09:10:34 Svalbard kernel: ? report_bug+0x109/0x17e Nov 19 09:10:34 Svalbard kernel: ? do_exit+0x87/0x923 Nov 19 09:10:34 Svalbard kernel: ? handle_bug+0x41/0x6f Nov 19 09:10:34 Svalbard kernel: ? exc_invalid_op+0x13/0x60 Nov 19 09:10:34 Svalbard kernel: ? asm_exc_invalid_op+0x16/0x20 Nov 19 09:10:34 Svalbard kernel: ? do_exit+0x87/0x923 Nov 19 09:10:34 Svalbard kernel: make_task_dead+0x11c/0x11c Nov 19 09:10:34 Svalbard kernel: rewind_stack_and_make_dead+0x17/0x17 Nov 19 09:10:34 Svalbard kernel: RIP: 0000:0x0 Nov 19 09:10:34 Svalbard kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Nov 19 09:10:34 Svalbard kernel: RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Nov 19 09:10:34 Svalbard kernel: </TASK> Nov 19 09:10:34 Svalbard kernel: ---[ end trace 0000000000000000 ]--- What does it mean? System is running a parity check following a crash yesterday.

Hi, I have two problems with my AppDataBackup plugin: I have several containers connected to GlueTun - when gluetun is updated automatically the connected containers are tagged for "rebuild" - AppDataBackup doesn't seem to know what to do here so it just tries to start the containers, but technically they "don't exist" as they need to be rebuilt. So the plugin sends me 15 warning/emails errors instead.... If I go to the Docker tab in the morning all the slave containers are sitting there stopped and waiting for rebuild - which they then do automatically, and then I can start them again. Aside from stopping GlueTun from updating automatically is there anything else I can do, or is this just a bug/known issue? I get an error every run that the VM data needs to be backed up but the VM Manager isn't running. It's not running because I'm not using it. However there isn't an option (that I can see) to exclude VM backups? I could of course run it with no VMs, but that seems a bit unnecessary? Any tips? My debug log is: e78f91bd-7896-47f3-85dc-569b52350eb8 Thanks! CP.

I want to move off the 'nightly' build and on to the 'latest' build. If I change the image then everything works as expected except that the docker image won't run - it just crashes on startup. If I install a second instance of Mealie, and specify the 'latest' version it will run just fine, BUT, I cannot restore a backup from the 'nightly' app as the restore fails (but without telling me why). So it seems I am trapped on the nightly version. I don't understand why this is the case, or how I can get my recipes out of the 'nightly' app and into the 'latest' app. It's driving me nuts, and probably because I'm missing something really stupidly obvious. 😞 Help?

So that is the crazy thing - when I remove the it87 driver, the auto fan, the go file changes, and reboot....the fans behave the same way. If I boot off a live Linux DVD and muck around there for an hour or more then everything is nice and quiet....always quiet. BUT If I boot into Unraid again then for the first minute everything is normal and quiet....and then the fans get louder and then nothing but 100% fan again....even if the CPU is idle and just 50C, fans go nuts....and only the fans I tried to control! The CPU fan I haven't controlled, that does not go 100%....if goes up and down like normal.... Like seriously....this is only happening in Unraid. I swear there is something in the config that has changed after starting to try the fan control and now Unraid *is* doing something, just not what I want. 😞 I would cry, except that I must go to bed. It is late...and the alarm clock will show me no mercy in the morning.

Thanks for your help 🙂 Yes, this path I have followed....my controller is it87.2624... * All but pwm1 are set to 1. * All can be set to any value (e.g. 100 or 150) but nothing changes and the values are not overwritten... Might be time to look for an external controller....because right now I cannot control fan via BIOS or via Unraid and that is driving me crazy.

Then I think I have followed those instructions? I think this in one where you say to put this in the go file: # Chip drivers modprobe coretemp /usr/bin/sensors -s But this I already have....I even have added this now: # Chip drivers modprobe it87 force_id=0x8689 modprobe coretemp /usr/bin/sensors -s And it is happy: it8689-isa-0a40 Adapter: ISA adapter in0: 1.44 V (min = +0.00 V, max = +3.06 V) in1: 1.98 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: 504.00 mV (min = +0.00 V, max = +3.06 V) in5: 1.81 V (min = +0.00 V, max = +3.06 V) in6: 1.99 V (min = +0.00 V, max = +3.06 V) 3VSB: 3.36 V (min = +0.00 V, max = +6.12 V) Vbat: 3.12 V fan1: 1523 RPM (min = 10 RPM) Array Fan: 1439 RPM (min = 0 RPM) Array Fan: 1178 RPM (min = 0 RPM) Array Fan: 1198 RPM (min = 0 RPM) temp1: +37.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +44.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp3: +60.0°C (low = +0.0°C, high = +127.0°C) sensor = Intel PECI temp4: +42.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp5: +48.0°C (low = +0.0°C, high = -124.0°C) sensor = thermistor temp6: +32.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor intrusion0: ALARM It is like crazy - here I run pwmconfig immediately after a reboot - you can see the fan speeds are slower at the start of the test....like the even sort of seem to respond! But by the end of the test they are racing again and the definitely do not want to play with me: # pwmconfig version 3.6.0 This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. Found the following devices: hwmon0 is nvme hwmon1 is nvme hwmon2 is nvme hwmon3 is coretemp hwmon4 is acpitz hwmon5 is it8689 Found the following PWM controls: hwmon5/pwm1 current value: 66 hwmon5/pwm1 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm2 current value: 63 hwmon5/pwm2 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm3 current value: 63 hwmon5/pwm3 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm4 current value: 63 hwmon5/pwm4 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm5 current value: 66 hwmon5/pwm5 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm6 current value: 63 hwmon5/pwm6 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) There are no usable PWM outputs. root@Svalbard:~# pwmconfig # pwmconfig version 3.6.0 This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. Found the following devices: hwmon0 is nvme hwmon1 is nvme hwmon2 is nvme hwmon3 is coretemp hwmon4 is acpitz hwmon5 is it8689 Found the following PWM controls: hwmon5/pwm1 current value: 66 hwmon5/pwm1 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm2 current value: 63 hwmon5/pwm2 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon5/pwm3 current value: 63 hwmon5/pwm3 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon5/pwm4 current value: 63 hwmon5/pwm4 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon5/pwm5 current value: 66 hwmon5/pwm5 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon5/pwm6 current value: 63 hwmon5/pwm6 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y Giving the fans some time to reach full speed... Found the following fan sensors: hwmon5/fan1_input current speed: 1638 RPM hwmon5/fan2_input current speed: 1380 RPM hwmon5/fan3_input current speed: 1144 RPM hwmon5/fan4_input current speed: 1167 RPM hwmon5/fan5_input current speed: 0 ... skipping! hwmon5/fan6_input current speed: 0 ... skipping! Warning!!! This program will stop your fans, one at a time, for approximately 5 seconds each!!! This may cause your processor temperature to rise!!! If you do not want to do this hit control-C now!!! Hit return to continue: Testing pwm control hwmon5/pwm2 ... hwmon5/fan1_input ... speed was 1638 now 1400 no correlation hwmon5/fan2_input ... speed was 1380 now 1149 no correlation hwmon5/fan3_input ... speed was 1144 now 919 no correlation hwmon5/fan4_input ... speed was 1167 now 933 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm2, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) Did you see/hear a fan stopping during the above test (n)? Testing pwm control hwmon5/pwm3 ... hwmon5/fan1_input ... speed was 1638 now 1496 no correlation hwmon5/fan2_input ... speed was 1380 now 1205 no correlation hwmon5/fan3_input ... speed was 1144 now 982 no correlation hwmon5/fan4_input ... speed was 1167 now 1001 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm3, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) Did you see/hear a fan stopping during the above test (n)? Testing pwm control hwmon5/pwm4 ... hwmon5/fan1_input ... speed was 1638 now 1537 no correlation hwmon5/fan2_input ... speed was 1380 now 1436 no correlation hwmon5/fan3_input ... speed was 1144 now 1175 no correlation hwmon5/fan4_input ... speed was 1167 now 1194 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm4, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) Did you see/hear a fan stopping during the above test (n)? Testing pwm control hwmon5/pwm5 ... hwmon5/fan1_input ... speed was 1638 now 1516 no correlation hwmon5/fan2_input ... speed was 1380 now 1436 no correlation hwmon5/fan3_input ... speed was 1144 now 1175 no correlation hwmon5/fan4_input ... speed was 1167 now 1196 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm5, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) Did you see/hear a fan stopping during the above test (n)? Testing pwm control hwmon5/pwm6 ... hwmon5/fan1_input ... speed was 1638 now 1555 no correlation hwmon5/fan2_input ... speed was 1380 now 1433 no correlation hwmon5/fan3_input ... speed was 1144 now 1171 no correlation hwmon5/fan4_input ... speed was 1167 now 1196 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm6, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) Did you see/hear a fan stopping during the above test (n)? Testing is complete. If I re-run the test there is no longer any change - 100% only!

If it helps my current go file is this: #!/bin/bash # Chip drivers modprobe coretemp /usr/bin/sensors -s # Start the Management Utility /usr/local/sbin/emhttp

This is what I'm trying to find! The simple entry in the go file and how to set the fan a speed. I've looked in the thread but I cannot find this post....I can find lots of other things but not that part. If you could share that with me that would be super helpful. :-)

Yes. Less than ideal... The bit I can't figure out is why Unraid (somehow) seizes control of the fans and ramps them up to 100%. Like control them, or don't.....but don't force them to 100% and then pretend that you can't talk to the fans. The CPU fan changes speed all the time, so BIOS is controlling that just fine - but the other fans, which are also pegged to the CPU in BIOS, don't change at all, they just stay at 100%. And before I started messing with the fan stuff they didn't run at 100% either. So there's definitely something going on... I could create a new Unraid usb stick but it's have to figure out how to migrate my config without migrating any fan stuff....

I have been chasing my tail for a week or more. It seems that with PWM fans and Gigabyte board this is not uncommon. I have followed many guides and forum posts....but always I come up empty handed. I will summarise my problem (if that is possible) and provide some logs data for you. I have installed the Dynamix Temperature and Fan Control plugins and neither gave me anything fan-control related until I also installed the IT87 plugin. Now at least I have data and I can see my four fans: CPU = CPU (Unraid detected as FAN1) CPU_OPT = Not used SYS_FAN1 = Drive Bay Rear (Unraid detected as FAN2) SYS_FAN2 = Drive Bay Front Lower (Unraid detected as FAN3) SYS_FAN3 = Drive Bay Front Upper (Unraid detected as FAN4) PUMP = Unused I have verified this verified by finger-braking the fans and seeing the changing values come through - so I know the fans are right and the speed is right. The fans are also all PWM fans (e.g NOCTUA 140mm NF-A14 PWM 1500RPM Case Fan) and they are controlled to the fan motherboard headers. The BIOS has been told that these fans should be set to PWM (not auto). If I run sensors-detect I get this: # sensors-detect version 3.6.0 # System: Gigabyte Technology Co., Ltd. Z790M AORUS ELITE AX # Kernel: 6.1.106-Unraid x86_64 # Processor: Intel(R) Core(TM) i7-14700K (6/183/1) 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): 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... Success! (driver `coretemp') 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): 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): 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): 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): Found unknown SMBus adapter 8086:7a23 at 0000:00:1f.4. Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at efa0 (i2c-0) Do you want to scan it? (YES/no/selectively): Client found at address 0x49 Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Analog Devices ADT7410/ADT7420'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... No Probing for `National Semiconductor LM73'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Probing for `SMSC EMC1023'... No Probing for `SMSC EMC1043'... No Probing for `SMSC EMC1053'... No Probing for `SMSC EMC1063'... No Client found at address 0x4b Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Analog Devices ADT7410/ADT7420'... No Probing for `Analog Devices ADT7411'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Probing for `Analog Devices ADT7481'... No Client found at address 0x51 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Next adapter: i915 gmbus dpa (i2c-1) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus dpb (i2c-2) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus dpc (i2c-3) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc1 (i2c-4) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc2 (i2c-5) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc3 (i2c-6) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc4 (i2c-7) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc5 (i2c-8) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc6 (i2c-9) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AUX USBC2/DDI TC2/PHY C (i2c-10) Do you want to scan it? (yes/NO/selectively): yes Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. Unloading i2c-dev... OK And running sensors gives me this: acpitz-acpi-0 Adapter: ACPI interface temp1: +16.8°C (crit = +20.8°C) MB Temp: +27.8°C (crit = +105.0°C) nvme-pci-0600 Adapter: PCI adapter Composite: +44.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +44.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +51.9°C (low = -273.1°C, high = +65261.8°C) nvme-pci-0700 Adapter: PCI adapter Composite: +47.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +47.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +53.9°C (low = -273.1°C, high = +65261.8°C) it8689-isa-0a40 Adapter: ISA adapter in0: 1.46 V (min = +0.00 V, max = +3.06 V) in1: 1.98 V (min = +0.00 V, max = +3.06 V) in2: 2.02 V (min = +0.00 V, max = +3.06 V) in3: 2.00 V (min = +0.00 V, max = +3.06 V) in4: 144.00 mV (min = +0.00 V, max = +3.06 V) in5: 1.81 V (min = +0.00 V, max = +3.06 V) in6: 1.99 V (min = +0.00 V, max = +3.06 V) 3VSB: 3.36 V (min = +0.00 V, max = +6.12 V) Vbat: 3.12 V fan1: 1735 RPM (min = 10 RPM) fan2: 1439 RPM (min = 0 RPM) fan3: 1161 RPM (min = 0 RPM) fan4: 1188 RPM (min = 0 RPM) temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +44.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp3: +59.0°C (low = +127.0°C, high = +127.0°C) sensor = Intel PECI temp4: +41.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp5: +47.0°C (low = +0.0°C, high = -124.0°C) sensor = thermistor temp6: +32.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor intrusion0: ALARM coretemp-isa-0000 Adapter: ISA adapter CPU Temp: +64.0°C (high = +80.0°C, crit = +100.0°C) Core 0: +64.0°C (high = +80.0°C, crit = +100.0°C) Core 4: +54.0°C (high = +80.0°C, crit = +100.0°C) Core 8: +56.0°C (high = +80.0°C, crit = +100.0°C) Core 12: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 16: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 20: +56.0°C (high = +80.0°C, crit = +100.0°C) Core 24: +56.0°C (high = +80.0°C, crit = +100.0°C) Core 28: +56.0°C (high = +80.0°C, crit = +100.0°C) Core 32: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 33: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 34: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 35: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 36: +58.0°C (high = +80.0°C, crit = +100.0°C) Core 37: +58.0°C (high = +80.0°C, crit = +100.0°C) Core 38: +58.0°C (high = +80.0°C, crit = +100.0°C) Core 39: +58.0°C (high = +80.0°C, crit = +100.0°C) Core 40: +53.0°C (high = +80.0°C, crit = +100.0°C) Core 41: +53.0°C (high = +80.0°C, crit = +100.0°C) Core 42: +53.0°C (high = +80.0°C, crit = +100.0°C) Core 43: +53.0°C (high = +80.0°C, crit = +100.0°C) nvme-pci-0900 Adapter: PCI adapter Composite: +47.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +47.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +51.9°C (low = -273.1°C, high = +65261.8°C) So far, so good, BUT, since playing with this stuff my fans are also jammed up at 100% which is a real pain because that's loud. Previously they were BIOS managed and unless the CPU was running hot they were quiet - now they are full noise all of the time except when the machine is not running Unraid or Unraid hasn't full started. As soon as the array is started we got to full noise and we stay there! Running pwmconfig also achieves nothing: # pwmconfig version 3.6.0 This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. Found the following devices: hwmon0 is nvme hwmon1 is nvme hwmon2 is nvme hwmon3 is coretemp hwmon4 is acpitz hwmon5 is it8689 Found the following PWM controls: hwmon5/pwm1 current value: 57 hwmon5/pwm2 current value: 63 hwmon5/pwm2 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm3 current value: 79 hwmon5/pwm4 current value: 63 hwmon5/pwm4 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm5 current value: 79 hwmon5/pwm6 current value: 63 hwmon5/pwm6 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) Giving the fans some time to reach full speed... Found the following fan sensors: hwmon5/fan1_input current speed: 1739 RPM hwmon5/fan2_input current speed: 1436 RPM hwmon5/fan3_input current speed: 1159 RPM hwmon5/fan4_input current speed: 1186 RPM hwmon5/fan5_input current speed: 0 ... skipping! hwmon5/fan6_input current speed: 0 ... skipping! Warning!!! This program will stop your fans, one at a time, for approximately 5 seconds each!!! This may cause your processor temperature to rise!!! If you do not want to do this hit control-C now!!! Hit return to continue: Testing pwm control hwmon5/pwm1 ... hwmon5/fan1_input ... speed was 1739 now 1730 no correlation hwmon5/fan2_input ... speed was 1436 now 1439 no correlation hwmon5/fan3_input ... speed was 1159 now 1161 no correlation hwmon5/fan4_input ... speed was 1186 now 1188 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm1, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) This lack of result is also I think why in the Dynamix Fan Controller software hitting 'DETECT' can result in random results as it simply can't find which PWM input controls which fan. But if if just let it do it's thing I can at least see in the logs that it is trying to control the fans: Sep 12 17:39:42 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1149rpm) to: 57 (22% @ 1101rpm) Sep 12 17:39:42 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1439rpm) to: 79 (30% @ 1436rpm) Sep 12 17:39:42 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1182rpm) to: 79 (30% @ 1184rpm) Sep 12 17:41:48 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1436rpm) to: 79 (30% @ 1439rpm) Sep 12 17:41:48 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1186rpm) to: 79 (30% @ 1188rpm) It just keeps running at 100%....all the time. 😞 So, in the post I quoted where you said to check a script if something was set to 1 I was interested. If this refers to setting for example pwm2_enable in order to allow control, and then similarly using an echo command to set a fan speed (e.g. echo 50 > pwm2) then sadly I cannot get that to go either.... The only this is is good at is 100%. It is very good at that. svalbard-diagnostics-20240919-1818.zip

Sorry for the reach back....@ich777 you refer to "another post" and a "script" to try and resolve fan-related issues. Are you able to provide a link to this post? I have fans that will only run at 100%, but I can see the sensor rpm data etc...I just cannot control them and this might be a answer I need. 🙂

The other off thing is that while the control doesn't really seem to work all the fans are set to run at 100%.....so the unraid machine sounds like a hovercraft....not sure how to control or stop that either... 😞

Have split my double fan, but the weirdness continues: BIOS: CPU = CPU CPU_OPT = Unused FAN1 = Drive Bay - REAR FAN2 = Drive Bay - FRONT LOWER FAN3 = Drive Bay - FRONT UPPER PUMP = Unused UNRAID Dashboard: FAN1 = CPU FAN2 = Drive Bay - REAR FAN3 = Drive Bay - FRONT LOWER FAN4 = Drive Bay - FRONT UPPER PWM Mappings in Fan Control: PWM1 = FAN2? PWM2 = FAN2? PWM3 = FAN1 = CPU??? PWM4 = FAN1 = CPU??? PWM5 = FAN3? PWM6 = FAN2? And of course nothing can actually be controlled - however I have verified that the fan rpm data is correct - so the data is right as jamming a finger in a fan quickly results in 0 rpm.

Hi, Just tried the Fan Control plugin. Have installed the ITE IT87 drivers, and can now see fan controllers and I can see fan rpm data on the dashboard. But I have a few weird problems - firstly this is the mapping from the logs I seem to have this mapping: /sys/devices/platform/it87.2624/hwmon/hwmon5/pwm1 --> /sys/devices/platform/it87.2624/hwmon/hwmon5/fan2_input /sys/devices/platform/it87.2624/hwmon/hwmon5/pwm2 --> /sys/devices/platform/it87.2624/hwmon/hwmon5/fan4_input /sys/devices/platform/it87.2624/hwmon/hwmon5/pwm3 --> /sys/devices/platform/it87.2624/hwmon/hwmon5/fan2_input /sys/devices/platform/it87.2624/hwmon/hwmon5/pwm4 --> /sys/devices/platform/it87.2624/hwmon/hwmon5/fan1_input /sys/devices/platform/it87.2624/hwmon/hwmon5/pwm5 --> /sys/devices/platform/it87.2624/hwmon/hwmon5/fan1_input /sys/devices/platform/it87.2624/hwmon/hwmon5/pwm6 --> /sys/devices/platform/it87.2624/hwmon/hwmon5/fan2_input Now I only have three fans connected (CPU, Case 1, Case2/3) - so a total of three fans sort of makes sense, but not the multiple PWM assignments - I thought that should be 1:1 and where there is no connected fan just plain 'nothing'.... Then, I also can't tell which fan is which - for example, which one is the CPU? I don't want to mess with that one....but let's pretend I don't care.....if I set all of them to be managed I can see in the logs that the system is trying to manage the fans: e.g. adjusting fan speed from: FULL (100% @ 1102rpm) to: OFF (0% @ 1165rpm) But nothing actually changes? The dashboard shows that the fan speed remains constant - nothing slows or drops to 0%. I'm running on a Gigabyte Aorus Z790M Elite AX, with fans connected to CPU_FAN and SYS-FAN1/2/3. I've not make any changes to the the config (e.g. adding acpi_enforce_resources=lax and modprobe it87 force_id=0x8628 to the flash config) - I can do this, but because it seemed to be working I wasn't sure I wanted to mess with it....maybe this *is* required to make it actually work? What am I missing? 😞