Kilrah

Members
  • Posts

    1968
  • Joined

  • Last visited

Everything posted by Kilrah

  1. Don't enable it then? It's just a GUI for rsync so you could use that directly, or rsnapshot to keep a history although that'll mean different folder structure.
  2. AFAIK it uses unraid's standard "popup window" and that's fixed size/doesn't support scrolling.
  3. Yep, by default Windows opens network shares as list view because creating thumbnails over the network can be slow.
  4. No, it'll constantly change as VPN providers rotate endpoints, websites update their lists etc, but pretty much every commercial VPN will be affected at times. Just know that whenever you have connection issues to something the VPN might be the reason.
  5. Some services block connections from known commercial VPN provider endpoints, good thing to keep in mind when using a VPN for everyday traffic.
  6. And you're using this one? The one pointed to by the first post is for an older version.
  7. SATA expanders are often unreliable. SAS ones are enterprise-grade stuff that works.
  8. It shows being installed and the backup being done every half hour in the syslog.
  9. Sounds like you'd have been using SAS expanders, that's perfectly fine. It's with SATA that they are not recommended.
  10. Some people use separate containers for downloading and seeding, could be a solution.
  11. No, it makes backups that are always fully self-contained so you can revert to something older than latest and it'd be consistent.
  12. Basically doesn't matter for a data share, executing files would require having a shell to the server, having a shell to the server can only be done as root, and root would have all permissions anyway.
  13. Can confirm it works again, i'm back to container. Was broken for a few unraid versions and it seems it got fixed. BTW the dperson/samba repo hasn't been maintained for 4 years, even if it's "internal" so not much to worry about security I've moved to quay.io/unixfox/samba
  14. You don't use NPM, that's only for web/http(s) which rustdesk toesn't have, you forward the ports directly from your router to the container.
  15. Actual program files are within the docker image, in your system share. That should be set to be on the SSD, but it's controller by the system share's settings. Appdata is set to go into the appdata share, again it should be set to the SSD and that share's settings define where it goes. Don't know where immich puts thumbnails, but if you want them on the SSD be sure that's mapped into appdata.
  16. Check if there is a BIOS update available for your mobo. AMD is pretty notorious for USB instability.
  17. Then where that goes is set in that share's settings.
  18. What hardware? Seems the devices disconnect altogether.
  19. The point of min free space is to prevent a single disk from becoming too full and force a switch to the next disk when said min free space is reached. Of course if no other disk fits the bill then you get "no space left".
  20. Your appdata share is set to 200GB min free space, both of your drives are below that at 114 and 188 respectively so anything trying to write to appdata will encounter a "disk full" error. I.e. it was never the Docker image.
  21. Yes paths are always taken from the container settings, then if that path is within one of the appdata sources it's considered internal