Multiple failed services after installation restart and cannot log into GUI

[dwanecl]

Hello All,

Long time VMware user but first time Proxmox user.

Installed Proxmox on VMware Workstation Pro without any issues as a lab. Installed on the same hardware that was previously running with Windows11/VMware Workstation Pro and I get failures on reboot and cannot connect to the GUI.

Here is my failures (Screenshot attached)

[FAILED] Failed to start console-setup.service - Set console font and keymap.
[FAILED] Failed to start pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon.
[FAILED] Failed to start pveproxy.service - PVE API Proxy.
[FAILED] Failed to start pve-ha-lrm.service - PVE Local HA Resource Manager Daemon.
[FAILED] Failed to start pveproxy.service - PVE API Proxy.
[FAILED] Failed to start pve-guests.service - PVE guests.

Here is my hardware:

GIGABYTE H610I H610 Intel LGA 1700 Mini-ITX Motherboard
13th Gen i9
CORSAIR Vengeance 32GB DDR5 @4800
1TB Western Digital NVMe
500GB Samsung SSD (This is where I am trying to install Proxmox)
Intel E1G44HTBLK 10/100/1000Mbps PCI-Express 2.0 Server Adapter

This is a single host, not a cluster

Any assistance would be greatly appreciated!

 

[Pifouney]

What's calling "dmesg" return ?

 

[dwanecl]

Sorry for the late response. I ended up trying XCP-NG, don't really care for it. I like the interface for Proxmox much better, reminds me more of ESXi than XCP-NG does.

I have attached my dmesg

 

[Pifouney]

Hey,
Thanks for your dmesg file.
Open -it, and search in this key: 1125.098434
At this time boot, you gonna found seg fault error.

2 thinks:
- Reboot on previous running kernel. If he boot, go to dmesg, and do the same search with keywords: "segfault" and "BUG".
If no entry with them, update your BIOS firmware, then retry and check.
- Similar entry founds: you've a hardware investigation to do. It's probably only a fortuity situation, where your hardware have many more error than previous because he's failing himself.

 

[dwanecl]

Thank You for the reply, pretty sure I found the issue. My processor (13th Gen i9) was hit with that intel bug prior to getting the updated firmware. I tried a new i5 in the system this morning and everything is working like a charm.