Vairfoley

I had port mirroring enabled on the switch port my server was connected to... huge facepalm. No more messages in the log and my VMs seem to have network connection again! Thanks!

I actually don't really need that override patch anymore. Any way I can turn that off without losing networking? I turned off bonding and now the error reads: kernel: br0: received packet on eth0 with own address as source address csssrv-diagnostics-20220130-1840.zip

Sure! I really appreciate the help. csssrv-diagnostics-20220129-1818.zip

Just as an update/bump: - Booting into safe mode leaves me without network access or my array - This problem persists before I start the array on normal mode

I'm getting this message CONSTANTLY on my unRAID 6.9.2 server. From what I've researched so far, I feel like this should be taking my whole network down, but it's not. All of my Docker containers along with the WebGUI are working perfectly fine on the network, but my VMs are not (maybe related?). Any help would be appreciated, thanks. csssrv-diagnostics-20220121-0709.zip

Switching USB ports on the same controller won't change the IOMMU group. I'm thinking you're probably going to have to use the ACS Override patch to get that controller into its own group. Once it's in its own group, you should be able to select the devices individually in the VM settings. This video should be able to help you out:

The message you're getting at POST isn't telling us which drive it's detecting a SMART error from. But the other notification says your Crucial MX300 (CT525MX300SSD1_174819E38A5D) SSD is showing an error. Usually, USB Flash Drives/Disks don't have SMART capabilities so it definitely looks like your SSD is failing and not the flash drive. It's not unheard of for an SSD to die in 3 years, especially if you're using it very heavily. The only way to know for sure would be testing to see if you still get the error with the SSD removed or if you can test the SSD with another computer.

I've been messing around with different USB configurations for my rig. I'm trying to pass-through some of my onboard USB controllers to a Windows 10 VM, but the controller I want to use (the one with the front panel USB headers) has the only 2.0 ports available. Does plugging into a 3.0 port (the ones I'd plug into would actually be 3.1 Gen 2 technically) with a 2.0 device get rid of the incompatibility issues? Is it 3.0 ports or 3.0 devices that cause issues? I also noticed that even though I have my 2.0 flash drive plugged into the 2.0 port, it still shows up under a USB 3.1 XHCI controller. Thanks in advance for any info. The parts I'm using are here: https://pcpartpicker.com/user/Vairfoley/saved/DsJ9rH