After update from 8.4 to 9.0 NFS doesn't work

[p-user]

Ok, little bit of progress. I changed in /etc/apt/sources.list.d/debian.sources the URIs, where I replaced ftp.nl.debian.org to deb.debian.org.
I also re-installed the intel microcode:

apt-get reinstall intel-microcode

And that would make the vms start and run again (halleluja!). Now the last problem to fix is to get the nfs mount working again.
No idea yet which packages I need to re-install,

Albert
P.S. Got my imap server running as a vm, contains mail back to 1999, so for me it's important that it is running.

 

[S Martin]

Maybe you have a similar problem than I had: My NFS did also not work after upgrading. My logfiles looked similar.

I Installed Proxmox on a new SSD and wanted to move the data or reinstall the data from the NFS.
The NFS did not work, because the kernel didn't want to load the NFS modules.
Then I found out, that an old kernel was booted.

Have a look at

uname -a

and

ls /lib/modules

The kernel from the old SSD and installation was booted and the new filesystem was used as root filesystem, So I had Proxmox 9.0 with the Kernel of 8.4.
I had to go to the BIOS and change the boot order, to use the new SSD.

systemctl reboot --firmware-setup

After that NFS was working again.

 

[p-user]

Thanks for all the tips and support. Currently I am reinstalling proxmox 9 and restoring from my backup (Proxmox Backup Server, don't wan't to upgrade that one!).

Anyway, the two problems I had, no nfs connection and not able to start a vm where fixed by reinstalling the following:

vm issues:
apt reinstall intel-microcode

nfs issues:
apt reinstall nfs-common libnfsidmap1

Both needed a reboot of course.

Since I buggered up my cluster (let's call this the panic mode) and since I don't trust the current Proxmox 9 upgrade installation (what else should be reinstalled), I started by first testing if the machines still work (with it's disk on nfs). Then I did a fresh install on one of the nodes, not putting it in a cluster yet, and reinstalling all vms from the backup. That all seems to work, so I will freshly install the second node as well.
As I used the Proxmox Backup Server as a qnode for the cluster, I have to look into that as well before I re-establish a new cluster.

Makes me wonder why the upgrade gave all these problems. Was the fact that I had ftp.nl.debian.org as the URI in de apt sources files the problem (I assume that would not make a difference). Did I run apt upgrade instead of apt dist-upgrade? As far as I remember I used dist-upgrade, don't know 100% sure by now. And would that be able to create such weird upgrades?

Luckily I had my backups (I use the PBS, but a separate USB drive would have worked too).

But for the moment I refrain from upgrading the PBS to version 4, as you can imagine.

Thanks to all the people for all the help and suggestions, specially to titou10 as he pointed me into the direction of the intel-microcode bit, and fiona for the nfs hints.

Regards,
Albert