upgrade 5.4

  1. N

    NFS mount problems after PVE and Corosync upgrade

    Yesterday we upgraded our entire Proxmox Cluster from PVE 5.4-5 to PVE 5.4-15 and Corosync to 3.x. Since then NFS mounts on some nodes are occasionally not available. Anyone else having similar problems? - We are now deleting/adding the NFS mounts again. Hope that will resolve the issues.
  2. R

    Upgrading from 5.4 -> 6.2 zvol linking fails

    Completed the upgrade from 5.4 to 6.2. After rebooting, attempted to add a new VM. The raw disk image is created successfully, however, the link fails to create: The contents for the zvol.rules is as follows: # Persistent links for zvol # persistent disk links: /dev/zvol/dataset_name # also...
  3. S

    Bug while upgrading from 5 to 6

    Today I've tried to upgrade my proxmox from the latest 5 release to version 6. My proxmox is not a pure proxmox installation, it was installed onto a debian system, to enable a full disk encryption. I had done everything according to this guide...
  4. mir

    proxmox 5.4 to 6.1

    Hi all, Today I took the plunge and upgraded my cluster from 5.4 to 6.1 using apt update, apt dist-upgrade. The upgrade in itself was painless however on small annoyance when upgrading the corosync qdevice package as explained here...
  5. C

    Mount no longer works in Proxmox 6 - NFS - Synology

    Ey, First time posting, as I have always been able to find solutions on the forums (great job on that). The setup: I have a 3 node Proxmox cluster, and today upgraded them to Proxmox VE 6. On VE 5.4 all nodes had a nfs mount and everything worked. Two of the nodes have a two network interfaces...
  6. B

    [SOLVED] qm start hangs after update to 5.4

    Hello, I have a single node which was running a couple of VM's without any issues for last 6 months (version (5.1.XX)). Today I've updated the node to the latest version - 5.4 (using apt-get update && apt-get dist-upgrade) and since then I cannot get any of my Windows VMs to start. Though...