Kydonakis

I have the system temp plugin installed for quite a while. This is my setting (motherboard: Gigabyte B560M AORUS PRO AX), not sure when and how I managed to tune it, but it works: Go file: ... modprobe it87 force_id=0x8628 ... Syslinux config: System temp setting: And the result: All good with the exception I noticed today during boot: Anything strange, misconfigured, weird in my settings (go file mostly)? Is there a correct/better way to setup the drivers needed to have temps and array fan speeds in the GUI? Thanks.

Crystal clear. Thanks for the reply.

Thanks for the reply. I went through the article yesterday and this is when I started checking things. Let me ask you this. For example, my win10 VM runs over a year and occupies 233G (according to "ls" command and the unraid VM tab in the GUI). It's allocated space now reads 221G. What you explain here is that it can occupy in reality, on the disk, let's say size equal to 300G due to the non-trimming over time? And the remaining 67G are unmapped and reported nowhere? Thanks.

Please tell me what is wrong here. I have an nvme (Samsung 970 EVO Plus 500G) in the "cache_nvme" pool which hosts only the "domains" share. My 5 VMS occupy about 353G based on their vdisk size (somewhat lower is the allocated space). The nvme drive has another 73G free space. The maths: 353+73 = 426G*, which is 74G less than the capacity of the drive. What am I missing here? Any ideas? * There are no hidden files in the nvme, only the .qcow2 files of the VMS.

That is what I suspected but needed a pro answer. Thanks!

Can someone please explain the following image? This disk was in a windows desktop before mounting it to unraid. Where is this *-part1 coming from? Can or should I remove it somehow?

I removed the statistics.sender.plg, old stuff remained in the server forever. iGPU is used for plex transcoding. I will keep an eye on the logs and report back if the crash occurs again. Thanks for your time.

Thanks for the reply. Server crashed. then had to unplug it to get back live. As soon as it booted I, I grabbed the first of the attached diagnostics (2022-02-16), then (think I indeed first grabbed the diagnostics) uninstalled corefreq without rebooting. After 24hours it crashed again. I unplugged and plugged it to get back online. I did a clear reboot and as soon it booted and then grabbed the second diagnostics file (2022-02-17).

