Jump to content

NoobSpy

Members
  • Content Count

    36
  • Joined

  • Last visited

Community Reputation

2 Neutral

About NoobSpy

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Hi, I have had this problem as well and it started here and I managed to fix it temporarily it seems. Four days ago I woke up to my server switching on and off trying to get a parity check going. Up until now I am not sure what had happened during the parity check with the Kingston 1TB nvme but it was so severe that my system would switch off and back on even with a rescue disk. I was convinced that the power supply was broken, even though I checked it with a PSU meter. To be safe I ordered a new one. I am hoping I can still cancel it. After a memtest, HDD test, I noticed the problems with the reboot would start when the nvme was inserted in the system. Somehow I managed to clone the contents of the Kingston to a different M.2 I had laying around. I formatted the Kingston and cloned the information back onto it. After putting it back into the server I could mount it with Unassigned Devices but UNRAID would not accept it. ‘unmountable -Unsupported partition layout' After searching the forum I stumbled onto this great post and found the format button all the way down on the MAIN page of the UNRAID GUI. The correct way to upgrade a cache drive is to format it with the format button on the MAIN page and rsync the files back from a backup. Cloning will just not work. Propositions to fix some problematic things: I would urgently ask for the feature that if the system has detected 3 concessive attempts to do a parity check but could not be completed. That UNRAID starts with the array switched off and a error message of some sorts. A more user friendly way to let people know how to upgrade a cache drive? I know and understand why the format button was placed there because it can format all unmountable -Unsupported partition layouts. But for the sake of someone sanity is it possible to have the format button inside the same row for all applicable cases just like Unassigned Devices has it? Best, Noobspy
  2. It was a figure of speech. I dont think 10 years on UnRaid will even be relevant. You cant keep supporting people who use ancient equipment without growing stagnant and stale. I would support a GoFundme and strech goals just to get some often requested things rolling.
  3. Wow this was asked in 2017 Now we are 3 years later ... I think 10 years later we still be debating something basic like this.
  4. Okay - The logic behind this I don't understand. If the share is set to 'only' why have files on the array? I would think if you have a use case place the file(s) in a share with flag set to 'yes or prefer' instead. I appreciate your explanation tho.
  5. Hi, Is it possible to upgrade mover so that files that should not be on the cache pool(s) or files that should not be on the array be moved automatically to the respective position. Fix common problems can identity that files are in the wrong positions. Is it somehow possible to incorporate that code into mover so this can be done automatically. This means we do not have to fire up krusader to do this manually. Best NoobSpy
  6. Thank you - Thank you - Thank you. I want to kiss you even if you dont want to.😙 I woke up sick today fearing I lost the client. The restore option worked and I Got my files back. I have no idea what went on. But I know this will not ever happen again. I want that share synced in real time. Not sure how but will find a way. Again thank you so much I feel a lot better now. NoobSpy
  7. Hi Guys, I hope someone can help me fix this problem that is stressing me out here. I made a huge mistake on my production server which hold my graphic design files. Yesterday I tried to expand my cache drive storage space by adding and nvme 1TB drive to to the cache pool. After I noticed this would not give the result I wanted because it became a mirror. I stopped the array and removed the nvme from the pool. I formatted the nvme and added it to a separate pool and started the array. Now I noticed that my original cache drive could not be read by Unraid and Unraid was spitting out errors it could not find the cache drive. I lost one good days of work from this cache because my backup run at night. No I absolutely did not format the original cache by mistake. Come today I have check the the cache drive with: sudo btrfs check /dev/sdc1 Result: cache and super generation don't match, space cache will be invalidated. There is still data on the disk looking at the bytes being used. sudo btrfs check --repair /dev/sdc1 Result: Unable to find blocks group 0 Unable to find blocks group 0 Unable to find blocks group 0 Help -- I NEED this drive mounted. Even willing to accept some dataloss in other area's How can I still mount sdc1 with blocks group 0 missing? Thanks in advance for any help on this. NoobSpy
  8. Thank you so much for your quick reply guys. Much appreciated. I am going to copy this build. But try to find a cheap LSI card. Use a better cooler.
  9. Hi, I am seeking to upgrade all hardware except drives (motherboard, memory, cpu etc.). I do not want to lose all my data. My question is can I build my new server swap in the drives, plugin the USB and get it up and running? TIA for you answers.
  10. Hi Guys - I dont get why I get permission denied when trying to create a .rar file on my cache drive? Could someone help me out and tell me what Im doing wrong ? Cheers!
  11. I have the same problem with two GPUs and found this on the net. When the VM shuts down, all devices used by the guest are deinitialized by its OS in preparation for shutdown. In this state, those devices are no longer functionnal and must then be power-cycled before they can resume normal operation. Linux can handle this power-cycling on its own, but when a device has no known reset methods, it remains in this disabled state and becomes unavailable. Since Libvirt and Qemu both expect all host PCI devices to be ready to reattach to the host before completely stopping the VM, when encountering a device that won’t reset, they will hang in a “Shutting down” state where they will not be able to be restarted until the host system has been rebooted. It is therefore reccomanded to only pass through PCI devices which the kernel is able to reset, as evidenced by the presence of a reset file in the PCI device sysfs node, such as /sys/bus/pci/devices/0000:00:1a.0/reset. This is something that has been a bug for a long time but isnt fixed. Maybe 6.6 will fix is when they upgrade Libvirt and Qemu.
  12. running on 6.5.1: Can someone please help me and point me in the direction I need to look at? I cant figure out what is causing this behavior after a VM shutdown. Why does the VM only work once after a sever reboot: May 1 12:39:44 Tower kernel: DMAR: [DMA Read] Request device [03:00.0] fault addr f400153000 [fault reason 06] PTE Read access is not set May 1 12:39:44 Tower kernel: DMAR: [DMA Read] Request device [03:00.0] fault addr f400154000 [fault reason 06] PTE Read access is not set May 1 12:39:44 Tower kernel: DMAR: [DMA Read] Request device [03:00.0] fault addr f400154000 [fault reason 06] PTE Read access is not set May 1 12:39:44 Tower kernel: DMAR: [DMA Read] Request device [03:00.0] fault addr f400154000 [fault reason 06] PTE Read access is not set May 1 12:39:44 Tower kernel: DMAR: DRHD: handling fault status reg 300 May 1 12:39:44 Tower kernel: usb 3-3: reset full-speed USB device number 2 using xhci_hcd May 1 12:39:45 Tower kernel: usb 3-3: reset full-speed USB device number 2 using xhci_hcd May 1 12:39:45 Tower kernel: usb 3-3: reset full-speed USB device number 2 using xhci_hcd May 1 12:39:45 Tower kernel: usb 3-3: reset full-speed USB device number 2 using xhci_hcd May 1 12:39:45 Tower kernel: usb 3-11: reset full-speed USB device number 6 using xhci_hcd May 1 12:39:46 Tower kernel: usb 3-11: reset full-speed USB device number 6 using xhci_hcd May 1 12:39:46 Tower kernel: usb 3-11: reset full-speed USB device number 6 using xhci_hcd May 1 12:39:46 Tower kernel: usb 3-11: reset full-speed USB device number 6 using xhci_hcd May 1 12:39:48 Tower dnsmasq-dhcp[22930]: DHCPDISCOVER(virbr0) 192.168.122.15 52:54:00:7a:46:4c May 1 12:39:48 Tower dnsmasq-dhcp[22930]: DHCPOFFER(virbr0) 192.168.122.15 52:54:00:7a:46:4c May 1 12:39:48 Tower dnsmasq-dhcp[22930]: DHCPREQUEST(virbr0) 192.168.122.15 52:54:00:7a:46:4c May 1 12:39:48 Tower dnsmasq-dhcp[22930]: DHCPACK(virbr0) 192.168.122.15 52:54:00:7a:46:4c Somfy May 1 12:40:12 Tower avahi-daemon[10408]: Interface vnet0.IPv6 no longer relevant for mDNS. May 1 12:40:12 Tower avahi-daemon[10408]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe7a:464c. May 1 12:40:12 Tower kernel: virbr0: port 2(vnet0) entered disabled state May 1 12:40:12 Tower kernel: device vnet0 left promiscuous mode May 1 12:40:12 Tower kernel: virbr0: port 2(vnet0) entered disabled state May 1 12:40:12 Tower avahi-daemon[10408]: Withdrawing address record for fe80::fc54:ff:fe7a:464c on vnet0. May 1 12:40:12 Tower kernel: logitech-djreceiver 0003:046D:C52B.0007: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2 May 1 12:40:12 Tower kernel: input: Logitech K830 as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0007/0003:046D:404C.0008/input/input4 May 1 12:40:12 Tower kernel: logitech-hidpp-device 0003:046D:404C.0008: input,hidraw1: USB HID v1.11 Keyboard [Logitech K830] on usb-0000:00:14.0-3:1 May 1 12:40:12 Tower kernel: pcieport 0000:00:02.0: AER: Uncorrected (Fatal) error received: id=0010 May 1 12:40:12 Tower kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, id=0010(Receiver ID) May 1 12:40:12 Tower kernel: pcieport 0000:00:02.0: device [8086:6f04] error status/mask=00000020/00000000 May 1 12:40:12 Tower kernel: pcieport 0000:00:02.0: [ 5] Surprise Down Error (First) May 1 12:40:12 Tower kernel: pcieport 0000:00:02.0: broadcast error_detected message May 1 12:40:14 Tower kernel: pcieport 0000:00:02.0: Root Port link has been reset May 1 12:40:14 Tower kernel: pcieport 0000:00:02.0: broadcast mmio_enabled message May 1 12:40:14 Tower kernel: pcieport 0000:00:02.0: broadcast resume message May 1 12:40:14 Tower kernel: pcieport 0000:00:02.0: AER: Device recovery successful May 1 12:40:14 Tower kernel: vfio-pci 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none May 1 12:40:14 Tower kernel: vfio-pci 0000:03:00.0: Refused to change power state, currently in D3 May 1 12:40:14 Tower kernel: vfio-pci 0000:03:00.1: Refused to change power state, currently in D3
  13. Hi all, I have a system with two GPUs a RX550 and a GT730 I have a Linux VM with a RX550 passed through. This VM works only one time after a full unraid reboot. As soon as I shut down the VM and and try to restart it I get the: internal error: Unknown PCI header type '127' edit: Just found this in the VM log: Apr 21 03:17:51 Tower kernel: DMAR: [DMA Read] Request device [03:00.0] fault addr f4001d6000 [fault reason 06] PTE Read access is not set I figured out it has to do with the video card(s): When i tried to pass through the GT which is in slot two the VM doesnt boot and doesnt spit out the error. I physically switched the GPUs per slot and again after reboot it works as soon i shut down the VM and restart I get the PCI error. I am not knowledgeable enough to figure this out. Could someone please help? Thank you! ================================== I have included my IOMMU groups below: IOMMU group 0: [8086:6f81] ff:0b.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01) [8086:6f36] ff:0b.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01) [8086:6f37] ff:0b.2 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 (rev 01) [8086:6f76] ff:0b.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link Debug (rev 01) IOMMU group 1: [8086:6fe0] ff:0c.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6fe1] ff:0c.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6fe2] ff:0c.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6fe3] ff:0c.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6fe4] ff:0c.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6fe5] ff:0c.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6fe6] ff:0c.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6fe7] ff:0c.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) IOMMU group 2: [8086:6ff8] ff:0f.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6ff9] ff:0f.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6ffc] ff:0f.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6ffd] ff:0f.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) [8086:6ffe] ff:0f.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent (rev 01) IOMMU group 3: [8086:6f1d] ff:10.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent (rev 01) [8086:6f34] ff:10.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent (rev 01) [8086:6f1e] ff:10.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01) [8086:6f7d] ff:10.6 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01) [8086:6f1f] ff:10.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox (rev 01) IOMMU group 4: [8086:6fa0] ff:12.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 (rev 01) [8086:6f30] ff:12.1 Performance counters: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 (rev 01) IOMMU group 5: [8086:6fa8] ff:13.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS (rev 01) [8086:6f71] ff:13.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS (rev 01) [8086:6faa] ff:13.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01) [8086:6fab] ff:13.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01) [8086:6fac] ff:13.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01) [8086:6fad] ff:13.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder (rev 01) [8086:6fae] ff:13.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Broadcast (rev 01) [8086:6faf] ff:13.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast (rev 01) IOMMU group 6: [8086:6fb0] ff:14.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control (rev 01) [8086:6fb1] ff:14.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control (rev 01) [8086:6fb2] ff:14.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error (rev 01) [8086:6fb3] ff:14.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error (rev 01) [8086:6fbc] ff:14.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01) [8086:6fbd] ff:14.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01) [8086:6fbe] ff:14.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01) [8086:6fbf] ff:14.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface (rev 01) IOMMU group 7: [8086:6fb4] ff:15.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Thermal Control (rev 01) [8086:6fb5] ff:15.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Thermal Control (rev 01) [8086:6fb6] ff:15.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Error (rev 01) [8086:6fb7] ff:15.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Error (rev 01) IOMMU group 8: [8086:6f68] ff:16.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Target Address/Thermal/RAS (rev 01) [8086:6f6e] ff:16.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Broadcast (rev 01) [8086:6f6f] ff:16.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast (rev 01) IOMMU group 9: [8086:6fd0] ff:17.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 0 Thermal Control (rev 01) [8086:6fb8] ff:17.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01) [8086:6fb9] ff:17.5 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01) [8086:6fba] ff:17.6 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01) [8086:6fbb] ff:17.7 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface (rev 01) IOMMU group 10: [8086:6f98] ff:1e.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) [8086:6f99] ff:1e.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) [8086:6f9a] ff:1e.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) [8086:6fc0] ff:1e.3 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) [8086:6f9c] ff:1e.4 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) IOMMU group 11: [8086:6f88] ff:1f.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) [8086:6f8a] ff:1f.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit (rev 01) IOMMU group 12: [8086:6f00] 00:00.0 Host bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 (rev 01) IOMMU group 13: [8086:6f02] 00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01) IOMMU group 14: [8086:6f03] 00:01.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01) IOMMU group 15: [8086:6f04] 00:02.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 01) IOMMU group 16: [8086:6f08] 00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 3 (rev 01) IOMMU group 17: [8086:6f28] 00:05.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management (rev 01) [8086:6f29] 00:05.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug (rev 01) [8086:6f2a] 00:05.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors (rev 01) [8086:6f2c] 00:05.4 PIC: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC (rev 01) IOMMU group 18: [8086:8d7c] 00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR (rev 05) [8086:8d62] 00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05) IOMMU group 19: [8086:8d31] 00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05) IOMMU group 20: [8086:8d3a] 00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #1 (rev 05) IOMMU group 21: [8086:15a1] 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V (rev 05) IOMMU group 22: [8086:8d2d] 00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 (rev 05) IOMMU group 23: [8086:8d20] 00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio Controller (rev 05) IOMMU group 24: [8086:8d10] 00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #1 (rev d5) IOMMU group 25: [8086:8d14] 00:1c.2 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #3 (rev d5) IOMMU group 26: [8086:8d16] 00:1c.3 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #4 (rev d5) IOMMU group 27: [8086:8d18] 00:1c.4 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #5 (rev d5) IOMMU group 28: [8086:8d26] 00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 (rev 05) IOMMU group 29: [8086:8d47] 00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller (rev 05) [8086:8d02] 00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05) [8086:8d22] 00:1f.3 SMBus: Intel Corporation C610/X99 series chipset SMBus Controller (rev 05) IOMMU group 30: [1002:699f] 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon RX 550] (rev ff) [1002:aae0] 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aae0 (rev ff) IOMMU group 31: [10de:1287] 04:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730] (rev a1) [10de:0e0f] 04:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) IOMMU group 32: [8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 33: [8086:08b3] 07:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83) IOMMU group 34: [1b21:1242] 08:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller