geiserx

I checked in the IPMI and the PCIe doesn't even appear it seems. The first is an HBA card, and the other two I suspect they are both NVMe's. What's up with this card? Is it broken perhaps?

I recently bought this https://amzn.eu/d/3DFmZAM But listing with `lspci -v` and grepping for anything like ASM1061, StarTech, or Marvell, doesn't produce any fruitful result. So I suspect it's not even recognized. In any case, you can check the output of `lspci`: 00:00.0 Host bridge: Intel Corporation Device 4640 (rev 02) 00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c) 00:02.1 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c) 00:02.2 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01) 00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller 00:14.0 USB controller: Intel Corporation Alder Lake-S PCH USB 3.2 Gen 2x2 XHCI Controller (rev 11) 00:14.2 RAM memory: Intel Corporation Alder Lake-S PCH Shared SRAM (rev 11) 00:15.0 Serial bus controller: Intel Corporation Alder Lake-S PCH Serial IO I2C Controller #0 (rev 11) 00:15.1 Serial bus controller: Intel Corporation Alder Lake-S PCH Serial IO I2C Controller #1 (rev 11) 00:16.0 Communication controller: Intel Corporation Alder Lake-S PCH HECI Controller #1 (rev 11) 00:16.3 Serial controller: Intel Corporation Device 7aeb (rev 11) 00:17.0 SATA controller: Intel Corporation Alder Lake-S PCH SATA Controller [AHCI Mode] (rev 11) 00:1a.0 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #25 (rev 11) 00:1b.0 PCI bridge: Intel Corporation Device 7ac0 (rev 11) 00:1b.4 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #21 (rev 11) 00:1c.0 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #1 (rev 11) 00:1c.1 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #2 (rev 11) 00:1c.2 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #3 (rev 11) 00:1c.3 PCI bridge: Intel Corporation Device 7abb (rev 11) 00:1d.0 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #9 (rev 11) 00:1f.0 ISA bridge: Intel Corporation Device 7a88 (rev 11) 00:1f.3 Audio device: Intel Corporation Alder Lake-S HD Audio Controller (rev 11) 00:1f.4 SMBus: Intel Corporation Alder Lake-S PCH SMBus Controller (rev 11) 00:1f.5 Serial bus controller: Intel Corporation Alder Lake-S PCH SPI Controller (rev 11) 01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) 02:00.0 Non-Volatile memory controller: Micron/Crucial Technology T500 NVMe PCIe SSD (rev 01) 05:00.0 Non-Volatile memory controller: Micron/Crucial Technology T500 NVMe PCIe SSD (rev 01) 06:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-LM (rev 06) 07:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-LM (rev 06) 09:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 06) 0a:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 52) I tried rebooting and had to delete al secure boot keys in order for it to boot up again, because I was directly getting into BIOS without the ability to boot up from USB in my Asus PRO WS680M. I really believe this is related. I do have two eSATA cables connected to a pair of FANTEC QB-35US3-6G turned on, but the disks are not recognized at all, surely because of what I was mentioning earlier. Thank you for your help