Hello there and thanks for the effort. It is the second day in a row the server crashed and became unresponsive. From the logs I managed to grab through my remote log server I see the following (attached at the end). I am not the expert in linux but I suspected corefreq as the cause and uninstalled it before the second crash. Any advice on what is going on and if the issue is indeed related to corefreq? My system has Gigabyte Technology Co., Ltd. B560M AORUS PRO AX Intel Core i7-10700 64gb ddr4 HyperX predator ram (4x16 dimms) Before uninstalling corefreq on 2022-02-16 Feb 16 11:18:20 Tower kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Feb 16 11:18:20 Tower kernel: rcu: #0116-...0: (0 ticks this GP) idle=772/1/0x4000000000000000 softirq=62494954/62494954 fqs=14977 Feb 16 11:18:20 Tower kernel: #011(detected by 12, t=60002 jiffies, g=133319997, q=11304) Feb 16 11:18:20 Tower kernel: Sending NMI from CPU 12 to CPUs 6: Feb 16 11:18:20 Tower kernel: NMI backtrace for cpu 6 Feb 16 11:18:20 Tower kernel: CPU: 6 PID: 7350 Comm: php Tainted: G W O 5.10.28-Unraid #1 Feb 16 11:18:20 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. B560M AORUS PRO AX/B560M AORUS PRO AX, BIOS F4 03/04/2021 Feb 16 11:18:20 Tower kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x79/0x18a Feb 16 11:18:20 Tower kernel: Code: c1 e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 74 0c 0f ba e0 08 72 1a c6 47 01 00 eb 14 85 c0 74 0a 8b 07 84 c0 74 04 f3 90 <eb> f6 66 c7 07 01 00 c3 48 c7 c0 00 30 02 00 65 48 03 05 f0 8e f8 Feb 16 11:18:20 Tower kernel: RSP: 0018:ffffc900002a4e58 EFLAGS: 00000002 Feb 16 11:18:20 Tower kernel: RAX: 0000000000180101 RBX: ffffc900002a4e80 RCX: 0000000000000000 Feb 16 11:18:20 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8881000b9540 Feb 16 11:18:20 Tower kernel: RBP: ffff88814911a000 R08: ffffffff82013888 R09: ffffffff82013580 Feb 16 11:18:20 Tower kernel: R10: 000a5d1eae38384c R11: 0000000000000000 R12: 0000000000000000 Feb 16 11:18:20 Tower kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 00002c52b99306c0 Feb 16 11:18:20 Tower kernel: FS: 0000148fc63ab780(0000) GS:ffff88907c380000(0000) knlGS:0000000000000000 Feb 16 11:18:20 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 16 11:18:20 Tower kernel: CR2: 0000148fc96eaf52 CR3: 000000011e53e003 CR4: 00000000007726e0 Feb 16 11:18:20 Tower kernel: PKRU: 55555554 Feb 16 11:18:20 Tower kernel: Call Trace: Feb 16 11:18:20 Tower kernel: <IRQ> Feb 16 11:18:20 Tower kernel: queued_spin_lock_slowpath+0x7/0xa Feb 16 11:18:20 Tower kernel: nr_blockdev_pages+0x13/0x64 Feb 16 11:18:20 Tower kernel: si_meminfo+0x3a/0x57 Feb 16 11:18:20 Tower kernel: Sys_MemInfo+0x20/0x9b [corefreqk] Feb 16 11:18:20 Tower kernel: ? update_cfs_rq_load_avg+0x14b/0x154 Feb 16 11:18:20 Tower kernel: ? timekeeping_get_ns+0x19/0x2f Feb 16 11:18:20 Tower kernel: ? Sys_DumpTask+0xe9/0xf1 [corefreqk] Feb 16 11:18:20 Tower kernel: Cycle_Skylake+0x53a/0x730 [corefreqk] Feb 16 11:18:20 Tower kernel: __hrtimer_run_queues+0xb7/0x10b Feb 16 11:18:20 Tower kernel: ? Cycle_Skylake_X+0x711/0x711 [corefreqk] Feb 16 11:18:20 Tower kernel: hrtimer_interrupt+0x8d/0x15b Feb 16 11:18:20 Tower kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Feb 16 11:18:20 Tower kernel: asm_call_irq_on_stack+0xf/0x20 Feb 16 11:18:20 Tower kernel: </IRQ> After uninstalling corefreq on 2022-02-17 Feb 17 12:17:56 Tower kernel: rcu: INFO: rcu_sched self-detected stall on CPU Feb 17 12:17:56 Tower kernel: rcu: #0115-....: (60000 ticks this GP) idle=25a/1/0x4000000000000000 softirq=3595028/3595028 fqs=14991 Feb 17 12:17:56 Tower kernel: #011(t=60001 jiffies g=8644697 q=12441) Feb 17 12:17:56 Tower kernel: Sending NMI from CPU 5 to CPUs 2: Feb 17 12:17:56 Tower kernel: NMI backtrace for cpu 2 Feb 17 12:17:56 Tower kernel: CPU: 2 PID: 31137 Comm: sh Tainted: G W O 5.10.28-Unraid #1 Feb 17 12:17:56 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. B560M AORUS PRO AX/B560M AORUS PRO AX, BIOS F4 03/04/2021 Feb 17 12:17:56 Tower kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x79/0x18a Feb 17 12:17:56 Tower kernel: Code: c1 e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 74 0c 0f ba e0 08 72 1a c6 47 01 00 eb 14 85 c0 74 0a 8b 07 84 c0 74 04 f3 90 <eb> f6 66 c7 07 01 00 c3 48 c7 c0 00 30 02 00 65 48 03 05 f0 8e f8 Feb 17 12:17:56 Tower kernel: RSP: 0018:ffffc900001f4e58 EFLAGS: 00000002 Feb 17 12:17:56 Tower kernel: RAX: 0000000000200101 RBX: ffffc900001f4e80 RCX: 0000000000000000 Feb 17 12:17:56 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8881000b9540 Feb 17 12:17:56 Tower kernel: RBP: ffff888148c5c000 R08: ffffffff82013888 R09: ffffffff82013580 Feb 17 12:17:56 Tower kernel: R10: 0000bbd29ebe3599 R11: 0000000000000000 R12: 0000000000000000 Feb 17 12:17:56 Tower kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000040192991d6a Feb 17 12:17:56 Tower kernel: FS: 0000152b91169740(0000) GS:ffff88907c280000(0000) knlGS:0000000000000000 Feb 17 12:17:56 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 17 12:17:56 Tower kernel: CR2: 0000152b911ece40 CR3: 0000000165a5a001 CR4: 00000000007726e0 Feb 17 12:17:56 Tower kernel: PKRU: 55555554 Feb 17 12:17:56 Tower kernel: Call Trace: Feb 17 12:17:56 Tower kernel: <IRQ> Feb 17 12:17:56 Tower kernel: queued_spin_lock_slowpath+0x7/0xa Feb 17 12:17:56 Tower kernel: nr_blockdev_pages+0x13/0x64 Feb 17 12:17:56 Tower kernel: si_meminfo+0x3a/0x57 Feb 17 12:17:56 Tower kernel: Sys_MemInfo+0x20/0x9b [corefreqk] Feb 17 12:17:56 Tower kernel: ? ttwu_do_wakeup.isra.0+0xe/0x8c Feb 17 12:17:56 Tower kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Feb 17 12:17:56 Tower kernel: ? paravirt_sched_clock+0x5/0x8 Feb 17 12:17:56 Tower kernel: ? timekeeping_get_ns+0x19/0x2f Feb 17 12:17:56 Tower kernel: ? Sys_DumpTask+0xe9/0xf1 [corefreqk] Feb 17 12:17:56 Tower kernel: Cycle_Skylake+0x53a/0x730 [corefreqk] Feb 17 12:17:56 Tower kernel: __hrtimer_run_queues+0xb7/0x10b Feb 17 12:17:56 Tower kernel: ? Cycle_Skylake_X+0x711/0x711 [corefreqk] Feb 17 12:17:56 Tower kernel: hrtimer_interrupt+0x8d/0x15b Feb 17 12:17:56 Tower kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Feb 17 12:17:56 Tower kernel: asm_call_irq_on_stack+0xf/0x20 logs20220217.txt logs20220216.txt

