Search results

  1. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    problem solved with that new update !!! NFS 4.1 and working !!
  2. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    7.2.1-69057 Update 1 should solve the issue... installing
  3. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    I've moved all my CT and VM to lvm-local, and waiting for Synology Support to find a solution (downgrade or fix)
  4. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    After this night, the NFS v3 felt too :( so no long time solution :(
  5. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    talked too fast... just working for LXC's... not for VM's ! strangely
  6. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    It's working on vers=3 ! (but in my case I'll still need 4.1 cause synology is a cluster, and for reconnect in case of balancing node, 4.1 is needed). but that saves me until there ! thx !
  7. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    no it's private :( The support told me to try with another NFS version too, i'm trying atm
  8. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    i'm feeling less alone thx ;) what's your Synology DSM version ? mine : DSM 7.2.1-69057 my logs seems fine, except timeouts
  9. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    i updated the to the latest apt update : same issue
  10. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    normally not, I have a qdevice docker on my synology HA (192.168.1.125) [root@NEBZNUC2 pve]$ cat corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: NEBZNUC nodeid: 1 quorum_votes: 1 ring0_addr: 192.168.1.100 } node { name: NEBZNUC2...
  11. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    the vm or ct did not started yet, if i relaunch the command after that, : Oct 06 08:40:20 NEBZNUC pvedaemon[1116]: <root@pam> successful auth for user 'root@pam' Oct 06 08:43:09 NEBZNUC pvedaemon[1115]: <root@pam> starting task UPID:NEBZNUC:00000651:00005857:651FAC7D:vzstart:113:root@pam: Oct 06...
  12. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    when i restart almost everything : systemctl restart pvedaemon;systemctl restart pvestatd;systemctl restart pveproxy;systemctl restart corosync I see a little bit better : but the vm's seems down when i try to connect, and their CPU is 0% and few minutes later, everything is grey again...
  13. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    and mount is ok : [root@NEBZNUC images]$ pvesm list NFS-SYNO Volid Format Type Size VMID NFS-SYNO:100/vm-100-disk-0.qcow2 qcow2 images 34359738368 100 NFS-SYNO:101/vm-101-disk-0.raw raw rootdir 8589934592 101 NFS-SYNO:101/vm-101-disk-1.raw...
  14. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    indeed first node : [root@NEBZNUC system]$ systemctl status pveproxy.service ● pveproxy.service - PVE API Proxy Server Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled) Active: active (running) since Thu 2023-10-05 16:14:42 CEST; 55min ago Process...
  15. N

    No VM/LXC can start after Proxmox update and Synology update to 7.2.1

    Dears, I just updated my both proxmox (cluster) and restart them, but since, no vm/lxc are starting anymore :( Cluster seems alright : Cluster information ------------------- Name: NEBZCLUSTER Config Version: 11 Transport: knet Secure auth: on Quorum information...