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...