Weird Behavior After Attempted GPU driver Install

Nate_et

New Member
Nov 19, 2024
1
0
1
Hello all,

First time posting here so if I haven't provided enough information I apologise in advance.

I was following the guide here: https://www.reddit.com/r/Proxmox/comments/1c9ilp7/proxmox_gpu_passthrough_for_jellyfin_lxc_with/

I ran
Code:
Apt install gcc
,
Code:
Apt install build-essential
and then rebooted and ran
Code:
apt install pve-headers-$(uname -r)

I then tried to install the GPU drivers from Nvidia's website which failed to install. As it transpires the GPU (GT 710) that I was trying to use doesn't play well so i stopped trying to install the GPU drivers and decided to run and update while I had the down time.

I ran
Code:
apt dist-upgrade
and everything seemed to run fine and I didn't see any errors. I rebooted my host and then when it came back up none of my containers or VM's had started and they all errored with the error "activating LV 'pve/data' failed: Activation of logical volume pve/data is prohibited while logical volume pve/data_tmeta is active." for all my containers and vm's.

I left it for about 15 minutes but the error persisted so I rebooted to host again and everything came back up and started running. Thinking I was out of the woods I tried accessing my containers and VM's and found that while I could access them sporadically, they would keep rejecting HTTP traffic for services that have web GUI's like Frigate for example.

I wondered if a package hadn't installed correctly so I tried to apt dist-upgrade again and got:

Code:
root@pveserverhost:~# apt dist-upgrade
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.



now when I check pveversion i get this:
Code:
root@pveserverhost:~# pveversion -v
proxmox-ve: not correctly installed (running kernel: 5.15.143-1-pve)
pve-manager: 8.2.8 (running version: 8.2.8/a577cfa684c7476d)
proxmox-kernel-helper: 8.1.0
pve-kernel-5.15: 7.4-11
pve-kernel-5.15.143-1-pve: 5.15.143-1
pve-kernel-5.15.136-1-pve: 5.15.136-1
pve-kernel-5.15.116-1-pve: 5.15.116-1
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.104-1-pve: 5.15.104-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.8
libpve-cluster-perl: 8.0.8
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.11
libpve-storage-perl: 8.2.7
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.9-1
proxmox-backup-file-restore: 3.2.9-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.3.0
pve-cluster: 8.0.8
pve-container: 5.2.1
pve-docs: 8.2.4
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.14-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.4
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

When i run
Code:
dpkg --configure -a

I get the following:

Code:
root@pveserverhost:~# dpkg --configure -a
Setting up memtest86+ (6.10-4) ...
/usr/sbin/grub-mkconfig: 9: /etc/default/grub: nomodeset: not found
dpkg: error processing package memtest86+ (--configure):
 installed memtest86+ package post-installation script subprocess returned error exit status 127
Setting up proxmox-kernel-6.8.12-3-pve-signed (6.8.12-3) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.8.12-3-pve /boot/vmlinuz-6.8.12-3-pve
update-initramfs: Generating /boot/initrd.img-6.8.12-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.8.12-3-pve /boot/vmlinuz-6.8.12-3-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.8.12-3-pve /boot/vmlinuz-6.8.12-3-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.8.12-3-pve /boot/vmlinuz-6.8.12-3-pve
/usr/sbin/grub-mkconfig: 9: /etc/default/grub: nomodeset: not found
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.12-3-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.12-3-pve-signed (--configure): installed proxmox-kernel-6.8.12-3-pve-signed package post-installation script subprocess returned error exit status 2
Setting up proxmox-kernel-6.8.12-4-pve-signed (6.8.12-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.8.12-4-pve /boot/vmlinuz-6.8.12-4-pve
update-initramfs: Generating /boot/initrd.img-6.8.12-4-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.8.12-4-pve /boot/vmlinuz-6.8.12-4-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.8.12-4-pve /boot/vmlinuz-6.8.12-4-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.8.12-4-pve /boot/vmlinuz-6.8.12-4-pve
/usr/sbin/grub-mkconfig: 9: /etc/default/grub: nomodeset: not found
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.12-4-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.12-4-pve-signed (--configure): installed proxmox-kernel-6.8.12-4-pve-signed package post-installation script subprocess returned error exit status 2
Setting up proxmox-kernel-6.5.13-6-pve-signed (6.5.13-6) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.5.13-6-pve /boot/vmlinuz-6.5.13-6-pve
update-initramfs: Generating /boot/initrd.img-6.5.13-6-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.5.13-6-pve /boot/vmlinuz-6.5.13-6-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.5.13-6-pve /boot/vmlinuz-6.5.13-6-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.5.13-6-pve /boot/vmlinuz-6.5.13-6-pve
/usr/sbin/grub-mkconfig: 9: /etc/default/grub: nomodeset: not found
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.5.13-6-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.5.13-6-pve-signed (--configure): installed proxmox-kernel-6.5.13-6-pve-signed package post-installation script subprocess returned error exit status 2
Setting up proxmox-kernel-6.8.12-2-pve-signed (6.8.12-2) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.8.12-2-pve /boot/vmlinuz-6.8.12-2-pve
update-initramfs: Generating /boot/initrd.img-6.8.12-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.8.12-2-pve /boot/vmlinuz-6.8.12-2-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.8.12-2-pve /boot/vmlinuz-6.8.12-2-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.8.12-2-pve /boot/vmlinuz-6.8.12-2-pve
/usr/sbin/grub-mkconfig: 9: /etc/default/grub: nomodeset: not found
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.12-2-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.12-2-pve-signed (--configure): installed proxmox-kernel-6.8.12-2-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.8:
 proxmox-kernel-6.8 depends on proxmox-kernel-6.8.12-4-pve-signed | proxmox-kernel-6.8.12-4-pve; however:
  Package proxmox-kernel-6.8.12-4-pve-signed is not configured yet.
  Package proxmox-kernel-6.8.12-4-pve is not installed.
  Package proxmox-kernel-6.8.12-4-pve-signed which provides proxmox-kernel-6.8.12-4-pve is not configured yet.
dpkg: error processing package proxmox-kernel-6.8 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-kernel-6.5:
 proxmox-kernel-6.5 depends on proxmox-kernel-6.5.13-6-pve-signed | proxmox-kernel-6.5.13-6-pve; however:
  Package proxmox-kernel-6.5.13-6-pve-signed is not configured yet.
  Package proxmox-kernel-6.5.13-6-pve is not installed.
  Package proxmox-kernel-6.5.13-6-pve-signed which provides proxmox-kernel-6.5.13-6-pve is not configured yet.
dpkg: error processing package proxmox-kernel-6.5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.8; however:
  Package proxmox-kernel-6.8 is not configured yet.
dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.
dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 memtest86+
 proxmox-kernel-6.8.12-3-pve-signed
 proxmox-kernel-6.8.12-4-pve-signed
 proxmox-kernel-6.5.13-6-pve-signed
 proxmox-kernel-6.8.12-2-pve-signed
 proxmox-kernel-6.8
 proxmox-kernel-6.5
 proxmox-default-kernel
 proxmox-ve

Any help would be much appreciated.

TIA

- Nate
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!