Search results

Can you please provide us with more information, where you see that the disk read only and full? Can you also check the dmesg for the mentioned disk `dmesg | grep -i ext` or xfs if you're using XFS filesystem?

Hi, The Windows VM with VirtIO have a bug, see the below link[0]. To see if that related to the below bug, you can check the `Event Log` in Windows VM looking for `vioscsi`. [0]...

Hi, Can you please post the output of `pveversion -v`?

Hi, Try to give Corosync a new vote, you can do that by issuing the following command: pvecm expected 1

You have to boot your VM and press [ESC] bottom during the boot, then go to `Device Manager -> Secure Boot Configuration -> Attempt Secure Boot`.

Usually, the delete replication take some time.

Hi, Thank you for the network config! Did you set 1 to the `net.ipv4.ip_forward`? You maybe not need `pointopoint` as well. Can you please check if the gateway you configured to the VM is set to the `37.27.96.129`?

Hi, Can you please also share your network configuration `cat /etc/network/interfaces`?

Can you please post the full output of the `pveversion -v`? Do you see anything other the above entry in the syslog? you can try to run `journalctl -xe` command you can check the `dmesg`.

Hi, Did you fix your issue? If not, you can find the job PID using `ps aux` command. if you not find please post the output of the following command: cat /etc/pve/replication.cfg

Hi, Please can you tell us more details/information/require and the VM config?

Can you please share the repository? you can get them using the following commands: grep '' /etc/apt/sources.list && grep '' /etc/apt/sources.list.d/*

The issue might because the `enp3s0` is being used in both vmbr0 and vmbr1. If you have only one NIC you may follow the following config [0] [0] https://pve.proxmox.com/wiki/Open_vSwitch#Example_1:_Bridge_+_Internal_Ports_+_Untagged_traffic

Note, this is not a Proxmox VE issue. Anyway you can basically edit the ~/.bashrc or ~/.zshrc file and add `unset MAILCHECK` at the bottom

I'm glad to hear that you fix the first issue yourself! Regarding the loggin I would run `journalctl -f` on the shell and see what it prints during the trying login.

Hi, Thank you for the output! The above entries look normal to me. The error `err -5 - Input/output error` usually point to the problem of the disk, and since you tested to backup on a different storage and the other VMs backup works well, I would test the `backup mode` on Snapshot or Suspend...

Thank you for the output! From the output of the corosync-cfgtool I don't see the IP of the px4-pra, is that full output? if yes - can you please check if the Corosync config is the same on all your 4 nodes? Can you also try to restart the corosync service and then provide us with the status...

Hi, Thank you for the outputs! To troubleshooting, I would: - Test a backup on a different storage - Does the issue only on the 101 VM? - Could you check if the SSHFS mount is stable and accessible? You can test by manually copying a large file to the `/backup-shared/` and monitoring the...

To know if all networks are reachable you can use: corosync-cfgtool -n Are you sure you login with right Realm i.e., PVE or PAM?

Glad to hear that the issue is solved :) I will go ahead and set your thread as [SOLVED] to help other users who have the same issue.