[SOLVED] Cannot Access Web Interface PVE 8.0-2

[ramreddy]

Hello all,

I have installed Proxmox VE 8.0-2 in Supermicro X10SRL-F. Motherboard has two 1gbe NICs and also two 10Gbe NICs.
Installation succeeds without any issues, but after booting up I cannot access the GUI through the URL that is displayed in console.

I am a newbie to home lab setup and this is my first. Apologies for missing any details.
Was able to find some old forum threads and found that

"systemd-udev-settle.service" and "ifupdown2-pre.service" are not able to start correctly. Was able to follow bunch of old threads in this forum which helped me run following commands


1. Ran ip a and cat /etc/network/interfaces to see that all 4 NICs are detected but all of those show status as DOWN

2. Ran ifup vmbr0 which threw an error saying another program is already running etc.

3. Some other thread suggested to restart "ifupdown2-pre.service" but was not able to do so.

4. Checked journalctl and saw that "systemd-udev-settle.service" and "ifupdown2-pre.service" are not able to start properly.

5. Observed similar errors when proxmox is booting up. Below is screenshot


6. I see same usb device descriptor failure log messages continuously getting printed on proxmox login console

Some more details if it helps
- I have 2 SSDs as boot drives in SATA ports
- 6 HDDs connected for data in SATA ports
- Keyboard and Mouse are connected through wireless USB bluetooth
- Monitor is connected through VGA and USB to HDMI cable
- Dedicated IPMI LAN is connected directly to router (this seems to be working)
- I have checked by changing cables and ports eliminating any router related issues.

I do not have any more leads on how to make my proxmox install work :-(
Any help would be really great and appreciate a lot.

 

[ramreddy]

I see some forum threads suggesting to mask ifupdown2-pre.service might solve the problem

https://forum.proxmox.com/threads/proxmox-6-network-wont-start.56362/

I will give it a shot, but wondering if there is an easy way to find out which exact device/driver is causing udev-settle to hang. As of now, I am bit out of my depth to get to root cause/resolution.
Appreciate any help. Thanks a lot.

 

[ramreddy]

I have resolved the issue by masking "systemd-udev-settle.service" and "ifupdown2-pre.service".

Also, figured out root cause was VGA to HDMI cable that I am using to connect to monitor. https://www.amazon.com/dp/B08MF2L1ZF?psc=1&ref=ppx_yo2ov_dt_b_product_details

Who would have guessed Either way, unmasked the services and validated that all issues are gone.