Nanuk_

Thanks! I'll pull the new 2 sticks out for now and monitor my NAS for anymore corruption errors on the nvmw.

My dashboard is shows corruption errors reported for my boot drive data partition - it started happening last week after I installed 2 additional RAM sticks and configured the BIOS for my 5950x so it doesn't lock up anymore. I ran an extended SMART test and in the Web UI under Self Test for that drive it says "Completed with No Errors" orion-diagnostics-20260718-0345.zip

Damn! I was hoping I just needed to toggle something in BIOS. Thanks!

I received this message from "orion-diagnostics-20260708-2206.zip". Your server has detected hardware errors. The output of mcelog has been loggeg. Post your diagnostics and ask for assistance on the Unraid forums More Information Found this in the syslog: Jul 8 20:47:20 Orion root: Fix Common Problems: Error: Machine Check Events detected on your server Jul 8 20:47:20 Orion root: mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead. Jul 8 20:47:20 Orion root: CPU is unsupported I am running a Ryzen 5950x with a 2080 Ti. I recently disabled secure boot because Unraid won't start with it on after I added more RAM. I also just installed Immich and FolderView Plus, but the problem happened after I reinstalled Scrutiny It didn't install right away because I got this error "The container name "/scrutiny" is already in use by container" which I solved by deleting the container and then installing it. I did notice that all my containers had shut off and only Scrutiny was running. I've disabled it for now while I wait for a response here.

Yes, it worked. Looks stable so far except for a few missing docker containers. But that's probably because I moved some stuff around to make room on the nvme before moving them back after converting it to a bootable partition.

orion-diagnostics-20260515-1653.zipUploading Attachment... orion-diagnostics-20260515-1658.zip

Actually this was the fdisk result for both nvme before the reboot. I SSHd into the server and ran it once the reboot button showed up.

I've run fdisk -l /dev/nvme0n1 fdisk -l /dev/nvme1n1 and run the internal boot wizard multiple times, but the bios won't detect the (nvme1n1) as a UEFI boot drive no matter what I do. Does anyone have experience with MSI bios that can help?

Hello all, is anyone having a bios issue with the MSI bios not allowing the selected nvme drive as a boot option after running the "Internal boot" wizard and rebooting? I have secure boot disabled and AHCI enabled but I still get select the nvme as a boot option after running the wizard, rebooting and going to bios. Uploading Attachment...

New plugin update is out. Does anyone know the proper steps to get it working again? Is it update then restart Unraid?

Hmmm.... I believe I already have it set up that way. I have the transcode cache on an NVMe. maybe it's freaking out because it's not on the same share as the actual media files?

I think it maybe be the newer version of Unraid now detects my Wifi and since I have ethernet installed because I want more stable transfer speeds. I get this in my docker container. IPv4 custom network on interface br0: Subnet: 10.0.0.0/24 Gateway: 10.0.0.1 DHCP pool: not set IPv4 custom network on interface wlan0: Subnet: 10.0.0.0/24 Gateway: 10.0.0.1 DHCP pool: not set

Made the same changes: Updated the BIOS Global c-state control disabled. RAM speed was already set 2666 Will wait to see if I get the error pops up again? Apr 5 21:12:07 Orion emhttpd: shcmd (131): /usr/local/sbin/mount_image '/mnt/system-nvme/docker/docker-xfs.img' /var/lib/docker 25 Apr 5 21:12:07 Orion kernel: loop2: detected capacity change from 0 to 52428800 Apr 5 21:12:07 Orion kernel: XFS (loop2): Mounting V5 Filesystem 2811cf8d-9764-4493-adf9-3b778498401b Apr 5 21:12:07 Orion kernel: XFS (loop2): Ending clean mount Apr 5 21:12:07 Orion root: meta-data=/dev/loop2 isize=512 agcount=4, agsize=1638400 blks Apr 5 21:12:07 Orion root: = sectsz=512 attr=2, projid32bit=1 Apr 5 21:12:07 Orion root: = crc=1 finobt=1, sparse=1, rmapbt=1 Apr 5 21:12:07 Orion root: = reflink=1 bigtime=1 inobtcount=1 nrext64=1 Apr 5 21:12:07 Orion root: = exchange=0 metadir=0 Apr 5 21:12:07 Orion root: data = bsize=4096 blocks=6553600, imaxpct=25 Apr 5 21:12:07 Orion root: = sunit=0 swidth=0 blks Apr 5 21:12:07 Orion root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=0 Apr 5 21:12:07 Orion root: log =internal log bsize=4096 blocks=16384, version=2 Apr 5 21:12:07 Orion root: = sectsz=512 sunit=0 blks, lazy-count=1 Apr 5 21:12:07 Orion root: realtime =none extsz=4096 blocks=0, rtextents=0 Apr 5 21:12:07 Orion root: = rgcount=0 rgsize=0 extents Apr 5 21:12:07 Orion root: = zoned=0 start=0 reserved=0 Apr 5 21:12:07 Orion emhttpd: shcmd (133): /etc/rc.d/rc.docker start Apr 5 21:12:07 Orion rc.docker: Starting Docker daemon...

