TheTechnoPilot

So 7.1.4 absolutely trashed my server, with it both not respecting the original Tips and Tweeks PBO disable I had on it causing it to run far hotter which required I instead needed to hard disable in the bios (though it still ran 20C hotter on average oddly at 75C versus 55C), but also entirely unable to get through a parity check without crashing 15% in I discovered when I came home to it shutdown and then repeat the instance each time I tried. The first time it even caused a communication error with my parity drive, causing it to record a single CRC error during the crash. Rolled back to the known good 7.0.0 and have since been able to completely rebuild parity with zero issue (ran it as a write correction check to learn more about what happened and logged 5.74 million errors). This ran on 7.1.4, upgraded directly from 7.0.0 for about 20 days, before my monthly parity check brought the full issues to light and brought it down. It even caused issues with my Windows VM (on a bare-metal passed SATA SSD), which was running at the time and kept failing to start after the crash in 7.1.4. After uninstalling the NVidia plug-in completely post rollback and redownloading the driver, plus a few boot attempts and a Windows repair pass it is finally back up on my 7.0.0 rollback, and I am writing this from that OS. Everything is back to normal including the idle temps except my UnRaid Connect is not willing to register (tried a full uninstall and reinstall after it wasn't connecting, and now just won't register). MOBO - ASUS ROG Crosshair VIII Impact (BIOS 4402) CPU - AMD 5950X Power Supply - Corsair SFX 750W w/ Cyberpower 1500VA UPS GPU - 3080TI Founders Drives - Rocket 4.0 2TB Cache, EXO 20TB (ST20000NM007D-3DJ103) Parity, EXO 18TB (ST18000NM000J-2TV103) Array, EXO 16TB (ST16000NM001G-2KK103) Array, EXO 16TB (ST16000NM001G-2KK103) Array, IronWolf 16TB (ST16000NE000-2WX103) Array, 850 EVO 1TB SATA Windows Bare-Metal Sadly, no, I don't have the pre-rollback diagnostics to post. Getting the server back up and working for my business was more important, especially as I was working on a brand new documentary at the time.

Hi all, So my UnRaid server has finally been running exactly as I desire it too over the last couple months, with my final upgrade in the past week to the GPU it will have for the foreseeable future. Now I’m down to dealing with some house keeping items and one of those is my RGB setup (because we all know RGB increases array read and write speeds! 😝). I’m running an ASUS X570 Impact DTX board with on-board ASUS Aura controlling two RGB fans and an EK waterblock plus all the motherboard lighting (so I can’t just use another USB only controller). I’ve been trying to pass this controller through to my primary Windows 10 VM so that the Aura software can control my lighting, but despite getting the Aura controller to show up in my electable USB device list in Windows using device ID pass-through of the single device with the name from the PCI-E device list (note that even having forced breakout of PCI-E groups for other purposes, it still shares it’s group with some other devices so I can’t pass through the whole PCI-E group) the ASUS software is claiming to not see the controller when I attempt to start it. I would of course love to control this just natively in UnRaid so I don’t need to start my VM to have my lighting the way I want, but I would love to even just have that work at this point. Does anyone have any ideas of how I can either handle this natively within UnRaid, or get it to properly pass through to control in Windows? Thanks in advance for any tips!

Didn't really think it would fix this issue, just a worthwhile upgrade for me while I'm going through all this to improve overall compatibility across the board for my setup was my thinking.

I've not yet, but I'm having general VM issues I need to sort through first before diving deeper into working on getting it working in MacOS. In trying to find solutions to this weird issue I stumbled upon the reset fix issue and seeing your work also seems to deal with board audio pass-through issues along with Ryzen sensors and I haven't bothered upgrading from 6.7.2 yet, this seemed like a good thing to look at and reason to upgrade. Right now my MacOS VM is still running High Sierra and want to get that going first ideally on the new card, but need to fix this basic pass-through error first before even going there.

Hey there bud, bit of a noobie here when it comes to this level. Running a 3900X on an ROG B450-I board with a Strix Vega 64 and still back on 6.7.2. Looks like upgrading to your build is my best bet now having just moved to the Vega 64 and discovering it is not a smooth sailing as I hoped (MacOS VMs so needed to keep to the Radeon camp). Sorry for asking such a basic question, but perhaps it could also help others, what is my best bet for upgrading to your specific build with these fixes as I've not done such an upgrade before.