Hoopster

Ah, OK. A different situation than mine then. The br0 call trace issue has been around for three years. It has something to do with the way docker/macvlan networking works on the physical hardware. The issue is not an unRAID specific issue and has been reported on Ubuntu and other Linux distros. The potential fix (hopefully, it is a real fix) in unRAID 6.9.2 apparently involves a Linux kernel patch. As such, it highlights that Limetech really did not have much control over this one. I am just glad the VLAN thing worked for me three years ago or all my docker containers would have to be in bridge or host mode. That can get messy when they start fighting over wanting the same ports.

LOL - I was going to ask if you had Ubiquiti UniFi hardware. A large percentage of us who have these macvlan call traces have UniFi. However, I believe @bonienl also has some UniFi and he has not had the call traces so that cannot be the sole determining factor. By default, the UniFI routers pass all LAN traffic freely among the "Corporate" LANs which includes any VLANs. I currently have my unifi-controller in bridge mode which puts it on the same subnet as the router, switches and APs it controls as there are no port conflicts with other containers. However, early on in my VLAN experimentation, I believe I had it on the VLAN and did not have any issues. I am not 100% certain of this, but that is my recollection In my case, Controller Hostname/IP setting in the controller is the unRAID server IP address since the controller is in bridge mode; however, if it is put on a VLAN it would need to be set to the IP address assigned in the controller container. I eagerly await unRAID 6.9.2 "soon"

I have a Xeon E-2288G which is the Xeon equivalent of the i9-9900K and HW transcoding works great. However, I am not transcoding any 4K content. You should make sure your Plex docker container is up to date. There were some recent Plex releases that messed up 4K/HDR transcoding. The very latest versions just released a couple of days ago on both the public and Plex Pass channels seem to have fixed it. EDIT: I guess results vary. For some it works, for other there are still issues. Start reading here. And see this Plex forum thread. https://forums.plex.tv/t/4k-hdr-hevc-hw-transcoding-is-broken-on-1-22-1-4200/702328 Bottom line is it is a Plex issue.

