Nanuk_

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.

Uploading Attachment... orion-diagnostics-20260515-1658.zip

Actually this was the fdisk result for both nvme before the reboot. I opened another browser tab and ran it once the reboot button showed up.

I've run fdisk -l /dev/nvme0n1 fdisk -l /dev/nvme1n1

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?

Hello! 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". Should I remove this?