Pcie Sata position cards vs. network card - strange issues

[Sep]

I have small server with several disks. Eventually I run out of SATA ports on my motherboard. So I bought Sata extension cards for Pcie. I am amble to run 2 cards (2 SATA each). However in the moment I do add 3rd, my network card (on the MB) stops working.

1. Network card works till the moment of boot into Proxmox (even blinking in the moment of the bootloarder)
2. It is detectable in BIOS

So I guess it is Proxmox VE issue.

My HW components are these

ASUS PRIME Z690-P WIFI D4 MBoard
AXAGON PCES-SA2N, 2x internal SATA 6G port, PCIe controller
Bunch of SATA HDDS and SSDs
2 Nvme mirrored drives on the MB

I updated Kernel to 5.19 and I am running the latest versions of everything.
BIOS in default conf.

Any tips?

 

[shanreich]

Can you post your dmesg output after booting?

 

[Sep]

here

 

[Sep]

but this is the configuration only with the 2 PCIE slots filled (ie network card is working)

 

[shanreich]

I was already wondering, can you post the output of when you have plugged in all 3 cards, where the NIC stops working? You also seem to be missing a driver for the Wi-Fi adapter on the MoBo but I assume you don't really mind.

 

[Sep]

i do not have the way to extract the log from the computer in the moment 3 cards are there :/

 

[shanreich]

Is it because of no network connectivity? Because you can access the dmesg output from previous boots via journalctl [1]

[1] https://unix.stackexchange.com/questions/181067/how-to-read-dmesg-from-previous-session-dmesg-0

 

[Sep]

oh ... did not know. Hmm has to study and try.

 

[Sep]

oh it is huge ... how can I select some last 24 hours?

 

[shanreich]

With journalctl you should be able to list all the previous boots via journalctl --list-boot :

 -3 2eaf619886f1421bac36c4ba6479fa99 Thu 2022-10-06 09:20:06 CEST—Thu 2022-10-06 17:56:28 CEST
 -2 bc0fdb2d17884c5aa1fb8324bb351c0a Fri 2022-10-07 09:13:36 CEST—Fri 2022-10-07 16:27:19 CEST
 -1 098afba1b4304140b071b162ef411225 Tue 2022-10-11 09:23:16 CEST—Tue 2022-10-11 18:08:27 CEST

Then in this list you pick the specific boot where you know the problem occurred and then dump its dmesg like so (in my instance I chose -3 for example):

journalctl -k -b -3

 

[Sep]

got it ... will alsoi reduce priority of messages

will do the exact config changes

 

[Deepen Dhulla]

Do check your SMPS power/Watts, you might be needing more power to handle extra load.

 

[Sep]

Well I have 750W source on it ...

 

[Sep]

here is the configuration ... one of the connected drive is failed (the one I need to run replace in mirror

 

[shanreich]

Hm this log seems a bit short, have you filtered by priority? Would be good to see all messages, as this log seems to be missing the interesting parts

 

[shanreich]

remove the -p 4 and dump it into a text file like: journalctl [...] > output.txt

 

[Sep]

full

 

[shanreich]

Are you really sure this is the full one? Did you export the logs via redirecting? ( > output.txt). To me it looks like you are pasting from terminal, and there is still some stuff missing...

 

[Sep]

ok i did > output.txt .... where I can locate it

 

[shanreich]

ok i did > output.txt .... where I can locate it

Depends on the current working directory of your terminal, it should be in the folder where the terminal currently is opened (you can find it via pwd). You should be able to copy it to your local machine via scp .