Jump to content

Squid

Community Developer
  • Posts

    28,769
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. You should post your diagnostics after this happens.
  2. Try again later. That just means that for whatever reason the system was unable to reach the repository to check for updates. Nothing sinister. If issues continue, set static DNS addresses (208.67.222.222 / 208.67.220.220)
  3. It's never checking for updates (Update Check Frequency)
  4. Try a different USB port, ideally USB2 when you boot up. You can also try the Flash Remount Plugin (you'll have to reboot after installing, and the system has to be in a working state when you install) Failing that, transfer the key to a new device
  5. How many connections are you allowing on NZBGet? You should pretty much use as many as your provider allows (eg: 20) What is presumably your downloads (d.......s) share is set to use cache: yes, so new files get written to the cache drive and ultimately moved to the array You appdata is spanning between disk 1 and the cache. You should stop docker in Settings - Docker, run mover then re-enable it after the move is done.
  6. No. It actually looks like the flash drive was either pulled out or dropped offline. Reboot is your recourse (a parity check will ensue no matter what, which should be safe to cancel) If this continues, then try the Flash remount plugin.
  7. No it's not. The are still technically "sparse", but will always eventually grow to the maximum size of the vdisk and never shrink, won't be trimmed etc (ie: as you add files to the VM, the image will grow, but when you delete files it won't shrink. You eventually (shortly) get to a point where the vdisk is the maximum size and stays there forever To enable this, you need to do (and as a bonus, write performance will also increase)
  8. Perhaps the mover tuning plugin has the ability to selectively move based upon file type. Not quite sure. The base OS makes no provisions for this.
  9. There's no error checking at all on the custom entry, so whatever you use should get automatically added.
  10. Why I'm not sure, but what's happening is that the clients are displaying the names as 8.3 (ie: a "DOS" formatted name)
  11. Stopping happens before (while the services at being stopped). Starting happens after the disks are mounted
  12. How much memory do you have? 4G is the functional minimum. Anything less and I wouldn't try anything on it other than strictly a file server.
  13. You need to post your diagnostics after waiting for a minimum of 120 seconds in that state
  14. You want the VM to sleep when the RDP connection is terminated. Unraid has no idea about that. You have to handle that on the client. To power stuff up you can try playing around with
  15. Settings - VM Settings This is all client side and you'd have to investigate there.
  16. No. It's hardcoded into the WebUI at 120seconds. The next release is increasing the timeout to 5 minutes. Any plugin where its possible for a request to take longer than the timeout has to account for that and program itself accordingly. Note that even with the timeout the command(s) were still continuing while you are on that page. IE: the script would have finished, but the spinner would never have disappeared
  17. Pause just pauses execution on the VM and keeps it powered up. Hibernate is the same as Windows. Dumps the contents of RAM, its current state to the vdisk and powers down. That's hibernate. You set the default action in unraid to be hibernate instead of shutdown and install the virtio-tools from the ISO into the VM so that it supports that function Because a VM is for all intents and purposes the same thing as a baremetal machine. When you log out of your Windows box. It stays on also.
  18. OK. So the net result of the test was that the VM tab worked and you could actually add a VM?
  19. Quirk of the GUI where it defaults to certain items when things are wrong, but the setting doesn't actually reflect the setting that appears
×
×
  • Create New...