H0riz0n

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

H0riz0n's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I did notice a small increase in power consumption, temperatures no, but that's probably due to the custom loop its running on(I prefer my servers silent when not in a data center). I initially thought the issue was related to the MB and BIOS as Gigabyte had a beta BIOS for the unit up until the 10th. The memory has been tested with Memtest with no issues, and has had no issues running at the full 2666MHz with Fedora installed and Windows 10 installed, running in the same motherboard/CPU. The memory was also recently removed and reinstalled when I had to replace the failed pump in the unit.
  2. Neither are ideal, but if you had to go with one I would choose running a virtual firewall distro. For grins and giggles I implemented something like this a little while back in lab with ESXi as the hypervisor and IPfire as the virtual firewall. As some one who works in large scale cloud environments, many of today's cloud based solutions deploy virtual firewalls/appliances to handle networking, so theirs no real security issue there, as long as you follow best practices when it comes to networking. As for the complications of deploying a Linux/Unix based firewall, distros like pfSense, IPfire, Smoothwall take a lot of the complication out of it.
  3. First I would like to thank Paul for his time and effort in the current issues. Currently I'm running a R7 1800X, with the Gigabyte AX370-Gaming-5 with the latest F5 BIOS which has the AGESA 1.0.0.4 updates. Corsair Vengeance LPX 32GB 2666mhz. I was having serious stability issues until I noted the C-State settings. Since being disabled in the BIOS my system seems to be running stable, while running half a dozen docker containers and 4 VM's of varying OS's. I will note that when enabling the XMP profiles in my BIOS anything over 2400mhz causes unRAID(6.3.3) to kernel panic on boot. Curious if anyone else is seeing similar issues, especially since Ryzen benefits from faster memory.