pixeldoc81

Well, you are right, not best practice, that's for shure! I've added a note about unsafe settings and link MS article.

IPv6 vs IPv4 / Hostname vs. IP for UNC SMB accessIf you try to access your Unraid Server via UNC path with hostname: \\tower Windows will ether use IPv4 or IPv6, depending on availability and configuration on Client and Server. Try to use IPv4 address in UNC path instead to avoid IPv6 issue: \\192.168.0.5 Guest Access via SMB from Windows to Unraid / SambaWARNING: These settings are considered unsave ! https://learn.microsoft.com/en-us/windows-server/storage/file-server/smb-signing Disable Windows SMB signing required for SMBSet-SmbClientConfiguration -RequireSecuritySignature $false -ForceAllow Windows Guest Logon via SMBSet-SmbClientConfiguration -EnableInsecureGuestLogons $true -ForceNote: Username on Windows and Unraid needs to be different for this to work out of the box.

FYI, link to source code: NEW: https://github.com/unraid/fix.common.problems/ OLD: https://github.com/Squidly271/fix.common.problems/

The issue does still happen on UNRAID 7.0.1 nchan stats https://tower.local/nchan_stub_status total published messages: 8639286 stored messages: 0 shared memory used: 130308K shared memory limit: 131072K channels: 0 subscribers: 0 redis pending commands: 0 redis connected servers: 0 redis unhealthy upstreams: 0 total redis commands sent: 0 total interprocess alerts received: 0 interprocess alerts in transit: 0 interprocess queued alerts: 0 total interprocess send delay: 0 total interprocess receive delay: 0 nchan version: 1.3.7 syslog Apr 24 16:17:47 tower nginx: 2025/04/24 16:17:47 [error] 4015853#4015853: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Apr 24 16:17:47 tower nginx: 2025/04/24 16:17:47 [error] 4015853#4015853: *10106188 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Apr 24 16:17:48 tower nginx: 2025/04/24 16:17:48 [crit] 4015853#4015853: ngx_slab_alloc() failed: no memory Apr 24 16:17:48 tower nginx: 2025/04/24 16:17:48 [error] 4015853#4015853: shpool alloc failed Apr 24 16:17:48 tower nginx: 2025/04/24 16:17:48 [error] 4015853#4015853: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Apr 24 16:17:48 tower nginx: 2025/04/24 16:17:48 [error] 4015853#4015853: *10106193 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Apr 24 16:17:48 tower nginx: 2025/04/24 16:17:48 [crit] 4015853#4015853: ngx_slab_alloc() failed: no memory Apr 24 16:17:48 tower nginx: 2025/04/24 16:17:48 [error] 4015853#4015853: shpool alloc failed Apr 24 16:17:48 tower nginx: 2025/04/24 16:17:48 [error] 4015853#4015853: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Apr 24 16:17:48 tower nginx: 2025/04/24 16:17:48 [error] 4015853#4015853: *10106194 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"

