Community Developer
  • Content count

  • Joined

  • Last visited

  • Days Won


saarg last won the day on March 26

saarg had the most liked content!

Community Reputation

22 Good

About saarg

  • Rank
    Advanced Member


  • Gender
  • Location
    Up North!
  1. You need to store the config in a place that is not in memory. Every time unraid boots it unpacks the filsystem to the memory. Your new path will survive a reboot.
  2. That error is most likely a browser window open from before the reboot or margarita/controlr phone app.
  3. Then you need to fork our github repo and build it yourself.
  4. Go to the apps tab and push the CA manual in the bottom left corner. Then choose the Advanced - dockerhub integration. Then your question should be answered.
  5. Do not use vnc and GPU pass through at the same time. The GPU doesn't work as it should then. Have you tried dumping the vbios and adding it to the XML? Might fix ovmf problem.
  6. I see you have chosen seabios and not OVMF for the VM. Any reason? Try with OVMF. For this you have to make a new VM. If you choose win 10 OVMF is default.
  7. Did you isolate core 1 and 9 before testing? Are you running the VMS at the same time. If you are, try running only one and see if it helps. Did you verify that the MSI fix was applied? Have you tried using ddu to remove graphics drivers and reinstall it? Is it a clean win 10 install or upgraded?
  8. The problem of setting up Plex every reboot might be related to your path to the appdata. Try rebooting the container now to see if the same thing happens.
  9. The high latency might be caused by setting the emulator pin wrong. Not sure what else it could be, but you might want to try to install the tips and tricks plugin and set the CPU governor to performance.
  10. Have you tried changing the pcie gen in the bios for the slot the card is in?
  11. The snow you are seeing in the libreelec VM is a HDMI cable problem most likely. Replace it with a good quality cable and if you are using 4k resolution be sure it handles 18Gbps bandwidth. You should remove core 0 and maybe its thread from the emulator pin as unraid likes to use this one. I'm not sure how much CPU is needed for the emulator but try one core for each VM and it should be one that is isolated. I'm speaking about cores you can choose in the VM template and not physical cores.
  12. Just try what I suggested to see if it works. Then deal with the situation later. I don't see why you would want to spread the Plex appdata on all your drives. This will spin up all drives when someone is browsing Plex. Choose one drive and if it gets full, move to another drive.
  13. Change the appdata folder path to /mnt/diskX/appdata/PlexMediaServer and see if that works better. Replace the X with one of your disks.
  14. Did you also reboot unraid?
  15. You have your share set to use the cache disk (if you have one. You didn't say). If you have one, check if it's full. It's also advice to use a disk share for the plex appdata as FUSE doesn't play nice with plex. Another thing might be your docker image is full. It might be plex stores metadata in temp before writing it to the config folder.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.