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.

CoolHam

Members
  • Joined

  • Last visited

  1. Thanks for the additional information. I have opened an issue. https://github.com/e7d/docker-prometheus-nvidiasmi/issues/1
  2. Just wanted to jump in and confirm I am also having the same issue as moarSmokes. Seems like the most recent Unraid upgrade has broken it for some reason. Thank you for all the free, community work you do ich777! I'm sure you will have this fixed when you have the time to spare!
  3. Hello - I recently migrated my unraid server to some new hardware. I am using the built in 2.5Gig network interface on the motherboard. Unraid initially boots fine and I can start the array, then after about 20-30 minutes, the server cannot be accessed through the network anymore (physical connection w/monitor works fine). I exported the syslog and it appears to be a IGC error of some kind. The error in question is from line 8-40 in the file. I have tried a different network cable. Any help is appreciated! Thanks. New Relevant Hardware: AMD Ryzen 9 7950X 16-Core/32-Thread ASUS ROG STRIX X670E-E GAMING WIFI 6E Socket AM5 Kingston FURY Beast 64GB (2x32GB) DDR5 5600MHz Edit: Solution: The IGC error appears to be related to a power management feature that suspends the network interface after some time. It is supposed to "wake" but this feature does not work with the many current linux kernals. In order to fix the issue, I had to disable these power management features by appending these two startup parameters in the unraid /syslinux/syslinux.cfg file. pcie_port_pm=off pcie_aspm.policy=performance The entire line should read "append initrd=/bzroot pcie_port_pm=off pcie_aspm.policy=performance" This is clearly more of a work-around than a fix, but its what worked for me so far. This reddit thread helped a lot: syslog
  4. Okay. If yours is the same I suppose that is some good news... When I boot the VM the connected display stays black. I am just testing with a Windows 10 install right now, not using LibreElec.
  5. Thanks for the write up Marv, I followed it exactly however It did not solve the error Im having. Its not entirely the same thing, But I have an UHD 750 and when running the VM, I get this: 2023-01-15T22:59:11.306752Z qemu-system-x86_64: -device {"driver":"vfio-pci","host":"0000:00:02.0","id":"hostdev0","bus":"pci.0","addr":"0x2"}: IGD device 0000:00:02.0 has no ROM, legacy mode disabled 2023-01-15T22:59:11.724838Z qemu-system-x86_64: vfio-pci: Cannot read device rom at 0000:00:02.0 Device option ROM contents are probably invalid (check dmesg). Skip option ROM probe with rombar=0, or load from file with romfile= Any ideas as to why

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.