total published messages: 2681425 stored messages: 0 shared memory used: 130308K shared memory limit: 131072K channels: 0 subscribers: 0 redis pending commands: 0 redis connected servers: 0 redis unhealthy upstreams: 0 total redis commands sent: 0 total interprocess alerts received: 0 interprocess alerts in transit: 0 interprocess queued alerts: 0 total interprocess send delay: 0 total interprocess receive delay: 0 nchan version: 1.3.7 syslog: Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [crit] 3495097#3495097: ngx_slab_alloc() failed: no memory Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [error] 3495097#3495097: shpool alloc failed Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [error] 3495097#3495097: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [error] 3495097#3495097: *3131170 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [crit] 3495097#3495097: ngx_slab_alloc() failed: no memory Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [error] 3495097#3495097: shpool alloc failed Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [error] 3495097#3495097: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [error] 3495097#3495097: *3131171 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [crit] 3495097#3495097: ngx_slab_alloc() failed: no memory Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [error] 3495097#3495097: shpool alloc failed Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [error] 3495097#3495097: nchan: Out of shared memory while allocating channel /devs. Increase nchan_max_reserved_memory. Feb 17 23:21:18 server nginx: 2025/02/17 23:21:18 [error] 3495097#3495097: *3131172 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/devs?buffer_length=1 HTTP/1.1", host: "localhost" Feb 17 23:21:19 server nginx: 2025/02/17 23:21:19 [crit] 3495097#3495097: ngx_slab_alloc() failed: no memory Feb 17 23:21:19 server nginx: 2025/02/17 23:21:19 [error] 3495097#3495097: shpool alloc failed Feb 17 23:21:19 server nginx: 2025/02/17 23:21:19 [error] 3495097#3495097: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Feb 17 23:21:19 server nginx: 2025/02/17 23:21:19 [error] 3495097#3495097: *3131173 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Feb 17 23:21:19 server nginx: 2025/02/17 23:21:19 [crit] 3495097#3495097: ngx_slab_alloc() failed: no memory Feb 17 23:21:19 server nginx: 2025/02/17 23:21:19 [error] 3495097#3495097: shpool alloc failed Feb 17 23:21:19 server nginx: 2025/02/17 23:21:19 [error] 3495097#3495097: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Feb 17 23:21:19 server nginx: 2025/02/17 23:21:19 [error] 3495097#3495097: *3131178 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 17 23:21:20 server nginx: 2025/02/17 23:21:20 [crit] 3495097#3495097: ngx_slab_alloc() failed: no memory Feb 17 23:21:20 server nginx: 2025/02/17 23:21:20 [error] 3495097#3495097: shpool alloc failed Feb 17 23:21:20 server nginx: 2025/02/17 23:21:20 [error] 3495097#3495097: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Feb 17 23:21:20 server nginx: 2025/02/17 23:21:20 [error] 3495097#3495097: *3131179 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Feb 17 23:21:20 server nginx: 2025/02/17 23:21:20 [crit] 3495097#3495097: ngx_slab_alloc() failed: no memory Feb 17 23:21:20 server nginx: 2025/02/17 23:21:20 [error] 3495097#3495097: shpool alloc failed Feb 17 23:21:20 server nginx: 2025/02/17 23:21:20 [error] 3495097#3495097: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Feb 17 23:21:20 server nginx: 2025/02/17 23:21:20 [error] 3495097#3495097: *3131180 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 17 23:21:21 server nginx: 2025/02/17 23:21:21 [crit] 3495097#3495097: ngx_slab_alloc() failed: no memory Feb 17 23:21:21 server nginx: 2025/02/17 23:21:21 [error] 3495097#3495097: shpool alloc failed Feb 17 23:21:21 server nginx: 2025/02/17 23:21:21 [error] 3495097#3495097: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Feb 17 23:21:21 server nginx: 2025/02/17 23:21:21 [error] 3495097#3495097: *3131181 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Feb 17 23:21:21 server nginx: 2025/02/17 23:21:21 [crit] 3495097#3495097: ngx_slab_alloc() failed: no memory Feb 17 23:21:21 server nginx: 2025/02/17 23:21:21 [error] 3495097#3495097: shpool alloc failed Feb 17 23:21:21 server nginx: 2025/02/17 23:21:21 [error] 3495097#3495097: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Feb 17 23:21:21 server nginx: 2025/02/17 23:21:21 [error] 3495097#3495097: *3131182 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 17 23:21:22 server nginx: 2025/02/17 23:21:22 [crit] 3495097#3495097: ngx_slab_alloc() failed: no memory Feb 17 23:21:22 server nginx: 2025/02/17 23:21:22 [error] 3495097#3495097: shpool alloc failed Feb 17 23:21:22 server nginx: 2025/02/17 23:21:22 [error] 3495097#3495097: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. dmesg: [Mon Feb 17 23:20:06 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:20:06 2025] nginx[3495093]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 10 (core 2, socket 0) [Mon Feb 17 23:20:06 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:21:06 2025] nginx[3495097]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 1 (core 1, socket 0) [Mon Feb 17 23:21:06 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:21:07 2025] nginx[3496422]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 3 (core 3, socket 0) [Mon Feb 17 23:21:07 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:22:07 2025] nginx[3496423]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 1 (core 1, socket 0) [Mon Feb 17 23:22:07 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:22:08 2025] nginx[3497690]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 9 (core 1, socket 0) [Mon Feb 17 23:22:08 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:23:07 2025] nginx[3497742]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 11 (core 3, socket 0) [Mon Feb 17 23:23:07 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:23:08 2025] nginx[3498986]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 3 (core 3, socket 0) [Mon Feb 17 23:23:08 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:24:07 2025] nginx[3499049]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 9 (core 1, socket 0) [Mon Feb 17 23:24:07 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:24:10 2025] nginx[3500248]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 11 (core 3, socket 0) [Mon Feb 17 23:24:10 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:25:20 2025] nginx[3500304]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 8 (core 0, socket 0) [Mon Feb 17 23:25:20 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:25:20 2025] nginx[3502195]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 11 (core 3, socket 0) [Mon Feb 17 23:25:20 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:25:22 2025] nginx[3502196]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 10 (core 2, socket 0) [Mon Feb 17 23:25:22 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. [Mon Feb 17 23:25:22 2025] nginx[3502201]: segfault at 0 ip 0000000000000000 sp 00007ffdb7dbe498 error 14 in nginx[400000+24000] likely on CPU 2 (core 2, socket 0) [Mon Feb 17 23:25:22 2025] Code: Unable to access opcode bytes at 0xffffffffffffffd6. Unraid 7.0.0 with latest Patch (also happend on Unraid 6.11.x - 6.12.x) VM1 Firefox on Windows Tab: https://tower.local/VMs/UpdateVM?uuid=83303fef-9e86-cdb9-6382-2d241f21adb3 Running for some days i guess PC Firefox on Windows Tab: https://tower.local/Docker Running for some days with hibernation inbetween

