Thank you for the output!
Looks everything ok to me. The next step is to check the syslog looking for interesting message, you can run `journalctl -b` to check the syslog.
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,
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`?
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
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
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.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.