Installation issues on server

lightstal

New Member
Nov 4, 2024
16
0
1
I have an Inspur SA5215M5 with dual xeon gold 6138 and 224gb of ram.

Every single fresh install I try always ends in an error with regards to the pvedaemon unable to start. Even installing on top of debian manually I am having issues with starting pveproxy and pvedaemon.
 
Hi,

can you provide the exact error message(s) you encounter? E.g. after a fresh installation - where the error occurs -, what does journalctl -b -u pvedaemon.service -u pveproxy.service report? (In codetags, please)
 
Hi,

can you provide the exact error message(s) you encounter? E.g. after a fresh installation - where the error occurs -, what does journalctl -b -u pvedaemon.service -u pveproxy.service report? (In codetags, please)
Hi thanks for the reply I just got done installing a fresh version of proxmox v8.2 this is also one of the errors I've been getting.

WXTel1T.png

38G62na.png


I would assume you would want to see my /etc/fstab file as well so here it is below
me3mqOS.png


hUAsbt3.png


Contents of
pvs -a
vgs -a
lvs -a

FoggevW.png
 
Last edited:
Hi,

can you provide the exact error message(s) you encounter? E.g. after a fresh installation - where the error occurs -, what does journalctl -b -u pvedaemon.service -u pveproxy.service report? (In codetags, please)
Here are the screenshots you requested as well.
i4dQhfd.png
 
Hi,

so based on the messages about watchdog: BUG: soft lockup .., I'd most likely guess some hardware problem, either CPU/firmware or disk (controller), maybe.
Looks like it hangs when trying to load some kernel module, so some hardware device is not playing along nicely.

I'd suggest updating all the system firmware to the latest version as possible and even contact your vendor about it, as they might have workarounds for that.
 
Hi,

so based on the messages about watchdog: BUG: soft lockup .., I'd most likely guess some hardware problem, either CPU/firmware or disk (controller), maybe.
Looks like it hangs when trying to load some kernel module, so some hardware device is not playing along nicely.

I'd suggest updating all the system firmware to the latest version as possible and even contact your vendor about it, as they might have workarounds for that.
Would that be the only issue as all my firmware has been updated to the latest available version by the vendor.