Jump to content

Squid

Community Developer
  • Posts

    28,770
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. Hitting ignore permanently removes the issue
  2. Doesn't matter. Its just a bug where the default paths in VM settings have to be filled out and be valid locations. Except that your diagnostics show that the 2 entries are filled out. @ljm42 is the guy who figured all this stuff out re why the GUI thinks the array isn't running. I would guess that @johnnie.black wants to see the diagnostics to see if the message from Fix Common Problems is valid or not for the type of SSDs that you have.
  3. If you're still running 6.4.0, upgrade to 6.4.1 (May have to do it manually - download the 6.4.1 zip file from limetech's website, and extra all the bz* files from it and overwrite the ones on the flash drive) There was a bug in 6.4.0 that caused this. After 6.4.1 is up, you'll still have to make a change in VM Settings.
  4. You can stick it right on the tabs via the Custom Tab plugin.
  5. When you enter in the name for the tab, there's a drop down. If you start entering in NZBGet for instance, NZBGet will appear below. If you select it, then you're given those extra options
  6. You should post your diagnostics before you reboot
  7. Show me the exact error that its displaying
  8. Go to CA settings in top right and enable dockerHub search results
  9. Not that I use this plugin, but I will say that if you have your docker.img file (if you use docker applications) stored on your cache drive, then its pretty much a given that at any point in time your cache drive is active.
  10. I'm not going to speak for lsio, but what I assume is that because all of their containers have updates available for them rain or shine on Fridays, it is a real aggravation for them to keep track of a change log for everything. You'd be best off hitting the app's Project Page and viewing the changelog / commits there.
  11. *If* it was indeed CA that crashed your server, then it's only ever happened for you. CA is arguably the most stable and bug free of any plugin for unRaid. Far far more likely that you have bad memory, power supply, etc and that it was a coincidence.
  12. Install Fix Common Problems plugin (the URL for a separate install is listed in the thread) Put it into troubleshooting mode, then try and replicate the problem. Post the resulting file that FCP generated.
  13. CA Auto Update already installed and doing it for you? If so, disable notifications from Dynamix for docker update checks
  14. Debating to rename this thread to Community Applications/General Support/Preclear Questions
  15. A mod will move accordingly as only certain people can create new topics in that forum
  16. You're missing the first forward slash in the script. It should be /var/local/emhttp/var.ini
  17. Yup. As @wgstarks pointed out, preclear is currently not compatible with unRaid 6.4.1 and CA by default will only display apps that are compatible with your unRaid version.
  18. Are you sure the template that's showing in Previous Apps isn't identical (name, tag, etc) to the one you've got installed?
  19. All errors / warnings found will always be shown until a rescan is done. Because a scan takes some time to run the display is static so it's faster to fix the problems if you're bouncing back and forth from different screens in the GUI
  20. By reinstalling you probably got rid of the orphans already as a side effect
×
×
  • Create New...