On the 9300-16i, I have been seeing the connected drives under a ‘physical drives’ menu that appears if drives are connected… on the 9305 I did not…
Would you expect the drives to spin up on boot?
I’ll try booting into proxmox and running lshw on both cards tomorrow. Thanks for the route to test!
Ok. Did a bunch more testing here tonight.
I have 2x 8tb SAS drives that have worked for several weeks now. Those show up in bios reliably regardless of which connector I use. So I think the HBA is working and the cables are good.
Of the 10x 10tb drives, 1 drive shows up reliably. It also seems to work on any connector I use. But it is the only drive the works.
Here is 8 of the 10 installed and only one showing in BIOS. I think the other 7 are not even spinning up.
An additional weird thing is that at least 1 other of the 10 drives did show up the first time I plugged it in from inside the xpenology VM. I did 'hot swap' that one in, but it then passed a SMART test. But since it passing the test and me pulling it, it hasn't worked again. I'm also not positive which drive it is because originally I wasn't expecting things to behave so weirdly, so I didn't start taking notes...
As another test, I got a hold of a 9305-16i to see if the drives would read on that. And while that card would show up in BIOS, none of the drives -- including the 8th that have always worked -- showed up or spun up at all! I wonder if that card is not compatible with my mobo?
Is it possible other BIOS settings are interfering?
Ok. Did a bunch more testing here tonight.
I have 2x 8tb SAS drives that have worked for several weeks now. Those show up in bios reliably regardless of which connector I use. So I think the HBA is working and the cables are good.
Of the 10x 10tb drives, 1 drive shows up reliably. It also seems to work on any connector I use. But it is the only drive the works.
Here is 8 of the 10 installed and only one showing in BIOS. I think the other 7 are not even spinning up.
An additional weird thing is that at least 1 other of the 10 drives did show up the first time I plugged it in from inside the xpenology VM. I did 'hot swap' that one in, but it then passed a SMART test. But since it passing the test and me pulling it, it hasn't worked again. I'm also not positive which drive it is because originally I wasn't expecting things to behave so weirdly, so I didn't start taking notes...
As another test, I got a hold of a 9305-16i to see if the drives would read on that. And while that card would show up in BIOS, none of the drives -- including the 8th that have always worked -- showed up or spun up at all! I wonder if that card is not compatible with my mobo?
Is it possible other BIOS settings are interfering?
Ah. Will trying to hit swap damage the drives? Or just won’t work?
Drives are hot-swappable with this HBA, right?
Will give this a go! thanks!
One of the drives for reference:
Ok. Fair enough.
I'm still working on the first 2, but on the 3rd, yes there are a couple drives that are up and working on the card. 2x 8tb drives (also HGST).
They are SAS drives, not sata. Mobo does have SATA, but not SAS.
I do!
Thanks for the link!
Yah. Trying to make an Uber server.
Bunch of drives for a nas vm
3060 for a bit of a gaming pc cam for things like moonlight.
Rx590 is for a hackintosh vm to make local backups of my iCloud stuff.
And a unix vm to manage docker containers.
Also plan to put Plex in a LXC (I think that’s the term) on Proxmox so it can hardware decode using the igpu.
Me again. The guy with the NIC problem from before.
I installed the Rx590 and it shows up in lspci as an RTX 2070. I was hoping it was just Proxmox not having drivers or something, but when I pass it into the Hackintosh it's meant for, it shows as NVIDIA there too:
Now I did get the Rx590 off eBay, but I'm it was listed as and looks like this: https://www.powercolor.com/product?id=1551768831
So I think it is actually a Rx590.
This is lspci. 01:00.0 is a RTX 3060. 03:00.0 is the Rx590.
00:00.0 Host bridge: Intel Corporation Device a740 (rev 01)
00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] (rev 04)
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:16.0 Communication controller: Intel Corporation Alder Lake-S PCH HECI Controller #1 (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 7ac4 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #2 (rev 11)
00:1c.4 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #5 (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 Z690 Chipset LPC/eSPI Controller (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)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (17) I219-V (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation GA106 [GeForce RTX 3060] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GA106 High Definition Audio Controller (rev a1)
02:00.0 Non-Volatile memory controller: Sandisk Corp Western Digital WD Black SN850X NVMe SSD (rev 01)
03:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2070] (rev a1)
03:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1)
03:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1)
03:00.3 Serial bus controller: NVIDIA Corporation TU106 USB Type-C UCSI Controller (rev a1)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
05:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device 5415 (rev 01)
06:00.0 PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA (rev ca)
07:00.0 PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA (rev ca)
Like the title says. I installed a GPU, everything posts and boots fine. The lights on the Ethernet port are lit up and will stay lit up indefinitely (I assume) if I leave it at the kernel select screen.
But as soon as I load a kernel, the lights go dark. It also is not shown as an active client on my gateway, so it’s not working at all.
I’ve tried lots of commands I’ve found to force it up. It looks to me like the NIC assigned to vmbr0 is correct. Etc. I just can’t get it to work.
If I remove the GPU, it immediately works again. NIC stays up after the kernel loads and I can access the web UI as normal.
rooteprox. *
root@prox:*# ip a
root@prox: *# cat /etc/network/interfaces
auto lo
iface lo inet loopback
iface enp0s31f6 inet manual
auto vmbro
iface vmbro inet static
address 192.168.1.3/24
gateway 192.168.1.1
bridge-ports enp0s31f6
bridge-stp off bridge-fd o
iface enps0 inet manual
source /etc/network/interfaces.d/*
root@prox: ~# service network restart
Failed to restart network.service: Unit network.service not found.
Ok. I can’t get past the inquisitor deathmatch. JMK/CAT is my usual big gun when needed.. but they also got smoked.
Any idea what squads do send in? I’m a bit over 8m go. Have JMK, JML, and Jabba (and potentially a thing for ‘J’s?)
I’m not a lawyer, but if I wasn’t planning to do anything related to the other ‘dedsec’, I wouldn’t even consider what the owner of that dedsec would think.
Businesses have the same name ALL THE TIME.
Unless you’re trying to piggyback on or undermine that other dedsec, I, the non-lawyer, can’t imagine how they’d have any standing to raise a concern.
Whatever you’re doing must have led you to the dedsec name (I assume it’s a website for dog-eat-dog security), there’s just no way in my (non-lawyer) mind that EA or Ubisoft has any right to stop you from saving dogs from being eaten.
I (the non-lawyer) would 100% not pay a lawyer for their opinion on this.