Good news:
After commenting out the shares on the affected NAS in /etc/pve/storage.cfg and restarting pvestatd, my PVE cluster works fine again! pvesm statusdoes no longer stall and shows the expected result. All question marks in the GUI have...
Hm, removing the affected shares via GUI doesn't work - Connection error - Timeout.
Would it be sufficient to remove them directly from the storage.cfg with a text editor? And then restart a certain service, I guess?
Now I can say you were definitely pointing in the right direction:
pvesm list stalls when I apply it to shares on a certain NAS, while shares on another NAS (luckily my productive one) can be questioned successfully. On the aforementioned NAS, I...
Thank you for your proposal.
Since all my VMs' storage resources are on remote storage and moving them to local doesn't work, this would mean I have to shut down all VMs. Please understand that I do not yet feel desperate enough to take this...
You are right, the docs explicitly recommend apt dist-upgrade in any case.
So, to answer your question: Yes, I'm certain I used apt upgrade to install the packages last week, following a habit to only use apt dist-upgrade when it is about a major...
Hello all,
I'm running a PVE cluster consisting of three HP DL380 Gen 10 hosts. All updates from PVE 6 through 9 always ran flawless, until I updated from 9.0.5 to 9.1.6 via apt update && apt upgrade which made the names of LXC containers and...