Same issue here under almost same settings (start at 00:30 end of month). Parity check didn't start.

ok, I see. It is only the "reset status" of the gpu bios that causes the fans to rotate at some speed and this comes with no extra load (power consumption). Thanks for the information. It is then, in my case, either choosing between a 24/7 half-speed fan spin (vm shut down) and the zero fan speed that comes with an extra 50-60W on the idle vm (cpu consumption and random windows disk readings/writings).

Thanks for the reply. Very nice plugin for monitoring. One gpu (gtx1060) in my system which is used by one vm. While the vm is shut down, I see that the gpu fan are spinning so there should be some load on the gpu. This is what I am investigating here!

Thanks for the great plugin and support thread. So, a gpu that is bind to vfio and also used in a vm (shut down), won't appear in the plugin? My idea here is to try check the gpu power status, usage, fan speeds etc. while idle and before turning on the windows vm.

I have already setup the rest of the containers with the subfolder method and I was wondering how I can attach motioneye to the existing config.

Hi guys. Awesome support in this thread. Anyone to indicate me how to configure letsencrypt for a container that doesn't support a base url (e.g., motioneye container running on unraid-IP:8765)? Does it help if the container is running on its own lan IP or not? What needs to be added to the letsencrypt configuration file? Apologies if it has been already replied somewhere in the last 156 pages.

Thanks mate. I checked Squid's post but didn't realize it described my issue.

It has been couple weeks now that the plugin updates all linuxserver containers every night. Anyone else having the same issue? Or any clue what might be wrong here?

New unraid user here and many thanks for the plugin. I am running on a ASRock rack c236. So, I pull the container from the CA. But there is nothing in the global/dashboard sensors or footer settings. Neither in the readings. When I go fan control/configure I get a "Checking IPMI fan Locations..." echo and after a while all "locations" are tagged as "none". I guess I miss something big here. Can you please advice?