Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid 7.1.4 random errors. Unsure where to start troubleshooting

Featured Replies

Hey all, I have had a couple random issues starting to creep up on my unraid install and trying to figure out what is going on. First, I keep getting the Nvidia driver to go into an unresponsive state. nvidia-smi says no devices. GPU wont show in settings or in the dashboard widget. Reboot brings back the device for between 1 and 7 days. Within the last week Fix Common Problems kicked off a error stating that there was hardware issue (Ryzen 5800x). I took a look at the diagnostic logs but there wasn't anything that I could glean from the logs. Lastly, my rig locked and the DRAM light kicked on for the motherboard. Seems like the whole thing is going downhill.

I am running a Memtest currently but looking at the community to help me understand other things I can test. Seems like these issues are related but since we are taking ram, gpu, and cpu I am having a hard time focusing on what component could be the issue.

MCE hardware Error from logs

Jun 17 18:23:18 Oldtown kernel: mce: [Hardware Error]: Machine check events logged
Jun 17 18:23:18 Oldtown kernel: [Hardware Error]: Corrected error, no action required.
Jun 17 18:23:18 Oldtown kernel: [Hardware Error]: CPU:1 (19:21:0) MC20_STATUS[-|CE|-|AddrV|-|-|CECC|-|-|Scrub]: 0x850fc389c08500af
Jun 17 18:23:18 Oldtown kernel: [Hardware Error]: Error Addr: 0x0000000000000000
Jun 17 18:23:18 Oldtown kernel: [Hardware Error]: IPID: 0x0000000000000000
Jun 17 18:23:18 Oldtown kernel: [Hardware Error]: Bank 20 is reserved.
Jun 17 18:23:18 Oldtown kernel: [Hardware Error]: cache level: L3/GEN, tx: RESV

oldtown-diagnostics-20250626-0915(latest).zip oldtown-diagnostics-20250618-0759(hardware error).zip

  • Author

Thanks for the reply @JorgeB .

Current BIOS Settings:

Aura - Off

DDR - 2666 for 2x16GB

SVM - Enabled

IOMMU - Enabled

HD Audio - Off

Onboard Lan - Off (I have a 10Gbit network card)

WiFi - Off

Bluetooth - Off

Fans - Turbo

I thought that CStates were largely fixed so I didn't do any CState / idle power management settings. I just went in and turned back on Power Supply Idle to be Typical Current Idle.

Would this cause issues with DRAM and the Nvidia GPU disappearing or am I troubleshooting multiple problems?

Edited by kbareis

  • Community Expert

It can, also see that part about slightly increasing voltage for 5000 CPUs, it can also help with stability issues in some cases

  • Author

So I think I just stumbled upon my issue. The VM I am running appears to be grabbing the Nvidia GPU when my docker images are backed up and upgraded over night. By rebooting the VM, the gpu comes back and is viewable via the Dashboard and nvidia-smi. However, the docker images that want to use it cannot and must be rebooted as well.

So the final question is, how do I force the VM / VM manager to not steal the GPU? The GPU for the VM is set to virtual already.

  • Community Expert

The VM should only use the GPU if it's on the XML.

  • Author

Cross posted on the thread for the Nvidia driver. https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/198/#findComment-1564122

If you take a look at the screen recording, you can see the graphics driver for the VM is virtual but as soon as the VM is shut down, the GPU comes back and is available for the system again. This seems to happen overnight when Backup/Restore Appdata is backing up my containers.

oldtown-diagnostics-20250628-1220.zip

  • Community Expert
14 hours ago, Wedgetastic said:

the GPU comes back and is available for the system again

Try binding the GPU to vfio-pci, that should prevent it from ever being used by the driver/OS

  • 2 weeks later...
  • Author

I ended dropping back to the production driver and the GPU is no longer being grabbed by the VM

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.