@jademonkee Yes, as long as you do not configure CPU Isolation (Settings > CPU Pinning), the Cores can / will be used by all processes & docker. Otherwise, configure CPU Isolation for some Cores (Beware of HT Pairs) and use them exclusively for vm / docker whatever. AFAIK Core 1&2 will always be used by UNRAID itself.

@jademonkee On UNRAID 7 a lot of the Stuff described here can be changed via the GUI. Editing the XML should not be necessary.

I believe I hit the same Problem. Check you fail2ban.log for any iptables Errors. iptables error in `fail2ban.log`: 2025-01-09 21:23:55,807 149A58AACB38 ERROR 149a5a398030 -- exec: { iptables -w -C f2b-vaultwarden-auth -j RETURN >/dev/null 2>&1; } || { iptables -w -N f2b-vaultwarden-auth || true; iptables -w -A f2b-vaultwarden-auth -j RETURN; } for proto in $(echo 'tcp' | sed 's/,/ /g'); do { iptables -w -C DOCKER-USER -p $proto -m multiport --dports http,https -j f2b-vaultwarden-auth >/dev/null 2>&1; } || { iptables -w -I DOCKER-USER -p $proto -m multiport --dports http,https -j f2b-vaultwarden-auth; } done 2025-01-09 21:23:55,807 149A58AACB38 ERROR 149a5a398030 -- stderr: 'iptables: No chain/target/match by that name.' 2025-01-09 21:23:55,807 149A58AACB38 ERROR 149a5a398030 -- returned 1 2025-01-09 21:23:55,808 149A58AACB38 ERROR Failed to execute ban jail 'vaultwarden-auth' action 'iptables-multiport' info 'ActionInfo({'ip': '111.222.333.444', 'family': 'inet4', 'fid': <function Actions.ActionInfo.<lambda> at 0x149a5ab85800>, 'raw-ticket': <function Actions.ActionInfo.<lambda> at 0x149a5ab85f80>})': Error starting action Jail('vaultwarden-auth')/iptables-multiport: 'Script error' The Problem is, the linuxserver.io docker 1.1.0 container has `iptables v1.8.10 (nf_tables)` and UNRAID 6.12.14 has `iptables v1.8.9 (legacy)`. So the container is using an other iptables modules as UNRAID as the docker host. One can check this by running `iptables --version` and the docker host and in the fail2ban container. The solution is to change the banaction to use iptables-legacy. Example: [DEFAULT] banaction = iptables-multiport[iptables=iptables-legacy] Then the iptables rule should be added correctly in iptables on the UNRAID docker host and the blocking should work. root@unraid:~# iptables -L -n ... Chain DOCKER-USER (1 references) target prot opt source destination f2b-vaultwarden-auth 6 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 80,443 RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 ... Chain f2b-vaultwarden-auth (1 references) target prot opt source destination REJECT 0 -- 111.222.333.444 0.0.0.0/0 reject-with icmp-port-unreachable RETURN 0 -- 0.0.0.0/0 0.0.0.0/0

