Search results

  1. S

    [SOLVED] Deleted node still visible in web/corosync.conf

    Thank you, that did the trick! I did not know that you had to increment the version.
  2. S

    [SOLVED] Deleted node still visible in web/corosync.conf

    I think "dismantling the cluster" != "removing a node from a two node cluster". I intend to add back nodes at a later stage so I don't want to remove the cluster as a whole. There is also some storage and some backup schedules configured which if possible I don't want to reconfigure.
  3. S

    [SOLVED] Deleted node still visible in web/corosync.conf

    I don't see anything strange in the syslog. Dismantling the cluster is currently no option.
  4. S

    [SOLVED] Deleted node still visible in web/corosync.conf

    I removed a node from a two node cluster. I first had to set quorum_votes: 2 inside /etc/pve/corosync.conf on the remaining node. pvecm delnode pvec1n2 worked perfectly. The removed node is offline and not connected to the network. However the deleted node is still visible as a red entry on the...
  5. S

    backup/vzdump failed with err -5 - Input/output error

    I’ve now set a temp path inside /etc/vzdump.conf. That solves the problem partially. Both containers now backup successful but that one VM (131) still gives me error 5.
  6. S

    backup/vzdump failed with err -5 - Input/output error

    Hmm there seems to be a problem with /dev/sda kernel: ata1.00: irq_stat 0x40000008 kernel: ata1.00: failed command: READ FPDMA QUEUED kernel: ata1.00: cmd 60/80:30:00:93:79/00:00:11:00:00/40 tag 6 ncq dma 65536 in res 41/40:00:40:93:79/00:00:11:00:00/00 Emask 0x409 (media error) <F>...
  7. S

    backup/vzdump failed with err -5 - Input/output error

    Hi I’ve got 3 VMs and 2 containers running. I normally do backups onto a Synology NFS share. Both containers as well as one VM give me error 5 (below) when trying to back them up onto the NFS share. It can’t be a permission issue since two VMs work fine. It’s probably also not related to the...