You have this issue. Try the WSD options fix mentioned in the thread or disable WSD. As to the issue in the thread title, the default log size is only 128M and is in RAM. Try this command to see what is in the log to see if something in particular contains a lot of log files: du -sm /var/log/*

IP addresses on br0 work great on many systems with no call traces. The problem only arises with certain hardware setups. Some have it, some don't and so far there has been no common denominator identified. If you have the problem, VLANs seem to be the solution that works for most.

As mentioned by @jonathanm you have lots of macvlan broadcast call traces in your syslog. These will eventually crash the server. If you have IP addresses assigned to docker containers on br0/br1 see this thread for some possible solutions.

If you go to the terminal and type "sensors" what do you see? On my board it is the Nuvoton nct6791 providing voltage info. Here is what I see for my board and I am running unRAID 6.9.1:

Edit the network.cfg file text file in the /config folder of your unRAID boot flash drive. Before editing this file, you might just try renaming it and rebooting. This will force the creation of a new network.cfg file with default settings. Default uses DHCP.

I assume you want this for all appdata for all docker containers and not just Plex? If you want your appdata to live on the M2 SSD, make appadata "Use cache pool : only/prefer" in the appdata share settings and specify the M2 drive pool as the cache pool to be used. Only means no appdata files can exist anywhere else and if you run out of space, you will get errors. Prefer means store appdata files on the selected cache pool as long as there is space, but, if there is no space, let them overflow to the array. You will have to move the current appdata off the unassigned device and to the M2 cache pool and modify docker paths and docker settings to point to the new appdata location. Where is your docker.img file currently stored? Is it in the default location of the system share are did you create its elsewhere?

You won't get the full speed of an SSD unless you are writing from SSD to SSD over a 10Gb network or internally in the server. If you are writing from an HDD to an SSD over a 1Gb network you should be able to come close to saturating the network; however, there are always some overhead factors that will reduce that somewhat. If you have the share set to "use cache: yes" you are correct, this is how it should work. Writes the share are first cached on the cache drive with no parity calculations involved as cache is not part of the parity-protected array. When the mover runs at night, the data is moved from cache to the HDD(s) that are included in the share and parity is calculated and written then. There are a few threads in the forums about improving write speed with SSDs, in particular Samsung SSDs. This involves formatting the cache drive with 1MiB partition alignment. See the unRAID 6.9.0 release notes for more information.

Most people do not have a parity drive implemented in this stage when they first set up the array which means data transfer can happen at the full speed of the individual disks. Parity is "turned on" after the initial data dump. Calculating parity in real-time has a cost. The volume added on a daily basis after the initial data transfer will determine if you are OK with real-time parity updates or if you prefer to use the cache disk method or enable Turbo Write.

When I has this issue over a year ago, the guidance was to delete the entire codecs folder. That forces Plex to download again any needed codecs as they are needed. The EAC3 codecs seem particularly prone to getting messed up. This completely resolved my Plex audio issues and I have had none since. YMMV.

You have the media share set to cache:prefer. This tells unRAID to write new files to this share on the cache drive if it exists and has space (prefer the cache drive as the share storage location). If it has no space, it will write files to the array. Not only are all new files for the Media share currently going to cache but they are never moved to the array by the Mover because of the prefer setting. In fact, running Mover will result in your cache drive filling up again as it will move files from the Media share off the array and to the cache drive as long as there is free space. Even if you manually free up space on the cache drive, as soon as you write anything to the Media share or run the Mover, it is going straight to cache and staying there. You should set the share to cache:yes if you want files written there temporarily and moved to the array (disks 1-5) by the Mover. # Generated settings: shareComment="" shareInclude="disk1,disk2,disk3,disk4,disk5" shareExclude="" shareUseCache="prefer" shareCachePool="cache" shareCOW="auto" # Share exists on cache,disk1,disk2,disk3,disk4

You probably need to clear the Windows credentials associated with your unRAID server in the Windows Credential Manager. Windows only allows one user access to folders via SMB and it is probably still storing your old Guest/blank credentials for non-secure access. Until you clear those from the Credential Manager, even if you enter a new secure user and password, it will ignore them and continue to use the stored credentials. I don't know if MacOS has something similar.

Not necessarily. There are still many good uses for unassigned devices: Plug in an external USB drive and backup share data to it automatically via a UD script Use a USB device as a location for the syslog A UD for VMs is still preferred by some A UD as a download, personal cloud data, transcode or media conversion location may still be preferable in some cases over a cache pool Unassigned Devices supports formats such as NTFS which allow these devices to read in Windows outside the array.

You have a ton of call traces in your syslog. I don't think I have ever seen so many. Call traces are almost always related to hardware issues as yours seem to be. This is just some of them and they seem to be related to CPU processes. Unfortunately, I can't tell you what they mean but a bunch of call traces will definitely result in an eventual server lockup. Hopefully, someone will have more insights. Mar 30 02:54:36 WadeWilson kernel: Call Trace: Mar 30 02:54:36 WadeWilson kernel: <IRQ> Mar 30 02:54:36 WadeWilson kernel: dump_stack+0x6b/0x83 Mar 30 02:54:36 WadeWilson kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Mar 30 02:54:36 WadeWilson kernel: nmi_cpu_backtrace+0x7d/0x8f Mar 30 02:54:36 WadeWilson kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Mar 30 02:54:36 WadeWilson kernel: rcu_dump_cpu_stacks+0x9f/0xc6 Mar 30 02:54:36 WadeWilson kernel: rcu_sched_clock_irq+0x1ec/0x543 Mar 30 02:54:36 WadeWilson kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Mar 30 02:54:36 WadeWilson kernel: update_process_times+0x50/0x6e Mar 30 02:54:36 WadeWilson kernel: tick_sched_timer+0x36/0x64 Mar 30 02:54:36 WadeWilson kernel: __hrtimer_run_queues+0xb7/0x10b Mar 30 02:54:36 WadeWilson kernel: ? tick_sched_do_timer+0x39/0x39 Mar 30 02:54:36 WadeWilson kernel: hrtimer_interrupt+0x8d/0x160 Mar 30 02:54:36 WadeWilson kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Mar 30 02:54:36 WadeWilson kernel: asm_call_irq_on_stack+0x12/0x20 Mar 30 02:54:36 WadeWilson kernel: </IRQ> Mar 30 02:54:36 WadeWilson kernel: sysvec_apic_timer_interrupt+0x71/0x95 Mar 30 02:54:36 WadeWilson kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Mar 30 02:54:36 WadeWilson kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x79/0x18a Mar 30 02:54:36 WadeWilson 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 80 2f 02 00 65 48 03 05 90 92 f8 Mar 30 02:54:36 WadeWilson kernel: RSP: 0018:ffffc90000e9fb70 EFLAGS: 00000202 Mar 30 02:54:36 WadeWilson kernel: RAX: 0000000000000101 RBX: ffffc90000e9fbb8 RCX: 000ffffffffff000 Mar 30 02:54:36 WadeWilson kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea000403b6e8 Mar 30 02:54:36 WadeWilson kernel: RBP: ffffea0015370e00 R08: ffff888000000000 R09: 0000000000000000 Mar 30 02:54:36 WadeWilson kernel: R10: 0000000000000001 R11: 000000000000000c R12: ffffea00040945c0 Mar 30 02:54:36 WadeWilson kernel: R13: ffff88810133b300 R14: 0000160000000000 R15: ffff888133da1140 Mar 30 02:54:36 WadeWilson kernel: queued_spin_lock_slowpath+0x7/0xa Mar 30 02:54:36 WadeWilson kernel: page_vma_mapped_walk+0x4a4/0x4f8 Mar 30 02:54:36 WadeWilson kernel: remove_migration_pte+0x59/0x214 Mar 30 02:54:36 WadeWilson kernel: rmap_walk_anon+0xe7/0x156 Mar 30 02:54:36 WadeWilson kernel: remove_migration_ptes+0x49/0x63 Mar 30 02:54:36 WadeWilson kernel: ? pmd_pfn+0x3a/0x3a Mar 30 02:54:36 WadeWilson kernel: migrate_pages+0x4e0/0x7c1 Mar 30 02:54:36 WadeWilson kernel: ? move_freelist_tail+0xba/0xba Mar 30 02:54:36 WadeWilson kernel: ? isolate_freepages_block+0x26b/0x26b Mar 30 02:54:36 WadeWilson kernel: compact_zone+0x6b2/0x905 Mar 30 02:54:36 WadeWilson kernel: ? set_next_entity+0x47/0x6c Mar 30 02:54:36 WadeWilson kernel: proactive_compact_node+0x75/0xa2 Mar 30 02:54:36 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 02:54:36 WadeWilson kernel: kcompactd+0x1ee/0x22c Mar 30 02:54:36 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 02:54:36 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 02:54:36 WadeWilson kernel: kthread+0xe5/0xea Mar 30 02:54:36 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 02:54:36 WadeWilson kernel: ret_from_fork+0x22/0x30 Mar 30 02:54:55 WadeWilson kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 7-... } 60222 jiffies s: 3377 root: 0x1/. Mar 30 02:54:55 WadeWilson kernel: rcu: blocking rcu_node structures: l=1:0-15:0x80/. Mar 30 02:54:55 WadeWilson kernel: Task dump for CPU 7: Mar 30 02:54:55 WadeWilson kernel: task:kcompactd0 state:R running task stack: 0 pid: 425 ppid: 2 flags:0x00004008 Mar 30 02:54:55 WadeWilson kernel: Call Trace: Mar 30 02:54:55 WadeWilson kernel: ? proactive_compact_node+0x75/0xa2 Mar 30 02:54:55 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 02:54:55 WadeWilson kernel: ? kcompactd+0x1ee/0x22c Mar 30 02:54:55 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 02:54:55 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 02:54:55 WadeWilson kernel: ? kthread+0xe5/0xea Mar 30 02:54:55 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 02:54:55 WadeWilson kernel: ? ret_from_fork+0x22/0x30 Mar 30 02:56:16 WadeWilson crond[2053]: exit status 255 from user root /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null Mar 30 02:57:36 WadeWilson kernel: rcu: INFO: rcu_sched self-detected stall on CPU Mar 30 02:57:36 WadeWilson kernel: rcu: #0117-....: (240002 ticks this GP) idle=03e/1/0x4000000000000000 softirq=389008/389008 fqs=59351 Mar 30 02:57:36 WadeWilson kernel: #011(t=240003 jiffies g=1768205 q=103075) Mar 30 02:57:36 WadeWilson kernel: NMI backtrace for cpu 7 Mar 30 02:57:36 WadeWilson kernel: CPU: 7 PID: 425 Comm: kcompactd0 Tainted: G D 5.10.1-Unraid #1 Mar 30 02:57:36 WadeWilson kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS (MS-7B79), BIOS A.K1 12/22/2020 Mar 30 02:57:36 WadeWilson kernel: Call Trace: Mar 30 02:57:36 WadeWilson kernel: <IRQ> Mar 30 02:57:36 WadeWilson kernel: dump_stack+0x6b/0x83 Mar 30 02:57:36 WadeWilson kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Mar 30 02:57:36 WadeWilson kernel: nmi_cpu_backtrace+0x7d/0x8f Mar 30 02:57:36 WadeWilson kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Mar 30 02:57:36 WadeWilson kernel: rcu_dump_cpu_stacks+0x9f/0xc6 Mar 30 02:57:36 WadeWilson kernel: rcu_sched_clock_irq+0x1ec/0x543 Mar 30 02:57:36 WadeWilson kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Mar 30 02:57:36 WadeWilson kernel: update_process_times+0x50/0x6e Mar 30 02:57:36 WadeWilson kernel: tick_sched_timer+0x36/0x64 Mar 30 02:57:36 WadeWilson kernel: __hrtimer_run_queues+0xb7/0x10b Mar 30 02:57:36 WadeWilson kernel: ? tick_sched_do_timer+0x39/0x39 Mar 30 02:57:36 WadeWilson kernel: hrtimer_interrupt+0x8d/0x160 Mar 30 02:57:36 WadeWilson kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Mar 30 02:57:36 WadeWilson kernel: asm_call_irq_on_stack+0x12/0x20 Mar 30 02:57:36 WadeWilson kernel: </IRQ> Mar 30 02:57:36 WadeWilson kernel: sysvec_apic_timer_interrupt+0x71/0x95 Mar 30 02:57:36 WadeWilson kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Mar 30 02:57:36 WadeWilson kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x79/0x18a Mar 30 02:57:36 WadeWilson 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 80 2f 02 00 65 48 03 05 90 92 f8 Mar 30 02:57:36 WadeWilson kernel: RSP: 0018:ffffc90000e9fb70 EFLAGS: 00000202 Mar 30 02:57:36 WadeWilson kernel: RAX: 0000000000000101 RBX: ffffc90000e9fbb8 RCX: 000ffffffffff000 Mar 30 02:57:36 WadeWilson kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea000403b6e8 Mar 30 02:57:36 WadeWilson kernel: RBP: ffffea0015370e00 R08: ffff888000000000 R09: 0000000000000000 Mar 30 02:57:36 WadeWilson kernel: R10: 0000000000000001 R11: 000000000000000c R12: ffffea00040945c0 Mar 30 02:57:36 WadeWilson kernel: R13: ffff88810133b300 R14: 0000160000000000 R15: ffff888133da1140 Mar 30 02:57:36 WadeWilson kernel: queued_spin_lock_slowpath+0x7/0xa Mar 30 02:57:36 WadeWilson kernel: page_vma_mapped_walk+0x4a4/0x4f8 Mar 30 02:57:36 WadeWilson kernel: remove_migration_pte+0x59/0x214 Mar 30 02:57:36 WadeWilson kernel: rmap_walk_anon+0xe7/0x156 Mar 30 02:57:36 WadeWilson kernel: remove_migration_ptes+0x49/0x63 Mar 30 02:57:36 WadeWilson kernel: ? pmd_pfn+0x3a/0x3a Mar 30 02:57:36 WadeWilson kernel: migrate_pages+0x4e0/0x7c1 Mar 30 02:57:36 WadeWilson kernel: ? move_freelist_tail+0xba/0xba Mar 30 02:57:36 WadeWilson kernel: ? isolate_freepages_block+0x26b/0x26b Mar 30 02:57:36 WadeWilson kernel: compact_zone+0x6b2/0x905 Mar 30 02:57:36 WadeWilson kernel: ? set_next_entity+0x47/0x6c Mar 30 02:57:36 WadeWilson kernel: proactive_compact_node+0x75/0xa2 Mar 30 02:57:36 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 02:57:36 WadeWilson kernel: kcompactd+0x1ee/0x22c Mar 30 02:57:36 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 02:57:36 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 02:57:36 WadeWilson kernel: kthread+0xe5/0xea Mar 30 02:57:36 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 02:57:36 WadeWilson kernel: ret_from_fork+0x22/0x30 Mar 30 02:57:56 WadeWilson kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 7-... } 240446 jiffies s: 3377 root: 0x1/. Mar 30 02:57:56 WadeWilson kernel: rcu: blocking rcu_node structures: l=1:0-15:0x80/. Mar 30 02:57:56 WadeWilson kernel: Task dump for CPU 7: Mar 30 02:57:56 WadeWilson kernel: task:kcompactd0 state:R running task stack: 0 pid: 425 ppid: 2 flags:0x00004008 Mar 30 02:57:56 WadeWilson kernel: Call Trace: Mar 30 02:57:56 WadeWilson kernel: ? proactive_compact_node+0x75/0xa2 Mar 30 02:57:56 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 02:57:56 WadeWilson kernel: ? kcompactd+0x1ee/0x22c Mar 30 02:57:56 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 02:57:56 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 02:57:56 WadeWilson kernel: ? kthread+0xe5/0xea Mar 30 02:57:56 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 02:57:56 WadeWilson kernel: ? ret_from_fork+0x22/0x30 Mar 30 03:00:16 WadeWilson crond[2053]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Mar 30 03:00:16 WadeWilson crond[2053]: exit status 255 from user root /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null Mar 30 03:00:36 WadeWilson kernel: rcu: INFO: rcu_sched self-detected stall on CPU Mar 30 03:00:36 WadeWilson kernel: rcu: #0117-....: (420005 ticks this GP) idle=03e/1/0x4000000000000000 softirq=389008/389008 fqs=104001 Mar 30 03:00:36 WadeWilson kernel: #011(t=420006 jiffies g=1768205 q=206469) Mar 30 03:00:36 WadeWilson kernel: NMI backtrace for cpu 7 Mar 30 03:00:36 WadeWilson kernel: CPU: 7 PID: 425 Comm: kcompactd0 Tainted: G D 5.10.1-Unraid #1 Mar 30 03:00:36 WadeWilson kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS (MS-7B79), BIOS A.K1 12/22/2020 Mar 30 03:00:36 WadeWilson kernel: Call Trace: Mar 30 03:00:36 WadeWilson kernel: <IRQ> Mar 30 03:00:36 WadeWilson kernel: dump_stack+0x6b/0x83 Mar 30 03:00:36 WadeWilson kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Mar 30 03:00:36 WadeWilson kernel: nmi_cpu_backtrace+0x7d/0x8f Mar 30 03:00:36 WadeWilson kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Mar 30 03:00:36 WadeWilson kernel: rcu_dump_cpu_stacks+0x9f/0xc6 Mar 30 03:00:36 WadeWilson kernel: rcu_sched_clock_irq+0x1ec/0x543 Mar 30 03:00:36 WadeWilson kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Mar 30 03:00:36 WadeWilson kernel: update_process_times+0x50/0x6e Mar 30 03:00:36 WadeWilson kernel: tick_sched_timer+0x36/0x64 Mar 30 03:00:36 WadeWilson kernel: __hrtimer_run_queues+0xb7/0x10b Mar 30 03:00:36 WadeWilson kernel: ? tick_sched_do_timer+0x39/0x39 Mar 30 03:00:36 WadeWilson kernel: hrtimer_interrupt+0x8d/0x160 Mar 30 03:00:36 WadeWilson kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Mar 30 03:00:36 WadeWilson kernel: asm_call_irq_on_stack+0x12/0x20 Mar 30 03:00:36 WadeWilson kernel: </IRQ> Mar 30 03:00:36 WadeWilson kernel: sysvec_apic_timer_interrupt+0x71/0x95 Mar 30 03:00:36 WadeWilson kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Mar 30 03:00:36 WadeWilson kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x79/0x18a Mar 30 03:00:36 WadeWilson 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 80 2f 02 00 65 48 03 05 90 92 f8 Mar 30 03:00:36 WadeWilson kernel: RSP: 0018:ffffc90000e9fb70 EFLAGS: 00000202 Mar 30 03:00:36 WadeWilson kernel: RAX: 0000000000000101 RBX: ffffc90000e9fbb8 RCX: 000ffffffffff000 Mar 30 03:00:36 WadeWilson kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea000403b6e8 Mar 30 03:00:36 WadeWilson kernel: RBP: ffffea0015370e00 R08: ffff888000000000 R09: 0000000000000000 Mar 30 03:00:36 WadeWilson kernel: R10: 0000000000000001 R11: 000000000000000c R12: ffffea00040945c0 Mar 30 03:00:36 WadeWilson kernel: R13: ffff88810133b300 R14: 0000160000000000 R15: ffff888133da1140 Mar 30 03:00:36 WadeWilson kernel: queued_spin_lock_slowpath+0x7/0xa Mar 30 03:00:36 WadeWilson kernel: page_vma_mapped_walk+0x4a4/0x4f8 Mar 30 03:00:36 WadeWilson kernel: remove_migration_pte+0x59/0x214 Mar 30 03:00:36 WadeWilson kernel: rmap_walk_anon+0xe7/0x156 Mar 30 03:00:36 WadeWilson kernel: remove_migration_ptes+0x49/0x63 Mar 30 03:00:36 WadeWilson kernel: ? pmd_pfn+0x3a/0x3a Mar 30 03:00:36 WadeWilson kernel: migrate_pages+0x4e0/0x7c1 Mar 30 03:00:36 WadeWilson kernel: ? move_freelist_tail+0xba/0xba Mar 30 03:00:36 WadeWilson kernel: ? isolate_freepages_block+0x26b/0x26b Mar 30 03:00:36 WadeWilson kernel: compact_zone+0x6b2/0x905 Mar 30 03:00:36 WadeWilson kernel: ? set_next_entity+0x47/0x6c Mar 30 03:00:36 WadeWilson kernel: proactive_compact_node+0x75/0xa2 Mar 30 03:00:36 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 03:00:36 WadeWilson kernel: kcompactd+0x1ee/0x22c Mar 30 03:00:36 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 03:00:36 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 03:00:36 WadeWilson kernel: kthread+0xe5/0xea Mar 30 03:00:36 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 03:00:36 WadeWilson kernel: ret_from_fork+0x22/0x30 Mar 30 03:00:56 WadeWilson kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 7-... } 420670 jiffies s: 3377 root: 0x1/. Mar 30 03:00:56 WadeWilson kernel: rcu: blocking rcu_node structures: l=1:0-15:0x80/. Mar 30 03:00:56 WadeWilson kernel: Task dump for CPU 7: Mar 30 03:00:56 WadeWilson kernel: task:kcompactd0 state:R running task stack: 0 pid: 425 ppid: 2 flags:0x00004008 Mar 30 03:00:56 WadeWilson kernel: Call Trace: Mar 30 03:00:56 WadeWilson kernel: ? proactive_compact_node+0x75/0xa2 Mar 30 03:00:56 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 03:00:56 WadeWilson kernel: ? kcompactd+0x1ee/0x22c Mar 30 03:00:56 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 03:00:56 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 03:00:56 WadeWilson kernel: ? kthread+0xe5/0xea Mar 30 03:00:56 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 03:00:56 WadeWilson kernel: ? ret_from_fork+0x22/0x30 Mar 30 03:03:36 WadeWilson kernel: rcu: INFO: rcu_sched self-detected stall on CPU Mar 30 03:03:36 WadeWilson kernel: rcu: #0117-....: (600008 ticks this GP) idle=03e/1/0x4000000000000000 softirq=389008/389008 fqs=148640 Mar 30 03:03:36 WadeWilson kernel: #011(t=600009 jiffies g=1768205 q=291987) Mar 30 03:03:36 WadeWilson kernel: NMI backtrace for cpu 7 Mar 30 03:03:36 WadeWilson kernel: CPU: 7 PID: 425 Comm: kcompactd0 Tainted: G D 5.10.1-Unraid #1 Mar 30 03:03:36 WadeWilson kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS (MS-7B79), BIOS A.K1 12/22/2020 Mar 30 03:03:36 WadeWilson kernel: Call Trace: Mar 30 03:03:36 WadeWilson kernel: <IRQ> Mar 30 03:03:36 WadeWilson kernel: dump_stack+0x6b/0x83 Mar 30 03:03:36 WadeWilson kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Mar 30 03:03:36 WadeWilson kernel: nmi_cpu_backtrace+0x7d/0x8f Mar 30 03:03:36 WadeWilson kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Mar 30 03:03:36 WadeWilson kernel: rcu_dump_cpu_stacks+0x9f/0xc6 Mar 30 03:03:36 WadeWilson kernel: rcu_sched_clock_irq+0x1ec/0x543 Mar 30 03:03:36 WadeWilson kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Mar 30 03:03:36 WadeWilson kernel: update_process_times+0x50/0x6e Mar 30 03:03:36 WadeWilson kernel: tick_sched_timer+0x36/0x64 Mar 30 03:03:36 WadeWilson kernel: __hrtimer_run_queues+0xb7/0x10b Mar 30 03:03:36 WadeWilson kernel: ? tick_sched_do_timer+0x39/0x39 Mar 30 03:03:36 WadeWilson kernel: hrtimer_interrupt+0x8d/0x160 Mar 30 03:03:36 WadeWilson kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Mar 30 03:03:36 WadeWilson kernel: asm_call_irq_on_stack+0x12/0x20 Mar 30 03:03:36 WadeWilson kernel: </IRQ> Mar 30 03:03:36 WadeWilson kernel: sysvec_apic_timer_interrupt+0x71/0x95 Mar 30 03:03:36 WadeWilson kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Mar 30 03:03:36 WadeWilson kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x79/0x18a Mar 30 03:03:36 WadeWilson 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 80 2f 02 00 65 48 03 05 90 92 f8 Mar 30 03:03:36 WadeWilson kernel: RSP: 0018:ffffc90000e9fb70 EFLAGS: 00000202 Mar 30 03:03:36 WadeWilson kernel: RAX: 0000000000000101 RBX: ffffc90000e9fbb8 RCX: 000ffffffffff000 Mar 30 03:03:36 WadeWilson kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea000403b6e8 Mar 30 03:03:36 WadeWilson kernel: RBP: ffffea0015370e00 R08: ffff888000000000 R09: 0000000000000000 Mar 30 03:03:36 WadeWilson kernel: R10: 0000000000000001 R11: 000000000000000c R12: ffffea00040945c0 Mar 30 03:03:36 WadeWilson kernel: R13: ffff88810133b300 R14: 0000160000000000 R15: ffff888133da1140 Mar 30 03:03:36 WadeWilson kernel: queued_spin_lock_slowpath+0x7/0xa Mar 30 03:03:36 WadeWilson kernel: page_vma_mapped_walk+0x4a4/0x4f8 Mar 30 03:03:36 WadeWilson kernel: remove_migration_pte+0x59/0x214 Mar 30 03:03:36 WadeWilson kernel: rmap_walk_anon+0xe7/0x156 Mar 30 03:03:36 WadeWilson kernel: remove_migration_ptes+0x49/0x63 Mar 30 03:03:36 WadeWilson kernel: ? pmd_pfn+0x3a/0x3a Mar 30 03:03:36 WadeWilson kernel: migrate_pages+0x4e0/0x7c1 Mar 30 03:03:36 WadeWilson kernel: ? move_freelist_tail+0xba/0xba Mar 30 03:03:36 WadeWilson kernel: ? isolate_freepages_block+0x26b/0x26b Mar 30 03:03:36 WadeWilson kernel: compact_zone+0x6b2/0x905 Mar 30 03:03:36 WadeWilson kernel: ? set_next_entity+0x47/0x6c Mar 30 03:03:36 WadeWilson kernel: proactive_compact_node+0x75/0xa2 Mar 30 03:03:36 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 03:03:36 WadeWilson kernel: kcompactd+0x1ee/0x22c Mar 30 03:03:36 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 03:03:36 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 03:03:36 WadeWilson kernel: kthread+0xe5/0xea Mar 30 03:03:36 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 03:03:36 WadeWilson kernel: ret_from_fork+0x22/0x30 Mar 30 03:03:56 WadeWilson kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 7-... } 600894 jiffies s: 3377 root: 0x1/. Mar 30 03:03:56 WadeWilson kernel: rcu: blocking rcu_node structures: l=1:0-15:0x80/. Mar 30 03:03:56 WadeWilson kernel: Task dump for CPU 7: Mar 30 03:03:56 WadeWilson kernel: task:kcompactd0 state:R running task stack: 0 pid: 425 ppid: 2 flags:0x00004008 Mar 30 03:03:56 WadeWilson kernel: Call Trace: Mar 30 03:03:56 WadeWilson kernel: ? proactive_compact_node+0x75/0xa2 Mar 30 03:03:56 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 03:03:56 WadeWilson kernel: ? kcompactd+0x1ee/0x22c Mar 30 03:03:56 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 03:03:56 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 03:03:56 WadeWilson kernel: ? kthread+0xe5/0xea Mar 30 03:03:56 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 03:03:56 WadeWilson kernel: ? ret_from_fork+0x22/0x30 Mar 30 03:06:36 WadeWilson kernel: rcu: INFO: rcu_sched self-detected stall on CPU Mar 30 03:06:36 WadeWilson kernel: rcu: #0117-....: (780011 ticks this GP) idle=03e/1/0x4000000000000000 softirq=389008/389008 fqs=193359 Mar 30 03:06:36 WadeWilson kernel: #011(t=780012 jiffies g=1768205 q=388324) Mar 30 03:06:36 WadeWilson kernel: NMI backtrace for cpu 7 Mar 30 03:06:36 WadeWilson kernel: CPU: 7 PID: 425 Comm: kcompactd0 Tainted: G D 5.10.1-Unraid #1 Mar 30 03:06:36 WadeWilson kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS (MS-7B79), BIOS A.K1 12/22/2020 Mar 30 03:06:36 WadeWilson kernel: Call Trace: Mar 30 03:06:36 WadeWilson kernel: <IRQ> Mar 30 03:06:36 WadeWilson kernel: dump_stack+0x6b/0x83 Mar 30 03:06:36 WadeWilson kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Mar 30 03:06:36 WadeWilson kernel: nmi_cpu_backtrace+0x7d/0x8f Mar 30 03:06:36 WadeWilson kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Mar 30 03:06:36 WadeWilson kernel: rcu_dump_cpu_stacks+0x9f/0xc6 Mar 30 03:06:36 WadeWilson kernel: rcu_sched_clock_irq+0x1ec/0x543 Mar 30 03:06:36 WadeWilson kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Mar 30 03:06:36 WadeWilson kernel: update_process_times+0x50/0x6e Mar 30 03:06:36 WadeWilson kernel: tick_sched_timer+0x36/0x64 Mar 30 03:06:36 WadeWilson kernel: __hrtimer_run_queues+0xb7/0x10b Mar 30 03:06:36 WadeWilson kernel: ? tick_sched_do_timer+0x39/0x39 Mar 30 03:06:36 WadeWilson kernel: hrtimer_interrupt+0x8d/0x160 Mar 30 03:06:36 WadeWilson kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Mar 30 03:06:36 WadeWilson kernel: asm_call_irq_on_stack+0x12/0x20 Mar 30 03:06:36 WadeWilson kernel: </IRQ> Mar 30 03:06:36 WadeWilson kernel: sysvec_apic_timer_interrupt+0x71/0x95 Mar 30 03:06:36 WadeWilson kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Mar 30 03:06:36 WadeWilson kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x79/0x18a Mar 30 03:06:36 WadeWilson 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 80 2f 02 00 65 48 03 05 90 92 f8 Mar 30 03:06:36 WadeWilson kernel: RSP: 0018:ffffc90000e9fb70 EFLAGS: 00000202 Mar 30 03:06:36 WadeWilson kernel: RAX: 0000000000000101 RBX: ffffc90000e9fbb8 RCX: 000ffffffffff000 Mar 30 03:06:36 WadeWilson kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea000403b6e8 Mar 30 03:06:36 WadeWilson kernel: RBP: ffffea0015370e00 R08: ffff888000000000 R09: 0000000000000000 Mar 30 03:06:36 WadeWilson kernel: R10: 0000000000000001 R11: 000000000000000c R12: ffffea00040945c0 Mar 30 03:06:36 WadeWilson kernel: R13: ffff88810133b300 R14: 0000160000000000 R15: ffff888133da1140 Mar 30 03:06:36 WadeWilson kernel: queued_spin_lock_slowpath+0x7/0xa Mar 30 03:06:36 WadeWilson kernel: page_vma_mapped_walk+0x4a4/0x4f8 Mar 30 03:06:36 WadeWilson kernel: remove_migration_pte+0x59/0x214 Mar 30 03:06:36 WadeWilson kernel: rmap_walk_anon+0xe7/0x156 Mar 30 03:06:36 WadeWilson kernel: remove_migration_ptes+0x49/0x63 Mar 30 03:06:36 WadeWilson kernel: ? pmd_pfn+0x3a/0x3a Mar 30 03:06:36 WadeWilson kernel: migrate_pages+0x4e0/0x7c1 Mar 30 03:06:36 WadeWilson kernel: ? move_freelist_tail+0xba/0xba Mar 30 03:06:36 WadeWilson kernel: ? isolate_freepages_block+0x26b/0x26b Mar 30 03:06:36 WadeWilson kernel: compact_zone+0x6b2/0x905 Mar 30 03:06:36 WadeWilson kernel: ? set_next_entity+0x47/0x6c Mar 30 03:06:36 WadeWilson kernel: proactive_compact_node+0x75/0xa2 Mar 30 03:06:36 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 03:06:36 WadeWilson kernel: kcompactd+0x1ee/0x22c Mar 30 03:06:36 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 03:06:36 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 03:06:36 WadeWilson kernel: kthread+0xe5/0xea Mar 30 03:06:36 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 03:06:36 WadeWilson kernel: ret_from_fork+0x22/0x30 Mar 30 03:06:56 WadeWilson kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 7-... } 781118 jiffies s: 3377 root: 0x1/. Mar 30 03:06:56 WadeWilson kernel: rcu: blocking rcu_node structures: l=1:0-15:0x80/. Mar 30 03:06:56 WadeWilson kernel: Task dump for CPU 7: Mar 30 03:06:56 WadeWilson kernel: task:kcompactd0 state:R running task stack: 0 pid: 425 ppid: 2 flags:0x00004008 Mar 30 03:06:56 WadeWilson kernel: Call Trace: Mar 30 03:06:56 WadeWilson kernel: ? proactive_compact_node+0x75/0xa2 Mar 30 03:06:56 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 03:06:56 WadeWilson kernel: ? kcompactd+0x1ee/0x22c Mar 30 03:06:56 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 03:06:56 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 03:06:56 WadeWilson kernel: ? kthread+0xe5/0xea Mar 30 03:06:56 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 03:06:56 WadeWilson kernel: ? ret_from_fork+0x22/0x30 Mar 30 03:07:16 WadeWilson crond[2053]: exit status 255 from user root /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null Mar 30 03:09:36 WadeWilson kernel: rcu: INFO: rcu_sched self-detected stall on CPU Mar 30 03:09:36 WadeWilson kernel: rcu: #0117-....: (960014 ticks this GP) idle=03e/1/0x4000000000000000 softirq=389008/389008 fqs=238149 Mar 30 03:09:36 WadeWilson kernel: #011(t=960015 jiffies g=1768205 q=548943) Mar 30 03:09:36 WadeWilson kernel: NMI backtrace for cpu 7 Mar 30 03:09:36 WadeWilson kernel: CPU: 7 PID: 425 Comm: kcompactd0 Tainted: G D 5.10.1-Unraid #1 Mar 30 03:09:36 WadeWilson kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS (MS-7B79), BIOS A.K1 12/22/2020 Mar 30 03:09:36 WadeWilson kernel: Call Trace: Mar 30 03:09:36 WadeWilson kernel: <IRQ> Mar 30 03:09:36 WadeWilson kernel: dump_stack+0x6b/0x83 Mar 30 03:09:36 WadeWilson kernel: ? lapic_can_unplug_cpu+0x8e/0x8e Mar 30 03:09:36 WadeWilson kernel: nmi_cpu_backtrace+0x7d/0x8f Mar 30 03:09:36 WadeWilson kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Mar 30 03:09:36 WadeWilson kernel: rcu_dump_cpu_stacks+0x9f/0xc6 Mar 30 03:09:36 WadeWilson kernel: rcu_sched_clock_irq+0x1ec/0x543 Mar 30 03:09:36 WadeWilson kernel: ? _raw_spin_unlock_irqrestore+0xd/0xe Mar 30 03:09:36 WadeWilson kernel: update_process_times+0x50/0x6e Mar 30 03:09:36 WadeWilson kernel: tick_sched_timer+0x36/0x64 Mar 30 03:09:36 WadeWilson kernel: __hrtimer_run_queues+0xb7/0x10b Mar 30 03:09:36 WadeWilson kernel: ? tick_sched_do_timer+0x39/0x39 Mar 30 03:09:36 WadeWilson kernel: hrtimer_interrupt+0x8d/0x160 Mar 30 03:09:36 WadeWilson kernel: __sysvec_apic_timer_interrupt+0x5d/0x68 Mar 30 03:09:36 WadeWilson kernel: asm_call_irq_on_stack+0x12/0x20 Mar 30 03:09:36 WadeWilson kernel: </IRQ> Mar 30 03:09:36 WadeWilson kernel: sysvec_apic_timer_interrupt+0x71/0x95 Mar 30 03:09:36 WadeWilson kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Mar 30 03:09:36 WadeWilson kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x79/0x18a Mar 30 03:09:36 WadeWilson 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 80 2f 02 00 65 48 03 05 90 92 f8 Mar 30 03:09:36 WadeWilson kernel: RSP: 0018:ffffc90000e9fb70 EFLAGS: 00000202 Mar 30 03:09:36 WadeWilson kernel: RAX: 0000000000000101 RBX: ffffc90000e9fbb8 RCX: 000ffffffffff000 Mar 30 03:09:36 WadeWilson kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea000403b6e8 Mar 30 03:09:36 WadeWilson kernel: RBP: ffffea0015370e00 R08: ffff888000000000 R09: 0000000000000000 Mar 30 03:09:36 WadeWilson kernel: R10: 0000000000000001 R11: 000000000000000c R12: ffffea00040945c0 Mar 30 03:09:36 WadeWilson kernel: R13: ffff88810133b300 R14: 0000160000000000 R15: ffff888133da1140 Mar 30 03:09:36 WadeWilson kernel: queued_spin_lock_slowpath+0x7/0xa Mar 30 03:09:36 WadeWilson kernel: page_vma_mapped_walk+0x4a4/0x4f8 Mar 30 03:09:36 WadeWilson kernel: remove_migration_pte+0x59/0x214 Mar 30 03:09:36 WadeWilson kernel: rmap_walk_anon+0xe7/0x156 Mar 30 03:09:36 WadeWilson kernel: remove_migration_ptes+0x49/0x63 Mar 30 03:09:36 WadeWilson kernel: ? pmd_pfn+0x3a/0x3a Mar 30 03:09:36 WadeWilson kernel: migrate_pages+0x4e0/0x7c1 Mar 30 03:09:36 WadeWilson kernel: ? move_freelist_tail+0xba/0xba Mar 30 03:09:36 WadeWilson kernel: ? isolate_freepages_block+0x26b/0x26b Mar 30 03:09:36 WadeWilson kernel: compact_zone+0x6b2/0x905 Mar 30 03:09:36 WadeWilson kernel: ? set_next_entity+0x47/0x6c Mar 30 03:09:36 WadeWilson kernel: proactive_compact_node+0x75/0xa2 Mar 30 03:09:36 WadeWilson kernel: ? fragmentation_score_node+0x2b/0x59 Mar 30 03:09:36 WadeWilson kernel: kcompactd+0x1ee/0x22c Mar 30 03:09:36 WadeWilson kernel: ? init_wait_entry+0x24/0x24 Mar 30 03:09:36 WadeWilson kernel: ? kcompactd_do_work+0x16f/0x16f Mar 30 03:09:36 WadeWilson kernel: kthread+0xe5/0xea Mar 30 03:09:36 WadeWilson kernel: ? kthread_unpark+0x52/0x52 Mar 30 03:09:36 WadeWilson kernel: ret_from_fork+0x22/0x30 Mar 30 03:09:57 WadeWilson kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 7-... } 961342 jiffies s: 3377 root: 0x1/. Mar 30 03:09:57 WadeWilson kernel: rcu: blocking rcu_node structures: l=1:0-15:0x80/. Mar 30 03:09:57 WadeWilson kernel: Task dump for CPU 7:

I have a special use case which may apply to few unRAID users, but I will document it here in case it is useful to others. I want to write my syslog to a location other than those officially supported by the syslog server. Although I am using a card reader, this should work with any Unassigned Devices location. Caveat: Officially, unRAID does not support card readers as boot flash devices. Don't tell Limetech, but I and others have been doing this for years 😁. In fact, here is a forum discussion of card readers that have unique GUIDs and work with unRAID. This solution involves using an available card slot in the card reader and a flash card as an unassigned device. Theoretically, this will work with any card reader with an empty slot and not just the particular Kingston card reader I am using. By default, the Syslog must be written to an existing share on unRAID with the option to mirror it to the boot flash drive if you need to do some troubleshooting. Alternatively, you can write it to a remote syslog server. It is not recommended to have the syslog mirrored to the boot flash drive constantly as that could result in a lot of writes to the flash drive and you don't want unnecessary wear and tear on your boot flash. If your server will not boot, writing to a share won't do you much good as you will not be able to access the syslog. With some tweaking of the config files, you can get the syslog mirrored to an unassigned device. This has already been documented. What I want to accomplish: Use the unused Micro SD card slot in my Kingston MobileLite G2 card reader as a location to which to write the syslog. The SD card slot is currently used as the flash drive from which unRAID boots. If I can do this, I never need to mirror the syslog to the boot flash drive. NOTE: this card reader is no longer available (perhaps on eBay) but it has a unique GUID and is USB 2.0 which is preferred for unRAID. I also have the MobileLite G3 USB 3.0 version in another server and it works great. Other versions of this card reader do not have a unique GUID. Keep in mind, this flash drive will count against the drive total in your unRAID license as it will be an Unassigned Device that is attached at the time the array starts. It counts even if the Micro SD slot is empty! Might as well use it for something. I have been using the Kingston reader as my boot flash drive for 10 years. It's great as the GUID is associated with the reader, and I can swap flash cards to my heart's content to test different unRAID configurations and troubleshoot. If the flash card fails, I just copy a backup onto a new flash card with no need to license a new flash drive. The Micro SD slot has always been unused and has showed up as an unassigned device. Steps to make this work: Format a Micro SD card as an NTFS partition (I gave the card the label "SYSLOG"). You could do FAT32 like with the boot drive as well. I had a spare 32GB Micro SD card and I chose to format it as NTFS as this is supported by Unassigned devices and makes it directly readable in Windows as is FAT32. If the server won't boot, I can just remove the card from the reader and view the syslog in Windows or post it to the forums for help. Of course, you could also do this with the boot flash drive if you mirrored the syslog there, but I want to avoid that. Put the card in the reader and mount it as an Unassigned Device in unRAID. As seen below, the boot flash is in the SD slot and I now have the SYSLOG card in the Micro SD slot. Yes, the flash drive is public (not recommended) while I did this. Edit the Unassigned Device (UD) settings to enable automount and sharing: Modify the syslog config files on the boot flash drive to point to the UD location: Change the server_folder line in /boot/config/rsyslog.cfg to point to the UD location: server_folder="/mnt/disks/SYSLOG/" In rsyslog.conf, change the $template remote variable to point to the UD location: $template remote,"/mnt/disks/SYSLOG//syslog-%FROMHOST-IP%.log" If you want to preserve your existing syslog info, copy syslog-[ip address of server].log from the current location to the UD location. Disable and then Enable the syslog server to restart it and force it to read the new config. The local syslog folder should now show <custom> If you want to test that syslog is now writing to the new location, log out of the GUI and log back in. This should be recorded in the syslog in the UD location. UPDATE: To make all of the above work properly, I found it necessary to run a user script that restarts the syslog server after the array starts on a server reboot. This script contains the following: #!/bin/bash /etc/rc.d/rc.rsyslogd restart Setting it up to run on array start makes it all automatic so you can set it and forget it. Celebrate your success in writing the syslog to a removable and replaceable UD location that does not hammer your boot flash drive and does not use an unRAID share.

You should attach your diagnostics to a new post (Tools --> Diagnostics from the GUI).

I am still running the 5.14.23 controller and recently added a U6 Lite AP. It provisioned just fine and installed an update to the 5.43.23.12533 firmware. Seems to be working fine. My AC APs are on firmware version 4.3.28.11361 and show no updates available. There are available updates to 5.43.23.12533 for the USG and switches, but I have not installed these updates yet. The U6-LR AP requires controller 6.0.34 or higher.

Frnt_Fan1 and Frnt_Fan 2 are my two HDD cage fans and are setup identically. On Hard drives to poll, I just have the HDDs selected as they are ones in the cages and I have deselected the SSD/NVMe drives. The way my case is designed, the air from the HDD cage fans flows through the HDD cages and then is redirected back over the MB. I have set the minimum HDD fan speed to 50% to keep air flowing back to the MB and it helps with CPU and PCH temps (nothing can fix the MB temp reading) to have air flow at at least 50% even when all HDDs are spun down. CPU Fan settings:

Assigning static IP addresses to docker involves making the appropriate network selection in the docker container. I set up a VLAN in my router and unRAID specifically for docker containers to which I wanted to assign a static IP address. It shows up as Custom:br0.3 in the Network selection in the container. If you have your eth0 bridged in Network settings, you should also have a Custom:br0 that will allows the same. I followed the same rules here as with static address and the router DHCP and I did not allow the VLAN in unRAID to assign DHCP addresses. I wanted to manually assign them and so I made sure they were not in the router DHCP range as the router DHCP and VLAN DHCP have no concept of communicating with each other and need to be in separate ranges to avoid any possible conflicts.

Depending on how long your router allows DHCP addresses to be reserved and how often your server is offline will have a lot to do with determining if the server IP address can be assigned to another device. Some routers basically let DHCP assigned addresses persist permanently while others have a limit of 7 days or less. Once your server grabs the preferred address, nothing else should get that same address assigned unless the server is forced to give it up or is offline. I once had a router that did not make it easy to assign static IP addresses but allowed fairly long lease time. To make sure that address would never be assigned elsewhere I did as John M said and set my DHCP pool to begin at 192.168.1.21 and left anything below .21 to be assigned as static addresses. Worked great. My current router allows static IPs to be assigned, but, I still keep DHCP to a range outside of the static addresses. Just disconnecting the phone would not necessarily let the router reassign that address immediately unless you rebooted the server and it saw that address was available.

Yes. It is that easy. Many prefer to assign the static address in the router if that is supported and leave unRAID at DHCP in Network Settings. However, if your router does not support assigning static addresses to clients (most do support this). The way you mentioned is the way to do it in unRAID.

I'm guessing the two-part connector plugs into the modular power supply. On the 24-pin end for the motherboard it is likely that a 4-pin block can be separated from one end if the motherboard supports only 20 pins.

Be my guest. Use/modify it as you wish. It is nothing more than the standard UD Backup script modified to backup some additional shares. This is fine. It will take a while but just plug it in and let it run. I initially did about 8TB. I can't remember exactly how long it took but it was not an unreasonable amount of time.