Jump to content

Squid

Community Developer
  • Posts

    28,770
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. If the app / tag the template has listed can no longer be downloaded, it gets blacklisted because it can't be installed at all. It's also the reason why the Update Available is listed as being "Not Available"
  2. Would also be helpful if you said what test FCP stopped on since that's listed along with the %
  3. Since it *appears* to be related to the dark theme or theme engine, probably best to ask in it's support thread, as it's not an issue with Unraid itself.
  4. Probably need to update to 6.9.0-rc2+ for the appropriate driver to be available.
  5. The Kernel Helper requires unRaid 6.9.0-rc2+ to run so it's not listed unless you're on that version.
  6. Don't zoom it in so much
  7. Squid

    Happy Birthday!

    Best wishes (and finally a pic without Tom in a Hawaiian shirt!)
  8. /tmp is full. Easiest recovery is a reboot. Do you have a container storing into tmp (like Plex transcoding?)
  9. Last update to the Grafana Unraid Stack container was 20 days ago.
  10. You were probably running 6.8.3. It likely would have given you an IP if you were on 6.9-rc2 (updated drivers)
  11. It sounds like you're booting into the default mode. Boot into GUI mode from the boot menu (you can select this as default) via Main, Boot Device, Click on Flash, then SYSLINUX Configuration
  12. Install the nVidia driver plugin? Also, while not much comfort, at least there is very little reason (other than the odd piece of management) for you to actually use the webGUI of Unraid. Pretty much you should be utilizing another system to interact with the GUI.
  13. https://github.com/limetech/webgui
  14. Make sure that it's set to update the drivers
  15. Feb 7 19:41:45 Asgard kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#1_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0xe6a2d4 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c0 socket:1 ha:0 channel_mask:1 rank:2) Bad memory. Your system event log in the bios should have more info beyond Dimm 0, Channel 0
  16. Some hardware combinations will issue a MCE when initializing the cores. Nothing to worry about and can be safely ignored.
  17. Unraid has a ulimit of unlimited set. The containers *should* inherit that. If they don't, then in the extra parameters you add in --ulimit options https://docs.docker.com/engine/reference/commandline/run/#set-ulimits-in-container---ulimit
  18. You may also consider updating the OS. Based on the copyright, it looks like you're running 6.3.5 while the latest stable version is 6.8.3
  19. Marvel based cards aren't particularly recommended due to various issues that seem endemic to them. LSI based are the ones to use.
  20. Blame docker itself. They're the ones who allow it and have the system ignore it. That's what you're missing. There is never any reason to change the listening port in bridge mode within the app. You only ever change the host port. Post your docker run command. https://forums.unraid.net/topic/57181-docker-faq/?tab=comments#comment-564345
  21. It's in settings (Network Services, WOL)
  22. RDP isn't particularly designed for gaming, but rather handling windows itself.
  23. Try one of the ACS override options. I would think that by and large the PCIe's coming off of the CPU instead of the chipset will always wind up in the same group without ACS
  24. Go to Settings, FCP and click the button to fix it
×
×
  • Create New...