IamSpartacus

Members
  • Posts

    802
  • Joined

  • Last visited

Everything posted by IamSpartacus

  1. I see. So if i wanted to move 7.5TB off one drive and scatter it across 8 new drives, I'd have to select subfolders and do a different move job for each subfolder?
  2. I'm trying to do a scatter by moving a directory on disk1 to multiple disks (disks8-15, all empty). However, when I start the move it only moves the files to the first disk (disk8) in the group of disks I'm trying to move the data to. What am I missing?
  3. It's not Plex that causes high CPU, RAM, or Disk I/O. It's the mover process. I have mitigated this for the time being by scheduling my mover to only run once a day at 5am. But now that I've moved into doing a lot of 4K, sometimes i need to manually run the mover during the day and I have to hope no one is using Plex.
  4. Good thought but in my testing this was not the case. Yes Plex scans on library changes but with all the resources I have at my disposal the scan is done in less than 30 seconds. The issue seems to be CPU IOWait. Watching netdata during the mover process IOwait jumps up significantly and I don't understand why.
  5. I leave my server on 24/7 but I'd still like this feature. Sometimes I need to reboot my server while in the middle of a parity check and I have to cancel the parity check.
  6. Any acknowledgement on this? I'm not quite sure how this is not a bug but regardless this is something that should be at least "implemented" in the next minor release.
  7. How does one get 3rd Party Plugin settings (ie. CopyCompleted) to be persistent through restarts?
  8. I assume there is an easy answer on this but me being fairly noob at Linux hopefully someone can explain it to me. Looking at the used space of my disks in the WebGUI the numbers do not match up if I do a du -sh on the directory (ie. /mnt/disk1). Is the GUI calculating the space differently than the CLI?
  9. Just not needed. I'm using a GPU for HW transcoding so I don't have a lot of CPU needs anymore. 24 (and now 32) CPU threads is plenty.
  10. I typically go with server CPUs for two reasons: IPMI and PCIe lanes. That said, I actually wound up selling this server. It worked amazingly well but I had a gaming PC with a Threadripper 1950x and dual 1080Ti's just sitting idle not doing anything so I turned that into my Unraid server + Windows 10 Gaming VM. Just added a JBOD case for my disks.
  11. Is there a way through the VM XML to delay the startup of a VM?
  12. My backups seem to be going but I keep getting alerts when they are done that there is an error. Yet I don't see any in the produced logs? 20190429_0430_unraid-vmbackup.log 20190429_0430_unraid-vmbackup_error.log
  13. Yes I'm 100% sure because I've never pinned CPUs for any docker containers. But I have just taken your advice and limited the CPUs this particular container can use and it appears to have fixed the issue for the time being.
  14. I agree about CPU 28 being 27 and thus not one of the pinned cores. But Look at the 3rd process down in my most recent Screen Shot. It's using CPU 31 (or CPU 30).
  15. No docker containers have pinned CPUs. Please see attached.
  16. I have 4 cores and 8 threads isolated on my Threadripper 1950x for a Windows 10 VM. Yet docker containers and other system processes are clearly using these threads. beast-diagnostics-20190423-2053.zip
  17. I have 4 cores and 8 threads isolated on my Threadripper 1950x for a Windows 10 VM. Yet docker containers and other system processes are clearly using these threads. beast-diagnostics-20190423-2053.zip
  18. Downloads need to go to cache. I need all the IO my NVMe cache drive can provide in order to DL at 105MB/s while also extracting a 75GB file (4k). I am using Turbo write. I thought maybe that was my issue because all the drives were being read at 240MB/s during the mover so I thought there just wasn't enough disk IO left for Plex direct plays but I then tested with Turbo write off and I get the same issue.
  19. Yea right now I just have my mover moving once a day at 5am. It's tough because I have users on the West Coast and then my wife is up early with our 3 month old so I have a very small window now haha.
  20. Agreed. I did search but I almost never find relevant topics when I search here.