New old hardware and some installation issues. Proliant 380 G7

[SecConIT]

I got my hands on two Proliant servers with SAS and a lot of disk, up to about 7TB, 146GB DDR3 RAM and each 2 x Intel Xeon at 2,6Ghz.

After trying my best to upgrade hardware firmware and bios and all I could find they are in good shape and work very well. A test installation with WSRV 2019 went with zero issues, Raid and configuration of that works fine. I am rather happy with these and I have good use for them.

Server A should run VM's. I was initially inclined to use ESXI for that, but they cut the CPU compatibility for the Xeon's on these machines. When running proxmox setup the first weird error I get is the following:



The setup keeps running after that and throws no additional errors. I wonder if it is related to: https://xcp-ng.org/forum/topic/3128/acpi-spcr-unexpected-spcr-access-width-defaulting-to-byte-size

After the setup is done and I get an IP address I am unable to connect to said IP address:



In this it might be worth mentioning that when setting up the NIC there are several to choose from, due to internal SAS NIC's:




So I am looking for an explanation as to the connectivity issue, my previous experience with proxmox is ok, but limited and I do not normally use any kind of CLI...

 

[LnxBil]

In this it might be worth mentioning that when setting up the NIC there are several to choose from, due to internal SAS NIC's:

That has nothing to do with SAS. You have an additional quad-port card in there with two chipsets. The other is the onboard card.
Best is, if you don't need the quad port card, just remove it from the machine and plug in both onboard nics.

The setup keeps running after that and throws no additional errors.

Even if it sounds weird, it's normal to see errors on Linux boot. You don't see these errors on Windows, but they are still there. It's often deviation from official specifications for stuff and such and most of the time, they're harmless. (You know that they're harmless if you don't see them more often or if everything works as expected).

 

[SecConIT]

Ok, I will review that card, I am guessing I should select one of the be2net entries from the list, there are 3 NIC ports in the rear of the chassi , one is dedicated for ILO, and all are plugged in. Will try to install again after that. I find it odd it got an IP, suggesting network connectivity.

I am aware of errors appearing in boots, but this looked a bit more serious than the usual probing and reverting...

 

[SecConIT]

Fibre channel ports available, and an additional fibre channel card was in the server, now removed. That should bring down those ports to max 2 I think... testing again later

 

[SecConIT]

Nope, from the screenie above now I have only the *BNX* ports available and I tried a different one during setup and it seems not working....

getting

This page isn’t working right now
192.168.1.222 didn’t send any data.


ERR_EMPTY_RESPONSE

 

[LnxBil]

Nope, from the screenie above now I have only the *BNX* ports available and I tried a different one during setup and it seems not working....

getting

This page isn’t working right now
192.168.1.222 didn’t send any data.


ERR_EMPTY_RESPONSE

That error occurs if you just connect with http instead of https. Please change http to https and it may just work.

 

[SecConIT]

That error occurs if you just connect with http instead of https. Please change http to https and it may just work.

I swear, I tried...have this on and off always... then suddenly it just pops in. Damn browsers... all good now it seems.

Thanks for your patience guys...