Kilrah

Members
  • Posts

    2000
  • Joined

  • Last visited

Everything posted by Kilrah

  1. Are you accessing the array at all at the same time? Any other read/write will slow down the check, it only runs full speed if nothing else touches the array.
  2. 1) You don't want to put your backup destination into the appdata share itself 2) Is that folder actually on the cache drive? What's your share configuration for the appdata share?
  3. Likely a single location was corrupted, but now since it can't be repaired it keeps reporting errors everytime it's accessed... Sorry, make that a check filesystem on the cache then.
  4. All depends on how it evolves, now it's just a single corrupted block in the Docker image, maybe it even fixes itself if that gets deleted/rewritten when updating a container, or maybe it gets worse. Could just leave it as is until it breaks more I guess.
  5. You can do a scrub of the cache pool, and if no errors recreate the docker image https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file If the problem comes back it'll likely be a hardware issue and you'll want that memtest.
  6. Unraid doesn't allow transfer/resale. https://unraid.net/policies-2023
  7. If you're using a reverse proxy that's probably what needs to be configured right
  8. But it has that already, assumed you were using it.
  9. Did you do the next step mentioned earlier? You need to actually grow the partition in the VM. And since the VM files are sparse the allocation will only change when the space actually gets filled in the VM.
  10. Interesting. Guess that means some tweaking since the order is going to be different when using groups. A delay that's not necessary for docker service start may be for backups.
  11. There isn't one. The flexibility is what you lose with a zfs pool, it's one thing that can't be broken down or (easily) expanded. Do you have extra SAS/SATA ports to shuck the externals and connect them internally?
  12. Stopping is fine because it doesn't move to the next before the container is stopped and once it's stopped... well it's stopped for real, but on start many take a while for the actual app to start after the container itself is up So yeah having start delays like on the main Docker page would be useful
  13. Kinda makes sense as it is for the most important to be at the top. Problem with a VPN container is it'll likely take some time before it's ready, but since there's no delay setting it'll be "started" in a second or 2 then the next is started, but actually it'll need maybe 30 seconds to connect to the VPN and actually be available for others to use...
  14. A single CRC error is nothing, just a spurious comminucation failure between drive and controller.
  15. hdplex stuff is usually good. Note only 10A on the 5V rail and single 4-pin for SATA power so you probably don't want more than maybe 5 drives on there.
  16. Siehe vorherigen Post und Unraid-Version prüfen...
  17. 1) You have no mapping for the "upload" folder, that's probably it 2) You've made several separate shares for it, is it intended? 3) You're giving access to the entire server as "import" directory, doesn't seem wise
  18. https://forums.unraid.net/topic/162221-rsync-script-löscht-dateien/?do=findComment&comment=1406619
  19. It'll be in the backup folder for that run. Did you reboot since last run?
  20. They wouldn't be able to know about it unless they're actively crawling it during the <minute of downtime it should have...
  21. That is for appointing someone to configure your server for you. Licensing issues have nothing to do with this and will be solved when you fill up the form with your problem without any payment obviously.
  22. 1) Your screenshot doesn't show the reason it isn't 2) Contact support, forum can't help with licensing