This is how a typical syslog looks like everytime: Jul 1 13:26:43 WatchTower kernel: device veth2c79359 entered promiscuous mode Jul 1 13:26:43 WatchTower kernel: eth0: renamed from vethe879fce Jul 1 13:26:44 WatchTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2c79359: link becomes ready Jul 1 13:26:44 WatchTower kernel: br-efe125878f68: port 2(veth2c79359) entered blocking state Jul 1 13:26:44 WatchTower kernel: br-efe125878f68: port 2(veth2c79359) entered forwarding state Jul 1 13:26:45 WatchTower kernel: br-efe125878f68: port 2(veth2c79359) entered disabled state Jul 1 13:26:45 WatchTower kernel: vethe879fce: renamed from eth0 Jul 1 13:26:45 WatchTower kernel: br-efe125878f68: port 2(veth2c79359) entered disabled state Jul 1 13:26:45 WatchTower kernel: device veth2c79359 left promiscuous mode Jul 1 13:26:45 WatchTower kernel: br-efe125878f68: port 2(veth2c79359) entered disabled state Jul 1 13:27:45 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered blocking state Jul 1 13:27:45 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered disabled state Jul 1 13:27:45 WatchTower kernel: device veth0ed10ae entered promiscuous mode Jul 1 13:27:45 WatchTower kernel: eth0: renamed from veth95735b7 Jul 1 13:27:45 WatchTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0ed10ae: link becomes ready Jul 1 13:27:45 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered blocking state Jul 1 13:27:45 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered forwarding state Jul 1 13:27:47 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered disabled state Jul 1 13:27:47 WatchTower kernel: veth95735b7: renamed from eth0 Jul 1 13:27:47 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered disabled state Jul 1 13:27:47 WatchTower kernel: device veth0ed10ae left promiscuous mode Jul 1 13:27:47 WatchTower kernel: br-efe125878f68: port 2(veth0ed10ae) entered disabled state Jul 1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered blocking state Jul 1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered disabled state Jul 1 13:28:47 WatchTower kernel: device vethf9ef870 entered promiscuous mode Jul 1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered blocking state Jul 1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered forwarding state Jul 1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered disabled state Jul 1 13:28:47 WatchTower kernel: eth0: renamed from vethf1f9499 Jul 1 13:28:47 WatchTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf9ef870: link becomes ready Jul 1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered blocking state Jul 1 13:28:47 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered forwarding state Jul 1 13:28:48 WatchTower kernel: vethf1f9499: renamed from eth0 Jul 1 13:28:48 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered disabled state Jul 1 13:28:48 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered disabled state Jul 1 13:28:48 WatchTower kernel: device vethf9ef870 left promiscuous mode Jul 1 13:28:48 WatchTower kernel: br-efe125878f68: port 2(vethf9ef870) entered disabled state Jul 1 13:29:48 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered blocking state Jul 1 13:29:48 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered disabled state Jul 1 13:29:48 WatchTower kernel: device veth7372316 entered promiscuous mode Jul 1 13:29:48 WatchTower kernel: eth0: renamed from veth1f254a4 Jul 1 13:29:48 WatchTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7372316: link becomes ready Jul 1 13:29:48 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered blocking state Jul 1 13:29:48 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered forwarding state Jul 1 13:29:50 WatchTower kernel: veth1f254a4: renamed from eth0 Jul 1 13:29:50 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered disabled state Jul 1 13:29:50 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered disabled state Jul 1 13:29:50 WatchTower kernel: device veth7372316 left promiscuous mode Jul 1 13:29:50 WatchTower kernel: br-efe125878f68: port 2(veth7372316) entered disabled state Jul 1 13:30:50 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered blocking state Jul 1 13:30:50 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered disabled state Jul 1 13:30:50 WatchTower kernel: device veth6e4aa48 entered promiscuous mode Jul 1 13:30:50 WatchTower kernel: eth0: renamed from veth378aea0 Jul 1 13:30:50 WatchTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6e4aa48: link becomes ready Jul 1 13:30:50 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered blocking state Jul 1 13:30:50 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered forwarding state Jul 1 13:30:52 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered disabled state Jul 1 13:30:52 WatchTower kernel: veth378aea0: renamed from eth0 Jul 1 13:30:52 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered disabled state Jul 1 13:30:52 WatchTower kernel: device veth6e4aa48 left promiscuous mode Jul 1 13:30:52 WatchTower kernel: br-efe125878f68: port 2(veth6e4aa48) entered disabled state If I inspect the link, it belongs to Prometheus and all the exporters I've configured. If I turn it off, it stops. I suspect this is causing frequent kernel panics, but I can't prove it. Nevertheless, could anyone please tell me what's going on internally?

Any updates? I can't seem to make my UHD770 iGPU to work both in UnRAID and iKVM, after following your advice. It's either one or the other, that I can make use of. I own the Asus Pro WS W680M-ACE SE.