Jump to content

trurl

Moderators
  • Posts

    43,943
  • Joined

  • Last visited

  • Days Won

    137

Everything posted by trurl

  1. You could New Config without them and rebuild parity.
  2. If nothing was on it then I guess not
  3. Nothing can move open files. You have to disable Docker in Settings before you can work with that.
  4. trurl

    disk.cfg

    Did you have a current flash backup?
  5. trurl

    disk.cfg

    Also the pools folder in config has the assignments for any pools.
  6. trurl

    disk.cfg

    Was your flash backup missing config/super.dat?
  7. If you want to "fill the gap" where disk4 was by changing the assignments do so now, then While parity is rebuilding, on Main - Array Devices, you should see lots of Reads from all assigned data disks, lots of Writes to both parity disks, zeros in the Errors column. If it looks like there are problems, post new diagnostics.
  8. right Do you have adblocker or anything else that might interfere?
  9. You should add attributes 1 and 200 for monitoring on all your WD drives. When you do, you will see several drives with SMART ( 👎 ) warnings on the Dashboard page. And setup Notifications to alert you by email or other agent as soon as a problem is detected.
  10. Looks like you must have already done New Config
  11. Assuming this is a new flash drive with a new key file, then copy config folder from your flash backup except for the old key file.
  12. Dynamix File Manager is a plugin and will work with Docker disabled. It will be built-in with v6.13
  13. These latest diagnostics shows appdata, domains, and system shares with files on the array. Ideally, these would all be on cache or other fast pool, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.
  14. Here is a post I made some time ago about 2 "surprises" to watch out for
  15. I only meant that your syslog showed the files that had been moved. Examine it for yourself to see what I mean.
  16. https://docs.unraid.net/unraid-os/manual/shares/user-shares/
  17. speed isn't important for the boot drive. Does it have a unique GUID?
  18. Another possible cause of corruption is bad RAM.
  19. Unraid will not automatically reboot. Some BIOS can be set to boot when power is restored, otherwise rebooting on its own suggests a hardware problem.
  20. Often the cause of docker image corruption is overfilling it. And filling docker.img is often caused by an application writing to a path that isn't mapped. I have been using default 20G docker.img for years with no problem, but I have never ran more than 16 containers.
×
×
  • Create New...