Jump to content

itimpi

Moderators
 View Profile  See their activity

  • Posts

    20,780

  • Joined

  • Last visited

  • Days Won

    57

 Content Type 

Everything posted by itimpi

  1. itimpi
    if you have lots of rame then you probably want it mapped to a RAM location on Unraid (e.g. /tmp/plex), and otherwise to a SSD pool.
  2. itimpi
    I suspect that this is due to a bug that has been identified in the Unraid shutdown sequence where the location containing the required binaries gets unmounted too early. If so this is fixed for the 6.12.4 release which I think is probably getting close now. I would check when that is available if the problem still occurs or there is something else going on.
  3. itimpi
    This suggests you have their working sets mapped to a location that is not an actual physical one so ends up being in RAM which is why they get lost on reboot.
  4. itimpi
    There may be a permissions issue, or it may be the one that docker is currently using. I would try the Dynamix File Manager plugin in preference to Krusader as that would not be affected by a permissions issue.
  5. itimpi
    The simplest solution is to replace the failed disk and rebuild its contents. You solution is valid if you do not intend to replace the failed drive.
  6. itimpi
    You are looking for a docker container that is growing in size as it runs. Probably the commonest is Plex transcoding to a location that is internal to its container, whereas ideally that location should be mapped to an external location on the Unraid host. The Container Size button on the Docker tab can help with this.
  7. itimpi
    You have to decide which one is the most current (probably the one on the cache, and then you can delete the other one. Note that the high utilization of docker.img is unrelated to this issue - it tends to mean that the way you have plex configured it is writing to a location internal to the docker.img file rather than to an external mapped location.
  8. itimpi
    How are you passing the drives to the VM? Perhaps you should provide the xml for a problem VM?
  9. itimpi
    Post your diagnostics to get any sort of informed feedback. Can you describe the issues you have been having in a bit more detail.
  10. itimpi
    You can use the process documented here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page to sort out your drives.
  11. itimpi
    Are you booting in Legacy or UEFI mode? Have you tried both modes?
  12. itimpi
    Not sure to be honest! One thing to remember is that UD devices cannot participate in user shares whereas pools can. Whether that will affect your workflow I am not sure. it is possible the mover restriction might disappear in the 6.13 release, but until we actually get visibility of that release that is just a guess.
  13. itimpi
    Mover does not support moving files between pools.
  14. itimpi
    With those settings it will be in the ‘logs’ folder on the flash drive.
  15. itimpi
    You might want to try enabling the syslog server so we can get a syslog that survives a reboot. Posting your current diagnostics might allow us to see if you got an unclean shutdown or not. If you did not then this would suggest something actively shutdown your server.
  16. itimpi
    Unraid does not rely on drive letters being constant - it works on drive serial numbers. Not sure therefore why you got the effects you describe.
  17. itimpi
    The network interface seems to be continually going up and down. Have you tried rebooting the router. i notice that you seem to have Jumbo frames enabled. In my experience these tend to cause more problems than they are worth and provide negligible performance gain.
  18. itimpi
    Single drive pools can be any supported file system. Multi-drive pools have to be ZFS or btrfs. Btrfs provides maximum flexibility in expanding pools, particularily with drives of mixed sizes, whereas ZFS normally provides maximum performance.
  19. itimpi
    1). Using a dtive for cache is about improving writing (not reading) speed but is completely optional. 2). The OS is not ‘installed’ in the traditional sense. It is always loaded off the flash drive at boot time to run from RAM.
  20. itimpi
    There is a known problem with docker that can cause this that had been fixed in the 6.12.3 release.
  21. itimpi
    Have you set a Minimum Free Space value for the pool?
  22. itimpi
    Have you tried the steps for troubleshooting Unclean shutdown that are covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.
  23. itimpi
    You should not assume that anyone from the Unraid team sees every post on this forum as it is primarily used for community support. To get a formal answer I would expect you need to email Unraid support.
  24. itimpi
    Just for reference passing memtest is not definitive, whereas failing it is.
  25. itimpi
    Glad to here that it worked successfully That is useful information to know if it coms up again in the forum.
×
×
  • Create New...