Jump to content

Squid

Community Developer
  • Content Count

    20028
  • Joined

  • Last visited

  • Days Won

    218

Everything posted by Squid

  1. You add your command to that script Go to the flash share
  2. You can use any particular file editor, including notepad on Windows (over the network). No need to worry about linux style line endings on the go file. But, personally, I'd just use nano from the terminal nano /boot/config/go CTRL-X will save and exit.
  3. Nope.. After recreating the image with an appropriate size, go to Apps - Previous Apps and check off whatever you had installed and they'll be reinstalled the exact same way with the paths, ports, etc.
  4. the docker image never grows. It is always at the size which you set within Settings - Docker. You also cannot shrink it to a different size simply by changing that setting. To do that, you've got to delete the image and reinstall your apps (Apps- Previous Apps) You've got it currently set to 200G, but at some point you had it set to 420G and didn't delete the image when lowering it's size.
  5. you can do something like this mkdir /tmp/docker mount /mnt/user/system/docker.img /tmp/docker cd /tmp/docker/btrfs/subvolumes then you can use the appropriate command lines to search each of the subvolumes that are in there to find your file. Probably easiest to use midnight commander (mc) at the command prompt to do this.
  6. Should also be noted that the VMs while are technically thin provisioned, will always grow in size and never shrink unless you do this
  7. A new tag for your xml templates is available. <multiLanguage>true</multiLanguage> Adding this tag is a manual edit to your template. dockerMan does NOT have the option to add this tag in. If this line is in your template, CA (versions after unRaid 6.9.0-beta 2 is released) will show the user (if they click on the app's icon or the more info icon) that the application itself is multi-language compatible. Use this where the app's GUI allows the user to easily switch between languages (eg: sabnzbd)
  8. Mar 29 07:41:14 Serverbox kernel: irq 17: nobody cared (try booting with the "irqpoll" option) Post the output of this command from the terminal: cat /proc/interrupts
  9. Is it auto updating via the auto update plugin? Is there a custom network or something that you're using on it?
  10. OK. Disregard my reply in the CA thread. This is probably far more likely to be at first guess a problem with your memory. As a first step, run at least a pass or two of Memtest on the boot menu to see if there's any errors from that. After that, post your diagnostics
  11. EDIT: Replied in your other thread, as it appears this is not CA related
  12. Yeah, the all ignored could / should be collapsed by default, since it's simply a history of everything you've ignored regardless of it's its found again.
  13. There is not (and never will be) any guarantee for a drive to be assigned a particular sdX name at boot time. It's all dependent upon the order in which the drives enumerate themselves. They do tend to not change if you don't add / remove drives though (but no guarantee) If you're scripting all this then you would have to extract the appropriate designation for the drive from /var/local/emhttp/disks.ini
  14. As a start, I would assign a static IP address to your server and DNS addresses of 208.67.222.222 and 208.67.220.220 and also fill out the gate way with the address of your router and then see if that makes any difference.
  15. https://forums.unraid.net/topic/57181-docker-faq/#comment-564309
  16. The solution is probably what the post above yours specified.
  17. New build or not, its 100% bad memory (or possibly very badly seated memory). Your event log in the BIOS might contain further suggestions on which stick is giving the problems (other than Channel 0, Dimm 0)
  18. Stopping & restarting the array should get rid of the share showing up over the network. But, if it still does, then it's been created again by the application and you have to fix that.
  19. We'll switch a PM'ing. This may wind up being a back and forth thing.
  20. Been deprecated and only only appears if you've had it previously installed or if you enable show deprecated in ca setting
  21. Deleting the contents of /config/plugins/user.scripts on the flash drive followed by an uninstall then a reinstall will set it back to default. You will however loose your scripts. If you need to keep your scripts then dont delete the contents of the scripts folder
  22. Yeah, the VOLUME is what the app explicitly suggests be stored out of the image /var/www/shaarli/cache mapped to /mnt/user/appdata/shaarli-cache /var/www/shaarli/data mapped to /mnt/user/appdata/shaarli-data And maybe the config files are already set to go to /var/www/shaarli/cache which means that once that mapping is in place it should be more or less good to go.
  23. You may have to do both. Set the config file to reference say something like /shaarli-data. and you would add a new path mapping to your template of //shaarli-data mapped to something like /mnt/user/appdata/shaarli-data The real place to start on this is if they list somewhere an example of the docker run command, a docker compose file, or a dockerfile so that you can then easier figure out what path mappings it suggests on docker.