itimpi

Moderators
  • Posts

    19353
  • Joined

  • Last visited

  • Days Won

    53

Everything posted by itimpi

  1. We normally say reboot as that is easier for most users, but no reason you should not manually delete the old log.
  2. What release are you currently running? There was definitely an issue around this in the early 6.12.x releases but they have largely been fixed now I believe. Having said that I have seen some suggestions that there might be more improvements around this area in the 6.12.7 release.
  3. Why use New Config to add a drive. That is not the normal way of doing it. New Config should only be used in extreme circumstances.
  4. If you look in the config/shares folder on the flash drive there will be .cfg files for every current share and shares that might have existed in the past. You can safely delete any that do not correspond to shares you currently have.
  5. I interpret that phase as meaning that any settings that refer to drives in any way get reset to their defaults.
  6. I think that is by design. Using New Config is not something that is done in normal running.
  7. It should always show something! were you using the Mirror to flash option, or the alternative of putting you servers address into the Remote Server field?
  8. That means that you almost certainly feel foul of the behaviour described in the Caution in this of the online documentation accessible via the Manual link at the bottom of the Unraid GUI. If you had used something like Dynamix File Manager plugin to do this it would have protected you from this problem as it always uses a copy/delete strategy for moving files. You can use Dynamix File Manager to delete the empty folders.
  9. I think there is something missing from your list of events but not sure. the problem almost certainly arose from you mixing disk shares and user shares. The /data location is a user share and applies regardless of what array drive or pool the files are on. The cache_large for instance is a physical device and any files you delete from there that are also deleted from the user share. did you by any chance us a move rather than a copy when you tried to move files? This can have unexpected effects.
  10. No idea. You should ask in the support thread for the container you are using.
  11. It definitely would as it stops you being able to remove a drive keeping data intact.
  12. I do not use Plex so I am guessing. You might be ale to correlate the timing with specific Plex activity. I think that the paths inside the container is set at the Plex level. You then need to match those to the volume mappings you have for the Plex container. Note that I also mentioned the Plex temp folder - I believe that can get large while Plex is scanning.
  13. I would think that Plex is the most likely culprit! Do you have something like Plex transcode folder set so that it is internal to the docker.img file? What about the Plex tmp folder?
  14. Do you have the Connect plugin installed? It had a bug (cleared in the latest update) which did excessive logging and could cause this. After updating the plugin you need to reboot the server to clear the log space. If it is not that, then running du -h /var/log should show what is the likely culprit.
  15. That message does not explain why the system would stop responding. It means that the cache has fallen below the minimum free space value allowed to write a new file to the cache, so the file will be written directly to the array instead. You have 100GB set as the minimum free for the cache so that is the value probably triggering it. I see that you have macvlan networking enabled for docker, but have not disabled bridging on eth0 as is recommended in the Unraid release notes to get maximum stability when using macvlan. Any reason for this?
  16. If I remember correctly you need to have the array stopped to change it.
  17. It normally downloads as a zip file if done from the GUI. If you generated it via the command line it will have been put into the ‘logs’ folder on the flash drive.
  18. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. it might help if you gave a clue about what type of errors? Perhaps a screenshot of the Main tab might clarify things?
  19. That card should definitely work with Unraid. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. That would at least allow us to see if it is visible at the handware level. Do you have any alternative PCIe slots you can try the card in? Do you have another system you can try the card in to check it is not faulty?
  20. I do not think that setting makes any difference as for read purposes Unraid finds a file that logically belongs to a share even when it is on a drive that is not on the include list of drives.
  21. Not sure why you were getting the excessive usage, but at the very least you should set the Minimum Free Space setting on the cache to avoid it filling up completely as btrfs file systems tend to misbehave if they get too full.
  22. No idea why it will not reboot - that suggests something at the motherboard level. Is the BIOS battery flat as that can cause symptoms like this. In terms of working out why it is crashing you should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field.
  23. It could be the Cache Dirs plugin which would keep issuing 'find' commands to try and keep directory entries in RAM. It is a good idea to configure that plugin to only scan folders that need it as it does not work very well if there are too many files/folders in the ones it is scanning.
  24. You should set the Minimum Free Space on the cache to be larger than any file you expect to download so that when it drops below this new files overflow to the main array rather than filling the cache pool to the point of causing problems.
  25. That shows that the Connect plugin is the culprit. The most recent update to that plugin fixes the excessive logging issue, but you will still need to reboot the server to clear the log space used.