Search results

1 - remove completely your current scst installation 2 - install pve headers: apt install pve-headers-`uname -r` 3- install scst with the method described in this readme: https://github.com/ubuntu-pkg/scst 4- now you can follow the wik pve.proxmox.com/wiki/Tape_Drives, only for configuration...

Hi, y tried to join two nodes : On node1: How to fix ? Thanks

Solved: the switch was defective. I just replaced it.

The network isn't overloaded. In the example above, replication transfers 6GB of data. Normally it should only transfer new data? (about 200Mo for this VM ...) EDIT : there is weird lines in daemon.log: Jun 20 09:59:49 proxmox corosync[16543]: notice [TOTEM ] Retransmit List: 13f4 Jun 20...

The duration of the replication was only a few seconds, and since two days, it lasts several hours. On all my VMs. Any idea ? Exemple of replication log : 2018-06-19 10:08:13 104-0: start replication job 2018-06-19 10:08:16 104-0: guest => VM 104, running => 25050 2018-06-19 10:08:16 104-0...

Fixed by juste reinstalling proxmox on both nodes

And what about transport: udpu ? https://forum.proxmox.com/threads/how-to-configure-a-simple-cluster-of-3-nodes-on-unicast.26749/

Is it necessary to have a multicast network?

I tried joining a new node, and it crashed the host server : First step I created a cluster on first server. Second step on second server : pvecm add 10.16.2.254 Please enter superuser (root) password for '10.16.2.254': Password for root@10.16.2.254: Etablishing API connection with host...

This storage is working now, yet there is still the error message in the log, weird... What does mean "client watchdog expired - disable watchdog updates" ?

Hi, My Proxmox (ve 5.1) server was not working a few days ago and I hard-reboot it. It did not work and I had to use 'rescue boot' with the boot CD to fix that. Since then, I have a storage that does not work anymore. Here is the log file (/var/log/daemon.log) just before the crash: Apr 9...