DieFalse

Members
  • Posts

    428
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by DieFalse

  1. I agree, I almost got the 1950X and may still when the passthrough and iommu is fixed. I am running a R7 1700 at 3900Mhz with a Kraken x61 cooler with no issues. The stock Wraith Spire ran at 3800 with no issues and I don't want to use 1.7v to get to 4ghz so I will stick with a stable 3.9ghz. This will last me until the price on the TR4 comes down or its bugs are fixed.
  2. I use the ASRock Taichi x370 and love it. Look into a X370 chipset board. Yes, but I have limited pass-through expierence other than clicking the checkbox next to the one I want passed through. Getting unraid up and going is very easy, I had no issues with my Ryzen build aside from a glitch with display resolution in Unraid, Everything else just works and my VMs (Win7, Win2k12 Server Datacentre) all work flawlessly.
  3. Ok, updated the Unraid version and have the R7 1700 running at 3.4Ghz all cores stable. Display is still stuck at 800x600 with the same video cards as before, so I am unsure what that issue is. Since it is unrelated to this thread, I will start another for hardware/software config support. Thank you all for your help!
  4. Thank you for the information, I picked up a R7 1700, Taichi x370 mobo, and 32gb ddr4. This kept me right in line with the budget and after phbigred pointing out the PCIe/NVME really being the only benefit to threadripper, I will wait to upgrade if they prove necessary later. Now I am running on the new setup however, my display seems to be locked at 800x600 which is annoying. Will try to figure that out after updating unraid to 6.4 to accommodate the Ryzen.
  5. In the opinion of the experts here, is it worth it to get the threadripper 1900 over the R7 1700?
  6. I do plan on adding more RAM and I am ok with Ryzen now that the major bugs are resolved. Perhaps the R7 1700? The VMs are not all on at the same time, most I run is 3 and its for testing software configurations etc. One runs all the time for background low process apps.
  7. This would be a fun project for sure, I wish someone would "gift" me a tesla card. Being able to pass through to a VM would make a killer multi-gamer single-pc setup among many other uses... You could even mine off them if you wanted to.
  8. Im with you, however I am about to switch from the Official Plex docker to Binhex-Plexpass, If I find information I will share, however the only thing I can find so far is to backup the library and then delete the docker used and install the new one, config it then load the library backup into before starting it. I'd also appreciate any help
  9. Curious, do you have CEC-ON on the TV? Does turning it off fix this?
  10. I am changing from my AMD FX-8150 build to an Intel for added hardware transcoding capabilities. Can someone please verify that this hardware setup will work: *Also will run about 6 VMs ranging from Linux to Windows Server 2012 Proposed build: Intel I7-6700K (Passmark 11109) ASUS STRIX B250H Gaming LGA 1151 ATX Intel Motherboard w/ Onboard HD GPU 32GB DDR4 RAM 36TB HDD array + 512GB SSD 2x R9-270X in SLI link config Current Build: AMD FX-8150 VT/IOMMU enabled Sabertooth 990FX Motherboard (no onboard gpu) 24GB DDR3 RAM 24TB HDD array + 512GB SSD 2x R9-270X in SLI Link Config Side note, I did post in the Plex Forums as well with no response. Was hoping someone here would have some advice. I am using a Core X9 Thermaltake case with added HDD rack with plenty of cooling, a 1200watt PSU, and would like to get away from AMD as power consumption for utilization makes no sense anymore with AMD. I can go server or desktop grade board/cpu if anyone wants to suggest a different mobo/cpu combo to best suite my requirements.
  11. So I ran into this problem just after doing a full backup on the old version. Yay for changing a cache drive from 128gb ssd to 512gb ssd. I restored the DB thinking I had broke the DB in the cache swap however the issue still occurred. So you are correct in thinking this would not fix it. I tried to update the docker manually and it would not work. Only disabling the TLS and enabling it fixed it with the old DB usage. Updating the docker manually skipped over the db due to the previous docker upgrade. This is as far as I got.