Jump to content
We're Hiring! Full Stack Developer ×

Squid

Community Developer
  • Posts

    28,733
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. If the HBA has an auxiliary power connector then yes I'd be using it... But either way, more expansion cards / components = more points of failure. You can always explicitly ask Avago if it is or not. However a good rule of thumb is what price you paid for it. If you bought a supposedly new HBA for less than $100 when it retails for $650 it's a good bet that it's counterfeit.
  2. https://github.com/dcflachs/compose_plugin
  3. Jan 29 16:01:11 Tartarus kernel: mpt3sas_cm1: SAS host is non-operational !!!! Your HBA reset itself right at the time all of this happened... You can try I suppose to reseat it. But, is the HBA counterfeit? I had a counterfeit HBA at one point that did pretty similar things. Also curious why you'd be using an HBA in the first place instead of your internal ports...
  4. Have you looked at replacing the network cables. One oddity about ethernet is that a single bad cable anywhere in the network can also have the same results as what you're seeing. And are you sure that there is no IP address conflicts with your static IPs?
  5. updated the OP. The script list though I have absolutely no time to keep it updated and haven't done for quite awhile.
  6. The plugin will not install on 6.12+, so it's a install once, forget about it completely and you're safe going forward
  7. Where are you trying to pin the containers to? Isolated cores or the non-isolated cores... Also, what version of the OS as IIRC there was an issue with earlier kernel releases where this could have happened. As a general rule, there's not much need to pin containers to cores at all unless you want to limit their performance by not using all the non-isolated cores
  8. The post about the plugin was not referencing you, but rather the community and everyone creating a script / manually patching the file. Recipe for disaster since if / when you upgrade the OS you're going to forget that you were applying a patch manually via a script somewhere and now that patch is going to potentially cause problems whereas the plugin handles that occurrence correctly
  9. The mere switch didn't solve your problem... Something else was amiss...
  10. HIGHLY recommended to NOT patch your docker files manually and instead use the plugin. Patching manually means that if / when you update the OS to 6.12 any manually patches that you are applying automatically will potentially interfere with the OS and be a big pain to troubleshoot
  11. Is it the exact same repository that shows in Apps as is showing in Docker (advanced view)?
  12. The original author has deleted the plugin, so it's time to update to 6.11.5
  13. /boot/config/plugins/dockerMan/userprefs.cfg
  14. Nope it's down, and will be down for a couple hours until I can see what the he'll happened Currently AFK
  15. https://forums.unraid.net/topic/134016-fix-to-a-small-issue-with-updating-oci-docker-images/page/2/#comment-1220827
  16. CA shows everything installed so long as the user-template exists on the flash drive (/config/plugins/dockerMan/templaes-user) If you've deleted it or it became corrupt or if you installed a container manually via the command line or docker compose then it will not show it as being installed, because CA is unable to manage it. IE: Does "Edit" appear in the drop down on the docker tab, and if it does will it return an error when selecting it
  17. Spin up a bare bones VM using VNC as the display type. From it you can access all of your containers remotely via remote access option on MyServers / TeamViewer etc.
  18. https://forums.unraid.net/topic/84229-dynamix-wireguard-vpn/?tab=comments#comment-780665
  19. The reverse is also true on dark theme... and for the same reasons
  20. Does it continue with the docker service stopped?
  21. Have you seen this? https://unraid.net/blog/ssl-certificate-update-2
×
×
  • Create New...