Jump to content

Squid

Community Developer
  • Posts

    28,770
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. User scripts only supports disks_mounted and stopping_svcs For anything else the user would have to create the appropriate folder in /usr/local/..... and toss the script in there either via go or user script at array start (one time)
  2. No clue. AFAIK, memory ballooning is mostly an enterprise feature. Probably most (if not all) users here don't use it, but I'm sure there's quite a bit of info via Google on KVM / memory ballooning / Ubuntu.
  3. Dec 4 06:58:39 nickles-UNRAID shfs: cache disk full This immediately preceded the start of your issues with the docker image. IIRC, BTRFS does not particular like (or handle well) drives becoming full, and very quick glance shows at least the media share writes to the cache drive until its 100%
  4. Dec 3 19:49:51 unRAID emhttpd: unclean shutdown detected Your system is powered off on the times when the wakeup doesn't work. What I would do is uninstall the S3 sleep plugin, and see if the system says up for an extended period of time (ie: the length of time it would take for you to notice that you had to push the power button to wake it up) and go from there.
  5. You don't need to uninstall it. Harmless error, and it is being fixed today
  6. You hit Edit from the dashboard / docker tab on the app, make a change ( any change ), revert the change and then hit apply
  7. If its stuck, then yeah your options become limited. And another thing which will also cause the system to fail on Sync Filesystems is if you happen to be running a PreClear on a drive...
  8. If you were in the shell and the current directory happens to be /mnt/user/... (or simply /mnt/user), then the system won't be able to stop the array properly. There's a plugin called StopShell which will forcibly kill any processes like that which will impede a shutdown
  9. https://forums.unraid.net/topic/99690-solved-minor-script-errors-on-boot-caused-by-unknown-plugin/?tab=comments#comment-919752
  10. Your mce came up during initialization of the cores. Happens on some combinations of hardware and can be safely ignored.
  11. Forgivable. When was the last time CA didn't have an update for this long?
  12. That way that I did it was to look at all the .plgs within /boot/config/plugins and see which code section was long enough to hit a line 87 and then copied / pasted that section and saw that line 87 contained an ==, then uninstalled the plugin rebooted and saw the error didn't reappear. The way most people would have done it is uninstall one by one followed by a reboot and see when the error disappeared.
  13. Problem is right in your post. Memory read error on channel 0, dimm 0 Your system event log may shed more clues on the exact dimm this refers to.
  14. It's actually UD. First time I've turned on my monitor in about a year and the same thing is there. @dlandon
  15. /dev/loop2 40G 39G 128M 100% /var/lib/docker The docker image is full, and SAB (because it's saying only 120odd MB is free is looking at downloading into it). Show the docker run command as detailed here https://forums.unraid.net/topic/57181-docker-faq/?tab=comments#comment-564345 Also a screenshot of what appears when on the docker tab you press Container Size
  16. Much simpler to just go to Tools, Diagnostics and then attach the entire ZIP file to your next post
  17. One possibility is if the KB / Mouse were disconnected for some reason. Installing the HotPlug plugin should fix you up, unless you're using passthrough on a USB controller which is connected to the VM
  18. Unraid does support minimum RAM and maximum RAM allocated to the VM's when editing the template. Not really sure if anyone has ever played with this, or what requirements are necessary on the VM side of things.
  19. Depends upon where Sab is downloading to. If it's to a share that's cache-only, and the cache drive only has 127MB free, then Sab is telling the truth.
  20. Because it's in the dockerfile itself to use 3000, and then the actual software itself winds up listening on 3080 due to the environment variable, and then template doesn't support mappings.
  21. Container size on the docker tab will also help to see where the bloat is. Usual cause of the image filling up is excessive logging and downloading into the image. There's a couple entries in the Docker FAQ about that.
  22. You can try this https://forums.unraid.net/topic/83965-server-keeps-crashing/?tab=comments#comment-785306
  23. Probably this Dec 1 17:39:34 Morioh kernel: ixgbe 0000:04:00.1: Warning firmware error detected FWSM: 0x00000000 Which is being continually logged. BIOS update?
×
×
  • Create New...