I am using pure-ftpd on Docker (Community Store App) as a Replacement. Works ok for me. I using it for my IP-Cameras to store the recorded Files via FTP on my Server.

You are right, this is a single disk mounted with unassigned devices plugin. Using a single disk pool did not cross my mind. I will give it a try. IMHO better error handling would be great. Is the swapfile plugin source on github to maybe contribute a pr?

I've encountered a issue. The swap file location was configured to: `/mnt/disks/ssd1`, but automount for the disk was not enabled, so the filesystem was not mounted. The script will try to create the swap file in `/mnt/`filesystem, where is not enough disk space. The script `/usr/local/emhttp/plugins/swapfile/scripts/rc.swapfile` has no error check for `dd` command creating the swap file and thus did not detect any error: # Create swap file logit "Creating swap file ${SWAP_LOCATION}/${SWAP_FILENAME} please wait ..." dd if=/dev/zero of=${SWAP_LOCATION_NEW}/${SWAP_FILENAME_NEW} bs=1M count=${SWAP_SIZE_MB_NEW} Maybe we should check if target filesystem has enough free space before creating the swap file to avoid this issue? At least the script should check if `dd` command was successfull and or should check if swap file does have the desired size?

https://forums.unraid.net/topic/104711-solved-looking-for-the-command-to-disable-screen-blanking/

BTW, this is how apply the Setting via SSH (non permanent): TERM=linux setterm -blank 0 -powerdown 0 -powersave off >/dev/tty0 </dev/tty0 This is an extended config: setterm -blank 0 -powerdown 0 -powersave off

Similar Error messaged filling up syslog on my Server, but not local log. UNRAID 6.12.10 Unraid Connect Plugin was installed, have uninstalled it now. root@srv:~# grep -o 'Increase nchan_max_reserved_memory' /mnt/user/system/syslog-127.0.0.1.log | wc -l 74452 root@srv:~# awk -v phrase="Increase nchan_max_reserved_memory" '{count += gsub(phrase, "")} END {print count}' /mnt/user/system/syslog-127.0.0.1.log 74452 root@srv:~# awk -v phrase="Increase nchan_max_reserved_memory" '{count += gsub(phrase, "")} END {print count}' /mnt/user/system/syslog-127.0.0.1.log.1 261773 root@srv:~# grep -o '"/usr/local/emhttp/us"' /mnt/user/system/syslog-127.0.0.1.log root@pd-srv:~# du -h /mnt/user/system/syslog-127.0.0.1.log* 48M /mnt/user/system/syslog-127.0.0.1.log 159M /mnt/user/system/syslog-127.0.0.1.log.1 548M /mnt/user/system/syslog-127.0.0.1.log.2 1.6G /mnt/user/system/syslog-127.0.0.1.log.3 1.6G /mnt/user/system/syslog-127.0.0.1.log.4 root@srv:~# du -h -d 1 /var/log 0 /var/log/pwfail 16K /var/log/unraid-api 0 /var/log/preclear 0 /var/log/swtpm 2.5M /var/log/samba 0 /var/log/plugins 28K /var/log/pkgtools 0 /var/log/nginx 0 /var/log/nfsd 16K /var/log/libvirt 3.1M /var/log