orion-diagnostics-20260405-2042.zipHello! The “Fix common problems” plugin has alerted me to post my system diagnosis after the following error: Apr 5 19:47:03 Orion root: Fix Common Problems Version 2025.08.07 Apr 5 19:47:16 Orion root: Fix Common Problems: Error: Machine Check Events detected on your server Apr 5 19:47:16 Orion root: mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead. Apr 5 19:47:16 Orion root: CPU is unsupported

Sorry, Is this not that? Not being combative in tone. Really want to learn and fix this. /temp/mnt/media-nvme/Media/TdarrCache/

Hmmmm.... but I constrained Tdarr's RAM usage to 16GB. Extra Parameters = --runtime=nvidia --memory=16g When you say "work area" do you mean this? /mnt/media/mnt/user/Media/ /temp/mnt/media-nvme/Media/TdarrCache/ /app/server/mnt/system-nvme/docker/appdata/tdarr/server/ /app/configs/mnt/system-nvme/docker/appdata/tdarr/configs/ /app/logs/mnt/system-nvme/docker/appdata/tdarr/logs/

I don't remember installing a RAM-Disk plugin so I'm not sure why Unraid keeps making a RAM-Disk. Is this new with the current version? Ah wait I am apparently using "[Plugin] RAM-Disk for Docker logs"(https://forums.unraid.net/topic/185193-plugin-ram-disk-for-docker-logs/). Should I remove this?

orion-diagnostics-20260331-1648.zip I'm noticed a "Out of memory errors detected on your server" error in "Fix Common Problems". I've created a diagnostic file and posted it here. I used to have 128GB but 2 DIMMs went bad and I'm down to 64GB. After looking at the logs I found this: Mar 30 12:45:54 Orion kernel: CPU: 1 UID: 0 PID: 189224 Comm: Tdarr_Server Tainted: P O 6.12.54-Unraid #1 Mar 30 12:45:54 Orion kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Mar 30 12:45:54 Orion kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D52/MPG X570S CARBON MAX WIFI (MS-7D52), BIOS 1.B0 03/24/2025 Mar 30 12:45:54 Orion kernel: Call Trace: Mar 30 12:45:54 Orion kernel: <TASK> Mar 30 12:45:54 Orion kernel: dump_stack_lvl+0x47/0x70 Mar 30 12:45:54 Orion kernel: dump_header+0x44/0x190 Mar 30 12:45:54 Orion kernel: oom_kill_process+0x82/0x190 Mar 30 12:45:54 Orion kernel: out_of_memory+0x3f6/0x430 Mar 30 12:45:54 Orion kernel: mem_cgroup_out_of_memory+0x79/0xb0 After looking further into the logs I found this: Mar 30 12:45:54 Orion kernel: oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=4501c4190269d07e3727707b32bd473cb3c894842f01f55bf42578d867f0db0c,mems_allowed=0,oom_memcg=/docker/4501c4190269d07e3727707b32bd473cb3c894842f01f55bf42578d867f0db0c,task_memcg=/docker/4501c4190269d07e3727707b32bd473cb3c894842f01f55bf42578d867f0db0c,task=Tdarr_Node,pid=680048,uid=0 Mar 30 12:45:54 Orion kernel: Memory cgroup out of memory: Killed process 680048 (Tdarr_Node) total-vm:25476312kB, anon-rss:12988128kB, file-rss:13848kB, shmem-rss:0kB, UID:0 pgtables:337080kB oom_score_adj:0 Mar 30 12:45:56 Orion kernel: oom_reaper: reaped process 680048 (Tdarr_Node), now anon-rss:480kB, file-rss:2668kB, shmem-rss:0kB Mar 30 12:47:01 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 12:47:08 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 12:47:20 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 13:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 13:47:01 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 13:47:11 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 13:47:23 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 14:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 14:47:02 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 14:47:03 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 14:47:17 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 15:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 15:47:03 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 15:47:05 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 15:47:18 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 16:00:01 Orion move: mover: started Mar 30 16:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 16:00:07 Orion Parity Check Tuning: Send notification: mover running: (type=normal link=/Settings/Scheduler) Mar 30 16:00:22 Orion kernel: mdcmd (46): nocheck PAUSE Mar 30 16:00:22 Orion kernel: Mar 30 16:00:22 Orion kernel: md: recovery thread: exit status: -4 Mar 30 16:00:27 Orion Parity Check Tuning: Manual Correcting Parity-Check: Manually paused Mar 30 16:10:39 Orion move: mover: finished Mar 30 16:12:11 Orion Parity Check Tuning: Send notification: mover no longer running: Manual Correcting Parity-Check (56.3% completed) (type=normal link=/Settings/Scheduler) Mar 30 16:12:25 Orion kernel: mdcmd (47): check resume Mar 30 16:12:25 Orion kernel: Mar 30 16:12:25 Orion kernel: md: recovery thread: check P Q ... Mar 30 16:12:30 Orion Parity Check Tuning: Manual Correcting Parity-Check: Manually resumed Mar 30 16:47:01 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 16:47:02 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 16:47:14 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 16:57:25 Orion monitor_nchan: Stop running nchan processes Mar 30 17:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 17:47:02 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 17:47:08 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 17:47:20 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 18:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 18:47:01 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 18:47:03 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 18:47:20 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 19:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 19:47:02 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 19:47:03 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 19:47:16 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 20:00:01 Orion move: mover: started Mar 30 20:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 20:00:06 Orion Parity Check Tuning: Send notification: mover running: (type=normal link=/Settings/Scheduler) Mar 30 20:00:18 Orion kernel: mdcmd (48): nocheck PAUSE Mar 30 20:00:18 Orion kernel: Mar 30 20:00:18 Orion kernel: md: recovery thread: exit status: -4 Mar 30 20:00:23 Orion Parity Check Tuning: Manual Correcting Parity-Check: Manually paused Mar 30 20:08:21 Orion move: mover: finished Mar 30 20:12:12 Orion Parity Check Tuning: Send notification: mover no longer running: Manual Correcting Parity-Check (70.9% completed) (type=normal link=/Settings/Scheduler) Mar 30 20:12:27 Orion kernel: mdcmd (49): check resume Mar 30 20:12:27 Orion kernel: Mar 30 20:12:27 Orion kernel: md: recovery thread: check P Q ... Mar 30 20:12:32 Orion Parity Check Tuning: Manual Correcting Parity-Check: Manually resumed Mar 30 20:47:01 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 20:47:03 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 20:47:14 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 20:52:58 Orion monitor_nchan: Stop running nchan processes Mar 30 21:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 21:47:02 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 21:47:04 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 21:47:20 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 22:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 22:47:03 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 22:47:04 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 22:47:17 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your server Mar 30 23:00:01 Orion docker: Success: Backup of RAM-Disk created. Mar 30 23:42:26 Orion monitor_nchan: Stop running nchan processes Mar 30 23:47:01 Orion root: Fix Common Problems Version 2025.08.07 Mar 30 23:47:06 Orion root: Fix Common Problems: Warning: Deprecated plugin ca.cleanup.appdata.plg Mar 30 23:47:19 Orion root: Fix Common Problems: Error: Out Of Memory errors detected on your serverI've since removed the Deprecated plugin ca.cleanup.appdata.plg.

What is it's normal size?

orion-diagnostics-20260326-2057.zipAttaching another diagnostic file.

I ran "tail -f /var/log/syslog" and it looks like this entry just keep repeating. Mar 26 20:50:19 Orion kernel: get_swap_device: Bad swap file entry 3fff7ffffffff

What command do I run to find out what eating all the space in /var/log?

I tried truncating it and increasing the size but it keeps filling up. root@Orion:/var/log# mount -t tmpfs tmpfs /var/log -o size=8G,remount root@Orion:/var/log# truncate -s 0 /var/log/syslog root@Orion:/var/log# du -h /var/log 0 /var/log/pwfail 0 /var/log/preclear 0 /var/log/unraid-api 0 /var/log/.pm2/modules 4.0K /var/log/.pm2/pids 0 /var/log/.pm2/logs 24K /var/log/.pm2 0 /var/log/swtpm/libvirt/qemu 0 /var/log/swtpm/libvirt 0 /var/log/swtpm 0 /var/log/samba/cores/rpcd_winreg 0 /var/log/samba/cores/rpcd_classic 0 /var/log/samba/cores/rpcd_lsad 0 /var/log/samba/cores/samba-dcerpcd 0 /var/log/samba/cores/winbindd 0 /var/log/samba/cores/smbd 0 /var/log/samba/cores 144K /var/log/samba 0 /var/log/sa 0 /var/log/pm2 0 /var/log/plugins 0 /var/log/pkgtools/removed_uninstall_scripts 24K /var/log/pkgtools/removed_scripts 2.7M /var/log/pkgtools/removed_packages 2.7M /var/log/pkgtools 8.0K /var/log/nginx 0 /var/log/nfsd 0 /var/log/libvirt/qemu 0 /var/log/libvirt/ch 0 /var/log/libvirt 6.5G /var/log