Kilrah

Members
  • Posts

    1994
  • Joined

  • Last visited

Everything posted by Kilrah

  1. Folder on a ZFS drive is known to cause these issues. Best to go back to image if you have a ZFS cache.
  2. By default the log is written into the data location. You should be able to move it into the appdata folder by adding a line in config.php. https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/logging_configuration.html The "appdata_instanceid" folder might be a problem too, don't see a way to move it from a quick search but you could always cobble together an additional Docker mount for it.
  3. Unraid itself should never be exposed. Are you using wireguard? If not check that there isn't anything set there/remove what's in the /config/wireguard folder on the flash drive.
  4. Updated and went to browse my remote mount from unraid to check and had such messages as well. Downgraded as precaution because my server backs up 20TB worth of another machine's data using rsnapshot twice a day via SMB and it'd wreak complete havoc in the retention history if suddenly a bunch of files were not seen.
  5. /dev/shm is a ramdisk that's already available that you can just map and write into.
  6. You're not trying to mount a remote "Shares-Pools" when you already have a local "Shares-Pools", right? Try changing the name of one of them so they don't conflict.
  7. Use the grouping feature.
  8. Have you set up core isolation in Settings-> CPU pinning? If so then those wouldn't be used for anything else than VMs.
  9. Nein, immer gleich oder grösser.
  10. If you want plex to be backed up separately / differently then skip it in appdata backup and use a different method just for that.
  11. As mentioned it'd be only plugins, not apps/containers. Plugins are extensions to the OS, so the OS version matters. But it'll be the same, if you stay on an old version of unraid you'll have the old version of the plugin that works with it and that's it, it just won't get updates anymore just like unraid itself.
  12. It's got nothing to do with the new licensing, CA just doesn't support <6.12 anymore. The CA support thread has a link to install an earlier version.
  13. Manually extract the archive to a temp location and grab the file you want.
  14. Typically unraid will crash in short order if the USB is removed.
  15. Click the "manual backup" button. You haven't set a time to run at.
  16. AFAIK the problem is that once a drive was removed the UI doesn't show it in the list anymore so while it's still in the config file you can't see or unselect it in the UI.
  17. Believe the issue's been found and fixed for a future version, IIRC it happens if you leave the Docker page open for a long time and don't reload it before applying updates.
  18. I use that and also back up my databases with the "db backup" container.
  19. After the code to redeem you'd have gotten another email to download the key file, get it from there.
  20. Name resolution is always a bit flaky, accessing by IP is best.
  21. AFAIK you can set a plugin's min and max versions in CA, so you could have different plugins called the same with non-overlapping versions and people will see the one that work with theirs. An old version wouldn't get any more breaking/feature changes (or any changes at all) so if it works by the time the new one comes out the old one will likely continue to work without intervention.
  22. They are mounted to unraid in your screenshot, they must NOT be if the VM is to access them directly. Not sure passing a single partition even works, might have to pass the whole disk or nothing.