Here is an example from my Server. Mainboard: Supermicro X10DRI-F CPU: Intel Xeon E5-2630 v4 RAM: 4x 8GB ECC Memory UNRAID: 6.12.6 # dmesg | grep EDAC [ 129.472264] EDAC MC: Ver: 3.0.0 [ 129.482175] EDAC sbridge: Seeking for: PCI ID 8086:6fa0 [ 129.482194] EDAC sbridge: Seeking for: PCI ID 8086:6fa0 [ 129.482213] EDAC sbridge: Seeking for: PCI ID 8086:6f60 [ 129.482226] EDAC sbridge: Seeking for: PCI ID 8086:6fa8 [ 129.482234] EDAC sbridge: Seeking for: PCI ID 8086:6fa8 [ 129.482244] EDAC sbridge: Seeking for: PCI ID 8086:6f71 [ 129.482251] EDAC sbridge: Seeking for: PCI ID 8086:6f71 [ 129.482261] EDAC sbridge: Seeking for: PCI ID 8086:6faa [ 129.482269] EDAC sbridge: Seeking for: PCI ID 8086:6faa [ 129.482279] EDAC sbridge: Seeking for: PCI ID 8086:6fab [ 129.482286] EDAC sbridge: Seeking for: PCI ID 8086:6fab [ 129.482292] EDAC sbridge: Seeking for: PCI ID 8086:6fac [ 129.482296] EDAC sbridge: Seeking for: PCI ID 8086:6fac [ 129.482302] EDAC sbridge: Seeking for: PCI ID 8086:6fad [ 129.482307] EDAC sbridge: Seeking for: PCI ID 8086:6fad [ 129.482312] EDAC sbridge: Seeking for: PCI ID 8086:6f68 [ 129.482317] EDAC sbridge: Seeking for: PCI ID 8086:6f79 [ 129.482325] EDAC sbridge: Seeking for: PCI ID 8086:6f6a [ 129.482333] EDAC sbridge: Seeking for: PCI ID 8086:6f6b [ 129.482341] EDAC sbridge: Seeking for: PCI ID 8086:6f6c [ 129.482365] EDAC sbridge: Seeking for: PCI ID 8086:6f6d [ 129.482374] EDAC sbridge: Seeking for: PCI ID 8086:6ffc [ 129.482377] EDAC sbridge: Seeking for: PCI ID 8086:6ffc [ 129.482384] EDAC sbridge: Seeking for: PCI ID 8086:6ffd [ 129.482387] EDAC sbridge: Seeking for: PCI ID 8086:6ffd [ 129.482394] EDAC sbridge: Seeking for: PCI ID 8086:6faf [ 129.482399] EDAC sbridge: Seeking for: PCI ID 8086:6faf [ 129.482617] EDAC MC0: Giving out device to module sb_edac controller Broadwell SrcID#0_Ha#0: DEV 0000:ff:12.0 (INTERRUPT) [ 129.482623] EDAC sbridge: Ver: 1.1.2 # lsmod | grep edac sb_edac 24576 0 edac_core 65536 1 sb_edac # grep "[0-9]" /sys/devices/system/edac/mc/mc*/csrow*/ch*_ce_count /sys/devices/system/edac/mc/mc0/csrow0/ch0_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow0/ch1_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow0/ch2_ce_count:0 /sys/devices/system/edac/mc/mc0/csrow0/ch3_ce_count:0 # lshw -class memory | grep ecc capabilities: ecc configuration: errordetection=multi-bit-ecc # mcelog --client Memory errors SOCKET 0 CHANNEL 0 DIMM 0 DMI_NAME "P1-DIMMA1" DMI_LOCATION "P0_Node0_Channel0_Dimm0" corrected memory errors: 0 total 0 in 24h uncorrected memory errors: 0 total 0 in 24h SOCKET 0 CHANNEL 1 DIMM 0 DMI_NAME "P1-DIMMB1" DMI_LOCATION "P0_Node0_Channel1_Dimm0" corrected memory errors: 0 total 0 in 24h uncorrected memory errors: 0 total 0 in 24h SOCKET 0 CHANNEL 2 DIMM 0 DMI_NAME "P1-DIMMC1" DMI_LOCATION "P0_Node0_Channel2_Dimm0" corrected memory errors: 0 total 0 in 24h uncorrected memory errors: 0 total 0 in 24h SOCKET 0 CHANNEL 3 DIMM 0 DMI_NAME "P1-DIMMD1" DMI_LOCATION "P0_Node0_Channel3_Dimm0" corrected memory errors: 0 total 0 in 24h uncorrected memory errors: 0 total 0 in 24h One can get the Information without `edac-util`, but maybe it would be still nice to have. EDAC Kernel Module does load automatically. I don't know if UNRAID will trigger a warning via WebUI if ECC Errors are detected, but this may be OT. +1