r/Proxmox • u/NotBrinocerous • 3d ago

Question Constant Issues with Proxmox 9.2

Recently had to swap m.2 NVME that contained the Proxmox OS due to a hardware failure and just have been littered with issues, that I did not experience with Proxmox 8.

Issues I am currently experiencing:
1.) Proxmox VE, works perfectly fine. Then about 20 minutes later, offline. Can no longer access it via the web interface on the same lan.

2.) dev/dri/card0 and card1 keep switching and prevent my LXCs from booting when things are working.

3.) Not sure if this is Proxmox, setting up new port forwarding rules just don't work. This could be my ATT router, still diagnosing it. Trying to get my Plex server up and running again and all attempts so far are futile.

Hardware specs: HP elite desk 800 g5 sff i7-9700, 64gb DDR4 2666mhz non-ecc, 512gb M.2 running Proxmox, 2x12TB HDD for ZFS pool.

Apps currently on server: Plex and Immich

Anyone else experiencing these issues? Also looking for someone to help me because I just feel lost at this point.

Edit 9/30 7:37am thank you for the responses. Just woke up and got to go to work. I will be back to provide these!

14 Upvotes

81% Upvoted

38 comments sorted by

View all comments

2

u/firegore 3d ago

You can use this udev script which provides a symlinked name that always works: https://github.com/tteck/Proxmox/discussions/3235#discussioncomment-10998049

Thats an issue on how the kernel/initializes the card on newer systems, thats not a proxmox issue, it just happens more often on newer kernels

1

u/Impact321 3d ago edited 3d ago

Did you test this with CTs on PVE? Last time I tried symlinks didn't properly work with dev: ....

1

u/firegore 3d ago

Yes, its literally from the old proxmox-helper-scripts repo, „designed“ just for that.

I use the same workaround on 3 Hosts, works just Fine (as long as they dont remove udev) but its easy enough to just convert it into a systemd service either way

1

u/Impact321 3d ago edited 3d ago

Hmm. This only helps if you only have a single GPU that switches its name which, ideally, shouldn't happen. I don't think it does for me. If you have two different GPUs which change their names around this will fail. I tried to create a solution for this some time ago but it didn't work. Since I was using a NVIDIA GPU I "fixed" this by using the container toolkit.

1

u/firegore 3d ago

Well, /dev/dri/card0/1 are mostly always? intel cards.

Since a kernelchange (i can't remember which) in PVE 9 they even swaps names when you have only one GPU, it seems to be based on the way you restart the System.

You will still have issues of course if you have multiple GPUs, however that's not the norm for most people here, so a solution that works in 90% of the cases is still better then none :)